[Buildroot] [PATCH] system/device_table.txt: add /dev/null entry

[Baruch Siach]

Hi Peter,

On Thu, Nov 27, 2014 at 10:01:54AM +0100, Peter Korsgaard wrote:
> >>>>> "Baruch" == Baruch Siach <baruch at tkos.co.il> writes:
> >> > can't open /dev/null: No such file or directory
>  >> > can't open /dev/null: No such file or directory
>  >> > can't open /dev/null: No such file or directory
>  >> > can't open /dev/null: No such file or directory
>  >> > can't open /dev/null: No such file or directory
>  >> > can't open /dev/null: No such file or directory
>  >> > ...
>  >> 
>  >> Hmm, is this on a kernel without devtmpfs? Devtmpfs is expected to be
>  >> used with mdev (and we automatically enable it if you build a kernel
>  >> with BR).
> 
>  > I am currently using a kernel built with no devtmpfs support. Don't
>  > we support mdev without devtmpfs anymore? Once I added /dev/null the
>  > system seems to boot successfully as is, with /dev fully populated.
> 
> Well, it presumably doesn't get a lot of testing atleast as none of this
> stuff afaik has changed the last few years.
> 
> Is there any specific reason why you don't use devtmpfs? It's quite
> small and has been in the kernel since 2.6.32.

I have just started with a precompiled kernel image that I got with this 
evaluation board to see how far I can get. Eventually I plan to rebuild 
everything and also enable devtmpfs.

> With that said, if just adding /dev/null fixes it for you then we can
> certainly add it. What about similar things like /dev/console, /dev/tty
> or your serial port?

/dev/console is already in the rootfs.tar image, I'm not sure whare it comes 
from. All other device nodes are later generated by mdev.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -