Quote:
Originally posted by cuckoopint
btw, I recommend changing that 'track*.wav' to something a little more permanent, if this is only referring to one directory (ie. ~/wav/track*.wav) This helps since you can execute the alias from any directory. OTOH, track*.wav would make it universal to all directories you may be working with. Your call.
; )
|
Here's the whole story- I have a 166Mhz w/ 80M -15G SCSI & SCSI cdrw. I want to make a network cdburning machine. Preferrably each user could ssh in, , copy whatever files you want (data, audio, video) into /users/own/dir then cd /users/own/dir and do a
burnw. BUT I think I understand what you mean. You could change it so that you could execute it from any directory AND I could just burn everything in the directory instead of specifying .wav .mp3 etc. Oh and it just now hit me- I could really simplify copying files to /users/own/dir too!
I have windows users on the network who are scared of Linux. I suppose this is my way of forcing them to use it
! heh heh :P
Thanks for the quick how-to cuckoopint. Am I to understand that I could make hundreds, nay thousands of aliases this way?? bwaahaaha ; ) what fun I'll have.