Top products from r/unix

First, you need to learn cd ls. And the UNIX filesystem. Here is a PDF for the filesystem. You need to know this: http://www.pathname.com/fhs/pub/fhs-2.3.pdf

cd is a shell command, not a program. It changes your current working directory. This is what you use like Windows Explorer or OS X Finder. When you login, you will start at /home/USERNAME. To see all of the users on the system's home directories do:

cd ..
ls

Odds are there aren't many users besides you. If you login as root (not advised, especially at first). Root's home directory is /root.

Some things to learn are how a Linux system starts. Unfortunately if you are using a newer Debian 8, it uses systemd which is much a much more complex booting system than previous versions. Honestly, I would recommend installing Debian 7 and learn how it starts, then move to Debian 8. systemd is new and a bit controversial because it is not very "unixy".

The reason I mention systemd, is that it is the first "user space" process that runs when linux starts. The older mechanism is called init.

The reason that I say go with the older system is because it uses a series of shell scripts which is a text file filled with various commands to get things started. This is a good place to learn how things are done when starting out. systemd is a very big and complex system that I believe is too complicated to start with, but it's good to learn eventually.

If all this is too much at first, install a very base system. Then go to /usr/bin and read the man page for each command. To read a man page, do man COMMAND_NAME. Sometimes, you may need to do man 1 COMMAND_NAME as the /usr/bin/ commands are in section 1 of the UNIX manual. To quit viewing the page, press q. You can use the up and down arrows and space to navigate like a web page. You can also use j for down and k to go up.

I would also suggest a book. I started out with http://www.amazon.com/UNIX-Impatient-Edition-Paul-Abrahams/dp/0201823764 It's $20 or so dollars. If you don't have the money, PM me and I'll buy it for you.

Learn the shell. Bash is a good enough one. zsh is very cool as well.

Oh, it's probably worth noting that UNIX is a multi user system, where root is "God" of the system. Root can do basically anything, and the other users have less permissions to do things. I would recommend using a real user at first, to learn the differences.

Linux is really fun. It has a very steep learning curve because it is so complex and powerful, and that power is why it has been #1 is doing stuff like powering the internet, being used for wifi routers, and it is the basis of over 90% of all cellphones as well. UNIX has evolved to be basically Linux nowadays. There are some commercial UNIXes left, but Linux is good enough.

Keep posting here if

Sorry: a bare license is revocable in the USA; Yes you can.
Oh and obeying a pre-existing legal duty is not valid consideration either. Sorry.

