On Thu, Nov 29, 2012 at 10:30 PM, Linda Walsh wrote:

Jim Henderson wrote:

...

If you want to understand why Linux uses initrd, I suggest you take some time and talk with the Linux kernel developers, after reading up on the history of the Linux kernel.

---- Linux kernel developers will say it isn't necessary.

It's only when you want 1 kernel/disk image to move to rather diverse hardware -- which isn't something users generally do.

It's exactly what binary distributions do. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, 29 Nov 2012 17:30:25 -0800, Linda Walsh wrote:

Linux kernel developers will say it isn't necessary.

Then you have your answer.

It's only when you want 1 kernel/disk image to move to rather diverse hardware -- which isn't something users generally do.

How often do you take 1 disk image and try to move it to different pieces of HW?

These days? I generally don't need to do that any more, as I've gotten out of system administration.

You worked in an ancient enterprise with 250K users that had no HW standards? You are implying no ability to load needed parts over a network -- thus no net?

Ah, I see, you know what my specific requirements were better than I do. That's nice. Or rather, that's missing my point. But that's OK, I half expected it anyways. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Anders Johansson wrote:

No, but it is something distributions do - the idea is to have one solution that fits all users. I dare you to build one kernel that will work for all openSUSE users, or even just you and me

As others have posted here, you are asking me to reimplement a process that was in *closed source* unix 15-20 years ago. Now we have open source and you think this would be a major hurdle? While I can configure a kernel that will run on your system and I could guarantee it would boot, I'd have no idea how it would come up given that if I call init, init won't bring up your system reliably with systemd installed. Even pre-systemd, I saw a few init scripts that claimed there was an error (most have gotten smarter), if they couldn't load a module (even though it was already included in the kernel). They didn't bother looking in /sys/modules to see if it was loaded first.

...

You are going off into installation issues, which I am NOT talking about. I'm talking about post-installation -- steady state systems.

Then you are talking about forcing users to build their own kernels, that is great, do you have more ideas on how to kill linux?

--- I'm not talking about forcing users to do anything -- no more than having 'dkms' compile modules "forces users" to compile their own kernel. dkms runs *once* -- when you change the module or kernel, but after that -- your kernel just 'boots'. That is *designed* to happen without user interaction. You might as well throw out how users are forced to build initrd and talk about how that will kill linux... it hasn't yet -- but it also hasn't been required. Now opensuse planners are claiming it IS necessary. They can't boot the kernel, *then mount non-root disks*, THEN start services... That's impossible is the claim. Yet Windows has no problem doing the same thing without the need for an indirect place to boot from. It isn't even the case that the boot device has to be the same as the place where your system files are as of win7 -- they place a separate lilo-like boot-loader that will load the system files from a separate device (much to my surprise when I installed Win7 for the first time)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Nov 30, 2012 at 10:47 AM, Anders Johansson wrote:

Solaris on x86 has boot archive,

Solaris on SPARC has boot archive as well. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org