Hi Jurij,
ok, this is going to be a bit lengthy... :-)
Here's what my system says:
sun:~# file /usr/lib/klibc/bin/fstype
/usr/lib/klibc/bin/fstype: ELF 32-bit MSB executable, SPARC,
version 1 (SYSV), statically linked (uses shared libs), stripped
sun:~# ls -al /usr/lib/klibc/bin/fstype
-rwxr-xr-x 1 root root 3044 Nov 3
15:56 /usr/lib/klibc/bin/fstype
sun:~# sha1sum /usr/lib/klibc/bin/fstype
cb9a1b8e65a1bd3e8ab58a9affe7b4f32d7fcced /usr/lib/klibc/bin/fstype
sun:~# file /lib/klibc-gZY_j4EiGiPMbozhciEvacptnN8.so
/lib/klibc-gZY_j4EiGiPMbozhciEvacptnN8.so: ELF 32-bit MSB
executable, SPARC, version 1 (SYSV), statically linked, stripped
sun:~# sha1sum /lib/klibc-gZY_j4EiGiPMbozhciEvacptnN8.so
01392ec3964d79152c4958b8a8095557702458d6
/lib/klibc-gZY_j4EiGiPMbozhciEvacptnN8.so
sun:~# /usr/lib/klibc/bin/fstype < /dev/hda4
Segmentation fault
sun:~#
But what I meant with static vs. shared is this (note "uses shared
libs"):
[EMAIL PROTECTED]:/usr/src/klibc-1.4.30-sparc/usr/kinit/fstype # file
shared/fstype
shared/fstype: ELF 32-bit MSB executable, SPARC, version 1
(SYSV), statically linked (uses shared libs), stripped
[EMAIL PROTECTED]:/usr/src/klibc-1.4.30-sparc/usr/kinit/fstype # file
static/fstype
static/fstype: ELF 32-bit MSB executable, SPARC, version 1
(SYSV), statically linked, stripped
[EMAIL PROTECTED]:/usr/src/klibc-1.4.30-sparc/usr/kinit/fstype #
Another thing, that should probably be filed as another bug is that an
ext3 filesystem that was previously formatted as xfs is still being
recognised as xfs, and there's apparently a problem with FSSIZE:
[EMAIL PROTECTED]:/usr/src # strace
klibc-1.4.30-sparc/usr/kinit/fstype/static/fstype < /dev/hda4
> /dev/null
execve("klibc-1.4.30-sparc/usr/kinit/fstype/static/fstype",
["klibc-1.4.30-sparc/usr/kinit/fstype/static/fstype"], [/* 18
vars */]) = 0
pread(0, "XFSB\0\0\20\0\0\0\0\0\0\16\7x\0\0\0\0\0\0\0\0\0\0\0\0
\0"..., 1024, 0) = 1024
write(1, "FSTYPE=xfs\nFSSIZE=16174537324212"..., 39) = 39
exit(0) = ?
[EMAIL PROTECTED]:/usr/src #
> Are you sure you don't have some other (non-Debian) version of
> klibc-utils installed, and that got pulled in into the initrd somehow?
I don't know, how that could have happened (well, that means, I'm sure
it hasn't :-) ). I was doing a fresh install over the net using official
debian mirrors.
But even then this would't explain the segfault when I ran the 32 bit
shared version that I've compiled myself, while the static version
works...
Otherwise the system runs pretty well, in fact I'm writing this mail
right now with Evolution under GNOME from Debian Etch RC1 :-)
Here's the content of /proc/cpuinfo:
sun:~# cat /proc/cpuinfo
cpu : TI UltraSparc IIi (Sabre)
fpu : UltraSparc IIi integrated FPU
prom : OBP 3.31.0 2001/07/25 20:36
type : sun4u
ncpus probed : 1
ncpus active : 1
D$ parity tl1 : 0
I$ parity tl1 : 0
Cpu0Bogo : 800.37
Cpu0ClkTck : 0000000017d78400
MMU Type : Spitfire
sun:~#
Can I help you with some other specs of my system?
Tomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
