Mark Knecht wrote: > On Tue, Mar 27, 2012 at 2:43 PM, Dale <rdalek1...@gmail.com> wrote: > <SNIP> >> >> Right now, if Gentoo fails to boot because of the init thingy, I have no >> idea how to fix it. None at all. > > I understand. My question is why are you even using the initrd? > There's no requirement to use it today, at least on stable. There's > not even a discussion I've seen that says we _ever_ have to use it if > we don't use a separate /usr, so I'm not understanding where the > problem is. > > This is just my 2 cents, but assuming you have a lot of disk space why > not do a second Gentoo install, use initrd there to learn about it, > and just STOP doing updates to your current environment. If you don't > update it then it's not going to fail due to an update, right? > > I'm not picking on you or anything like that. It just seems to me that > you're worrying about the worst instead of doing the easiest. Let's > let the heavy lifters do some work, watch people get through it, and > only then decide what to do. No reason to cause problems with our > systems. I've masked a few packages and am being careful about > updates. > > Good luck, > Mark > >
Right now it won't be a problem but when I get my set up like I want it, it will be. I'm trying to learn it on a system that doesn't care right now. As posted elsewhere, if I boot with the init thingy then I can't su to root. My solution right now was to boot without the init thingy. However, if I get to where I can set up my system like I want, that would be a problem for me. This is holding me back from doing several things on my system and one of them is using LVM for everything but / and /boot. 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"
