mounting uzip image: Invalid argument

I'm making a live cd and i just hit a wall with uzip.

I started by creating a null 1GB file, which i filled with FreeBSD. After that i compressed the file with mkuzip.

Any attempts to mount this compressed image has failed, here is the output of truss when using mount_cd9660 to mount the image:

koti# truss mount_cd9660 /dev/md0.uzip testi
....
lstat("/stor/livecd/testi",0xbfbfe390) = 0 (0x0)
stat("/stor/livecd/testi",0xbfbfe420) = 0 (0x0)
open("/dev/md0.uzip",0x0,00) = 3 (0x3)
ioctl(3,CHIOGPICKER,0xbfbfe15c) ERR#25 'Inappropriate ioctl for device'
close(3) = 0 (0x0)
mount("cd9660","/stor/livecd/testi",1,0xbfbfe8c0) ERR#22 'Invalid argument'
mount_cd9660: write(2,0xbfbfdd00,14) = 14 (0xe)
/dev/md0.uzipwrite(2,0xbfbfdd20,13) = 13 (0xd)
: write(2,0x281348d0,2) = 2 (0x2)
Invalid argument
write(2,0xbfbfdd00,17) = 17 (0x11)
exit(0x1)
process exit, rval = 256
koti#

My system is FreeBSD 6.1-p11.

If anyone has any ideas on how to get this working, or what's wrong, please tell me.

Cheers,
Erik
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • mounting uzip image: Invalid argument
    ... I started by creating a null 1GB file, which i filled with FreeBSD. ... Any attempts to mount this compressed image has failed, here is the output of truss when using mount_cd9660 to mount the image: ... koti# truss mount_cd9660 /dev/md0.uzip testi ...
    (freebsd-hackers)
  • Re: Timers and timing, was: MySQL Performance 6.0rc1
    ... In message, "Steven Hartland" ... >For interest I ran truss on a typical game server we run under ... >FreeBSD to get a feel for how much this issue would affect ...
    (freebsd-current)
  • linuxolator problem on amd64
    ... FreeBSD 6.2-STABLE amd64 ... cd `dirname $0` ... cannot set up thread-local storage: cannot set up LDT for thread-local storage ... truss: execution type Linux ELF32 is not supported -- using FreeBSD ELF64: Bad address ...
    (freebsd-hackers)
  • Re: tool to view programs trace
    ... >> ports [i've never gotten ltrace to work on either linux or freebsd, ... note that FreeBSD truss has no relationship to ... [otherwise, sure, gnu cat and freebsd cat have no relationship to one ...
    (comp.unix.programmer)