Hi, On Thu, 13 Aug 1998, Ramin Sina wrote:
/bin/sh -c fdisk -l >/tmp/stp3168_1_S 2> /tmp/stp3168_1_E
Did you ever have a look at these files:
/tmp/stp3168_1_S /tmp/stp3168_1_E
They might give you interesting information, that's why fdisk's stdout and stderr get redirected to those files.
-
Thanks for yor response. The error output states that:
The number of cylinders for this disk is set to 16383. This is larger than 1024, and may cause problems with: 1) software that runs at boot time (e.g.m LILO) 2) booting and partitioning software from other OSs (e.g.), DOS FDISK, OS/2 FDISK)
But I have no problems with LILO and the fdisk I use is within linux.
It's just a warning. What you see is just the start of fdisk's output. After that I assume it hits some CD-ROM drive and hangs.
But instead of looking at them now, try to run `fdisk -l' yourself on the command line.
And I almost forgot this: you mentioned a removable disk, so try to do your test in a situation identical to when your yast crash happened.
fdisk -l spits out the output and then hangs again (Uninterruptable Sleep). The last few times these happened was when I had no removable drives at all.
But you do have an EIDE CDROM drive, do you? Please check if the behaviour is different depending on if there is a disk in the drive or not.
Ramin -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e