linux-kernel - Re: 2.6.18-rc7-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Sep 2006 18:57:34 +0200
From:	Olaf Hering <olaf@...fle.de>
To:	Andrew Morton <akpm@...l.org>
Cc:	"Martin J. Bligh" <mbligh@...igh.org>,
	linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...dowen.org>
Subject: Re: 2.6.18-rc7-mm1

On Tue, Sep 19, Andrew Morton wrote:


> What version of udev is it running?

021 likely, a simple udevstart that looks for 'dev' entries.
Where do they hide now in -mm?

> > [: [0-9]*: bad number
> > 
> >
> 
> That all looks rather bad.

'bad number' is harmless, affects only the persistant /dev/disk/ symlinks,
happens since the SCSI target patches in 2.6.9.

> > ReiserFS: sda2: Using r5 hash to sort names
> > looking for init ...
> > found /sbin/init
> > /init: cannot open .//dev//console: no such file
> 
> Bizarrely-formed pathname.  Does it always do that?

Yes, I wonder why /dev/console got lost in the first place.

/lib/mkinitrd/kinit.sh
...
rm -rf /bin /lib*
#
exec /run_init "$@" < "./$udev_root/console" > "./$udev_root/console" 2>&1
...

> Has udev actually attempted to do anything by this stage?

udevstart spawns alot /sbin/udev processes to propagate /dev
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/