Bug 14225

Summary:	missing files after interactive rebuild
Product:	[Retired] Red Hat Linux	Reporter:	Michael Redinger <michael.redinger>
Component:	MAKEDEV	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-07-19 18:21:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Redinger 2000-07-18 16:17:14 UTC

I issued the following command to rebuild the whole dev files:

( cd /etc/makedev.d/ ; for i in * ; do /dev/MAKEDEV -c /etc/makedev.d/ -d
/tmp/n $i ; done )

However, afterwards some files which are in the dev RPM package are still
missing.
Eg. console, loop*, cui*, cua*

Comment 1 Nalin Dahyabhai 2000-07-19 14:08:01 UTC

The filenames in /etc/makedev.d are not device names.  (They
contain information about device nodes that MAKEDEV can read
and create, but they are not device names.)

Comment 2 Michael Redinger 2000-07-19 14:34:01 UTC

Hm, never said that. The above command eg. expands to:

/dev/MAKEDEV -c /etc/makedev.d/ -d /tmp/n ide

This is, build all the ide devices (the ide file then contains config options
which actually create hd[x]). Nothing wrong with that, I think.

Looking at the syntax this is also okay:

MAKEDEV [-c configdir] [-d devicedir] [-m maxdevices] [-v] [-n] device

Just as in my example. With the only difference that I do not specify the
devices directly but use the "device groups" (ie. the files in /etc/makedev.d
which again do contain directives how to create the actual devices).

Comment 3 Nalin Dahyabhai 2000-07-19 15:24:06 UTC

Actually, "MAKEDEV ide" shouldn't be creating a lot of those
symlinks, just any that point to the IDE devices.  Fixed in 3.0.5.

Comment 4 Michael Redinger 2000-07-19 16:21:36 UTC

Sorry, but I do have to reopen this again ...
Hope I can make clean what I do mean exactly this time.

The problem is: when builing the dev files as described above, not all devices
are created.
That is, when I issue the following commands:
/dev/MAKEDEV (...) cdrom
/dev/MAKEDEV (...) dac960
(...)

/dev/MAKEDEV (..) linux-2.2.x
(...)
/dev/MAKEDEV (...) usb
/dev/MAKEDEV (...) v4l

I did now have a closer look at it - especially linux-2.2.x does not do what I
expected. The linux-2.2.x config file contains many entries. But only the
symlinks for core, fd, sterr, stdin, stdout are created.

Did I misunderstand this? Is MAKEDEV not expected to work this way (ie. should
it be called explicitely for everything, eg. hda)?

Comment 5 Nalin Dahyabhai 2000-07-19 18:21:51 UTC

Exactly.  The name of the file is just a mnemonic for the
maintainer.  The %install in the .spec file just runs MAKEDEV
multiple times to generate the contents of /dev.  A name like
"ide" only works because it's a partial match for ide0, ide1,
and so on, and those are aliased to hda, hdb, hdc, hdd....