Grub install tools?
in [Slackware]
|
Prev: Unsupported kdelibs
Next: lost icons in xfce
From: Mike Jones on 17 Feb 2010 19:17 Responding to Grant: [...] > >>> The good news: >>> http://www.linuxplanet.com/linuxplanet/tutorials/6981/1/ The bad news: >>> http://www.linuxplanet.com/linuxplanet/tutorials/6981/2/ >>> >>> More information found at >>> http://www.gnu.org/software/grub/grub.en.html >> >> >>OFCOL! Whats going on lately? Everything seems to be becoming insanely >>(more) complex for no good reason! Is M$ planting spooks in Linux >>development teams? %| > > It's the nature of the beast -- developers seem rarely to stay back with > a 'finished' project to iron out all the bugs. > I was going to mention the MC 4.1.X-MP project, but as the install of the latest version just barfed over my HDD I'm not so sure about that either. Maybe there is a season for this kind of thing? -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Jerry Peters on 18 Feb 2010 17:09 Grant <g_r_a_n_t_(a)bugs.id.au> wrote: > On Wed, 17 Feb 2010 16:42:06 GMT, Mike Jones <Not(a)Arizona.Bay> wrote: > >>Responding to Bit Twister: >> >>> On Wed, 17 Feb 2010 15:41:08 +0000 (UTC), Douglas Mayne wrote: >>> >>>> The first thing to remember about grub is that device >>>> numbering/nomenclature begins with "0". C-style, I guess. >>> >>> Gotta love progress. >>> >>> GRUB is Legacy software. >>> >>> All Hail GRUB2. >>> >>> You will just love grub2. ;-/ > > Not if it still insists on using undefined disk space like first cylinder, > sectors 2..63. This single stupid notion stops me considering grub. Why? Might as well put the disk space to some use. > > Besides, lilo works fine for me. Lilo is fine until one has >2TB drives > to boot. But in my mind, I'd rather the OS stay on a smaller disk, away > from such large, possibly RAID, data drives. Except if anything goes wrong, with lilo you're screwed. With grub I can at least try to find something that will boot, or edit the kernel command line. It's saved me from having to boot my rescue system several times. Jerry
From: James Woodard on 20 Feb 2010 01:18 On Wed, 17 Feb 2010 23:28:47 +0100, Tuxedo wrote: > GangGreene wrote: > > [...] > >> /boot/grub/menu.lst > > Thanks for the hint! it is where my current grub menu gets its options > but the file resides in the partition of my other ubuntu-like distro. > Trying to edit it from there is a bit hard, because the ubuntu installer > didn't give me a possibility to define a root password as far as I know > and the file is owned by root. Not a problem to edit it from within > Slackware, and at least I have a working bootloader now, wherever it is > :-) > > Tuxedo Ubuntu doesn't think users are smart enough to have access to root privileges. Instead, it adds the first user to the sudoers list. sudo gedit /boot/grub/menu.lst password:(first users password) To change this behavior, sudo passwd root will create a root password. Thus allowing you to screw up your machine anyway you please.
From: Auric__ on 20 Feb 2010 13:13 On Sat, 20 Feb 2010 06:18:05 GMT, James Woodard wrote: > Ubuntu doesn't think users are smart enough to have access to root > privileges. Of course, for the vast majority of people, it's right. -- I'll survive.
From: John F. Morse on 20 Feb 2010 15:56
Auric__ wrote: > On Sat, 20 Feb 2010 06:18:05 GMT, James Woodard wrote: > > >> Ubuntu doesn't think users are smart enough to have access to root >> privileges. >> > > Of course, for the vast majority of people, it's right. > Exactly! Remember that Micr0$lut gave all Windoze users "root" access, and now what do you have? A zillion bots spamming and sending out their own viruses, Trojans, adware, malware, DDOS, .... Ubuntu attracts many Win-droids -- just read a.o.l.ubuntu. These people need someone or something to "protect" the rest of us. -- John When a person has -- whether they knew it or not -- already rejected the Truth, by what means do they discern a lie? |