:: Re: [Dng] A novice attempt to speed…
トップ ページ
このメッセージを削除
このメッセージに返信
著者: Isaac Dunham
日付:  
To: Jaret Cantu
CC: dng
題目: Re: [Dng] A novice attempt to speed up Devuan development
On Sun, May 17, 2015 at 12:38:59PM -0400, Jaret Cantu wrote:
> >Yes. I am on Debian wheezy. I think I always mention that.
> Probably did. I am just forgetful, tried, and always assuming that everyone
> on the Devuan list is at least striving for Jessie. I know it is a very
> incorrect assumption to make, but I can't seem to help myself. Still
> haven't coffeed today.
>
> >There are actually more lines need to have /usr/sbin otherwise I get more
> >errors when I tried to start udev.
> >
> >root@d945gclf:/etc/init.d# /etc/init.d/udev stop
> >[ ok ] Stopping the hotplug events dispatcher: udevd.
> >root@d945gclf:/etc/init.d#
> >root@d945gclf:/etc/init.d# /etc/init.d/udev start
> >/etc/init.d/udev: 191: /etc/init.d/udev: udevadm: not found
> >root@d945gclf:/etc/init.d#
> >
> ><change line 191 to add /usr/sbin>
> >
> >root@d945gclf:/etc/init.d# /etc/init.d/udev start
> >[....] Starting the hotplug events dispatcher: udevd/etc/init.d/udev: 197:
> >/etc/init.d/udev: udevd: not found
> >[warn] 127 ... (warning).
> >[warn] Waiting 15 seconds and trying to continue anyway ... (warning).
> >
> >[....] Synthesizing the initial hotplug events.../etc/init.d/udev: 206:
> >/etc/init.d/udev: udevadm: not found
> >failed.
> >[....] Waiting for /dev to be fully populated.../etc/init.d/udev: 216:
> >/etc/init.d/udev: udevadm: not found
> >done (timeout).
> >root@d945gclf:/etc/init.d#
> >
> ><change line 197, 206 and 216 to add /usr/sbin>
> >
> >root@d945gclf:/etc/init.d# /etc/init.d/udev start
> >[ ok ] Starting the hotplug events dispatcher: udevd.
> >[ ok ] Synthesizing the initial hotplug events...done.
> >[ ok ] Waiting for /dev to be fully populated...done.
> >root@d945gclf:/etc/init.d#
>
> Ooooooh, did I only fix that in one place in the repo?
>
> I had done some editing to my files after installing.
>
> PATH="/usr/sbin:/usr/bin:/sbin:/bin"
>
> Probably not a wise decision. I just threw in the one absolute path since
> that is what was stopping me from booting (since it appeared before the
> modified PATH, which I had added earlier).


While that probably works for most people, it isn't quite up to the level
that Debian expected formerly:

Anything before mountall, networking, and mountnfs.sh should not use paths
under /usr, because /usr could be a (possibly remote) mount.
Configuring /dev with something in /usr is particularly bad;
coincidentally, eudev was forked partly because systemd-udev started
complaining about configurations with a separate /usr.

On configuration files:
Roger Leigh would probably know the proper way to handle this.
You might try looking at the "microcode.ctl" package source, or sysvinit.

HTH,
Isaac Dunham