Post #102,713
5/20/03 6:09:52 AM
|
Solution to the LILO problem
..that is, kernel beyond 1024th cylinder on a dual boot machine.
Don't know why I didn't think of this before...
For the following to work, support for the filesystem of the other OS - say Windows - must be in the intended kernel, or loaded from an initrd module.
On a dual boot machine with, say, a FAT32 first partition - boot from a Linux floppy - or the "rescue" system of your favorite distribution. Mount the Linux and Windows partitions as needed - say, /dev/hda3 (Linux) on /mnt and /dev/hda1 (Windows) on /mnt/c. Move or copy the files in /mnt/boot to /mnt/c. For example, an image entry should look like
image = /c/vmlinuz
Edit /mnt/etc/lilo.conf by replacing /boot with /c. Run the command
lilo -C /mnt/etc/lilo.conf -r /mnt -b /dev/hda
(The -r does a chroot to /mnt.)
Done! Who needs a stinkin' boot directory? For systemic clarity you can symlink everything that is now in the root directory of the other partition from /boot.
This would work for HPFS and OS/2. I will also work for NTFS, assuming you can get the right files onto the drive. You'd need to boot XP/2K/NT, mount the Linux paritition (readonly) and copy them over that way.
-drl
|
Post #102,714
5/20/03 7:32:55 AM
|
That's insane.
Not to mention stupid.
Or prone to error.
But hey.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #102,742
5/20/03 10:05:42 AM
|
Re: That's insane.
Hmm, but loading a separate OS to corrupt your processor settings before booting the main deal, now that's OK. (Same argument can be made against loadlin.) Actually my solution is very general and simple.
The only drawback to my method is disk security. It's no more prone to error than any root level activity.
-drl
|
Post #102,761
5/20/03 11:16:15 AM
|
But then, I find the whole idea of dual-booting insane
Maybe I'm not as hardware-deprived as I used to be, but I just don't see *any* benefit, unless you're developing WINE.
Many fears are born of stupidity and ignorance -
Which you should be feeding with rumour and generalisation.
BOfH, 2002 "Episode" 10
|
Post #102,768
5/20/03 11:34:33 AM
|
GTA 3
Oh, and Serious Sam :-D
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #102,783
5/20/03 12:23:17 PM
|
Counter-Strike, and DV editing, too
My point being this is why I have 3 boxes at home: one for CS, one for DV, one for Debian server.
Many fears are born of stupidity and ignorance -
Which you should be feeding with rumour and generalisation.
BOfH, 2002 "Episode" 10
|
Post #102,779
5/20/03 12:13:02 PM
|
I agree
..if you're not hardware challenged. The fallback machine should do it. I do it also on the main one, because there are things I can do in Linux I can't do in Windows (and vv).
-drl
|
Post #102,822
5/20/03 3:29:26 PM
|
triple-boot
My desktop is OS/2 only but my laptop triple boots Win98-OS/2-Linux.
98's used for after hours support - I'd rather VPN than drive to the office.
Linux is mostly used to rip CDs for my Linux based MP3 player. It'll see more use if the side venture pans out.
At this time I don't use 98 or Linux often enough to warrent dedicated hardware.
One thing I find interesting - under Windows and Linux the display won't go beyond 64K colors when I'm using the native resolution(1400x1050). Under OS/2 I can get 16.8M(don't know if it's 24 or 32 bit).
My desktop system at home is OS/2 only.
Darrell Spice, Jr. [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
|
Post #102,904
5/21/03 6:20:03 AM
|
My record is 7
..for an SMS project.
1) Bootloader was Boot Manager. Entries: OS/2 3, OS/2 4, Windows
Choose Windows and you get:
2) Windows boot menu: Windows 95, Windows NT 3.51, Windows NT 4.0
So what was the 7th? WinOS/2, of course :)
-drl
|
