All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] understanding and using buildroot
@ 2010-03-23 17:53 Ravi Kumar Kulkarni
  2010-03-23 18:57 ` Paulius Zaleckas
  0 siblings, 1 reply; 8+ messages in thread
From: Ravi Kumar Kulkarni @ 2010-03-23 17:53 UTC (permalink / raw)
  To: buildroot

Hello everybody,
finally after 2 weeks of struggling i managed to build buildroot!
 i have some doubts to clarify on usage of buildroot and regarding some packages
i have built buildroot jffs2 image from using daily snapshot and
booted onto target.
but
a)when i get login prompt what password should i enter for a user and for root?
b)and what should be enabled to so as to login as root?

my /etc/passwd file is as belw

root:x:0:0:root:/root:/bin/sh
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:100:sync:/bin:/bin/sync
mail:x:8:8:mail:/var/spool/mail:/bin/sh
proxy:x:13:13:proxy:/bin:/bin/sh
www-data:x:33:33:www-data:/var/www:/bin/sh
backup:x:34:34:backup:/var/backups:/bin/sh
operator:x:37:37:Operator:/var:/bin/sh
haldaemon:x:68:68:hald:/:/bin/sh
dbus:x:81:81:dbus:/var/run/dbus:/bin/sh
nobody:x:99:99:nobody:/home:/bin/sh
sshd:x:103:99:Operator:/var:/bin/sh
default:x:1000:1000:Default non-root user:/home/default:/bin/sh


and my /etc/securetty file is below

tty1
tty2
tty3
tty4
tty5
tty6
tty7
tty8
ttyS0
ttyS1
ttyS2
ttyS3
ttyAMA0
ttyAMA1
ttyAMA2
ttyAMA3
ttySAC0
ttySAC1
ttySAC2
ttySAC3
ttyUL0
ttyUL1
ttyUL2
ttyUL3
ttyPSC0
ttyPSC1
ttyPSC2
ttyPSC3
ttyCPM0
ttyCPM1
ttyCPM2
ttyCPM3


 now apart from this to build a ubifs file system image what should i configure?
im building kernel outside buildroot . is there no way to  build ubifs
without configuring kernelin buildroot?

i would be thankful if anybody clarifies the above doubts.
warm regards,
Ravi Kulkarni.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-23 17:53 [Buildroot] understanding and using buildroot Ravi Kumar Kulkarni
@ 2010-03-23 18:57 ` Paulius Zaleckas
  2010-03-23 19:14   ` Ravi Kumar Kulkarni
  0 siblings, 1 reply; 8+ messages in thread
From: Paulius Zaleckas @ 2010-03-23 18:57 UTC (permalink / raw)
  To: buildroot

On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
> Hello everybody,
> finally after 2 weeks of struggling i managed to build buildroot!
>   i have some doubts to clarify on usage of buildroot and regarding some packages
> i have built buildroot jffs2 image from using daily snapshot and
> booted onto target.
> but
> a)when i get login prompt what password should i enter for a user and for root?

Initially password for root is empty. Just press Enter when you get asked for 
password.

> b)and what should be enabled to so as to login as root?

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-23 18:57 ` Paulius Zaleckas
@ 2010-03-23 19:14   ` Ravi Kumar Kulkarni
  2010-03-23 19:49     ` Lionel Landwerlin
  0 siblings, 1 reply; 8+ messages in thread
From: Ravi Kumar Kulkarni @ 2010-03-23 19:14 UTC (permalink / raw)
  To: buildroot

On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
<paulius.zaleckas@gmail.com> wrote:
> On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
>>
>> Hello everybody,
>> finally after 2 weeks of struggling i managed to build buildroot!
>> ?i have some doubts to clarify on usage of buildroot and regarding some
>> packages
>> i have built buildroot jffs2 image from using daily snapshot and
>> booted onto target.
>> but
>> a)when i get login prompt what password should i enter for a user and for
>> root?
>
> Initially password for root is empty. Just press Enter when you get asked
> for password.
 i pressed enter but it is again comin back to login only.any idea wat
might be wrong?



>> b)and what should be enabled to so as to login as root?
>

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-23 19:14   ` Ravi Kumar Kulkarni
@ 2010-03-23 19:49     ` Lionel Landwerlin
  2010-03-25  6:37       ` Ravi Kumar Kulkarni
  0 siblings, 1 reply; 8+ messages in thread
From: Lionel Landwerlin @ 2010-03-23 19:49 UTC (permalink / raw)
  To: buildroot

Le mercredi 24 mars 2010 ? 00:44 +0530, Ravi Kumar Kulkarni a ?crit :
> On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
> <paulius.zaleckas@gmail.com> wrote:
> > On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
> >>
> >> Hello everybody,
> >> finally after 2 weeks of struggling i managed to build buildroot!
> >>  i have some doubts to clarify on usage of buildroot and regarding some
> >> packages
> >> i have built buildroot jffs2 image from using daily snapshot and
> >> booted onto target.
> >> but
> >> a)when i get login prompt what password should i enter for a user and for
> >> root?
> >
> > Initially password for root is empty. Just press Enter when you get asked
> > for password.
>  i pressed enter but it is again comin back to login only.any idea wat
> might be wrong?

Same problem here ... I do not
Boot your kernel with option init=/bin/sh, then change the root
password.

> 
> >> b)and what should be enabled to so as to login as root?
> >

You can edit the /etc/inittab file to login automatically as root by
default on the console. Like this :

tty0::respawn:/bin/sh # GENERIC_SERIAL

Quite useful for people doing development on your board.

Regards,

-- 
Lionel Landwerlin

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-23 19:49     ` Lionel Landwerlin
@ 2010-03-25  6:37       ` Ravi Kumar Kulkarni
  2010-03-25  6:45         ` Lionel Landwerlin
  0 siblings, 1 reply; 8+ messages in thread
From: Ravi Kumar Kulkarni @ 2010-03-25  6:37 UTC (permalink / raw)
  To: buildroot

Hi all,

