Jean-Yves BARBIER said:
You could enlarge it a bit, and use it to make your images for CDz
Hadn't thought of that... Are there any reliable tools out there for
resizing e2fs partitions? (I already gave it all of the space that hadn't
been claimed by my root and swap partitions...)
--
Geek
On 14-Nov-1999, Dave Sherohman [EMAIL PROTECTED] wrote:
Jean-Yves BARBIER said:
You could enlarge it a bit, and use it to make your images for CDz
Hadn't thought of that... Are there any reliable tools out there for
resizing e2fs partitions? (I already gave it all of the space that hadn't
On Mon, Nov 15, 1999 at 07:47:43AM -0800, aphro wrote:
On Sun, 14 Nov 1999, Dave Sherohman wrote:
esper Hadn't thought of that... Are there any reliable tools out there for
esper resizing e2fs partitions? (I already gave it all of the space that
hadn't
esper been claimed by my root and
Alisdair McDiarmid said:
The problem with this is that cdfisk still thinks the disk is 8GB:
there's no free space left at the end of the drive.
Why's that?
I had the same problem a while ago running a Potato system with a homemade
2.2.9 kernel and a 9 Gb drive. Windows could see the entire
On 14-Nov-1999, Dave Sherohman [EMAIL PROTECTED] wrote:
Alisdair McDiarmid said:
The problem with this is that cdfisk still thinks the disk is 8GB:
there's no free space left at the end of the drive.
Why's that?
I had the same problem a while ago running a Potato system with a
On Sun, Nov 14, 1999 at 04:18:47PM -0600, Dave Sherohman wrote:
..
to the global (top) section of/etc/lilo.conf. Now the only problem is that
I've got a 534 Mb partition that I can't decide where to mount, so it's just
sitting there, still unused... (Any suggestions?)
You could enlarge
A long time ago, in a galaxy far, far way, someone said...
The problem with this is that cdfisk still thinks the disk is 8GB:
there's no free space left at the end of the drive.
Why's that?
That's a good question. The best thing I can come up with is that the
kernel, when it read the
On Tue, 9 Nov 1999, Alisdair McDiarmid wrote:
alisda Ok - a kernel 2.0 limitation
alisda
alisda Oh, right.
8GB barrier is a not a limitation in at least 2.0.36 ..doubt it is in
earlier ones too, i believe it is a LILO issue, it is not detecting the
parameters of the drive correctly. Upgrade
easiest way is to copy the data over, delete the partition and re make
it. or you can grab powerquest partition magic 4 or above.
nate
On Tue, 9 Nov 1999, Alisdair McDiarmid wrote:
alisda I recently installed slink on a machine with a 15.2GB IBM harddisk
alisda and it only recognised about 8GB
A long time ago, in a galaxy far, far way, someone said...
I recently installed slink on a machine with a 15.2GB IBM harddisk
and it only recognised about 8GB of the drive.
Ok - a kernel 2.0 limitation
I went ahead and partitioned the drive normally, leaving the last
4GB for /home. Now
On Tue, Nov 09, 1999 at 02:24:54PM -0600, Phil Brutsche wrote:
A long time ago, in a galaxy far, far way, someone said...
I recently installed slink on a machine with a 15.2GB IBM harddisk
and it only recognised about 8GB of the drive.
Ok - a kernel 2.0 limitation
Oh, right.
I went
I recently installed slink on a machine with a 15.2GB
IBM harddisk
and it only recognised about 8GB of the drive.
I went ahead and partitioned the drive normally,
leaving the last
4GB for /home. Now I've upgraded to 2.2.x and potato
and I want to
use the whole of the disk by extending the /home
12 matches
Mail list logo