If you want to rag on me, fine, but if you can't do anything to answer the questions, then you are just noise. There are technical issues that I've repeatedly asked that have not been answered. Michael S. Dunsavage wrote:
Actually, I asked questions multiple times for key information and was waiting for any answer -- but to expect that is likely ludicrous.
In case you forgot:
1) So if no one moved files from /{bin,sbin,lib,lib64} --> their /usr equivs, what was the issue besides libblkid was on /usr? Wouldn't it be simpler and more compatible to move libblkid to /lib64?
There was 1 lib that mount needed that was on /usr. Because of that all files on root had to be moved to /usr?
(remember, we are talking *boot-time* files that currently exist in /bin and /usr/bin that have been duplicated on initrd -- including the boot.d sysVinit scripts). What it looks like is systemd couldn't handle things from boot, so they hid the sysVinit type scripts in initrd, so they can claim they switched fully to systemd, while hiding the large amount of boot that systemd doesn't handle in initrd). There's no reason that can't be on disk that I can see... I've asked why multiple times and never gotten a straight answer that showed WHY things had to change and be moved.
Then we have your note, that you never answered: 2. -- Anton Aylward wrote:
Linda Walsh said the following on 04/11/2013 09:59 PM:
Putting all of usr on /rootfs nearly does the same thing, as the reason for a small root was to have less on it needing updating. You are so missing the point.
Yes, I am. Could you tell me the point?
To me it creates a more unstable system, more prone to failure and more difficult to restore to running condition. This means more downtime and lower reliability overall. That's my point. So why do we want that?
--- I need a ram disk to boot that contains duplicates of things I have on my system -- wny not boot from the system. Boot used to rely on files in /bin, lib[64], /sbin... Now relies on those + /usr/bin /usr/lib /usr/lib64... how is that not less reliable if /usr is corrupt or not mounted?
I could bring up the file-system restore utils from the root partition -- now? Not in the default config.
I had others, but those seems difficult enough for anyone to answer, and I'm tired of typing...
Then stop typing. Well, type one more email. The one that removes you from this list. You say you're tired. We're tired too. Of you. Crying. Go. Away.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org