It were > 20 directories/files with a wrong owner.
___
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"
I don't use space in filenames, I just wanted to ensure, that file names
with spaces will be handled partly correctly.
At the moment I'm not working intensively. Every once in a while I take a
look at a directory and compare it with the backups. If there's something
wrong, I manually run chow
On Tue, 29 Jan 2013 12:23:09 +0100, Ralf Mardorf wrote:
> On Tue, 2013-01-29 at 10:08 +0100, Matthias Apitz wrote:
> > This is a mayor damage and can only be repaired by a new installation.
>
> Perhaps true, but if such a simple mistake can't be fixed, [...]
Excuse me, it's not a _simple_ mistake
On Tue, 29 Jan 2013 03:54:55 +0100, Ralf Mardorf wrote:
> On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom wrote:
> > On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
> >> Still not perfect, I guess I need something similar to ls -RAl for some
> >> directories :S and I didn't test what awk will do with na
I'm surprised, there's no /bin/sh for the backup:
# ls -ld /bin/sh
-r-xr-xr-x 1 rocketmouse wheel 142952 Dec 23 18:38 /bin/sh
# ls -ld /usr/TMP4DIFF/bin/sh
ls: /usr/TMP4DIFF/bin/sh: No such file or directory
This is an error in reasoning :D. I compared the original /bin, with a
restore from
On Tue, 29 Jan 2013 14:58:18 +0100, wrote:
mtree
I was confused, since the existing files only provide directories. Ok, I
guess I understand, I can let mtree generate new files using the backup. I
anyway need to take care about files that are missing by the backup.
Thank you.
--
Sent fr
I suspect it's less effort to use Thunar and instead of scrolling, as I
did before (when I missed some wrong owners), to switch sorting by owner
between ascending and descending, to ensure not to miss a bad owner again.
I'm surprised, there's no /bin/sh for the backup:
/bin
# find /usr/TMP4
Ralf Mardorf wrote:
> On Tue, 29 Jan 2013 12:44:55 +0100, Erich Dollansky
> wrote:
>> It cannot get worse. His experience will show also others how robust
>> FreeBSD is in case of failures.
>
> Indeed. Linux users ask me why I play with FreeBSD. I already could make a
> list with drawbacks and a
hread regarding to
> this issue anymore. I'll continue with this thread "Re: How to fix a
> broken owner for files from world & build from ports?" if this should
> be ok for the list, if not I can be quiet, no hard feelings. The
> thread could easily be filtered
my guesses might be
wrong, since I'm a FreeBSD novice, so this list wouldn't be absolutely
correct.
Regarding to the annoyance, I won't switch the thread regarding to this
issue anymore. I'll continue with this thread "Re: How to fix a broken
owner for files from
Hi,
On Tue, 29 Jan 2013 10:08:20 +0100
Matthias Apitz wrote:
> El día Monday, January 28, 2013 a las 10:28:06PM -1000, parv escribió:
>
>
> In general, I find all this thread (wrong file owner) a bit boring.
I find it very interesting.
> This is a mayor damage and can only be repaired by a n
El día Tuesday, January 29, 2013 a las 12:23:09PM +0100, Ralf Mardorf escribió:
> On Tue, 2013-01-29 at 10:08 +0100, Matthias Apitz wrote:
> > This is a mayor damage and can only be repaired by a new installation.
>
> Perhaps true, but if such a simple mistake can't be fixed, what happens
> when
On Tue, 2013-01-29 at 10:08 +0100, Matthias Apitz wrote:
> This is a mayor damage and can only be repaired by a new installation.
Perhaps true, but if such a simple mistake can't be fixed, what happens
when somebody makes a big mistake? Perhaps more people stay with Linux
than other *NIX, regardin
On Mon, 2013-01-28 at 22:28 -1000, parv wrote:
> in message ,
> wrote Ralf Mardorf thusly...
> >
> > Hi :)
> >
> > I hope it's ok, when I open a new thread for this issue.
> > First I need to know what files have a bad owner.
> >
> > I'm running
> > # freebsd-update IDS >> outfile_28Jan2013.ids
> >
El día Monday, January 28, 2013 a las 10:28:06PM -1000, parv escribió:
> in message ,
> wrote Ralf Mardorf thusly...
> >
> > Hi :)
> >
> > I hope it's ok, when I open a new thread for this issue.
> > First I need to know what files have a bad owner.
> >
> > I'm running
> > # freebsd-update IDS >>
in message ,
wrote Ralf Mardorf thusly...
>
> Hi :)
>
> I hope it's ok, when I open a new thread for this issue.
> First I need to know what files have a bad owner.
>
> I'm running
> # freebsd-update IDS >> outfile_28Jan2013.ids
> perhaps this will give some useful output, regarding to a wrong owne
On Tue, 29 Jan 2013 04:19:08 +0100, Ralf Mardorf
wrote:
On Tue, 29 Jan 2013 04:15:17 +0100, Ralf Mardorf
wrote:
On Tue, 29 Jan 2013 04:04:21 +0100, Joshua Isom
wrote:
On 1/28/2013 8:54 PM, Ralf Mardorf wrote:
On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom
wrote:
On 1/28/2013 7:
On Tue, 29 Jan 2013 04:15:17 +0100, Ralf Mardorf
wrote:
On Tue, 29 Jan 2013 04:04:21 +0100, Joshua Isom wrote:
On 1/28/2013 8:54 PM, Ralf Mardorf wrote:
On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom
wrote:
On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
Still not perfect, I guess I need so
On Tue, 29 Jan 2013 04:04:21 +0100, Joshua Isom wrote:
On 1/28/2013 8:54 PM, Ralf Mardorf wrote:
On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom
wrote:
On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
Still not perfect, I guess I need something similar to ls -RAl for
some
directories :S and I di
On 1/28/2013 8:54 PM, Ralf Mardorf wrote:
On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom wrote:
On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
Still not perfect, I guess I need something similar to ls -RAl for some
directories :S and I didn't test what awk will do with names including a
space.
T
On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom wrote:
On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
Still not perfect, I guess I need something similar to ls -RAl for some
directories :S and I didn't test what awk will do with names including a
space.
Try `find /dir -ls`. You can pipe it into s
On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
Still not perfect, I guess I need something similar to ls -RAl for some
directories :S and I didn't test what awk will do with names including a
space.
Try `find /dir -ls`. You can pipe it into sed like this `find /dir -ls|
sed -e 's%/dir%%g'` and th
On Tue, 29 Jan 2013 02:21:55 +0100, Ralf Mardorf
wrote:
The output of "freebsd-update IDS >> outfile_28Jan2013.ids" is useless
for this purpose.
I now will do it like that:
root@freebsd:/mnt/dump/tmp # bzcat
../dump-9.1-RELEASE-20130123_193142-usr_f.dump | restore rf -
unfortunately i
The output of "freebsd-update IDS >> outfile_28Jan2013.ids" is useless for
this purpose.
I now will do it like that:
root@freebsd:/mnt/dump/tmp # bzcat
../dump-9.1-RELEASE-20130123_193142-usr_f.dump | restore rf -
unfortunately it happened:
/mnt/dump: write failed, file system is full
wri
On Mon, 28 Jan 2013 18:18:05 +0100, Ralf Mardorf wrote:
> I still have no idea how to check this for the files build from ports.
Are there _many_ on the list (rocketmouse:* in /usr/local)?
If not: A simple reinstallation of that port would be sufficient,
except you can easily spot the installatio
Hi :)
I hope it's ok, when I open a new thread for this issue.
First I need to know what files have a bad owner.
I'm running
# freebsd-update IDS >> outfile_28Jan2013.ids
perhaps this will give some useful output, regarding to a wrong owner for
files from world.
It's still running.
I still
26 matches
Mail list logo
