I finally rid myself of Windoze. I have now an empty hda1, and hda6 is
the boot partition. Is there a problem in moving the boot partition to
the primary hda1? I don't man how to do it - that's not a problem.
Can the boot partition sit on a primary? Thanks.

--

In article <2jqqh8F13u5dvU1@uni-berlin.de>,
edjlb@yahoo.com says...
> I finally rid myself of Windoze. I have now an empty hda1, and hda6 is
> the boot partition. Is there a problem in moving the boot partition to
> the primary hda1? I don't man how to do it - that's not a problem.
> Can the boot partition sit on a primary? Thanks.
>

Short answer: yes

(my /boot partition is /dev/hda1)

In article <MPG.1b420940ff39be9798991d@news-50.giganews.com>,
Thomas Harold <tgh@tgharold.com> writes:
>
> In article <2jqqh8F13u5dvU1@uni-berlin.de>,
> edjlb@yahoo.com says...
>> I finally rid myself of Windoze. I have now an empty hda1, and hda6 is
>> the boot partition. Is there a problem in moving the boot partition to
>> the primary hda1? I don't man how to do it - that's not a problem.
>> Can the boot partition sit on a primary? Thanks.
>>
>
> Short answer: yes

True, but a longer answer (or one that could lead to a longer discussion)
is another question: why? There's the old saying, "if it ain't broke,
don't fix it." In this case, if Linux is booting and working OK, why
start moving stuff around, particularly the boot partition, which can be
trickier to move than many other partitions? There's a chance that you'll
break something, because of a mistyped command or the like. If you just
want to reclaim the disk space for use under Linux, you can run mkfs on
/dev/hda1 and mount it someplace convenient (possibly moving files to it
first). Of course, precisely how you'd do this would depend on the
current partition layout, available disk space, how you want to use the
extra space, etc.

--
Rod Smith, rodsmith@rodsbooks.com
http://www.rodsbooks.com
Author of books on Linux, FreeBSD, and networking

Rod Smith wrote:

> In article <MPG.1b420940ff39be9798991d@news-50.giganews.com>,
> Thomas Harold <tgh@tgharold.com> writes:
>>
>> In article <2jqqh8F13u5dvU1@uni-berlin.de>,
>> edjlb@yahoo.com says...
>>> I finally rid myself of Windoze. I have now an empty hda1, and hda6
>>> is
>>> the boot partition. Is there a problem in moving the boot partition
>>> to
>>> the primary hda1? I don't man how to do it - that's not a problem.
>>> Can the boot partition sit on a primary? Thanks.
>>>
>>
>> Short answer: yes
>
> True, but a longer answer (or one that could lead to a longer
> discussion) is another question: why? There's the old saying, "if it
> ain't broke, don't fix it." In this case, if Linux is booting and
> working OK, why start moving stuff around, particularly the boot
> partition, which can be trickier to move than many other partitions?
> There's a chance that you'll break something, because of a mistyped
> command or the like. If you just want to reclaim the disk space for
> use under Linux, you can run mkfs on /dev/hda1 and mount it someplace
> convenient (possibly moving files to it first). Of course, precisely
> how you'd do this would depend on the current partition layout,
> available disk space, how you want to use the extra space, etc.

Well, you're right - it did lead to problems, as in not booting at all.
I had hda1 (ex-windoze), 5 (swap), 6 (boot), 7 (home) and 8 (root).
Now, I have hda1 (boot), 5 (swap), 6 (home) and 7 (root). Re-sized,
too. After some trouble with fstab and grub, got the thing to boot,
even. However, after the initial grub stage notice, the screen is dark
- no grub menu. I hit enter, and boot proceeds, but with white hash
marks all over - can't read what's scrolling. The hashes disappear
about halfway through the gentoo messages and everything proceeds
normally. Any advice appreciated. Thanks a lot.

--

edjlb@yahoo.com wrote:
> I hit enter, and boot proceeds, but with white hash
> marks all over - can't read what's scrolling. The hashes disappear
> about halfway through the gentoo messages and everything proceeds
> normally. Any advice appreciated. Thanks a lot.

Sorry to respond to my own post. I had grub.conf's splashimage line
pointing to the old root partition. Updated it, and no problem.
Thanks again.

--