On Wed, Mar 24, 2010 at 1:34 AM, Lionel Landwerlin
<llandwerlin@gmail.com> wrote:
> Le mercredi 24 mars 2010 ? 00:44 +0530, Ravi Kumar Kulkarni a ?crit :
>> On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
>> <paulius.zaleckas@gmail.com> wrote:
>> > On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
>> >>
>> >> Hello everybody,
>> >> finally after 2 weeks of struggling i managed to build buildroot!
>> >> ?i have some doubts to clarify on usage of buildroot and regarding some
>> >> packages
>> >> i have built buildroot jffs2 image from using daily snapshot and
>> >> booted onto target.
>> >> but
>> >> a)when i get login prompt what password should i enter for a user and for
>> >> root?
>> >
>> > Initially password for root is empty. Just press Enter when you get asked
>> > for password.
>> ?i pressed enter but it is again comin back to login only.any idea wat
>> might be wrong?
>
> Same problem here ... I do not
> Boot your kernel with option init=/bin/sh, then change the root
> password.
>
>>
>> >> b)and what should be enabled to so as to login as root?
>> >
>
> You can edit the /etc/inittab file to login automatically as root by
> default on the console. Like this :
>
> tty0::respawn:/bin/sh # GENERIC_SERIAL
>
> Quite useful for people doing development on your board.
>
I tried the above possible options but no luck !!  :( and im getting
out of ideas!.

this is what my console gives me when i tried to login


(none) login: root
Dec 31 17:01:01 (none) auth.info login[63]: root login on 'ttyS0'
Dec 31 17:01:01 (none) daemon.info init: process '/sbin/getty -L ttyS0
115200 vt100 ' (pid 63) exited. Scheduling for restart.
Dec 31 17:01:01 (none) daemon.info init: starting pid 64, tty
'/dev/ttyS0': '/sbin/getty -L ttyS0 115200



(none) login: user
Password:
Dec 31 17:01:08 (none) daemon.info init: process '/sbin/

my /etc/ inittab file is shown below.
# /etc/inittab
#
# Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>
#
# Note: BusyBox init doesn't support runlevels.  The runlevels field is
# completely ignored by BusyBox init. If you want runlevels, use
# sysvinit.
#
# Format for each entry: <id>:<runlevels>:<action>:<process>
#
# id        == tty to run on, or empty for /dev/console
# runlevels == ignored
# action    == one of sysinit, respawn, askfirst, wait, and once
# process   == program to run

# Startup the system
null::sysinit:/bin/mount -t proc none /proc
null::sysinit:/bin/mount -t sysfs none /sys
null::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
null::sysinit:/bin/mkdir /dev/pts
null::sysinit:/bin/mount -t devpts devpts /dev/pts
null::sysinit:/bin/echo /sbin/mdev > /proc/sys/kernel/hotplug
null::sysinit:/sbin/mdev -s
null::sysinit:/bin/mount -o remount,rw /
null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname
null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
# now run any rc scripts
null::sysinit:/etc/init.d/rcS

# Set up a couple of getty's
tty1::respawn:/sbin/getty 38400 tty1
tty2::respawn:/sbin/getty 38400 tty2



# Put a getty on the serial port
ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL


# Logging junk
null::sysinit:/bin/touch /var/log/messages
null::respawn:/sbin/syslogd -n
null::respawn:/sbin/klogd -n
tty3::respawn:/usr/bin/tail -f /var/log/messages

# Stuff to do for the 3-finger salute
::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting
null::shutdown:/usr/bin/killall klogd
null::shutdown:/usr/bin/killall syslogd
null::shutdown:/bin/umount -a -r
null::shutdown:/sbin/swapoff -a

any clues?
warm regards,
Ravi Kulkarni.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-25  6:37       ` Ravi Kumar Kulkarni
@ 2010-03-25  6:45         ` Lionel Landwerlin
  2010-03-25  6:57           ` Ravi Kumar Kulkarni
  0 siblings, 1 reply; 8+ messages in thread
From: Lionel Landwerlin @ 2010-03-25  6:45 UTC (permalink / raw)
  To: buildroot

Le jeudi 25 mars 2010 ? 12:22 +0545, Ravi Kumar Kulkarni a ?crit :
> Hi all,
> 
> On Wed, Mar 24, 2010 at 1:34 AM, Lionel Landwerlin
> <llandwerlin@gmail.com> wrote:
> > Le mercredi 24 mars 2010 ? 00:44 +0530, Ravi Kumar Kulkarni a ?crit :
> >> On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
> >> <paulius.zaleckas@gmail.com> wrote:
> >> > On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
> >> >>
> >> >> Hello everybody,
> >> >> finally after 2 weeks of struggling i managed to build buildroot!
> >> >>  i have some doubts to clarify on usage of buildroot and regarding some
> >> >> packages
> >> >> i have built buildroot jffs2 image from using daily snapshot and
> >> >> booted onto target.
> >> >> but
> >> >> a)when i get login prompt what password should i enter for a user and for
> >> >> root?
> >> >
> >> > Initially password for root is empty. Just press Enter when you get asked
> >> > for password.
> >>  i pressed enter but it is again comin back to login only.any idea wat
> >> might be wrong?
> >
> > Same problem here ... I do not
> > Boot your kernel with option init=/bin/sh, then change the root
> > password.
> >
> >>
> >> >> b)and what should be enabled to so as to login as root?
> >> >
> >
> > You can edit the /etc/inittab file to login automatically as root by
> > default on the console. Like this :
> >
> > tty0::respawn:/bin/sh # GENERIC_SERIAL
> >
> > Quite useful for people doing development on your board.
> >
> I tried the above possible options but no luck !!  :( and im getting
> out of ideas!.
> 
> this is what my console gives me when i tried to login
> 
> 
> (none) login: root
> Dec 31 17:01:01 (none) auth.info login[63]: root login on 'ttyS0'
> Dec 31 17:01:01 (none) daemon.info init: process '/sbin/getty -L ttyS0
> 115200 vt100 ' (pid 63) exited. Scheduling for restart.
> Dec 31 17:01:01 (none) daemon.info init: starting pid 64, tty
> '/dev/ttyS0': '/sbin/getty -L ttyS0 115200
> 
> 
> 
> (none) login: user
> Password:
> Dec 31 17:01:08 (none) daemon.info init: process '/sbin/
> 
> my /etc/ inittab file is shown below.
> # /etc/inittab
> #
> # Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>
> #
> # Note: BusyBox init doesn't support runlevels.  The runlevels field is
> # completely ignored by BusyBox init. If you want runlevels, use
> # sysvinit.
> #
> # Format for each entry: <id>:<runlevels>:<action>:<process>
> #
> # id        == tty to run on, or empty for /dev/console
> # runlevels == ignored
> # action    == one of sysinit, respawn, askfirst, wait, and once
> # process   == program to run
> 
> # Startup the system
> null::sysinit:/bin/mount -t proc none /proc
> null::sysinit:/bin/mount -t sysfs none /sys
> null::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
> null::sysinit:/bin/mkdir /dev/pts
> null::sysinit:/bin/mount -t devpts devpts /dev/pts
> null::sysinit:/bin/echo /sbin/mdev > /proc/sys/kernel/hotplug
> null::sysinit:/sbin/mdev -s
> null::sysinit:/bin/mount -o remount,rw /
> null::sysinit:/bin/mount -a
> null::sysinit:/bin/hostname -F /etc/hostname
> null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
> null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
> # now run any rc scripts
> null::sysinit:/etc/init.d/rcS
> 
> # Set up a couple of getty's
> tty1::respawn:/sbin/getty 38400 tty1
> tty2::respawn:/sbin/getty 38400 tty2
> 
> 
> 
> # Put a getty on the serial port
> ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL

Replace previous line by :

ttyS0::respawn:/bin/sh

> 
> 
> # Logging junk
> null::sysinit:/bin/touch /var/log/messages
> null::respawn:/sbin/syslogd -n
> null::respawn:/sbin/klogd -n
> tty3::respawn:/usr/bin/tail -f /var/log/messages
> 
> # Stuff to do for the 3-finger salute
> ::ctrlaltdel:/sbin/reboot
> 
> # Stuff to do before rebooting
> null::shutdown:/usr/bin/killall klogd
> null::shutdown:/usr/bin/killall syslogd
> null::shutdown:/bin/umount -a -r
> null::shutdown:/sbin/swapoff -a
> 
> any clues?
> warm regards,
> Ravi Kulkarni.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-25  6:45         ` Lionel Landwerlin
@ 2010-03-25  6:57           ` Ravi Kumar Kulkarni
  2010-04-07  5:54             ` Ravi Kumar Kulkarni
  0 siblings, 1 reply; 8+ messages in thread
From: Ravi Kumar Kulkarni @ 2010-03-25  6:57 UTC (permalink / raw)
  To: buildroot

On Thu, Mar 25, 2010 at 12:30 PM, Lionel Landwerlin
<llandwerlin@gmail.com> wrote:
> Le jeudi 25 mars 2010 ? 12:22 +0545, Ravi Kumar Kulkarni a ?crit :
>> Hi all,
>>
>> On Wed, Mar 24, 2010 at 1:34 AM, Lionel Landwerlin
>> <llandwerlin@gmail.com> wrote:
>> > Le mercredi 24 mars 2010 ? 00:44 +0530, Ravi Kumar Kulkarni a ?crit :
>> >> On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
>> >> <paulius.zaleckas@gmail.com> wrote:
>> >> > On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
>> >> >>
>> >> >> Hello everybody,
>> >> >> finally after 2 weeks of struggling i managed to build buildroot!
>> >> >> ?i have some doubts to clarify on usage of buildroot and regarding some
>> >> >> packages
>> >> >> i have built buildroot jffs2 image from using daily snapshot and
>> >> >> booted onto target.
>> >> >> but
>> >> >> a)when i get login prompt what password should i enter for a user and for
>> >> >> root?
>> >> >
>> >> > Initially password for root is empty. Just press Enter when you get asked
>> >> > for password.
>> >> ?i pressed enter but it is again comin back to login only.any idea wat
>> >> might be wrong?
>> >
>> > Same problem here ... I do not
>> > Boot your kernel with option init=/bin/sh, then change the root
>> > password.
>> >
>> >>
>> >> >> b)and what should be enabled to so as to login as root?
>> >> >
>> >
>> > You can edit the /etc/inittab file to login automatically as root by
>> > default on the console. Like this :
>> >
>> > tty0::respawn:/bin/sh # GENERIC_SERIAL
>> >
>> > Quite useful for people doing development on your board.
>> >
>> I tried the above possible options but no luck !! ?:( and im getting
>> out of ideas!.
>>
>> this is what my console gives me when i tried to login
>>
>>
>> (none) login: root
>> Dec 31 17:01:01 (none) auth.info login[63]: root login on 'ttyS0'
>> Dec 31 17:01:01 (none) daemon.info init: process '/sbin/getty -L ttyS0
>> 115200 vt100 ' (pid 63) exited. Scheduling for restart.
>> Dec 31 17:01:01 (none) daemon.info init: starting pid 64, tty
>> '/dev/ttyS0': '/sbin/getty -L ttyS0 115200
>>
>>
>>
>> (none) login: user
>> Password:
>> Dec 31 17:01:08 (none) daemon.info init: process '/sbin/
>>
>> my /etc/ inittab file is shown below.
>> # /etc/inittab
>> #
>> # Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>
>> #
>> # Note: BusyBox init doesn't support runlevels. ?The runlevels field is
>> # completely ignored by BusyBox init. If you want runlevels, use
>> # sysvinit.
>> #
>> # Format for each entry: <id>:<runlevels>:<action>:<process>
>> #
>> # id ? ? ? ?== tty to run on, or empty for /dev/console
>> # runlevels == ignored
>> # action ? ?== one of sysinit, respawn, askfirst, wait, and once
>> # process ? == program to run
>>
>> # Startup the system
>> null::sysinit:/bin/mount -t proc none /proc
>> null::sysinit:/bin/mount -t sysfs none /sys
>> null::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
>> null::sysinit:/bin/mkdir /dev/pts
>> null::sysinit:/bin/mount -t devpts devpts /dev/pts
>> null::sysinit:/bin/echo /sbin/mdev > /proc/sys/kernel/hotplug
>> null::sysinit:/sbin/mdev -s
>> null::sysinit:/bin/mount -o remount,rw /
>> null::sysinit:/bin/mount -a
>> null::sysinit:/bin/hostname -F /etc/hostname
>> null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
>> null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
>> # now run any rc scripts
>> null::sysinit:/etc/init.d/rcS
>>
>> # Set up a couple of getty's
>> tty1::respawn:/sbin/getty 38400 tty1
>> tty2::respawn:/sbin/getty 38400 tty2
>>
>>
>>
>> # Put a getty on the serial port
>> ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
>
> Replace previous line by :
>
> ttyS0::respawn:/bin/sh

i did  now im not login prompt also. im  gettin ths

 17:00:12 (none) daemon.info init: process '/bin/sh' (pid 63) exited.
Scheduling for restart.
  17:00:12 (none) daemon.info init: starting pid 64, tty '/dev/ttyS0': '/bin/sh'

>>
>> # Logging junk
>> null::sysinit:/bin/touch /var/log/messages
>> null::respawn:/sbin/syslogd -n
>> null::respawn:/sbin/klogd -n
>> tty3::respawn:/usr/bin/tail -f /var/log/messages
>>
>> # Stuff to do for the 3-finger salute
>> ::ctrlaltdel:/sbin/reboot
>>
>> # Stuff to do before rebooting
>> null::shutdown:/usr/bin/killall klogd
>> null::shutdown:/usr/bin/killall syslogd
>> null::shutdown:/bin/umount -a -r
>> null::shutdown:/sbin/swapoff -a
>>

warm regards,
Ravi Kulkarni

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Buildroot] understanding and using buildroot
  2010-03-25  6:57           ` Ravi Kumar Kulkarni
@ 2010-04-07  5:54             ` Ravi Kumar Kulkarni
  0 siblings, 0 replies; 8+ messages in thread
