public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Windows on a second drive?
Date: Tue, 6 Sep 2005 08:58:34 +0100	[thread overview]
Message-ID: <20050906085834.13d94180@hactar.digimed.co.uk> (raw)
In-Reply-To: <5bdc1c8b05090519334e41dbc7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

On Mon, 5 Sep 2005 19:33:01 -0700, Mark Knecht wrote:

> Even though it says [MBR] above it won't proceed without creating at
> least one partition on drive 0. It appears I cannot install Windows XP
> on a second drive without writing 30MB to the boot drive?

Don't you just hate the arrogance of a system that tells you which of
your drives should be used to store your files! :(

> Is it possible to safely shrink an ext3 partition on the current drive
> 0 to make way for this?

You can resize an unmounted partition by running resize2fs to shrink the
filesystem, then delete the partition in cfdisk and recreate it slightly
larger than the new filesystem size and then running resize2fs again. Or
you could just boot from a Knoppix CD and run qtparted.

> The only other thought that comes to mind at this point, assuming I
> haven't missed something obvious, is to rearrange the drives in the
> box and make drive 1 into drive 0. If I then installed grub on the
> Windows drive and fixed up fstab and the contents of grub.conf to
> recognize Gentoo on drive 1, would it work?

This certainly seems the best solution. It saves Windows getting arsey
about drives or having to try to fool it with GRUB map commands. I'd
disconnect the Gentoo drive and install Windows, then replace the Gentoo
drive as slave, boot from a live CD, edit fstab and run grub. windows
should then remain blissfully unaware of your Gentoo installation, which
means it won't try to "fix" it for you at some random later date.


-- 
Neil Bothwick

Are you using Windows or is that just an XT?

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-09-06  8:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 13:38 [gentoo-user] Windows on a second drive? Mark Knecht
2005-09-05 13:49 ` Heinz Sporn
2005-09-05 14:17   ` Mark Knecht
2005-09-05 14:47     ` Heinz Sporn
2005-09-05 21:51       ` Mark Knecht
2005-09-06  2:24         ` agl
2005-09-06  2:56           ` Mark Knecht
2005-09-05 15:21     ` Neil Bothwick
2005-09-06  2:33       ` Mark Knecht
2005-09-06  7:58         ` Neil Bothwick [this message]
2005-09-06 10:06           ` Michael Kintzios
2005-09-06 11:22             ` Neil Bothwick
2005-09-06 12:12               ` Michael Kintzios
2005-09-06 13:32                 ` Neil Bothwick
2005-09-06 14:05                   ` Mark Knecht
2005-09-05 13:51 ` LostSon
2005-09-08 10:18 ` Chris Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-09-05 13:42 brettholcomb
2005-09-05 13:50 ` Mark Knecht
2005-09-05 14:11   ` Joe Menola
2005-09-05 14:37   ` Heinz Sporn
2005-09-05 17:17   ` Alex

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050906085834.13d94180@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox