Quote:
Originally Posted by NiLuJe
Depends entirely on what exactly fails to boot.
As-is, USBNet has a hard dependency on volumd, so it starts as soon as possible, right behind volumd.
|
I believe that
volumd starts without an issue, simply because
/mnt/us is exported over USB despite the thing being unable to finish booting.
Side note: The first time I rebooted with the Paperwhite
/opt in place, the words
*** MKK (something) JB *** were displayed for a moment or two. That means that USBNetwork (at least its daemons) should've started up, doesn't it?
Quote:
|
While bypassing volumd, and as such possibly starting earlier, is theoretically possible, it's in practice more trouble than it's worth, since it causes far too many side-effects.
|
I plan to boot with as little modifications as possible ... not only it is -as you mentioned- more trouble than it's worth, it also causes unpredictable failures into the future over and above those in the present.
Quote:
It should be starting before the Java framework, which is usually where shit happens.
If not, you can always reboot in diags and peek at logs from there.
|
The Java framework seems to have started, actually, as the progress bar fills up until there's only one 'step' left, before it fails and restarts.
I actually haven't tried installing the USBNetwork-on-boot package (I have USBNetwork, but it's not set to start on boot just yet), because files under
/opt might override the package or something. If the logs are accessible from
diags, then it would be a great boon to our present endeavor.