( https://www.amazon.com/Open-Source-Licensing-Software-Intellectual/dp/0131487876 )

>p46 "As long as the project continues to honor the terms of the licenses under which it recieved contributions, the licenses continue in effect. There is one important caveat: Even a perpetual license can be revoked. See the discussion of bare licenses and contracts in Chapter 4"
--Lawrence Rosen

>p56 "A third problem with bare licenses is that they may be revocable by the licensor. Specifically, /a license not coupled with an interest may be revoked./ The term /interest/ in this context usually means the payment of some royalty or license fee, but there are other more complicated ways to satisfy the interest requirement. For example, a licensee can demonstrate that he or she has paid some consideration-a contract law term not found in copyright or patent law-in order to avoid revocation. Or a licensee may claim that he or she relied on the software licensed under an open source license and now is dependent upon that software, but this contract law concept, called promissory estoppel, is both difficult to prove and unreliable in court tests. (The concepts of /consideration/ and /promissory estoppel/ are explained more fully in the next section.) Unless the courts allow us to apply these contract law principles to a license, we are faced with a bare license that is revocable.
--Lawrence Rosen

>p278 "Notice that in a copyright dispute over a bare license, the plaintiff will almost certainly be the copyright owner. If a licensee were foolish enough to sue to enforce the terms and conditions of the license, the licensor can simply revoke the bare license, thus ending the dispute. Remeber that a bare license in the absence of an interest is revocable."
--Lawrence Rosen

Lawrence Rosen - Open Source Licensing - Sofware Freedom and Intellectual property Law



>p65 "Of all the licenses descibed in this book, only the GPL makes the explicity point that it wants nothing of /acceptance/ of /consideration/:
>...
>The GPL authors intend that it not be treated as a contract. I will say much more about this license and these two provisions in Chapter 6. For now, I simply point out that the GPL licensors are in essentially the same situation as other open source licensors who cannot prove offer, acceptance, or consideration. There is no contract."
--Lawrence Rosen

----
>David McGowan, Professor of Law, University of Minnesota Law School:

>"Termination of rights

>[...] The most plausible assumption is that a developer who releases code under the GPL may terminate GPL rights, probably at will.

>[...] My point is not that termination is a great risk, it is that it is not recognized as a risk even though it is probably relevant to commercial end-users, accustomed to having contractual rights they can enforce themselves.

The approach I took is to start with commands and languages using regular expressions: find, grep, sed, awk, python or perl, etc. These are very powerful and useful commands.

Two books I highly recommend are [Unix Shells by Example] (http://www.amazon.com/UNIX-Shells-Example-4th-Edition/dp/013147572X/ref=sr_1_1?ie=UTF8&qid=1374157897&sr=8-1&keywords=unix+shells) and [A Practical Guide to Linux] (http://www.amazon.com/Practical-Guide-Commands-Editors-Programming/dp/013308504X/ref=sr_1_1?s=books&ie=UTF8&qid=1374157979&sr=1-1&keywords=practical+guide+to+linux)

Also check out (PDF warning!) [Advanced Bash Guide] (www.tldp.org/LDP/abs/abs-guide.pdf)

These all are excellent, and very useful.

This is a good book. You should supplement it with something like this because one of the big things about UNIX (and its derivitives) is the underlying philosophies around processes, files, and CLI tools.

I would heartily suggest putting linux on a PC (any old PC from the last decade will do, honestly) and learn by playing around on it. Ubuntu, Fedora, any free version will do. You could also do this in a VM on your windows or mac.

For those pushing OSX -- yeah, it's got UNIX/BSD under the covers but there are also a lot of differences you have to dig under to get to a "plain" UNIX environment with X11 etc. (I've been playing with UNIX on mac since the Mac II, understand this isn't linux prejudice talking). It'll be a lot easier to install a linux variant fresh somewhere.

I am reading the first edition now and it is really good so it can't hurt. It is a great into, and a good reference even for people who know what they are doing.

I am also reading this for school as well http://www.amazon.com/Practical-Guide-Fedora-Enterprise-Edition/dp/0133477436/ref=pd_sim_14_2?ie=UTF8&dpID=517h5KJOQVL&dpSrc=sims&preST=_AC_UL160_SR129%2C160_&refRID=0T274B6GDEYV9EQ9WGSG but I hear http://www.amazon.com/Practical-Commands-Editors-Programming-Edition/dp/013308504X isn't bad either

If you're looking for a book I highly recommend Unix Shells by Example:

http://www.amazon.com/UNIX-Shells-Example-4th-Edition/dp/013147572X/ref=la_B001H9RV1E_1_2?ie=UTF8&qid=1346897356&sr=1-2

I like it because it's light on the banter and explanation that's so common with tech books, and heavy on the examples. It's had a permanent spot on my work bookshelf for the last 10 years

1. use VirtualBox
   
2. Consider OpenBSD, it's sweet
   
3. read The Art of Unix Programming http://www.catb.org/esr/writings/taoup/
   
4. read this too, for sysadmin tasks: https://www.amazon.ca/UNIX-Linux-System-Administration-Handbook/dp/0131480057

Man that looks familiar so I want to say yes. It reminds me of this: https://www.amazon.com/Tricks-Unix-Masters-Waite-Group/dp/0672224496 which I still have on my bookshelf (but haven't opened in many years).

You have everything you need with the answers you've received so far. Pick yourself up a copy of "The Pirate Book" if you're interested in furthering your Linux knowledge in the future.

https://www.amazon.com/UNIX-Linux-System-Administration-Handbook/dp/0131480057/

Think Unix is the book I started with. It's works as a grammar book would teach you how to string together words to complete a thought. It was an enjoyable read and started me on the road to Unix over a decade ago.

I leant it to someone and never got my original copy back. I need to order another...

I just have a copy of Kernighan & Pike's Unix Programming Environment for my 1 year old. He seems to like it as much as the other books he has.

It seems that your comment contains 1 or more links that are hard to tap for mobile users.
I will extend those so they're easier for our sausage fingers to click!


Here is link number 1 - Previous text "K&R"



----
^Please ^PM ^/u/eganwall ^with ^issues ^or ^feedback! ^| ^Delete

If you're new to C, read K&R.

Once you've done that (or if you already know C) then read THE book on Unix programming

What are your credentials? Why should we read your guide instead of any other guide available (yes I know half of those are for Linux, not Unix)? Also, a guide to an OS family probably shouldn't include anectodes about college experience.

For administration, read:

https://www.amazon.com/UNIX-Linux-System-Administration-Handbook/dp/0131480057

For programming, read:

https://www.amazon.com/gp/product/0321637739/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

This is your new bible:


https://www.amazon.com/Programming-Language-2nd-Brian-Kernighan/dp/0131103628

​

​

I've been using so many CLI apps from Brew and an SSH headless Raspbian setup so these decals felt appropriate.

Rainbow Apple decal

Linux Tux decal

Is that why his paper refuting the idea that the GPL is revocable has not materialized in 6 months?

​

Is Moglen more learned about the law than Lawrence Rosen, Sapna Kumar, and David McGowan?

​

https://scholarship.law.duke.edu/faculty_scholarship/1857/

https://www.amazon.com/Open-Source-Licensing-Software-Intellectual/dp/0131487876

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=243237

​

It's always argument from ignorance with you people.

​

Tell me where is the promised paper from Moglen refuting the above? Tell me. Why did it never materialize?

​

TELL ME YOU FUCKING PIECE OF SHIT.

​

I need you to inform me, how obeying a pre-existing legal duty is valid consideration. Tell me. Explain it. I need you to inform me how NOTHING:ZERO:FREE is valid consideration. Can you. I need you to enlighten me as to how Illusory Promises are now enforceable suddenly in the USA.