bin/103366: tar fails if the tarball has device nodes when jailed

Gabor Kovesdan gabor at FreeBSD.org
Mon Sep 18 11:41:20 PDT 2006


>Number:         103366
>Category:       bin
>Synopsis:       tar fails if the tarball has device nodes when jailed
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 18 18:40:14 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Gabor Kovesdan
>Release:        FreeBSD 6.1-RELEASE-p3 amd64
>Organization:
n/a
>Environment:
System: FreeBSD server.t-hosting.hu 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #0: Sat Aug 19 11:08:15 CEST 2006 root at server.t-hosting.hu:/usr/src/sys/amd64/compile/FREEBSD amd64

>Description:

When one try to extract a tarball that contains device nodes in a jailed environment, it
always fails, even if those device nodes are excluded with --exclude.

>How-To-Repeat:

Try to install emulators/linux_dist-gentoo-stage3 jailed. The port is good, the device nodes
are excluded when installing. It installs fine in a host environment, but when jailed, one
will get such messages:

/usr/bin/tar: ./dev/rd/c3d10p6: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c4d19p5: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c6d9p4: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c6d28p2: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c0d19: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c2d10p3: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c5d28p1: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c3d3p3: Cannot mknod: Operation not permitted
/usr/bin/tar: ./dev/rd/c2d25p3: Cannot mknod: Operation not permitted
[...]

There is something weird between the jailed environment and tar. Since all of these
files are excluded from the extraction, it should just work silently.
This weirdness requires the mentioned package to be built manually from the port and it
might affect other areas as well.

>Fix:

Don't know.
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list