Messages in this thread | | | Date | Wed, 9 Jan 2002 15:44:25 -0500 | From | "Eric S. Raymond" <> | Subject | Re: initramfs programs (was [RFC] klibc requirements) |
| |
Doug McNaught <doug@wireboard.com>: > "Eric S. Raymond" <esr@snark.thyrsus.com> writes: > > > greg k-h: > > >What does everyone else need/want there? > > > > dmidecode, so the init script can dump a DMI report in a known > > location such as /var/run/dmi. > > > > I want this for autoconfiguration purposes. If I can have it, I > > won't need /proc/dmi. > > Why can't this happen inside the regular startup scripts? They know > where to put such files; the kernel-level stuff doesn't--I can't think > of any current situation where the kernel writes to an arbitrary file > in the filesystem as it boots. Sure, /var/run is in the FHS, but that > doesn't mean every system will have it. > > IMHO, since /var/run/dmi is not needed by any stage of the kernel > boot, it should be created in the regular startup scripts (invoked by > init(8)).
You're right, I don't need this to be done at kernel level. I do need it to be done *everywhere*. I'm not sure how else to guarantee this will happen. -- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
The American Republic will endure, until politicians realize they can bribe the people with their own money. -- Alexis de Tocqueville - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |