* [Buildroot] /dev files not being created correctly
@ 2009-04-14 13:55 Mark Fisher
2009-04-14 15:12 ` Bjørn Forsman
2009-04-15 5:39 ` Peter Korsgaard
0 siblings, 2 replies; 3+ messages in thread
From: Mark Fisher @ 2009-04-14 13:55 UTC (permalink / raw)
To: buildroot
Hi,
I'm relatively new to buildroot and am using the 2009.02 release of buildroot on a Fedora 9 platform and targeting an embedded device with an Intel Atom processor.
When the root filesystem is built the types of the files are all set to plain text files. So for instance the /dev/console is not set to be a character device. This has already create problems when I try to boot because the console could not be opened. I manually fixed /dev/console and /dev/null. I'm still having trouble booting the image and also after a?re-build my custom changes were lost.
Is this a known problem, and is there a fix? If not should I delete all the files in the /dev directory and then re-create them based on the settings in the device_table.txt?
Thanks,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090414/3d8edb79/attachment.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] /dev files not being created correctly
2009-04-14 13:55 [Buildroot] /dev files not being created correctly Mark Fisher
@ 2009-04-14 15:12 ` Bjørn Forsman
2009-04-15 5:39 ` Peter Korsgaard
1 sibling, 0 replies; 3+ messages in thread
From: Bjørn Forsman @ 2009-04-14 15:12 UTC (permalink / raw)
To: buildroot
2009/4/14 Mark Fisher <fobs12@ymail.com>
> Hi,
>
> I'm relatively new to buildroot and am using the 2009.02 release of
> buildroot on a Fedora 9 platform and targeting an embedded device with an
> Intel Atom processor.
>
> When the root filesystem is built the types of the files are all set to
> plain text files. So for instance the /dev/console is not set to be a
> character device. This has already create problems when I try to boot
> because the console could not be opened. I manually fixed /dev/console and
> /dev/null. I'm still having trouble booting the image and also after
> a re-build my custom changes were lost.
>
> Is this a known problem, and is there a fix? If not should I delete all the
> files in the /dev directory and then re-create them based on the settings in
> the device_table.txt?
>
The plain text files in /dev are just as they should be, but the rootfs with
those files is not the rootfs you want for your target. Try selecting a
different root file system type in menuconfig, like tar or ext2 or
something. By doing that you should get proper /dev/* files in your
generated rootfs images under ./binaries/<project>/.
>
> Thanks,
>
> Mark
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090414/1eb29339/attachment.htm>
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] /dev files not being created correctly
2009-04-14 13:55 [Buildroot] /dev files not being created correctly Mark Fisher
2009-04-14 15:12 ` Bjørn Forsman
@ 2009-04-15 5:39 ` Peter Korsgaard
1 sibling, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2009-04-15 5:39 UTC (permalink / raw)
To: buildroot
>>>>> "Mark" == Mark Fisher <fobs12@ymail.com> writes:
Mark> Hi,
Mark> I'm relatively new to buildroot and am using the 2009.02
Mark> release of buildroot on a Fedora 9 platform and targeting an
Mark> embedded device with an Intel Atom processor.
Mark> When the root filesystem is built the types of the files are
Mark> all set to plain text files. So for instance the /dev/console
Mark> is not set to be a character device. This has already create
Mark> problems when I try to boot because the console could not be
Mark> opened. I manually fixed /dev/console and /dev/null. I'm still
Mark> having trouble booting the image and also after a re-build my
Mark> custom changes were lost.
You shouldn't use the project_build_arm/*/root directory to boot from
NFS. The /dev entries are normal files as we don't want to require
root rights while building. Instead create a tarball (target
filesystem options->tar the root filesystem) and extract that (found
under binaries/) as root on your nfs server.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-04-15 5:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-14 13:55 [Buildroot] /dev files not being created correctly Mark Fisher
2009-04-14 15:12 ` Bjørn Forsman
2009-04-15 5:39 ` Peter Korsgaard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox