Philipp Thomas wrote:
The question is, how do I support a maximum of different devices *without* requiring the user to compile his own kernel.
For those, you *offer* them the option to rebuild the kernel with their needed-boot modules and install that to disk to enable direct boot.
The is free software, so why don't you implement something like that and then offer it to those that do want it?
It would have been trivial if the boot system hadn't been modified to be difficult to maintain, unfriendly, error-prone, boot-resistant, fault-intolerant -- the move to systemd with the now claimed false requirement of moving all to /usr/bin, has made things incredibly unstable and unusable for a development platform without severe repair work. If I were to work from 11.4, I could have it as a replacement for 12.3 timeframe for the stuff in there now, but trying systemd, has caused numerous hangs and having to bring it up by hand -- boot 'S' run bootscripts by hand, then run rcdir by hand. initscripts timed out -- and the system came up -- it was resilient. systemd, 1 thing hangs and the system has you locked out and you can't fix it without rebooting to single user -- if that works. I haven't been able to keep track of all the ways systemd is failing when it tries to come up -- and don't ask me to report bugs, as 1) there are too many and I wouldn't know where to start, and 2) no one is willing to fix the underlying problems, but continue to go down hill -- the move /usr isn't necessary, you said it yourself, but it is continue and causing more damage as it moves forward. I couldn't understand why boot processes no longer worked -- "boot.local" was reserved for calling site-local boot needed processes after boot and before single-user. It is no longer called, but worse, trying to add it, I am told: #chkconfig boot.local on insserv: Note: sysvinit service boot.local is shadowed by systemd local.service, Forwarding request to '/bin/systemctl --root / enable local.service'. Operation failed: No such file or directory insserv: Forward service request to systemctl returned error status : 256 insserv: script name boot.local is not valid, skipped! ==== Great -- boot.local isn't valid? Yet it is the same header and format as the rest. It loaded modules and set the font/tty cuz it doesn't get set right by systemd when one does a warm reboot. Now it doesnt' get called at all, and the drivers not loading caused systemd to hang and the sytem not to come up... wonderful! and this is in SuSE 12.1?? I deliberately enabled the break key in 'boot'.... - so if the system hung during boot, I could press break and interrupt boot and fix it. now.. it's locked out. This is Suse inovation??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org