You can use "ls -lo" to see the flags of existing files.
-l (The lowercase letter “ell”.) List files in the long format, as
described in the The Long Format subsection below.
-o Include the file flags in a long (-l) output. This option is
incompatible with IEEE Std 1003.1-2008 (“POSIX.1”). See
chflags(1) for a list of file flags and their meanings.
A mention for ls(1) from chflags(1):
Code:You can use "ls -lo" to see the flags of existing files.
ls(1)
Code:-l (The lowercase letter “ell”.) List files in the long format, as described in the The Long Format subsection below. -o Include the file flags in a long (-l) output. This option is incompatible with IEEE Std 1003.1-2008 (“POSIX.1”). See chflags(1) for a list of file flags and their meanings.
./fd:
total 1
dr-xr-xr-x 2 root wheel - 512 Jan 22 20:01 .
drwx-wxr-x 14 root wheel - 512 Jan 24 22:30 ..
cr-xr-xr-x 1 root wheel - 0x3 Jan 22 20:01 0
cr-xr-xr-x 1 root wheel - 0x4 Jan 22 20:01 1
cr-xr-xr-x 1 root wheel - 0xd Jan 22 20:01 10
cr-xr-xr-x 1 root wheel - 0xf Jan 22 20:01 12
cr-xr-xr-x 1 root wheel - 0x5 Jan 22 20:01 2
cr-xr-xr-x 1 root wheel - 0x6 Jan 22 20:01 3
cr-xr-xr-x 1 root wheel - 0x7 Jan 22 20:01 4
cr-xr-xr-x 1 root wheel - 0x8 Jan 22 20:01 5
cr-xr-xr-x 1 root wheel - 0x9 Jan 22 20:01 6
I've tried that but can't get rid of the files.I think they don't seem to have anything set but a-instead?
Maybe try this?:
Code:EXAMPLES Recursively clear all flags on files and directories contained within the foobar directory hierarchy: chflags -R 0 foobar
any errors?I've tried that but can't get rid of the files.
They are in a jail, which probably has some bearing but the jail is stopped.
service jail stop myjail
chflags -R noschg /myjail
rm -vfR /myjail
any errors?
As SirDice already told iocage is old & unsupported. Try something else.
iocage is still maintained and developed.I think we all do, but he isn't forcing anyone to follow his advice.I trust SirDice.
iocage was in dormant state for years, it is not the case anymore.It looks like I need to update my version.iocageis still maintained and developed.
Last commit was one month ago, last release was in December 2025.
![]()
GitHub - freebsd/iocage: A FreeBSD jail manager
A FreeBSD jail manager. Contribute to freebsd/iocage development by creating an account on GitHub.github.com
Much the same argument could be made for bhyve. Why do you need a vm-assisitant when it is a one liner?But then is the question , why use bastille or iocage. Just grab base.txz and untar. Your done.
mkdir -p /jails/jail0 bsdinstall jail /jails/jail0Never said that. EZJail is old and should not be used any more.As SirDice already told iocage is old & unsupported.
Those files don't have any flags.Here is what I get:-
Code:./fd: total 1 dr-xr-xr-x 2 root wheel - 512 Jan 22 20:01 . drwx-wxr-x 14 root wheel - 512 Jan 24 22:30 .. cr-xr-xr-x 1 root wheel - 0x3 Jan 22 20:01 0 cr-xr-xr-x 1 root wheel - 0x4 Jan 22 20:01 1 cr-xr-xr-x 1 root wheel - 0xd Jan 22 20:01 10 cr-xr-xr-x 1 root wheel - 0xf Jan 22 20:01 12 cr-xr-xr-x 1 root wheel - 0x5 Jan 22 20:01 2 cr-xr-xr-x 1 root wheel - 0x6 Jan 22 20:01 3 cr-xr-xr-x 1 root wheel - 0x7 Jan 22 20:01 4 cr-xr-xr-x 1 root wheel - 0x8 Jan 22 20:01 5 cr-xr-xr-x 1 root wheel - 0x9 Jan 22 20:01 6
I'm trying to delete some files and think the chflags are set.
I couldn't find any way to delete them. In the end I destroyed the jail.Those files don't have any flags.
So, most likely, we will never know why.I couldn't find any way to delete them. In the end I destroyed the jail.
I can only imagine that they were locked somehow by IOCAGE.So, most likely, we will never know why.
SirDice as long as you cannot name a serious reason, this is a highly private opinion. Can you?EZJail is old and should not be used any more
Latest release was released at 2015-11-23.SirDice as long as you cannot name a serious reason, this is a highly private opinion.