NewbieKwikis
Here are some kwikis for people that are new to Linux.
So what's a "newbie"?
In short, someone "new" to some topic or area of interest. For ArchLUG, this means Linux.
See Newbie.
For the "official" definition, or as official as computer slang can get, see the "Jargon File", maintained by the illustrious WikiWikiWeb : EricRaymond at http://www.catb.org/~esr/jargon/. It is also referred to by it's print version (or dead-tree version as "The New Hackers Dictionary". The 4.0.0 version was published in September 1996 as the third edition of The New Hacker's Dictionary from MIT Press (ISBN 0-262-68092-0).
There is a more useful HTML version using "frames" at http://www.catb.org/~esr/jargon/html/frames.html.
Getting Started with GNU/Linux
This excellent tutorial/guide was written by some of our friends in the Free Software Club of Kirksville (FSCK):
The even more famous RUTE User's Tutorial and Exposition can be found here:
Basic Linux Training Course
The Basic Linux Training Course (http://www.basiclinux.net/) is an eight week, introductory level course written specifically for those coming from a DOS/Windows background, without any knowledge of Unix or programming. The course is vendor and distribution neutral, and is designed around the initial installation and configuration.
The mailing list for the course requires that posts be on the topic of the lessons. The list is restricted to those enrolled in the course and is moderated.
New terms begin the first Monday of ever other month - January, March, May, July, September, and November.
Q: Why do I have to do all this "root" or "administrator" and then the "user" business when, in Wimdows....I could just turn the computer on and get going? A1: The simple answer is security...Banks use Unix...banks like security...you should too...Windows actually lets you have the option of "doing the user thing" but, because it is harder to do other stuff...like show you nice flash advertisings....that has never been a big issue with Windows...by putting the important stuff(like your OS!) in "root, or administrator" and your "other" stuff in user...if you do get pounced on by a hacker at least SOME of your stuff is safe...it might take a few times of "logging in" to "administrator" for you to get used to it....but when you hear your friend complaining about having to take his computer to have "stuff" removed and maybe a reinstall....you'll thank the inventor of..."root"..
Q: I am trying to write a one-liner to change the file permissions of a bunch of files at once. I've got this:
for i in $(find -iname desktop.ini); do chmod g+x "$i"; done
Unfortunately, 'find -iname desktop.ini' gives me output like:
.../victim/Start Menu/Programs/Startup/desktop.ini ...
What happens is that it tries to do:
chmod g+x ".../victim/Start" chmod g+x "Menu/Programs/Startup/desktop.ini"
which is not at all what I want it to do. Can anyone help?
A1: The problem is the whitespace and the command line argument parsing by the shell. Try this instead:
find . -iname desktop.ini -print0 | xargs -0 chmod g+x
Note that the -print0 and xargs -0 features are GNU/Linux-specific. Other operating systems (e.g. Solaris) may not implement them.
A2: On operating systems that don't offer the -print0 and xargs -0 extension, this seems to work:
find . -iname desktop.ini | sed -e 's/ /\\ /g' | xargs chmod g+x
The sed command adds backslashes to escape the spaces.
A3: Use a while loop with read, although this may be much slower than xargs especially with large numbers of files:
find . -iname desktop.ini | while read name ; do chmod g+x "$name"; done
A4: Almost as slow in performance as the previous answer, from reading the manual page for the 'find' command, one can make use of the '-exec' option to (surprisingly) execute an arbitrary command, such as 'chmod' in our case.
find . -iname desktop.ini -exec chmod g+x \{} \;
Hopefully, some kind WikiGnome will refactor all of this to our LinuxByExample page for the find command.
|
|