Re: wildcards and NFS...

2007-10-26 Thread David Brodbeck
On Oct 26, 2007, at 4:20 AM, Steve Kemp wrote: On Fri Oct 26, 2007 at 13:01:39 +0200, Bruno Boettcher wrote: so i added the following line to the /etc/exports /home/bboett/mp3/ 192.168.0.*(ro,insecure,root_squash,subtree_check) I do this just fine with: /mnt/mp3 192.168.1.0/255.255.255

Re: wildcards and NFS...

2007-10-26 Thread Steve Kemp
On Fri Oct 26, 2007 at 13:01:39 +0200, Bruno Boettcher wrote: > so i added the following line to the /etc/exports > /home/bboett/mp3/ 192.168.0.*(ro,insecure,root_squash,subtree_check) I do this just fine with: /mnt/mp3 192.168.1.0/255.255.255.0 (rw,sync,no_root_squash) Steve -- # The Debi

Re: wildcards and NFS...

2007-10-26 Thread Owen Townend
Hey, Try using this notation instead: /home/bboett/mp3/ 192.168.0.0/24 (ro,insecure,root_squash,subtree_check) cheers, Owen. On Fri, 2007-10-26 at 13:01 +0200, Bruno Boettcher wrote: > hello > > want to dispatch music from one computer through my house so i exported > the mp3 directory by nfs. >

Re: Wildcards

1998-06-08 Thread Nathan E Norman
On Mon, 8 Jun 1998 [EMAIL PROTECTED] wrote: : One last question! :). : If I want to keep a particular directory, and all files and : subdirectories completly private to my user, how do I do apply the : suggested filters to this? (If I do chmod 600 * -R or something, it will set all : the

Re: Wildcards

1998-06-08 Thread timothy
One last question! :). If I want to keep a particular directory, and all files and subdirectories completly private to my user, how do I do apply the suggested filters to this? (If I do chmod 600 * -R or something, it will set all the files correctly, but then since the directories don't ha

Re: Wildcards

1998-06-08 Thread servis
On 8 Jun, [EMAIL PROTECTED] wrote: > Thanks for everyone's help. > One more question that I couldn't find when I browsed the man pages. > What does the '$' mean/do in "grep "/$""? > and what does the '^' mean/do in "grep "^d""? >From 'man grep', lines 220-222: The caret ^ and the dollar s

Re: Wildcards

1998-06-08 Thread Steve Mayer
Timothy, The two symbols that you are asking about are parts of a "regular expression" search. The $ is telling grep to search for something at the end of a string. Therefore, "/$" is looking for a / (forward slash) as the last character in a string, (i.e. the ending slash on a directory entr

Re: Wildcards

1998-06-08 Thread timothy
Thanks for everyone's help. One more question that I couldn't find when I browsed the man pages. What does the '$' mean/do in "grep "/$""? and what does the '^' mean/do in "grep "^d""? Thanks, Timothy On 08-Jun-98 David Lauder wrote: > For directories, try: > > ls -lF | grep "/$" > or: >

Re: Wildcards

1998-06-08 Thread Bruce Mardle
> Is there a wildcard type thing to indicate all directories, or all > files etc? Like "dir /ad" in dos. And is there anything as cool as a wildcard > for file modes like all executeables? Use zsh and that would be "*(/)" and "*(*)", so the equivalent of "dir /ad" would be "ls -d *(/)".

Re: Wildcards

1998-06-08 Thread Tim Buller
On Sun, 7 Jun 1998 [EMAIL PROTECTED] wrote: > Is there a wildcard type thing to indicate all directories, or all > files etc? Like "dir /ad" in dos. I'm not sure what 'dir /ad' does. You can show all files (including those that start with ".") with 'ls -a'. Type 'ls --help' or 'man ls' f