Neil Bothwick wrote:
> On Tue, 27 Mar 2012 16:43:38 -0500, Dale wrote:
>
>> That's why I want something that I can install fast. Gentoo certainly
>> isn't the right choice for that. If Kubuntu fails, I can just reinstall
>> and not format /home.
>
> That's why ${DEITY} gave us backups: no need to reinstall just roll back
> to the last working version. Even if your backup is a couple of weeks
> old, it with be more up to date than any distro CD.
I don't have the space for a backup, certainly not a full back up of
even just the OS. I might could do one without all the KDE and other
extras but that's not a whole lot better than just reinstalling. I keep
copies of /etc and my world file on a stick thingy.
>
>> Right now, if Gentoo fails to boot because of the init thingy, I have no
>> idea how to fix it. None at all. I know the basics of what it does but
>> no idea how to fix it when it breaks. That's where I am now with regard
>> to my other post. I can't su to root when using the init thingy but can
>> when I don't use the init thingy. I have no clue where to even start to
>> fix it.
>
> Why not post the details of it? All an initramfs is is an init script and
> a few binaries. Extract the init script, the initramfs file is a plain
> cpio archive, and post it here.
I did post it a week or so ago in another thread. I thought it was a
KDE issue at first since I first noticed it in KDE. After a few other
tests, I found out it did the same outside of KDE. I went back to see
what was updated and didn't find anything that I thought could cause
such a thing so I thought I would try a older kernel, with no init
thingy. It worked. Then I tried the exact same kernel as I was using
before but removed the init options. It worked then. So far the only
way I can get it to fail is to boot with the inti thingy. That is even
tho I used the exact same kernel. Confuses me too.
>
>> Me clueless since this is something I tried to avoid in the past and not
>> sure why it is needed now either.
>
> Because upstream decided to work this way to avoid the problems caused by
> the anachronistic separation of / and /usr. This is not so much a
> decision by the udev devs as an acceptance that the current filesystem
> organisation was becoming ever more unworkable in the general case.
>
>
Yea, I know all that. They are breaking one thing to fix something else
so that they don't have to deal with fixing what they broke. I got that
a long time ago. ;-)
When I reboot, I'll use the init thingy and post all this in a new thread.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
