Re: Dual boot, multiple kernels, sytem map problem (was Re: Switching between two file systems.)

2001-03-06 Thread Fu-Dong Chiou
I have a desktop at home that has RedHat 7.0 installed & RedHat 6.0 
transferred (from another HD).  After specifying the location of the 
other kernel image as 

image=/chopin/boot/vmlinuz

I have no problem switching between rh6 and rh7, with no error messages.  
I thought I should be able to get around this problem using the same 
logic on this laptop HD, but I have been out of luck so far.  Why is it 
still complaining about a wrong System.map?

Chip


kmself@ix.netcom.com wrote:
> > > > I have a problem.  I have RedHat on /dev/hd1, and Debian on /dev/hd5
> > > > (that I just transferred from another HD).  The problem is, when I
> > > > boot into Debian, the system.map of RedHat is still being used, and
> > > > I got a lot of warning messages.  Is there a way that I get around
> > > > this problem?  Thanks!
> > >=20
> > > Post your /etc/lilo.conf file, and possibly, your disk partitioning
> > > scheme.
> > >=20
> >=20
> > Sorry, I should have done that.
> >=20
> > [EMAIL PROTECTED] ~#more /etc/lilo.conf=20
> > boot=3D/dev/hda
> > map=3D/boot/map
>   ^
> 
> Is this the system map you're referring to?
> 
> If so, I'm not sure I can answer your question -- you're using different
> kernels for each system.  I'm not aware of a way to specify per-stanza
> boot maps, but then, I haven't really tried.  Have you considered an
> alternative boot method for Debian -- say a boot floppy or lilo floppy?
> 
> > install=3D/boot/boot.b
> > prompt
> > timeout=3D30
> > message=3D/boot/message
> > linear
> > default=3DRedHat7
> >=20
> > image=3D/boot/vmlinuz-2.2.16-22
> > label=3DRedHat7
> > read-only
> > root=3D/dev/hda1
> >=20
> > image=3D/boot/vmlinuz
> > label=3DDebian
> > read-only
> > root=3D/dev/hda5
> >=20
> > Disk /dev/hda: 240 heads, 63 sectors, 662 cylinders
> > Units =3D cylinders of 15120 * 512 bytes
> >=20
> >Device BootStart   EndBlocks   Id  System
> > /dev/hda1   * 1   271   2048728+  83  Linux
> > /dev/hda2   272   661   29484005  Extended
> > /dev/hda5   *   272   542   2048728+  83  Linux
> > /dev/hda6   543   650816448+  83  Linux
> > /dev/hda7   651   661 83128+  82  Linux swap
> >=20
> >=20
> > Chip
> >=20
> 
> --=20
> Karsten M. Self http://kmself.home.netcom.com/
>  What part of "Gestalt" don't you understand?   There is no K5 cabal
>   http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
> 



Re: Dual boot, multiple kernels, sytem map problem (was Re: Switching between two file systems.)

2001-03-05 Thread MaD dUCK
also sprach Lee Elliott (on Mon, 05 Mar 2001 03:18:35AM +):
> Ah, yes.  Sorry, I keep forgetting to replace the replyto on this list.

and you keep forgetting to use the "include message in reply" feature
correctly, just like most other people:

> > > > > > on Wed, Feb 28, 2001 at 12:03:02PM -0500, Fu-Dong Chiou ([EMAIL 
> > > > > > PROTECTED]
> > > > > > edu) wrote:
> > > > > > > Hi,

is this necessary?

please guys, 7 levels of replies???

it doesn't take much to delete irrelvant junk.

> > > > > map=/boot/map
> > > >   ^
> > > > Is this the system map you're referring to?

i hope not. /boot/map and System.map are very different.

/boot/map is the boot sector map while System.map map memory
instructions to kernel instructions.

if you have multiple kernels, installing multiple System.maps in the
form of

/boot/System.map-2.2.18
/boot/System.map-2.4.2

will do what you want.

do not mess with /boot/map.

martin

[greetings from the heart of the sun]# echo [EMAIL PROTECTED]:1:[EMAIL 
PROTECTED]@@@.net
-- 
no keyboard present.
press f1 to continue.
zen engineering. 



Re: Dual boot, multiple kernels, sytem map problem (was Re: Switching between two file systems.)

2001-03-05 Thread Lee Elliott
Ah, yes.  Sorry, I keep forgetting to replace the replyto on this list.


