Mailinglist Archive: opensuse-factory (505 mails)

[Linda Walsh <suse@xxxxxxxxx>]

Per Jessen wrote:
> Rob OpenSuSE wrote:
>
> > In old days, it would take ages for an array of disks to spin up, 
>
> Staggered spin-up is still the norm. 
---
I have 24 external and 8 internal RAID disks (3 are 15K SAS, the rest are 2TB 
SATA), ...

My init-d start takes all of 20 seconds -- that's with all disks mounted and my 
disks
are set for auto-spinup -- but that happens during BIOS initialization and adds 
no noticeable
time over an empty controller....  

So...it is only a 2.6MHz CPU (2x4core), so it's NOT because it's a fast CPU...  


What benefit is systemd going to give me that will be worth _any_ hassles.

I don't need a ram disk to boot from.  I boot directly from a system image on 
the harddisk.  I realize that's NOT a something that would easily work for 
if one wanted to maintain 1 generic kernel that has all options builtin (though
having an option to auto-build a kernel with the necessary drivers for boot
on a given system, as a 'post boot' optimization step', for faster booting, 
would certainly be "lower impact" than forcing people to throw away current disk
partitioning.

Unless you are looking for close to 'instant' on, systems, I'm not sure how
much incremental benefit systemd is going to be delivering.

If you DO want such a system, booting off a SSD, would be the way to go and not
wait for any spinups.  You might still have to mount separate partitions for
people who still want the 'walls' of separate partitions between different
system-usage foci, but you wouldn't have to wait for spinups.


What type of benefit is expected to be coming from systemd over what I already 
have --
knocking 50% off of init's startup would save me 10 seconds.

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx