From: jasee on 17 Dec 2008 14:38 "Martin Gregorie" <martin(a)see.sig.for.address.invalid> wrote in message news:gibjjs$e43$2(a)localhost.localdomain... > On Wed, 17 Dec 2008 17:30:12 +0000, jasee wrote: > >> >> Yes, thanks, that's all pretty clear now (the bizarre quoting was >> Outllook's Expresses fault, if you save, then edit it, it has already >> inserted quotes) I'm just not now sure how you get multiple operating >> system lines in the boot loader, it's pretty clear from the previous >> explanation how you get one, but can you simply add another using grub? > > Just edit GRUB's boot menu, usually /boot/grub/grub.conf Thanks, that seems even easier!
From: Will Kemp on 18 Dec 2008 05:27 jasee wrote: > "Martin Gregorie" <martin(a)see.sig.for.address.invalid> wrote in message > news:gibjjs$e43$2(a)localhost.localdomain... >> On Wed, 17 Dec 2008 17:30:12 +0000, jasee wrote: >> >>> Yes, thanks, that's all pretty clear now (the bizarre quoting was >>> Outllook's Expresses fault, if you save, then edit it, it has already >>> inserted quotes) I'm just not now sure how you get multiple operating >>> system lines in the boot loader, it's pretty clear from the previous >>> explanation how you get one, but can you simply add another using grub? >> Just edit GRUB's boot menu, usually /boot/grub/grub.conf > > Thanks, that seems even easier! Yeah, what you really need to do is to have one linux system that's got a "primary" grub config in it - which uses the MBR. In any other linux systems you want to boot, install grub on that partition's boot sector. Then, in the "primary" grub.conf, add the following three lines for each other linux system: title <name of distro or something> rootnoverify (hd0,0) chainloader +1 Where "<name of distro or something>" is whatever you want to come up in the grub boot menu. And replace (hd0,0) with whichever partition the system you want to boot is on. In grub's notation, hd0,0 is /dev/sda1 (or /dev/hda1, or whatever). So, for example, /dev/sda4 would be hd0,3 and /dev/sdb2 would be hd1,1 (etc). -- http://SnapAndScribble.com
From: Nix on 20 Dec 2008 18:04 On 14 Dec 2008, Martin Gregorie spake thusly: > Personally, I wish that the 'info' system would just vanish: I'd like to > see a manpage for everything plus a set of web pages for really complex > programs. However, the GNU developers love the info system so I'm not > holding my breath. It's more that with texinfo (not info: nobody writes *info* pages anymore), we can produce printed books (via texi2dvi or texi2pdf), man pages (via texinfo2man or texi2pod/pod2man), a set of web pages (via makeinfo --html), or even the horrible info pages. So why on earth would we restrict ourselves to only one output format?
From: Nix on 20 Dec 2008 18:05 On 15 Dec 2008, Will Kemp verbalised: > Tony Houghton wrote: >> It has one advantage over HTML, you can do a client-side search over a >> hierarchy of pages (something that would have been a good idea for "Web >> 2.0" now I think of it). > > Interesting. I guess you'd have to manage to navigate your way around 'info info' to work out how to do it though! ;-) 's' isn't a very hard keystroke to just guess, and 'h' gives you quick help that also describes 's'. -- `We must stand together and fight for our shared cultural heritage as a group of people who cannot stand together to fight for our shared cultural heritage.' --- jspaleta on Balkan balkanization
From: Tony Houghton on 20 Dec 2008 19:18
On Sat, 20 Dec 2008 23:04:17 +0000 Nix <nix-razor-pit(a)esperi.org.uk> wrote: > On 14 Dec 2008, Martin Gregorie spake thusly: > > Personally, I wish that the 'info' system would just vanish: I'd like to > > see a manpage for everything plus a set of web pages for really complex > > programs. However, the GNU developers love the info system so I'm not > > holding my breath. > > It's more that with texinfo (not info: nobody writes *info* pages > anymore), we can produce printed books (via texi2dvi or texi2pdf), man > pages (via texinfo2man or texi2pod/pod2man), a set of web pages (via > makeinfo --html), or even the horrible info pages. > > So why on earth would we restrict ourselves to only one output format? There are also XML dialects, such as DocBook, that can be converted into (just about?) all of those. The trouble with TeX is that on top of the keywords, you have to remember which of a large number of possible combinations of backslashes, various types of bracket and commas etc was picked at random to adorn each one. :-/ -- TH * http://www.realh.co.uk |