kmself@ix.netcom.com wrote:
> 
> You meant to post this to list?
> 
> on Sat, Mar 03, 2001 at 02:06:16PM +, Lee Elliott ([EMAIL PROTECTED]) 
> wrote:
> > kmself@ix.netcom.com wrote:
> > >
> > > on Fri, Mar 02, 2001 at 06:39:54PM -0500, Fu-Dong Chiou ([EMAIL 
> > > PROTECTED]) wrote:
> > > > kmself@ix.netcom.com wrote:
> > > > >
> > > > > on Wed, Feb 28, 2001 at 12:03:02PM -0500, Fu-Dong Chiou ([EMAIL 
> > > > > PROTECTED]
> > > > > edu) wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I have a problem.  I have RedHat on /dev/hd1, and Debian on /dev/hd5
> > > > > > (that I just transferred from another HD).  The problem is, when I
> > > > > > boot into Debian, the system.map of RedHat is still being used, and
> > > > > > I got a lot of warning messages.  Is there a way that I get around
> > > > > > this problem?  Thanks!
> > > > >
> > > > > Post your /etc/lilo.conf file, and possibly, your disk partitioning
> > > > > scheme.
> > > > >
> > > >
> > > > Sorry, I should have done that.
> > > >
> > > > [EMAIL PROTECTED] ~#more /etc/lilo.conf
> > > > boot=/dev/hda
> > > > map=/boot/map
> > >   ^
> > >
> > > Is this the system map you're referring to?
> > >
> > > If so, I'm not sure I can answer your question -- you're using different
> > > kernels for each system.  I'm not aware of a way to specify per-stanza
> > > boot maps, but then, I haven't really tried.  Have you considered an
> > > alternative boot method for Debian -- say a boot floppy or lilo floppy?
> > >
> > > > install=/boot/boot.b
> > > > prompt
> > > > timeout=30
> > > > message=/boot/message
> > > > linear
> > > > default=RedHat7
> > > >
> > > > image=/boot/vmlinuz-2.2.16-22
> > > > label=RedHat7
> > > > read-only
> > > > root=/dev/hda1
> > > >
> > > > image=/boot/vmlinuz
> > > > label=Debian
> > > > read-only
> > > > root=/dev/hda5
> > > >
> > > > Disk /dev/hda: 240 heads, 63 sectors, 662 cylinders
> > > > Units = cylinders of 15120 * 512 bytes
> > > >
> > > >Device BootStart   EndBlocks   Id  System
> > > > /dev/hda1   * 1   271   2048728+  83  Linux
> > > > /dev/hda2   272   661   29484005  Extended
> > > > /dev/hda5   *   272   542   2048728+  83  Linux
> > > > /dev/hda6   543   650816448+  83  Linux
> > > > /dev/hda7   651   661 83128+  82  Linux swap
> > > >
> > > >
> > > > Chip
> > > >
> > >
> > > --
> > > Karsten M. Self http://kmself.home.netcom.com/
> > >  What part of "Gestalt" don't you understand?   There is no K5 cabal
> > >   http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
> > >
> > >   
> >
> > I have three Debians, all with different kernels, installed on my box at
> > home and use loadlin to boot from dos - three .bat files.  One system is
> > Potato, one is a 'frozen' Woody with X3.3.6 + utah_glx and the last is a
> > current Sid.  Each has it's own / and /usr partitions.  They all use the
> > same swap partition and they all mount a common data partition.  I've
> > then symlinked a few things into this common area such as e-mails etc.
> > so I can get to them from which ever system I've booted.
> >
> > The main reason for this was resilience.
> >
> > LeeE
> 
> --
> Karsten M. Self http://kmself.home.netcom.com/
>  What part of "Gestalt" don't you understand?   There is no K5 cabal
>   http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
> 
>   
>Part 1.2Type: application/pgp-signature




Dual boot, multiple kernels, sytem map problem (was Re: Switching between two file systems.)

2001-03-02 Thread kmself
on Fri, Mar 02, 2001 at 06:39:54PM -0500, Fu-Dong Chiou ([EMAIL PROTECTED]) 
wrote:
> kmself@ix.netcom.com wrote:
> > 
> > on Wed, Feb 28, 2001 at 12:03:02PM -0500, Fu-Dong Chiou ([EMAIL PROTECTED]
> > edu) wrote:
> > > Hi,
> > >
> > > I have a problem.  I have RedHat on /dev/hd1, and Debian on /dev/hd5
> > > (that I just transferred from another HD).  The problem is, when I
> > > boot into Debian, the system.map of RedHat is still being used, and
> > > I got a lot of warning messages.  Is there a way that I get around
> > > this problem?  Thanks!
> > 
> > Post your /etc/lilo.conf file, and possibly, your disk partitioning
> > scheme.
> > 
> 
> Sorry, I should have done that.
> 
> [EMAIL PROTECTED] ~#more /etc/lilo.conf 
> boot=/dev/hda
> map=/boot/map
  ^

Is this the system map you're referring to?

If so, I'm not sure I can answer your question -- you're using different
kernels for each system.  I'm not aware of a way to specify per-stanza
boot maps, but then, I haven't really tried.  Have you considered an
alternative boot method for Debian -- say a boot floppy or lilo floppy?

> install=/boot/boot.b
> prompt
> timeout=30
> message=/boot/message
> linear
> default=RedHat7
> 
> image=/boot/vmlinuz-2.2.16-22
> label=RedHat7
> read-only
> root=/dev/hda1
> 
> image=/boot/vmlinuz
> label=Debian
> read-only
> root=/dev/hda5
> 
> Disk /dev/hda: 240 heads, 63 sectors, 662 cylinders
> Units = cylinders of 15120 * 512 bytes
> 
>Device BootStart   EndBlocks   Id  System
> /dev/hda1   * 1   271   2048728+  83  Linux
> /dev/hda2   272   661   29484005  Extended
> /dev/hda5   *   272   542   2048728+  83  Linux
> /dev/hda6   543   650816448+  83  Linux
> /dev/hda7   651   661 83128+  82  Linux swap
> 
> 
> Chip
> 

-- 
Karsten M. Self http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?   There is no K5 cabal
  http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org


pgp3i5WNqV3MU.pgp
Description: PGP signature