On Thu, 21 Oct 2010, Daniel Pittman wrote:
> Probably a good time to transition to the glorious new world of stable
> device identifiers under /dev/disk, which saves you the pain of learning
> that "mostly stable" doesn't count in the new hotplug order.
>
> All bow down before your new udev master
Rich Shepard writes:
> On Fri, 8 Oct 2010, Rich Shepard wrote:
[...]
> After re-installing Slackware-13.0 a few times, everything but firefox is
> running. Soon I'll get up the courage to upgrade to -13.1 which changes all
> the ATA drive designations from hd* to sd* and alters all the IDs of th
On Fri, 8 Oct 2010, Rich Shepard wrote:
> This morning's report on the dirvish backup reported errors of files being
> removed before they could be backed up. This in a directory that I've not
> accessed for several years so nothing should have changed any files there.
> As a matter of fact, I'v
On Fri, Oct 8, 2010 at 08:39, Fred James wrote:
>
> As mentioned in a post by Ewan, it may be something that needs the
> application of 'fsck', in which case the procedure above may get ride of
> th file(s), but not the problem?
+1 for all of this.
so, make sure you check dmesg before the reboot
Michael Rasmussen wrote:
> On Fri, Oct 08, 2010 at 09:09:46AM -0500, Fred James wrote:
>
>> Rich Shepard
>> One way would be to ...
>> (a) cp all files except the 'unwanted' ones to a new (temporary)
>> directory outside of their current directory
>> (b) rm -rf the directory in which th
On Fri, 8 Oct 2010, Michael Ewan wrote:
> Unmount and fsck.
Michael,
I think this is what needs to be done. I cannot delete the directory when
it contains only these strange files.
This weekend. It's supposed to rain, I've mowed the yard and trimmed the
trees, and I need to upgrade the OS
On Fri, 8 Oct 2010, Michael Ewan wrote:
> What file system is this?
reiser4
Rich
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On 10/8/2010 7:55 AM, Rich Shepard wrote:
> On Fri, 8 Oct 2010, Paul Heinlein wrote:
>
>> Or, if the file has bizarre characters in its name that confuse rm,
>>
>>find . -inum 123456 -exec rm -- '{}' \;
>
> Paul,
>
> Same as above: can't find the file.
>
> Thanks,
>
> Rich
Unmount and fsck
On Fri, Oct 08, 2010 at 09:09:46AM -0500, Fred James wrote:
> Rich Shepard
> One way would be to ...
> (a) cp all files except the 'unwanted' ones to a new (temporary)
> directory outside of their current directory
> (b) rm -rf the directory in which the 'unwanted' files reside
> (c) m
Rich Shepard wrote:
>This morning's report on the dirvish backup reported errors of files being
> removed before they could be backed up. This in a directory that I've not
> accessed for several years so nothing should have changed any files there.
> As a matter of fact, I've done nothing in th
On Fri, 8 Oct 2010, Paul Heinlein wrote:
> Or, if the file has bizarre characters in its name that confuse rm,
>
> find . -inum 123456 -exec rm -- '{}' \;
Paul,
Same as above: can't find the file.
Thanks,
Rich
___
PLUG mailing list
PLUG@lists.pd
On Fri, 8 Oct 2010, Paul Heinlein wrote:
> You might try deleting it by inode number:
>
> # get the file's inode (e.g., 123456)
> ls -i
> # delete file by inode number
> find . -inum 123456 -exec rm {} \;
Darn! It tells me that all those files (when I ask specifically for one
inode) that, "fin
On Fri, 8 Oct 2010, Paul Heinlein wrote:
> You might try deleting it by inode number:
>
> # get the file's inode (e.g., 123456)
> ls -i
> # delete file by inode number
> find . -inum 123456 -exec rm {} \;
Or, if the file has bizarre characters in its name that confuse rm,
find . -inum 123456
On Fri, 8 Oct 2010, Rich Shepard wrote:
> This morning's report on the dirvish backup reported errors of
> files being removed before they could be backed up. This in a
> directory that I've not accessed for several years so nothing should
> have changed any files there. As a matter of fact,
This morning's report on the dirvish backup reported errors of files being
removed before they could be backed up. This in a directory that I've not
accessed for several years so nothing should have changed any files there.
As a matter of fact, I've done nothing in that partition recently.
A
15 matches
Mail list logo
