Re: two issues with cdfs
On Fri Nov 26 10, Andriy Gapon wrote: > on 26/11/2010 21:08 Alexander Best said the following: > > On Fri Nov 26 10, Andriy Gapon wrote: > >> on 26/11/2010 00:25 Alexander Best said the following: > >>> hi there, > >>> > >>> i've tripped over two issues with the cdfs: > >> > >> What's cdfs? :-/ > >> > >>> 1) take a > 4 GB example.file > >>> 2) do `mkisofs -iso-level 4 -input-charset ISO-8859-15 -V "Test 1" -o > >>> new.iso example.file` > >>> 3) mdconfig -a -t vnode -f new.iso > >>> 4) mount -t cd9660 /dev/mdX /some/place > >>> > >>> the resulting file size is only 3115015779 bytes, although it should be > >>> 7409981027 bytes (in my case). > >>> > >>> the second issue: > >>> > >>> 1) take a > 4 GB file > >>> 2) do `mkisofs -iso-level 4 -J -r -input-charset ISO-8859-15 -V "Test 2" > >>> -o new.iso example.file` > >>> 3) mdconfig -a -t vnode -f new.iso > >>> 4) mount -t cd9660 /dev/mdX /some/place > >>> > >>> there are 2 files with the same indode. the file size is 4294965248 bytes, > >>> although it should be 7409981027 bytes (in my case). > >> > >> Likely we don't support multi-extent files at the moment. > > > > at the moment? ;) any plans for the future? > > Plans/hopes etc. We haven't reached perfection yet, so no eternal code freeze > yet. i found a way to access the data on such disks. i simply copied the whole iso to my hdd using dd and then threw tar at it. since tar understands cdfs and also seems to support multi-extent i got the whole file. :) maybe adding an entry to BUGS section of mount_cd9660(8) might be a good idea. cheers. alex > > > does this limit also apply to > > blueray or does it use a different fs? > > Not sure, never had one in my hands. > > > udf support in FreeBSD is also quite > > limited. > > True. Port of NetBSD UDF is in project ideas. > > -- > Andriy Gapon -- a13x ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [CFR] a small change of ifconfig(8)
On 11/25/10, Weongyo Jeong wrote: > Hello all, > > I'm sending this email to check whether my approach is reasonable that I > added 2 line into ifconfig(8) to skip IFT_USB interfaces as follows: > > + if (sdl != NULL && sdl->sdl_type == IFT_USB) > + continue; > > And as additionally I added two changes of USB pf to call if_up(ifp) / > if_down(ifp) explicitly to UP usbus interfaces though normally it always > should be called through user ioctl calls. > > The reason why I make this patch is that I encountered a side-effect > output from ifconfig(8) after USB packet filter is committed. Yes usbus > interfaces are printed. > > Please give me some hints whether the patch is reasonable. If it's > reasonable, is there other tools which I should make patches? Currently ifconfig will with special rc.conf configuration "hang" after boot making multiuser mode impossible to happen. Perhaps ifconfig tries to do something fancy with usbus interfaces. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: two issues with cdfs
On Nov 28, 2010, at 8:58 AM, Alexander Best wrote: >>> On Fri Nov 26 10, Andriy Gapon wrote: on 26/11/2010 00:25 Alexander Best said the following: > 1) take a > 4 GB example.file Likely we don't support multi-extent files at the moment. >>> > i found a way to access the data on such disks. i simply copied the whole iso > to my hdd using dd and then threw tar at it. since tar understands cdfs and > also seems to support multi-extent i got the whole file. :) I believe this works without actually copying the image: tar xvf /dev/cd0 Cheers, Tim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on i386/i386
TB --- 2010-11-29 01:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-11-29 01:30:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-11-29 01:30:00 - cleaning the object tree TB --- 2010-11-29 01:30:31 - cvsupping the source tree TB --- 2010-11-29 01:30:31 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2010-11-29 01:30:55 - building world TB --- 2010-11-29 01:30:55 - MAKEOBJDIRPREFIX=/obj TB --- 2010-11-29 01:30:55 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-11-29 01:30:55 - TARGET=i386 TB --- 2010-11-29 01:30:55 - TARGET_ARCH=i386 TB --- 2010-11-29 01:30:55 - TZ=UTC TB --- 2010-11-29 01:30:55 - __MAKE_CONF=/dev/null TB --- 2010-11-29 01:30:55 - cd /src TB --- 2010-11-29 01:30:55 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 29 01:30:55 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] gzip -cn /src/cddl/usr.sbin/dtruss/dtruss.1 > dtruss.1.gz ===> cddl/usr.sbin/lockstat (all) cc -O2 -pipe -I/src/cddl/usr.sbin/lockstat/../../../sys/cddl/compat/opensolaris -I/src/cddl/usr.sbin/lockstat/../../../cddl/compat/opensolaris/include -I/src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/head -I/src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/lib/libdtrace/common -I/src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/lib/libproc/common -I/src/cddl/usr.sbin/lockstat/../../../sys/cddl/contrib/opensolaris/uts/common -I/src/cddl/usr.sbin/lockstat/../../../sys/cddl/contrib/opensolaris/compat -I/src/cddl/usr.sbin/lockstat/../../../sys -DNEED_ERRLOC -g -DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-unknown-pragmas -c /src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/cmd/lockstat/lockstat.c /src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/cmd/lockstat/lockstat.c: In function 'main': /src/cddl/usr.sbin/lockstat/../../../cddl/contrib/opensolaris/cmd/lockstat/lockstat.c:1062: internal compiler error: in var_ann, at tree-flow-inline.h:128 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 Stop in /src/cddl/usr.sbin/lockstat. *** Error code 1 Stop in /src/cddl/usr.sbin. *** Error code 1 Stop in /src/cddl. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-11-29 02:49:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-11-29 02:49:26 - ERROR: failed to build world TB --- 2010-11-29 02:49:26 - 3757.53 user 694.30 system 4765.36 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Issues with Jails/Routes/FIBs
Hi Julian,
Thanks for your email, alternate fib was running, it was just me logging in
using jexec only -.-"
Besides that, I'm running 8.1 RELEASE, but haven't seen to much information
about jails in 8.x and VIMAGE..
Really appreciate your help :)
Kind Regards,
Kevin
- Mensaje original -
De: "Julian Elischer"
Para: "Kevin Mai"
CC: freebsd-current@freebsd.org
Enviados: Domingo, 28 de Noviembre 2010 2:29:31
Asunto: Re: Issues with Jails/Routes/FIBs
On 11/25/10 11:38 AM, Kevin Mai wrote:
> Hi folks!
>
> I'm facing an issue here while trying to define separate routing
> tables for each jail and host.
You don't say what version of FreeBSD you are using..
> Let me show you briefly how it's done:
>
> The server has 3 physical NICs, each one connected to a different
> network (say, public network A, public network B, and LAN).
>
> Currently, the default gateway is set to be the LAN gateway, even
> though the two jails can see their own public network subnet.
can you explain what you mean by that?
> Internet: Destination Gateway Flags Refs Use Netif Expire
> default 172.16.2.1 UGS 1 3935 bce2
> 127.0.0.1 link#5 UH 0 0 lo0
> 172.16.2.0/24 link#3 U 0 0 bce2
> 172.16.2.127 link#3 UHS 0 0 lo0
> 100.16.97.0/24 link#1 U 0 0 bce0
> 100.16.97.5 link#1 UHS 0 0 lo0
> 100.16.98.0/24 link#2 U 0 0 bce1
> 100.16.98.5 link#2 UHS 0 0 lo0
>
> 100.16.97.0/24 and 100.16.98.0/24 are the two public networks and
> 172.16.2.0/24 is the LAN.
>
> I have already tried removing devfs rules from the jails, setting
> securelevel to -1 but I'm still out of luck..
>
> I know setfib can define alternate routing tables, and I even created
> a default gateway for two fibs, 1& 2:
>
> [r...@mrefns09 ~]# setfib 2 netstat -rn
> Routing tables
>
> Internet: Destination Gateway Flags Refs Use Netif Expire
> default 100.16.98.100 UGS 14 906 bce1
> 127.0.0.1 link#5 UH 0 0 lo0
> 172.16.2.0/24 link#3 U 0 0 bce2
> 100.16.97.0/24 link#1 U 0 39 bce0
> 100.16.98.0/24 link#2 U 0 0 bce1
>
> [r...@mrefns09 ~]# setfib 1 netstat -rn
> Routing tables
>
> Internet: Destination Gateway Flags Refs Use Netif Expire
> default 100.16.97.100 UGS 0 1758 bce0
> 127.0.0.1 link#5 UH 0 0 lo0
> 172.16.2.0/24 link#3 U 0 0 bce2
> 100.16.97.0/24 link#1 U 0 44 bce0
> 100.16.98.0/24 link#2 U 0 4 bce1
>
> And i've added the proper settings in rc.conf..
>
> jail_athea97_ip="100.16.97.5 netmask 255.255.255.0"
> jail_athea97_fib=1
ooh I hadn't seen that..
(goes to a recent machine to look at new jail confif stuff.)
cool. Hadn't seen that.. but it should work.
>
> jail_athea98_ip="100.16.98.5 netmask 255.255.255.0"
> jail_athea98_fib=2
>
> Am I missing something? because once I get into the jail the routing
> table is the same:
well HOW do you get into the jail?
the fib is inherited from your parent process so if your process is
not descended from
whatever you started the jail with, you will not inherrit the right
fib unless
you specifically include setfib() in the command.
> [r...@athea97 /]# netstat -rn
> Routing tables
>
> Internet: Destination Gateway Flags Refs Use Netif Expire
> default 172.16.2.1 UGS 13 6175 bce2
> 127.0.0.1 link#5 UH 0 0 lo0
> 172.16.2.0/24 link#3 U 0 0 bce2
> 172.16.2.127 link#3 UHS 0 0 lo0
> 100.16.97.0/24 link#1 U 0 0 bce0
> 100.16.97.5 link#1 UHS 0 0 lo0
> 100.16.98.0/24 link#2 U 0 0 bce1
> 100.16.98.5 link#2 UHS 0 0 lo0
>
> [r...@athea97 /]# setfib 1 netstat -rn
> Routing tables
>
> Internet: Destination Gateway Flags Refs Use Netif Expire
> default 100.16.97.100 UGS 15 1814 bce0
> 127.0.0.1 link#5 UH 0 0 lo0
> 172.16.2.0/24 link#3 U 0 0 bce2
> 100.16.97.0/24 link#1 U 0 44 bce0
> 100.16.98.0/24 link#2 U 0 4 bce1
>
> The other jail is acting the same way. I know that since I'm doing a
> jexec, the shell will have the host's route because, but, how can I
> know if it's getting the alternate routing table?
you need to do setfib 1 jexec {your command}
OR you should make your original jail command start up (however
indirectly) sshd or telnetd or whatever and
connect in via that. In that case your process will be descended from
the original
jailed process and you will get the effect you want.
However I have to point out to you that if you are using freebsd 8,
you might want to investigate the
"VIMAGE" extensions to jail. this does even more of what you want by
associating the network
changes with the jail and not just the process that was jailed.
(check the 'vnet' option to the jail command.)
> Thanks,
>
> Kevin
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current To
> unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Issues with Jails/Routes/FIBs
On 11/28/10 7:58 PM, Kevin Mai wrote: Hi Julian, Thanks for your email, alternate fib was running, it was just me logging in using jexec only -.-" Besides that, I'm running 8.1 RELEASE, but haven't seen to much information about jails in 8.x and VIMAGE.. if you are using 8 you really should be addressing either net@ or stable@ rather than current. if you compile the kernel with options VIMAGE you get the option to create each jail with a completely separate network stack. That includes with a completely differnet routing table and completely separate interfaces. The ifconfig command has a new vnet option that allows you to assign an exisiting interface into a jail for its exclusive use and the set fib command gives completely different sets of fibs for each jail. It's not very well supported yet in the rc scripts as far as I know and is pretty experimental, but it's getting more stable with time and may do exactly what you want. some examples may be found at: http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/netgraph/virtual.chain http://www.freebsd.org/cgi/cvsweb.cgi/src/share/examples/netgraph/virtual.lan as well, as looking at the jail and ifconfig man pages and looking up "vimage" on the net. Really appreciate your help :) Kind Regards, Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
