I would suggest you tell the bios to auto-detect your disk, and then
cfdisk it, and make the free space into another partition. This should
avoid eating your data.
If you've installed Lilo, the system will not boot, I don't believe.
Any change to the geometry will render it unable to access the
On Sat, 6 Feb 1999, wb2oyc wrote:
I would suggest you tell the bios to auto-detect your disk, and then
cfdisk it, and make the free space into another partition. This should
avoid eating your data.
If you've installed Lilo, the system will not boot, I don't believe.
Any change to the
On Sat, 6 Feb 1999, wb2oyc wrote:
I would suggest you tell the bios to auto-detect your disk, and then
cfdisk it, and make the free space into another partition. This should
avoid eating your data.
If you've installed Lilo, the system will not boot, I don't believe.
Any change to the
I had a bad 3.2G hard drive that was flaking on me, and it did so for
what I called the last time Monday at about 3am... what better time to
upgrade to a much more recent Debian version AND a new hard drive at the
same time? I had a 4.0G drive waiting to take its place, so why not?
So everything
On Sat, 6 Feb 1999, Dan Hugo wrote:
Apparently, I had forgotten to change the BIOS setting back to AUTO
for the IDE drive probing, which I had set up when I first found that
3.2G drive to be flaky. Ugh!
#includestdisclaim.h
I would suggest you tell the bios to auto-detect your disk, and
5 matches
Mail list logo
