Simon Geard wrote:
Not meaning to start an argument on that basis. But by 'modern'
desktops, I meant recent versions of Gnome or KDE, compared to more
lightweight setups.
As to the relevance to the thread, I know I didn't make that clear, but
my thinking was that device names really aren't
As promised, I ran a number of tests to clarify Udev
interaction with '/lib/udev/devices/' and the creation
of some essential nodes during a boot-up.
PRELIMINARIES
A. [/sbin]$ strings udevd | grep devices
/lib/udev/devices
/devices/
So, 'udevd' is aware of '/lib/udev/devices/'
Bruce Dubbs wrote:
When I rebooted, I got the following messages:
cannot open /dev/null
...
FATAL: Module LNXSYTEM: not found
...
When I added null back to /lib/udev/devices/ and reenabled
the copy in the bootscripts, I got none of these messages.
...
I don't have any modules to
SYSTEM
~~
ASUS P5E-VM HDMI with Intel G35/ICH9R.
Intel Core2 Duo CPU E8400 @ 3.00GHz, 4GB
(B)LFS i686-pc-linux-gnu, 2.6.37.1, Udev-166
PROBLEM
~~~
No problems. I'm just trying to recap and maybe bring
this thread to a merciful end.
In the following, I'm trying to present a time-line
al...@verizon.net wrote:
C. As nit-pickings (no urgency, we know how long it takes to change
will with must in the next (almost) daily revision of the book:)
C.1. 6.2.21 should say must instead of will
OK, we can do this. It's in section 6.2.1, not 6.2.21.
C.2. The whole Create some
Bruce Dubbs wrote,
It's in section 6.2.1, not 6.2.21
Hi Bruce,
Typo. Sorry.
C.2. The whole Create some devices and directories ... in
udev-1xx should go. Misleading, outdated and nonsensical.
No, it really can't go. I went into my sandbox, deleted
/lib/udev/devices/null, and commented
al...@verizon.net wrote:
Bruce Dubbs wrote,
When I rebooted, I got the following messages:
cannot open /dev/null
FATAL: Module platform: regulatory not set
FATAL: Module LNXSYTEM: not found
FATAL: Module doc not found
FATAL: pci:v... not found
This last was repeated about
On 02/25/2011 04:38 PM, Bruce Dubbs wrote:
Neal Murphy wrote:
On Friday 25 February 2011 15:02:23 Bruce Dubbs wrote:
It looks like the process is:
1. Use null and console at the start.
2. Mount a tmpfs on /dev hiding the original null and console devices.
3. Create all new devices,
On Fri, 2011-02-25 at 22:12 -0600, Bruce Dubbs wrote:
I suspect you have to add -L volume-label to mke2fs (or other partition
formatting tool) for at least one partition for by-label to be created.
Ah, yes, that makes sense - if the directory is created by the presence
of symlinks within it,
On Wed, 2011-02-23 at 14:41 -0500, Neal Murphy wrote:
On Wednesday 23 February 2011 04:54:10 Simon Geard wrote:
Are you unaware then, that udev provides the /dev/disks/by-label
directory, which contains volume labels as symlinks to the kernel-named
devices? For example, my fstab file
On Wed, 2011-02-23 at 11:24 -0600, Bruce Dubbs wrote:
What am I missing? My latest only has
$ ls /dev/disk
by-id by-path by-uuid
Odd - I see those, and by-label too. My main desktop is a little old
now (about ten months old, running udev 151), but I can't see them
dropping that feature.
On Wed, 2011-02-23 at 12:24 -0600, al...@verizon.net wrote:
BTW, there is a [rant][/rant] I'm skipping, although the idea
is not the first time to come up, where people grow from LFS
to BLFS and become confused and/or _misunderstood_ about falling
behind on the latest and greatest developments
Feb 25, 2011 04:26:29 AM, Simon Geard wrote:
On Wed, 2011-02-23 at 12:24 -0600, al...@verizon.net wrote:
BTW, there is a [rant][/rant] I'm skipping, although the idea
is not the first time to come up, where people grow from LFS
to BLFS and become confused and/or _misunderstood_ about
al...@verizon.net wrote:
3.2. The PROBLEM (the actual object of the OP) has been
my worries started recently when _finally_ a [light] bulb went
[off] in my head on reading
# Create some devices and directories that Udev cannot handle
# due to them being required very early in
Neal Murphy wrote:
On Friday 25 February 2011 15:02:23 Bruce Dubbs wrote:
It looks like the process is:
1. Use null and console at the start.
2. Mount a tmpfs on /dev hiding the original null and console devices.
3. Create all new devices, including null, on the tmpfs via udev and
the
Feb 25, 2011 03:11:51 PM, Bruce Dobbs wrote:
I haven't looked at this code in quite a while, but I don't
see these instructions as contradictory.
Hi Bruce,
I commented out 'cp -a /lib/udev/devices/null /dev' in udev script.
and did a reboot.
_I_ didn't notice any changes (messages, etc.) in
al...@verizon.net wrote:
I do have a confusion underlying this thread.
I have claimed (possibly wrongly), the Udev philosophy assumes a /dev
absolutely empty. Are the initial (metal) null and console nodes
an LFS specific requirement (based on its particular boot/log sequence
I tested and
On Fri, 2011-02-25 at 22:11 +1300, Simon Geard wrote:
On Wed, 2011-02-23 at 11:24 -0600, Bruce Dubbs wrote:
What am I missing? My latest only has
$ ls /dev/disk
by-id by-path by-uuid
Odd - I see those, and by-label too. My main desktop is a little old
now (about ten months old,
On Fri, 2011-02-25 at 13:21 -0600, al...@verizon.net wrote:
2. _Strictly_ for the record and completeness:
I do no use Gnome. Never have.
I use KDE (3.5.10) and Fluxbox (1.1.1).
However, IMHO this is absolutely irrelevant as far as the thread
subject is concerned.
Unfortunately, the above
Simon Geard wrote:
On Fri, 2011-02-25 at 22:11 +1300, Simon Geard wrote:
On Wed, 2011-02-23 at 11:24 -0600, Bruce Dubbs wrote:
What am I missing? My latest only has
$ ls /dev/disk
by-id by-path by-uuid
Odd - I see those, and by-label too. My main desktop is a little old
now (about ten
Simon Geard wrote:
As to the rest, it may be I've misunderstood your original post - the
confusion was over the claim that people are unaware they they have
those nodes on the metal /dev. Given these nodes are explicitly
created with a clear explanation as to why, it seemed to me that you
On Tue, 2011-02-22 at 22:38 -0500, Neal Murphy wrote:
[rant] Digressing a little, I have a bone to pick with Kay Seivers and Greg K-
H. Their attitude is that only symlinks should be used in /dev and created
from udev rules (for the most part), and those symlinks may only be named
with
On Tue, 2011-02-22 at 18:44 -0600, al...@verizon.net wrote:
Unaware, many people still carry a lot of old stuff (including
console and null) on their metal /dev.
Not accidental. You should re-read Preparing Virtual Kernel File
Systems in the LFS book, specifically section 6.2.1 in the current
Simon Geard wrote:
On Tue, 2011-02-22 at 22:38 -0500, Neal Murphy wrote:
[rant] Digressing a little, I have a bone to pick with Kay Seivers and Greg
K-
H. Their attitude is that only symlinks should be used in /dev and created
from udev rules (for the most part), and those symlinks may only
Feb 23, 2011 04:58:10 AM, Simon Geard wrote:
... those nodes [null and console] are supposed to be there in
/dev on the root partition.
If you don't have them, you've missed a step in the build.
Hi Simon,
We're totally in sync here (if you take a look at the grand
finale of my OP :)
I had
On Wednesday 23 February 2011 04:54:10 Simon Geard wrote:
Are you unaware then, that udev provides the /dev/disks/by-label
directory, which contains volume labels as symlinks to the kernel-named
devices? For example, my fstab file doesn't reference /dev/sda6 for
the /home partition - it uses
Hello,
SYSTEM
(B)LFS i686-pc-linux-gnu, 2.6.37.1, Udev-166
LFS book: Version SVN-20110218
Script activation order in '... rcsysinit.d/':
mountkernfs
consolelog
modules (no modules to install, in my case)
udev
...
INTRODUCTION
While my system has worked well for a long time,
a
On Tuesday 22 February 2011 19:44:24 al...@verizon.net wrote:
Notes: 1. cp ... console /dev in 'udev' script doesn't work.
(apparently, too late in the boot sequence.)
2. For reasons unknown, even if I start with the
metal /dev empty, I end up with both null
28 matches
Mail list logo
