Comments on: 10 FAQ After one Week on Linux http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/ It's as simple as 1, 2, 3... Mon, 19 Oct 2009 12:29:25 +0000 http://wordpress.com/ hourly 1 By: Recent Links Tagged With "fibonacci" - JabberTags http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-149 Recent Links Tagged With "fibonacci" - JabberTags Thu, 09 Oct 2008 19:49:49 +0000 http://168hours.wordpress.com/?p=127#comment-149 [...] public links >> fibonacci 10 FAQ After one Week on Linux Saved by HannahMontanaMody on Wed 08-10-2008 fibonacci garter stitch eyelet lace baby blanket [...] [...] public links >> fibonacci 10 FAQ After one Week on Linux Saved by HannahMontanaMody on Wed 08-10-2008 fibonacci garter stitch eyelet lace baby blanket [...]

]]> By: Davide Bolcioni http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-116 Davide Bolcioni Mon, 18 Aug 2008 11:48:52 +0000 http://168hours.wordpress.com/?p=127#comment-116 Clarification about #3 ... the .sh suffix (not extension, you can have multiple suffixes as in .tar.gz) is traditionally for shell fragments that are meant to be sourced, not executed. The .sh suffix tells "source me in sh(1)" while a .csh suffix would mean "source me in csh(1)" because the syntax of the respective shell is different so you would have to know ahead which is which. As a command is just executed according to the #! line at the top, no suffix is necessary for commands. Note that there is very little difference between a script and a binary, both are simply commands and most of the system treats them the same. Clarification about #3 … the .sh suffix (not extension, you can have multiple suffixes as in .tar.gz) is traditionally for shell fragments that are meant to be sourced, not executed. The .sh suffix tells “source me in sh(1)” while a .csh suffix would mean “source me in csh(1)” because the syntax of the respective shell is different so you would have to know ahead which is which.

As a command is just executed according to the #! line at the top, no suffix is necessary for commands. Note that there is very little difference between a script and a binary, both are simply commands and most of the system treats them the same.

]]> By: links for 2008-08-17 « My place http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-113 links for 2008-08-17 « My place Mon, 18 Aug 2008 03:08:38 +0000 http://168hours.wordpress.com/?p=127#comment-113 [...] 10 FAQ After one Week on Linux « Lists There are many cases when after looking at some of the FAQ on the web you ask yourself: “Are they for real? Who asks those questions anyway?” Questions like: “How Does Linux Kernel Versioning Work?” or “How much does Ubuntu cost?” don’t really provide you with the information you need. Mainly because they target a very specific kind of users. (tags: ubuntu linux faq) [...] [...] 10 FAQ After one Week on Linux « Lists There are many cases when after looking at some of the FAQ on the web you ask yourself: “Are they for real? Who asks those questions anyway?” Questions like: “How Does Linux Kernel Versioning Work?” or “How much does Ubuntu cost?” don’t really provide you with the information you need. Mainly because they target a very specific kind of users. (tags: ubuntu linux faq) [...]

]]> By: Penguin Pete http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-112 Penguin Pete Sun, 17 Aug 2008 20:10:51 +0000 http://168hours.wordpress.com/?p=127#comment-112 This is TERRIFIC! Consider yourself added to the sidebar of my blog. This is TERRIFIC! Consider yourself added to the sidebar of my blog.

]]> By: machinist http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-111 machinist Sun, 17 Aug 2008 19:28:17 +0000 http://168hours.wordpress.com/?p=127#comment-111 WRT uninstalling something compiled locally, standard practice (at least for me) is to pipe make install through tee and to a file (I do this for configure and make too). You then have a record of what went where, and can remove all traces if necessary. WRT uninstalling something compiled locally, standard practice (at least for me) is to pipe make install through tee and to a file (I do this for configure and make too). You then have a record of what went where, and can remove all traces if necessary.

]]> By: alucinor http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-110 alucinor Sun, 17 Aug 2008 18:15:35 +0000 http://168hours.wordpress.com/?p=127#comment-110 Program Files in Windows isn't even where all your "programs" are located anyways. There's programs in the c:\Windows and c:\Windows\System32 folders, there's program data in the registry, in c:\Program Data, in c:\Users\username\AppData\Local and c:\Users\username\AppData\Roaming, so Windows is pretty spread out too. Program Files in Windows isn’t even where all your “programs” are located anyways. There’s programs in the c:\Windows and c:\Windows\System32 folders, there’s program data in the registry, in c:\Program Data, in c:\Users\username\AppData\Local and c:\Users\username\AppData\Roaming, so Windows is pretty spread out too.

]]> By: 10 FAQ After one Week on Linux : HowtoMatrix http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-109 10 FAQ After one Week on Linux : HowtoMatrix Sun, 17 Aug 2008 17:44:52 +0000 http://168hours.wordpress.com/?p=127#comment-109 [...] Read more at Lists [...] [...] Read more at Lists [...]

]]> By: Jacob Helwig http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-107 Jacob Helwig Sun, 17 Aug 2008 04:54:55 +0000 http://168hours.wordpress.com/?p=127#comment-107 In #8, you forgot the ":" before "q!", and "wq". In #8, you forgot the “:” before “q!”, and “wq”.

]]> By: JJMacey http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-105 JJMacey Sat, 16 Aug 2008 23:18:43 +0000 http://168hours.wordpress.com/?p=127#comment-105 Hi All, Rather than make this soooo... complex grab a Linux Distro from Distrowatch, burn all that free goodness. Then just stare @ what you have there. BTW, I'd recommend downloading Ubuntu, openSuse11.0, and Linux Mint. You have a lot to stare @ there with those 3 simple CDs. Take a computer - and boot those live CDs. Scared - check out the Forums. When was this article written 1999? C'mon I smell something here. Terminal? Really. YaST or Synaptic the ideal solutions to adding about 35,000 applications. Run Linux, Run Free! JJMacey Phoenix, Arizona Hi All,

Rather than make this soooo… complex grab a Linux Distro from Distrowatch, burn all that free goodness. Then just stare @ what you have there. BTW, I’d recommend downloading Ubuntu, openSuse11.0, and Linux Mint. You have a lot to stare @ there with those 3 simple CDs.

Take a computer – and boot those live CDs. Scared – check out the Forums.

When was this article written 1999? C’mon I smell something here. Terminal? Really. YaST or Synaptic the ideal solutions to adding about 35,000 applications.

Run Linux, Run Free!

JJMacey
Phoenix, Arizona

]]> By: Mark http://168hours.wordpress.com/2008/08/14/10-faq-after-one-week-on-linux/#comment-103 Mark Sat, 16 Aug 2008 22:06:09 +0000 http://168hours.wordpress.com/?p=127#comment-103 A comment about "bar" and "foo" from a programming perspective. These two are commonly used in programming examples because it's assumed no software programmer in their right mind would use ridiculous variable names like those in real software. This way you can show some code and any developer looking at it immediately knows "hey, this is an example". It also flags something as being completely generic since in actual well-written code variable names should convey some meaning but foo/bar are meaningless. A comment about “bar” and “foo” from a programming perspective. These two are commonly used in programming examples because it’s assumed no software programmer in their right mind would use ridiculous variable names like those in real software. This way you can show some code and any developer looking at it immediately knows “hey, this is an example”. It also flags something as being completely generic since in actual well-written code variable names should convey some meaning but foo/bar are meaningless.

]]>