Re: CONFIG_DEVTMPFS

2009-12-16 Thread Michael Shigorin
On Wed, Dec 16, 2009 at 02:10:56PM +0100, Jacek Konieczny wrote:
> Enabling CONFIG_DEVTMPFS may be good as it would help solve
> many problems occurring with our current systems (most of us
> had probably seen a system with useless empty /dev after some
> boot or udev problem), without need to update (much) any of
> core packages. It could be used to simplify things, but such
> simplification is not worth breaking compatibility again. 

JFYI, I've done dev-minimal package in ALT Linux
hoping to use it for this very reason: some bare /dev
in case modern stuff fails again.

Unfortunately didn't get around to integrating it to distros
(hmm... maybe today is the day? ;-), only installed by hand
on a few systems.

-- 
  WBR, Michael Shigorin 
  -- Linux.Kiev http://www.linux.kiev.ua/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: CONFIG_DEVTMPFS

2009-12-16 Thread Jacek Konieczny
On Wed, Dec 16, 2009 at 01:50:45PM +0100, Patryk Zawadzki wrote:
> Adding uname(release) requirements to new geninitrd releases should
> deal with older kernels.

Yeah… all we need is yet another uname(release) dependency…

This way we will get  to choose: geninitrd or udev (or anything what
depends on it) or have e.g. working Xserver (last time I tried the
newest kernel didn't work with ATI cards, as kernel forced KMS and our
Xserver's ATI drivers couldn't handle it yet). All because some feature,
which could stay (maybe optional), was dropped, as 'obsoleted' by some
newest kernel feature… Fortunately, there is still the 'kernel-ltm'
package in th…

Enabling CONFIG_DEVTMPFS may be good as it would help solve many
problems occurring with our current systems (most of us had probably
seen a system with useless empty /dev after some boot or udev problem),
without need to update (much) any of core packages. It could be used to
simplify things, but such simplification is not worth breaking
compatibility again. 

Greets,
Jacek
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: CONFIG_DEVTMPFS

2009-12-16 Thread Patryk Zawadzki
On Wed, Dec 16, 2009 at 1:47 PM, Tomasz Pala  wrote:
> On Wed, Dec 16, 2009 at 12:22:50 +0100, Patryk Zawadzki wrote:
>
>> Linux 2.6.32.* comes with a handy function:
>>
>> CONFIG_DEVTMPFS:
> [...]
>> Maybe we could simplify our geninitrd?
> How to simplify and keep support for nondist kernels?

Tell people to enable this option. Just as we require them to compile
with certain filesystems enabled.

Adding uname(release) requirements to new geninitrd releases should
deal with older kernels.

-- 
Patryk Zawadzki
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: CONFIG_DEVTMPFS

2009-12-16 Thread Tomasz Pala
On Wed, Dec 16, 2009 at 12:22:50 +0100, Patryk Zawadzki wrote:

> Linux 2.6.32.* comes with a handy function:
> 
> CONFIG_DEVTMPFS:
[...]
> Maybe we could simplify our geninitrd?

How to simplify and keep support for nondist kernels?

-- 
Tomasz Pala 
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: CONFIG_DEVTMPFS

2009-12-16 Thread Pawel Golaszewski
On Wed, 16 Dec 2009, Jan Rękorajski wrote:
> > Linux 2.6.32.* comes with a handy function:
> > 
> > CONFIG_DEVTMPFS:
> > 
> > "This creates a tmpfs filesystem, and mounts it at bootup
> > and mounts it at /dev. The kernel driver core creates device
> > nodes for all registered devices in that filesystem. All device
> > nodes are owned by root and have the default mode of 0600.
> > Userspace can add and delete the nodes as needed. This is
> > intended to simplify bootup, and make it possible to delay
> > the initial coldplug at bootup done by udev in userspace.
> > It should also provide a simpler way for rescue systems
> > to bring up a kernel with dynamic major/minor numbers.
> > Meaningful symlinks, permissions and device ownership must
> > still be handled by userspace."
> > 
> > Maybe we could simplify our geninitrd?
> Better not. 
> http://readlist.com/lists/vger.kernel.org/linux-kernel/148/740255.html

Maybe not now because it's too fresh and buggy.
But in general - IMvHO it's the right direction.

-- 
pozdr.  Paweł Gołaszewski  jid:bluesjabbergdapl
--
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: CONFIG_DEVTMPFS

2009-12-16 Thread Jan Rękorajski
On Wed, 16 Dec 2009, Patryk Zawadzki wrote:

> Linux 2.6.32.* comes with a handy function:
> 
> CONFIG_DEVTMPFS:
> 
> "This creates a tmpfs filesystem, and mounts it at bootup
> and mounts it at /dev. The kernel driver core creates device
> nodes for all registered devices in that filesystem. All device
> nodes are owned by root and have the default mode of 0600.
> Userspace can add and delete the nodes as needed. This is
> intended to simplify bootup, and make it possible to delay
> the initial coldplug at bootup done by udev in userspace.
> It should also provide a simpler way for rescue systems
> to bring up a kernel with dynamic major/minor numbers.
> Meaningful symlinks, permissions and device ownership must
> still be handled by userspace."
> 
> Maybe we could simplify our geninitrd?

Better not.

http://readlist.com/lists/vger.kernel.org/linux-kernel/148/740255.html

-- 
Jan Rękorajski|  ALL SUSPECTS ARE GUILTY. PERIOD!
bagginsmimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC  |   -- TROOPS by Kevin Rubio
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


CONFIG_DEVTMPFS

2009-12-16 Thread Patryk Zawadzki
Linux 2.6.32.* comes with a handy function:

CONFIG_DEVTMPFS:

"This creates a tmpfs filesystem, and mounts it at bootup
and mounts it at /dev. The kernel driver core creates device
nodes for all registered devices in that filesystem. All device
nodes are owned by root and have the default mode of 0600.
Userspace can add and delete the nodes as needed. This is
intended to simplify bootup, and make it possible to delay
the initial coldplug at bootup done by udev in userspace.
It should also provide a simpler way for rescue systems
to bring up a kernel with dynamic major/minor numbers.
Meaningful symlinks, permissions and device ownership must
still be handled by userspace."

Maybe we could simplify our geninitrd?

-- 
Patryk Zawadzki
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en