Two things have made me thinking: a: 1) Console loads Fdisk, prompting ENGLISCH 2) X loadsFdisk, prompting DEUTSCH Can I control this behaviour via setting Env.Var. "LANG" like "de_DE" ? b: FDisk announces some VERY strang Data from Partition Table: </list> Command (m for help):AC-Note:~ # fdisk /dev/hda1 Command (m for help): p Disk /dev/hda1: 255 heads, 63 sectors, 130 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1p1 ? 121614 241076 959582258+ 75 PC/IX Partition 1 has different physical/logical beginnings (non-Linux?): phys=(288, 108, 46) logical=(121613, 91, 35) Partition 1 has different physical/logical endings: phys=(288, 110, 36) logical=(241075, 210, 24) Partition 1 does not end on cylinder boundary: phys=(288, 110, 36) should be (288, 254, 63) /dev/hda1p2 ? 82801 116350 269488144 65 Novell Netware 386 Partition 2 has different physical/logical beginnings (non-Linux?): phys=(363, 101, 35) logical=(82800, 34, 51) Partition 2 has different physical/logical endings: phys=(10, 110, 13) logical=(116349, 218, 61) Partition 2 does not end on cylinder boundary: phys=(10, 110, 13) should be (10, 254, 63) /dev/hda1p3 ? 33551 120595 699181456 53 OnTrack DM6 Aux3 Partition 3 has different physical/logical beginnings (non-Linux?): phys=(345, 32, 19) logical=(33550, 137, 11) Partition 3 has different physical/logical endings: phys=(324, 77, 19) logical=(120594, 153, 54) Partition 3 does not end on cylinder boundary: phys=(324, 77, 19) should be (324, 254, 63) /dev/hda1p4 ? 243332 243336 32669+ bb Unknown Partition 4 has different physical/logical beginnings (non-Linux?): phys=(65, 1, 0) logical=(243331, 96, 4) Partition 4 has different physical/logical endings: phys=(96, 0, 7) logical=(243335, 113, 11) Partition 4 does not end on cylinder boundary: phys=(96, 0, 7) should be (96, 254, 63) Partition table entries are not in disk order <list> These values appear VERY doubtable to me. /hda1 is Windoof /hda2 is Windoof Data /hda3 is Lx /hda4 is SWP How can I get this solved and fixed? Anther issue of writing the Part.Table had not the appropriate effect. -- *º¤., ¸¸,.¤º*¨¨¨*¤Oliver@home*º¤., ¸¸,.¤º*¨¨*¤
Oliver Ob wrote:
Two things have made me thinking:
a: 1) Console loads Fdisk, prompting ENGLISCH 2) X loadsFdisk, prompting DEUTSCH
Can I control this behaviour via setting Env.Var. "LANG" like "de_DE" ?
Sounds plausible, but I don't really know.
b: FDisk announces some VERY strang Data from Partition Table:
</list> AC-Note:~ # fdisk /dev/hda1
This is most likely the problem - you're running fdisk on a *partition* instead of on the *disk*. Do 'fdisk /dev/hda' instead.
Command (m for help): p
Disk /dev/hda1: 255 heads, 63 sectors, 130 cylinders Units = cylinders of 16065 * 512 bytes
<list>
These values appear VERY doubtable to me.
/hda1 is Windoof /hda2 is Windoof Data /hda3 is Lx /hda4 is SWP
How can I get this solved and fixed? Anther issue of writing the Part.Table had not the appropriate effect.
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
Chris Reeves schrieb:
FDisk announces some VERY strang Data from Partition Table:
</list> AC-Note:~ # fdisk /dev/hda1
This is most likely the problem - you're running fdisk on a *partition* instead of on the *disk*. Do 'fdisk /dev/hda' instead.
BIG BIG THANK YOU! My mistake! (Gosh, sometimes I am really ....ermmmnn...) Good to have to (instead of the german list-pedants...)
Hi, Oliver Ob wrote:
a: 1) Console loads Fdisk, prompting ENGLISCH 2) X loadsFdisk, prompting DEUTSCH
Can I control this behaviour via setting Env.Var. "LANG" like "de_DE" ?
1) Depends what you mean by console (bash?), but if you take a look at .bashrc in your home directory, you can change /insert this: export LANG=en_GB.ISO-8859-1 or export LANG=en_US.ISO-8859-1 for British/US English in apps started from there (if supported...). ISO-... means you can set a unicode charset that fits your language (-9 or so (?) for Turkish etc.) German : export LANG=de_DE.ISO-8859-1 Possibly, you have to take a look in .profile as well. 2) X has its own locale/language settings. I don't know exactly how they work, but I'm fiddling with them. Would interest me too, knowing exactly how they work. I think .xresources/xdefaultd, possibly .xim should be responsible for calling language/locale settings from the X-app. BR, Gudmund
participants (3)
-
Chris Reeves
-
Gudmund Areskoug
-
Oliver Ob