On Friday 11 Nov 2011 22:02:40 Grant Edwards wrote: > On 2011-11-11, Mark Knecht <[email protected]> wrote: > > On Fri, Nov 11, 2011 at 6:54 AM, Dale <[email protected]> wrote: > ><SNIP> > > > >> Now to teach him how to update the thing. > > > > I'll be interested in hearing how that goes. I had one weekend running > > Ubuntu and ended up running away as fast as I could. > > I use Ubuntu occasionally, and it's always a teeth-gritting, > hair-pulling experience. For me, it's the most non-intuitive distro > I've ever used. And it is the "Ubuntu" part I can't grok, not the > Debian part -- I never had any problems with Debian. I ran Debian on > a server at home for years, and even created a Debian subset distro > for a product many years back. > > > It wasn't that it was bad or didn't work, but that the management of > > it seemed so different from any distro I'd run before that I didn't > > want to deal with learning it. > > Exactly. Anytime you want to do something administrative, it's always > an ordeal unless you can just skip the "Ubuntu" stuff and do the > equivalent of editing /etc/network/interfaces (I never could get the > GUI network config thingy to work). > > > Let's see how that does for you. > > > > Again, remembering I didn't really give it much of a chance - I was > > running on a Power PC Mac Mini - two things that drove me mad were: > > > > 1) The basic install didn't tell me what the root password was. > > There isn't one by default. The first thing you do after an Ubuntu > install is always set the root password: > > $ sudo bash > # passwd > > The next thing you do is configure it to boot into text mode with all > the kernel messages visible. > > Then you've got something that's almost tolerable.
How do you that?!!! Pressing F2 or Esc on the Ubuntu GRUB2 splash just crashes the system. I think I also tried editting the default GRUB2 file, but couldn't get it to be more verbose. Is there some trick I'm missing? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