From: Ravi Kumar Kulkarni @ 2010-04-07  5:54 UTC (permalink / raw)
  To: buildroot

On Thu, Mar 25, 2010 at 12:27 PM, Ravi Kumar Kulkarni
<ravilinux4u@gmail.com> wrote:
> On Thu, Mar 25, 2010 at 12:30 PM, Lionel Landwerlin
> <llandwerlin@gmail.com> wrote:
>> Le jeudi 25 mars 2010 ? 12:22 +0545, Ravi Kumar Kulkarni a ?crit :
>>> Hi all,
>>>
>>> On Wed, Mar 24, 2010 at 1:34 AM, Lionel Landwerlin
>>> <llandwerlin@gmail.com> wrote:
>>> > Le mercredi 24 mars 2010 ? 00:44 +0530, Ravi Kumar Kulkarni a ?crit :
>>> >> On Wed, Mar 24, 2010 at 12:27 AM, Paulius Zaleckas
>>> >> <paulius.zaleckas@gmail.com> wrote:
>>> >> > On 03/23/2010 07:53 PM, Ravi Kumar Kulkarni wrote:
>>> >> >>
>>> >> >> Hello everybody,
>>> >> >> finally after 2 weeks of struggling i managed to build buildroot!
>>> >> >> ?i have some doubts to clarify on usage of buildroot and regarding some
>>> >> >> packages
>>> >> >> i have built buildroot jffs2 image from using daily snapshot and
>>> >> >> booted onto target.
>>> >> >> but
>>> >> >> a)when i get login prompt what password should i enter for a user and for
>>> >> >> root?
>>> >> >
>>> >> > Initially password for root is empty. Just press Enter when you get asked
>>> >> > for password.
>>> >> ?i pressed enter but it is again comin back to login only.any idea wat
>>> >> might be wrong?
>>> >
>>> > Same problem here ... I do not
>>> > Boot your kernel with option init=/bin/sh, then change the root
>>> > password.
>>> >
>>> >>
>>> >> >> b)and what should be enabled to so as to login as root?
>>> >> >
>>> >
>>> > You can edit the /etc/inittab file to login automatically as root by
>>> > default on the console. Like this :
>>> >
>>> > tty0::respawn:/bin/sh # GENERIC_SERIAL
>>> >
>>> > Quite useful for people doing development on your board.
>>> >
>>> I tried the above possible options but no luck !! ?:( and im getting
>>> out of ideas!.
>>>
>>> this is what my console gives me when i tried to login
>>>
>>>
>>> (none) login: root
>>> Dec 31 17:01:01 (none) auth.info login[63]: root login on 'ttyS0'
>>> Dec 31 17:01:01 (none) daemon.info init: process '/sbin/getty -L ttyS0
>>> 115200 vt100 ' (pid 63) exited. Scheduling for restart.
>>> Dec 31 17:01:01 (none) daemon.info init: starting pid 64, tty
>>> '/dev/ttyS0': '/sbin/getty -L ttyS0 115200
>>>
>>>
>>>
>>> (none) login: user
>>> Password:
>>> Dec 31 17:01:08 (none) daemon.info init: process '/sbin/
>>>
>>> my /etc/ inittab file is shown below.
>>> # /etc/inittab
>>> #
>>> # Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>
>>> #
>>> # Note: BusyBox init doesn't support runlevels. ?The runlevels field is
>>> # completely ignored by BusyBox init. If you want runlevels, use
>>> # sysvinit.
>>> #
>>> # Format for each entry: <id>:<runlevels>:<action>:<process>
>>> #
>>> # id ? ? ? ?== tty to run on, or empty for /dev/console
>>> # runlevels == ignored
>>> # action ? ?== one of sysinit, respawn, askfirst, wait, and once
>>> # process ? == program to run
>>>
>>> # Startup the system
>>> null::sysinit:/bin/mount -t proc none /proc
>>> null::sysinit:/bin/mount -t sysfs none /sys
>>> null::sysinit:/bin/mount -t tmpfs -o size=64k,mode=0755 none /dev
>>> null::sysinit:/bin/mkdir /dev/pts
>>> null::sysinit:/bin/mount -t devpts devpts /dev/pts
>>> null::sysinit:/bin/echo /sbin/mdev > /proc/sys/kernel/hotplug
>>> null::sysinit:/sbin/mdev -s
>>> null::sysinit:/bin/mount -o remount,rw /
>>> null::sysinit:/bin/mount -a
>>> null::sysinit:/bin/hostname -F /etc/hostname
>>> null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
>>> null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
>>> # now run any rc scripts
>>> null::sysinit:/etc/init.d/rcS
>>>
>>> # Set up a couple of getty's
>>> tty1::respawn:/sbin/getty 38400 tty1
>>> tty2::respawn:/sbin/getty 38400 tty2
>>>
>>>
>>>
>>> # Put a getty on the serial port
>>> ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
>>
>> Replace previous line by :
>>
>> ttyS0::respawn:/bin/sh
>
> i did ?now im not login prompt also. im ?gettin ths
>
> ?17:00:12 (none) daemon.info init: process '/bin/sh' (pid 63) exited.
> Scheduling for restart.
> ?17:00:12 (none) daemon.info init: starting pid 64, tty '/dev/ttyS0': '/bin/sh'
>
>>>
>>> # Logging junk
>>> null::sysinit:/bin/touch /var/log/messages
>>> null::respawn:/sbin/syslogd -n
>>> null::respawn:/sbin/klogd -n
>>> tty3::respawn:/usr/bin/tail -f /var/log/messages
>>>
>>> # Stuff to do for the 3-finger salute
>>> ::ctrlaltdel:/sbin/reboot
>>>
>>> # Stuff to do before rebooting
>>> null::shutdown:/usr/bin/killall klogd
>>> null::shutdown:/usr/bin/killall syslogd
>>> null::shutdown:/bin/umount -a -r
>>> null::shutdown:/sbin/swapoff -a
>>>
>

SOLVED ! The problem was in kernel config. kernel was not recognising
getty . now its working like a charm. thanks to buildroot
which allows to build filesystems at this ease.:) now im off to build
TinyX and hope to get xserver working.
warm regards,
Ravi Kulkarni

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2010-04-07  5:54 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-23 17:53 [Buildroot] understanding and using buildroot Ravi Kumar Kulkarni
2010-03-23 18:57 ` Paulius Zaleckas
2010-03-23 19:14   ` Ravi Kumar Kulkarni
2010-03-23 19:49     ` Lionel Landwerlin
2010-03-25  6:37       ` Ravi Kumar Kulkarni
2010-03-25  6:45         ` Lionel Landwerlin
2010-03-25  6:57           ` Ravi Kumar Kulkarni
2010-04-07  5:54             ` Ravi Kumar Kulkarni

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.