said by jdong :

oh, so slocate is sgid/suid?

$ ls -ld `which slocate`
-rwxr-sr-x  1 root slocate 26388 Apr 16  2004 /usr/bin/slocate

said by ghost16825 :

Of course this requires your message to be in message.txt. I'm sure someone can find a method without having to invoke cat at all.

said by deblin :

Ok, we're getting a bit carried away now

said by steve1515 :

Ya, it only resolves each found IP once since each key in the hash is unique.

I'm also thinking that there is a simpler way than using dig...Maybe some built in perl resolving function, but I don't know what it is.

sub iptoname {
        my ($ip) = @_;
        my (@list, $packed, @info, $hostname);
        @list = split(/\./,$ip);
        $packad = pack("C4",@list);
        if (@info = gethostbyaddr($packad,2)) {
                $hostname = $info[0];
        } else {
                $hostname = "";
        }
        $hostname;
}

said by wizard_ct :

Building on the split tip earlier, I'm sure the benefits of tarring to small chunks is obvious - burning to dvds, copying to a FAT partition (2gb limit) - what have you. Here's how to do it:

tar -cvf - /home/dirToBackup | split -b 1000m - backup-09-06-2005

Allows you to tar a directory to chunks in place, without needing to create the massive one first. This saves a ton of space.

Of course customize tar params and and split size to taste.

Use cat to recover on the other end.

cat backup-09-06-2005a? > backup.tar

You could easily do this in place as well if you needed.

said by Steve :

said by somebody quoted by paul1238 :

---

Some no0bs don't understand the number system that is associated with files and directories.

---

Neither the n00bs nor anybody else should fool with the numbers: it's difficult and often dangerous. Much better is to use the symbolic permissions, which are much less subject to surprises.

Symbolic permissions with chmod are a list of "sets", each of which is

scope
operation
permissions

"scope" is one or more of:

•u = user (the owner of the file)•g = group•o = other•a = same as ugo

"operation" is one of

•+ add the permissions to existing ones•- subtract the permissions to existing ones•= set the permissions absolutely

"permissions" is one or more or

•r read permissions•w write permissions•x execute permissions

(yes, there are other permissions, such as sticky bit and setuid, but that's all in the man pages).

By stringing these together you can do what you want:

chmod a+r * - make all files readable

Because these permissions are relative, they don't destroy existing permission bits that you don't care about. There is no single numeric mode that would do this because no matter what you pick, it's going to muck with the (for instance) execute bits that you don't really want to. This means that you'll end up with directories that you can't get to any more.

Even when you do want to set hardcode permissions, do it with the symbolic mods:

chmod a=rwx * - same as chmod 777
chmod og= * - take away *everything* from others and group, but not touching "user" permissions

I cannot think of a downsize of the symbolic permissions, but I sure as hell can with the numbers.

Steve