Peep Posted December 30, 2003 Report Share Posted December 30, 2003 I just did a clean install of the download edition of 9.2 and things seem to be going smoothly, but this just looks weird to me: [bill@localhost bill]$ df Filesystem Size Used Avail Use% Mounted on /dev/ide/host0/bus0/target0/lun0/part7 5.0G 1.1G 3.9G 22% / /dev/ide/host0/bus0/target0/lun0/part8 8.4G 232M 8.2G 3% /home /dev/ide/host0/bus0/target0/lun0/part1 2.6G 4.0K 2.6G 1% /mnt/windows why doesn't it say "hda7" and "hda8" etc? is this a problem, and if so, how do i fix it? thanks Quote Link to comment Share on other sites More sharing options...
RainierPeak Posted December 30, 2003 Report Share Posted December 30, 2003 Just wanted to confirm that I have the same, weird issue. Quote Link to comment Share on other sites More sharing options...
Peep Posted December 30, 2003 Author Report Share Posted December 30, 2003 ok, thanks. i probably won't worry about it so much then :P Quote Link to comment Share on other sites More sharing options...
roland Posted December 30, 2003 Report Share Posted December 30, 2003 /dev/hdx are links. They point to things like /dev/ide/host0/bus0/target0/lun0/partx roland Quote Link to comment Share on other sites More sharing options...
chris z Posted December 31, 2003 Report Share Posted December 31, 2003 i have the same problem/nuisance after upgrading to MDK9.2. after searching a bit, i found the following info. this is a known bug with MDK9.2 & the 2.4.xx kernel. see this BUG REPORT . excerpts from above link: Inside "software" forum, bgmline has posted in the "9.2 changes the way df and mount report mounted device names" a nice example of the problems created by this bug. The simple script: df |awk '{print $6}' works in 9,1, but fails in 9.2, because long devfs-style names cause the output to appear on two lines insterad of one. note that the kernel-2.6.x was fixed for this problem. maybe the fix is simple enough to be backported ? there is a ham handed fix listed that involves editing lilo if ya wanna do it. if it is indeed fixed with the 2.6 kernel, then i'll just deal with it until i can get an rpm of that kernel that works or until (perhaps) a patch is released for the 2.4 kernel. Chris Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.