public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Nick Warne <nick@linicks.net>,
	linux-kernel@vger.kernel.org, gregkh@suse.de,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 18:25:07 +0200	[thread overview]
Message-ID: <42B6EDE3.3040200@stesmi.com> (raw)
In-Reply-To: <200506201413.22471.vda@ilport.com.ua>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Denis.

>>>After all, udev is tied to /sys layout which changes with kernel
>>>and also udev is vital for properly functioning boot process
>>
>>Not if you use a static /dev.
> 
> 
> Static /dev kind of defeats the purpose of udev.
> I do not want to go back to the days when I had tons of
> /dev/{h,s}d{a,b,c,d,e,f}{0,1,2,3,4,5,6,7,8,9} for every
> IDE and SCSI block device possible. Same for /dev/tty*.
> I want them appear on the fly, if/when hardware is present.

Of course it defeats the purpose of udev. That's not what I
was answering however. It was the blanket statement that
"udev is vital for properly functioning boot process" as
if udev was necessary. udev (for me) is a very fine tool
that serves very many purposes, however it is not vital.

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFCtu3jBrn2kJu9P78RAghtAJwN9Nv5jYuVqchP66I2fM3khizUNACfWfjI
bwUjbisvDWk6qCCaC13u1no=
=z8Tr
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-06-20 16:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 12:32 2.6.12 udev hangs at boot Nick Warne
2005-06-18 13:03 ` Alistair John Strachan
2005-06-18 13:44   ` Nick Warne
2005-06-18 14:58     ` Andrew Walrond
2005-06-18 16:53 ` Jeff Garzik
2005-06-18 17:06   ` Nick Warne
2005-06-19 15:04     ` Andrew Haninger
2005-06-20 10:04     ` Denis Vlasenko
2005-06-20 10:17       ` Stefan Smietanowski
2005-06-20 11:13         ` Denis Vlasenko
2005-06-20 16:25           ` Stefan Smietanowski [this message]
2005-06-20 16:39           ` Bill Davidsen
2005-06-20 16:48       ` Greg KH
2005-06-20 17:24         ` Jeff Garzik
2005-06-20 17:34           ` Greg KH
2005-06-20 19:00             ` Nick Warne
2005-06-20 19:21               ` Greg KH
2005-06-20 19:32                 ` Nick Warne
2005-06-20 19:42                   ` David Lang
2005-06-21  6:28                     ` Greg KH
2005-06-21  6:31                       ` David Lang
2005-06-21  6:47                         ` Greg KH
2005-06-20 19:46                 ` Jesper Juhl
2005-06-20 19:34               ` Andrew Haninger
2005-06-20 19:49             ` Josh Boyer
2005-06-21  6:42               ` Greg KH
2005-06-20 19:24           ` Olaf Hering
2005-06-20 21:26         ` Daniel Barkalow
2005-06-20 22:14           ` Jesper Juhl
2005-06-20 22:26           ` Tomasz Torcz
  -- strict thread matches above, loose matches on Subject: below --
2005-06-18 15:32 Nick Warne
2005-06-21  6:40 ` Greg KH
2005-06-19 15:39 Nick Warne
2005-06-19 21:23 ` Andrew Haninger
2005-06-21  6:45 ` Greg KH
2005-06-21 17:06   ` Nick Warne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42B6EDE3.3040200@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=gregkh@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    --cc=vda@ilport.com.ua \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox