Re: HOWTO: FreeBSD ZFS Madness (Boot Environments)
On 5/4/2012 5:10 PM, Randal L. Schwartz wrote: >>>>>> "Randal" == Randal L Schwartz writes: > > Randal> Oh wait, it looks like zroot is still holding 1.04G of data... will > Randal> that ever go away? Shouldn't all the data be in the /ROOT/xxx > Randal> items? > > And worse, the things from the readme don't work: > > locohost# ./beadm create upgrade > cannot create 'zroot/ROOT/upgrade': invalid property '' > cannot open 'zroot/ROOT/upgrade': dataset does not exist > Created successfully > > So, no joy on this yet. > > This is FreeBSD 8.2. > Hi, Those errors will be fixed in the next release, out in the next day or so. Still testing it. If you want to help test, it's out on vermaden's github right now. An updated port will be available soon as well. Regards, Bryan Drewery ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: State of Packages
On 4/4/2013 1:57 PM, d...@safeport.com wrote: > Its seems certain that pkg_add is not [going to] be[ing] restored. Progress is being made on providing pkg_add and pkgng packages again. They will come back. > > Index of ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/9.1-RELEASE/ > > Name Size Last Modified > File:MANIFEST 1 KB 12/04/12 10:10:00 > File:base.txz 58452 KB 12/04/12 10:09:00 > File:doc.txz 1410 KB 12/04/12 10:10:00 > File:games.txz 1092 KB 12/04/12 10:10:00 > File:kernel.txz 56686 KB 12/04/12 10:10:00 > File:lib32.txz 9516 KB 12/04/12 10:10:00 > File:ports.txz 85867 KB 12/04/12 10:10:00 > File:src.txz 94190 KB 12/04/12 10:10:00 > > This pretty much invalidates 5.4 of the handbook. > > My questions: Does/will pkgng work? Are 9.1 packages on the ISO images? > I am in the progess of answering that one for myself but had some time > on my hands during the download :) > > _ > Douglas Denault > http://www.safeport.com > d...@safeport.com > Voice: 301-217-9220 > Fax: 301-217-9277 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: Typo in portmaster man page?
On 5/9/2013 3:25 AM, Leslie Jensen wrote: > > When reading the portmaster man page I just came to wonder if this isn't > a typo? > > > [--force-config|-G] [-aftv] -F > fetch distfiles only > > > > Shouldn't the -F be to the far left? > > Thanks > > /Leslie It seems consistent with how the other feature modes are documented. (I'm not the original author on portmaster). Personally the manpage really confuses me. There's been bigger issues to tackle first though so I have not touched the manpage much. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/gettext-0.18.3 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/libiconv-1.14_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/pkg-1.1.4_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/m4-1.4.16_1,1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/perl-5.14.4 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/gettext-0.18.3 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/m4-1.4.16_1,1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/m4-1.4.16_1,1/pkg-1.1.4_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/perl-5.14.4 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/perl-5.14.4/pkg-1.1.4_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/gettext-0.18.3 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/gettext-0.18.3/pkg-1.1.4_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/gettext-0.18.3/libiconv-1.14_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/libiconv-1.14_1 > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/libiconv-1.14_1/pkg-1.1.4_1 > >> Cleaning up > >> Umounting file systems > > > > could someone help me? > > thanks in advance > > Wolfgang > > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
On 7/23/2013 9:00 AM, Wolfgang Riegler wrote: > yes, there is > /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/usr/ports/ports-mgmt/pkg/ Can you try with NOLINUX=yes in your poudriere.conf? > > regards > > Wolfgang > > Am Dienstag, 23. Juli 2013, 08:48:38 schrieb Bryan Drewery: >> On 7/23/2013 8:36 AM, Wolfgang Riegler wrote: >>> Hi, >>> >>> I having trouble using poudriere since updating it to 3.0.4 on FreeBSD >>> 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete >>> output of trying to compile shells/bash: >>> >>> >>> # poudriere bulk -p hostportstree -f >>> /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv >>> >> Creating the reference jail... done >>> >> Mounting system devices for 91amd64-hostportstree >>> >> Mounting ports/packages/distfiles >>> >> Mounting packages from: >>> /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree >>> >> Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options >>> >> Logs: >>> /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s >>> >> WWW: >>> http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s >>> >> Appending to make.conf: /usr/local/etc/poudriere.d/make.conf >>> /etc/resolv.conf -> >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf >>> >> Starting jail 91amd64-hostportstree >>> >> Calculating ports order and dependencies >>> >> Computing deps for shells/bash >>> >> DEBUG: shells/bash depends on ports-mgmt/pkg >>> >> Computing deps for ports-mgmt/pkg >>> >> DEBUG: shells/bash depends on devel/bison >>> >> Computing deps for devel/bison >>> >> DEBUG: devel/bison depends on ports-mgmt/pkg >>> >> DEBUG: devel/bison depends on devel/m4 >>> >> Computing deps for devel/m4 >>> >> DEBUG: devel/m4 depends on ports-mgmt/pkg >>> >> DEBUG: devel/bison depends on lang/perl5.14 >>> >> Computing deps for lang/perl5.14 >>> >> DEBUG: lang/perl5.14 depends on ports-mgmt/pkg >>> >> DEBUG: devel/bison depends on lang/perl5.14 >>> >> DEBUG: devel/bison depends on devel/gettext >>> >> Computing deps for devel/gettext >>> >> DEBUG: devel/gettext depends on ports-mgmt/pkg >>> >> DEBUG: devel/gettext depends on converters/libiconv >>> >> Computing deps for converters/libiconv >>> >> DEBUG: converters/libiconv depends on ports-mgmt/pkg >>> >> DEBUG: devel/bison depends on lang/perl5.14 >>> >> DEBUG: devel/bison depends on devel/m4 >>> >> DEBUG: shells/bash depends on devel/gettext >>> >> DEBUG: shells/bash depends on converters/libiconv >>> >> pkg package missing, skipping sanity >>> >> Cleaning the build queue >>> >> Building 7 packages using 1 builders >>> >> Starting/Cloning builders >>> mount: linprocfs: File name too long >>> >> Hit CTRL+t at any time to see build progress and stats >>> >> [01] Starting build of ports-mgmt/pkg >>> make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory >> >> Does ports-mgmt/pkg exist in the ports tree you are using? >> >> >>> >> Error: Unknown stuck queue bug detected. Please submit the entire >>> build output to poudriere developers. >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 >>> /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 >>> /mnt/system/DATEN/poudriere/basefs/d
Re: Updating texlive-base with portupgrade fails (sort of)
On 8/25/2013 2:39 PM, Carmel wrote: > Using "portupgrade-devel-20130718,3" installed from the ports system, > attempting to update "texlive-base" always ends like this: > > ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400 > (consumed 00:11:57) > ---> Updating dependency info > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > ---> Upgrade of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:28 -0400 > (consumed 00:12:00) > ---> Session ended at: Sun, 25 Aug 2013 15:25:28 -0400 (consumed 00:12:19) > /usr/local/lib/ruby/site_ruby/1.9/pkgtools/pkgtools.rb:828: stack level too > deep (SystemStackError) > > I have attempted to reboot the system and then start the update > process; however it doesn't make any difference. Even though it appears > as if the port has been updated, when I run "pkgdb -aFv", I am greeted > with this: > > [...] > Checking texlive-base-20120701_7 > Checking texlive-full-20120701 > Stale dependency: texlive-full-20120701 -> texlive-base-20120701_8 > (print/texlive-base): > Disclose depends for texlive-full-20120701 > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > Fixed. (-> texlive-base-20120701_7) > [...] > > This is the only package that "portupgrade" seems to be chocking on. I > used "portupgrade" to initially install the complete "texlive" package, > so I am not sure why it is suddenly have problems. > I've just updated ports-mgmt/portupgrade-devel with a fix. Please give it a try and let me know. Version 20130916,3. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 8/16/2012 10:33 AM, Hartmann, O. wrote: > I tried to find rescue images and a rescue DVD of a snap shot server, > but there is no way to crawl through the informations on the web pages > towards a snapshot. All folders end up in 2011 and highly outdated > (www.freebsd.org, I didn't look at mirrors since I thought the main > server carries the most recent stuff). This isn't funny. No lead, no > hint, even in the download section. http://pub.allbsd.org/FreeBSD-snapshots/ Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Lockups/panics with arbitrary 7.2 boxes
On 8/24/2012 6:47 AM, Sriram Gorti wrote: > We have been observing the following on quite a few of our i386 > FreeBSD 7.2 systems in the course of the last few months: 7.2 reached EoL June 30th, 2010. See http://www.freebsd.org/security/ You should really upgrade. Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portaudit and automake14
On 8/28/2012 1:47 PM, David Newman wrote: > 1. On a 8.0-RELEASE system, I'm having a problem with the automake14 > port, where the portaudit port reports this vulnerability: > > http://portaudit.freebsd.org/10f38033-e006-11e1-9304-.html > > Refreshing the ports collection with 'portsnap fetch extract' and then > running 'portmaster automake14' returned the same error as before: > > automake -- Insecure 'distcheck' recipe granted world-writable distdir > > I then tried to do 'make deinstall && make reinstall' for automake14, > but that just deinstalled the port. The system returns the same error as > above when trying to reinstall. > > How to resolve? > > 2. This system also has a couple of other automake ports installed: > > automake-1.12.3 > automake-wrapper-20101119 > > How to determine if these are necessary in addition to automake14? automake14 is not vulnerable to this issue. The vuxml was recently updated to show that it only affects 1.5 and up. http://www.vuxml.org/freebsd/36235c38-e0a8-11e1-9f4d-002354ed89bc.html Not sure when portaudit updates, but in the meantime you can ignore that error: env DISABLE_VULNERABILITIES=1 portmaster ... You can also try deinstalling automake14 as it may not even be required on your system and the newer 1.12 may automatically be used instead. To be clear, automake14 is super old. automake-1.12.3 is current. > > Thanks > > dn > Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Somewhat OT: Using Pipes Inside a GNU Make File
On 9/5/2012 7:02 PM, Tim Daneliuk wrote: > A bit off topic, but I'm kind of stuck. I am using gmake and want to > do something like this: > >FOO := $(shell a | b | c) > > But this appears not to work. Only the 'a' command is executed. The > remainder > of the pipeline is ignored. Is there some clean way to implement this > kind of thing? > > I use this in a GNUMakefile and it works fine. BRANCH := $(shell git branch --no-color | grep "^*" | sed -e 's/^\* //') You may need to post a more specific example. Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Fetched Ports index falling out of date
On 10/16/2012 5:10 PM, Paul Macdonald wrote:
> Hi,
>
> For the past 4 days or so, i have noticed an issue where the ports INDEX
> is out of date.
>
> e.g
> portupgrade-2.4.10,2> succeeds index (index has
> 2.4.9.9,2)
> sqlite3-3.7.14.1> succeeds index (index has 3.7.14)
>
> This is on both 8.3 REL and 9.0 REL (amd64)
>
> Ports index update performed by make fetch index in /usr/ports
> and also tried portsdb -Fu
>
> Building with Uu fixes issue but i don't fancy doing that locally every
> day.
>
> Anyone else seeing this?
I've noticed this as well.
Mind showing me the output of this?
grep portmaster /usr/ports/INDEX-{7,8,9} 2>/dev/null|cut -d \| -f 1
Bryan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/27/2012 1:22 PM, Alexander Kapshuk wrote: > Quick question about portupgrade's support for pkgng. > > The /usr/ports/UPDATING says: > 20121015: > AFFECTS: users of ports-mgmt/portupgrade > AUTHOR: bdrew...@freebsd.org > > Portupgrade now supports pkgng. To use pkgng, enable it in your > make.conf, > and convert your databases. > > This is optional and not currently required. > > # make -C /usr/ports/ports-mgmt/pkg install clean > # echo 'WITH_PKGNG=yes' >> /etc/make.conf > # pkg2ng > # pkgdb -fu > > Having done all of the above, I ran portupgrade to update all the pkgs > that needed upgrading on my system, and got the message below: > root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' > USING PKGNG > Packages are not yet suported. Use pkg(8) directly. > > That doesn't sound like portupgrade supports pkgng, or did I misread the > message in the UPDATING file? PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. > > box0=; uname -a > FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 > 17:11:45 UTC 2012 > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > Thanks. > > Alexander Kapshuk. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 2:16 AM, Alexander Kapshuk wrote: > On 10/28/2012 03:00 AM, Bryan Drewery wrote: >> PKGNG is a replacement for the pkg_* tools that record package data in >> /var/db/pkg. >> >> It also allows for binary package upgrades. >> >> If you are wanting to use pkgng for binary packages, there's no need to >> use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. >> > Understood. Thanks. > > For some reason I thought I could use the PKGNG tool set together with > portupgrade the same way the pkg_* tools are used. pkgng obsoletes portupgrade -P and pkg_add -r. Even if portupgrade -P did have pkg support, it would not work right because of different OPTIONS/dependencies, and the desync between your local ports tree and the remote package server's versions. You can use 'pkg install' to replace 'portupgrade -P' right now, and just not use -P if you want to use the port. But it will not go smoothly. Picking one of the other is best. (Ports or packages) If you're managing multiple servers with packages, I recommend checking out ports-mgmt/poudriere (http://fossil.etoilebsd.net/poudriere) as it will build the binary packages to create your own remote pkgng repository. poudriere+pkgng really do obsolete portupgrade all together. > > Is there a straightforward way to go back to using the pkg_* tools in 9.1? If you have not installed, upgraded, or deinstalled anything, yes. You can cp all of the package dirs from /var/db/pkg.bak into /var/db/pkg, and remove WITH_PKGNG from /etc/make.conf and then run pkgdb -fu again. > > Thanks. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HELP: some process eat my /var
On 11/2/2012 2:05 PM, Eugen Konkov wrote: > 858M./crash > > 1.3G./db > > 3.7G./log Cleanup old coredumps in /crash. Ensure /etc/newsyslog.conf captures all of your big logfiles in /var/log. Also consider moving whatever is large in /var/db elsewhere. Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: poudriere amassing fetch errors
On 11/2/2012 11:52 AM, Wolfgang Riegler wrote: > Hi, > > unfortunately I have the same problem. A lot of fetch and checksum errors. I > have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf, > resolv.conf is copied to the poudriere jail and manual fetching of the ports > is working. > On every run of poudriere bulk different ports are failing due to fetch or > checksum errors. Sometimes no file is fetched, sometimes a small one and then > I get a checksum failure, sometimes the file is about two times bigger and I > get a checksum failure, too. > This doesn't sound like a poudriere-specific issue. There may be a general fetching issue with bsd.port.mk, that I plan to investigate further. > Normal make install clean is running fine on that machine. > > I'm using FreeBSD 9.1-rc2 and poudriere 2.2 (2.1. had the same issue) > > > I have some other problems as well: > - poudriere bulk doesn't exit; after building all pkgs it sleeps forever This issue should be fixed in poudriere-devel. > - I have two errors several times, but I don't know to which ports they > belong: > perl: not found > "Makefile", line 86: warning: "/bin/sh -c 'case `perl --version` in > *freebsd-thread*) echo yes ;; esac'" returned non-zero status > and > /usr/local/bin/apr-1-config: not found > "Makefile.common", line 115: warning: "/usr/local/bin/apr-1-config > --includedir" returned non-zero status > The first I'm not sure about. The 2nd are apache ports incorrectly depending on apr to be installed, which does not work in a fresh jail. If you run ports-mgmt/poudriere-devel bulk with -J1 you should see which port is causing these issues, so they can be reported to the maintainers. The specific problem as that the ports do not build properly within clean jails. > > Could anybody help me? > > Thanks > > Wolfgang > Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HELP: some process eat my /var
On 11/2/2012 2:20 PM, Eugen Konkov wrote: > Здравствуйте, Bryan. > > Вы писали 2 ноября 2012 г., 21:09:49: > > BD> On 11/2/2012 2:05 PM, Eugen Konkov wrote: >>> 858M./crash >>> >>> 1.3G./db >>> >>> 3.7G./log > > BD> Cleanup old coredumps in /crash. Ensure /etc/newsyslog.conf captures all > BD> of your big logfiles in /var/log. Also consider moving whatever is large > BD> in /var/db elsewhere. > > BD> Bryan > > Notice df -h > /dev/ada0s1d 30G 23G3.7G87%/var > > and notice du -h -d 1 > 6.2G > > I have only 6.2G are occupied by files > > where 18Gb of disk space? > Are you running MySQL? It uses hidden tmpfiles that may grow quite large. Restarting it may cleanup the space. Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: rm -rf and flags (schg, sunlnk)
On 11/14/2012 2:34 PM, Gary Aitken wrote:
> Assuming one makes a mirror of a file system for backup purposes,
> then renames the mirror and makes another one,
> then attempts to remove the original using "rm -rf",
> the rm will fail if any of the files have the schg or sunlnk bits set.
>
> Is there an easy way around this problem other than traversing the whole
> subtree,
> finding files with the flags set and unsetting them?
>
Two options:
find /PATH -flags schg -exec chflags noschg {} +
or
chflags -R noschg /PATH
Then
rm -rf /PATH
> thanks,
>
> Gary
Bryan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
