Heheh, now i can reproduce it ;-)
I did an in-place search&replace with sed on a bunch of symlinks to
directories, but i didn't remember they were symlinks. When you do that,
the symlink gets backed up as a normal file.
probably not the behauviour we want, but hey, thats live when you give
stupid
Once upon a Tue, Dec 05 2006, martijn hit keys in the following order:
>
> Once upon a Tue, Dec 05 2006, Andrew Pantyukhin hit keys in the
> following order:
> >
> > The general idea is that kernel never permits *any* write access to
> > directory files even if you have root privileges.
>
> well
Hello,
Once upon a Tue, Dec 05 2006, Andrew Pantyukhin hit keys in the following order:
>
> The general idea is that kernel never permits
> *any* write access to directory files even if
> you have root privileges.
well, it happened... i was root atm, in a jail, but i'll try to recreate
the bug..
On 12/5/06, martijn <[EMAIL PROTECTED]> wrote:
any ideas?
The general idea is that kernel never permits
*any* write access to directory files even if
you have root privileges.
Please check once again, what your problem
might be. Try backing up your disk with dd
and running fsck, or run fsck o
Hi,
I remembered thinking, should i backup the directory tree before this chang?
nah ;-)
i used sed in a directory with subdirs, and it changed all directories into
normal files :(
the exact command:
sed -i -e s/'pm_properties\([^a-z]\)/#__properties\1/g' *
after which i discovered i
