Re: Request for advise with mounting particular ISO 9660 sessions
I read from the porting instructions that i
shall assume userland to be like Linux.
Well, the kernel is the same as in FreeBSD,
the libc is the same as in libc.
Majority of userland is the same as Linux,
but see bellow.
But this line is a bit obscure to me:
Example of uname check: Linux|GNU|GNU/*)
I could need an example of the string which
Currently recognized: "FreeBSD" and "Linux".
salinger@asdfasdf:~$ uname -a
GNU/kFreeBSD asdfasdf 7.2-1-amd64 #0 Tue Oct 6 23:17:13 UTC 2009 x86_64 amd64 AMD Sempron(tm) Processor 3000+ GNU/kFreeBSD
salinger@asdfasdf:~$ uname -s
salinger@asdfasdf:~$ uname -o
Another question is the mount command option
by which one can address a non-default superblock
in an ISO 9660 image.
On Linux: mount -t iso9660 -o sbsector=...
On FreeBSD: mount_cd9660 -s ...
Given we have an ISO 9660 image with several
sessions of which one starts at block number
122880, would this Linux shell command work for
the superuser ?
mount -t iso9660 \
-o nodev,noexec,nosuid,ro,sbsector=122880 \
On FreeBSD xorriso would issue this line
mount_cd9660 -o noexec,nosuid -s 122880 \
Use the FreeBSD one, as "mount" is just
user friendly interface to kernel specific syscall.
salinger@asdfasdf:~$ /sbin/mount_cd9660 -h
/sbin/mount_cd9660: invalid option -- 'h'
usage: mount_cd9660 [-begjrv] [-C charset] [-o options] [-s startsector]
This command comes from freebsd-utils package, which is available
(and essential) for both kfreebsd-i386 and kfreebsd-amd64, see
Thanks for your care about GNU/kFreeBSD.