Linux has many flavours; I use Ubuntu. I’m told that some more elite Linux users find Ubuntu “too easy to use – anyone<\/em> can use it.” (I’m sure the Ubuntu developers are only too happy to hear such criticism.)<\/p>\n Although Ubuntu has a very user-friendly desktop, it also has the terminal. The highbrow might be more comfortable there. It’s the context I’m using today, because so far as I know, the terminal is common to all Linux users.<\/p>\n Let’s imagine you’ve just finished a program called prog0.txt<\/span>, which you’ve saved in your scripts<\/span> directory. You’ve tested it and you’re very pleased. Naturally, you want to safeguard it from impetuous changes.<\/p>\n Here’s how you can set it read-only:<\/p>\n On Linux, the text editor I use is gedit<\/strong>. When I open a read-only file in gedit<\/strong>, no indication appears that the file is read only. However, when I try to make a change to the file, a read-only message appears across the top. If I try to save any changes, I am forced to save them under a different file name.<\/p>\n Besides this simple use, the chmod<\/span> command has other capabilities. I’ll be covering some of them in future posts:)<\/p>\n Source:<\/em><\/p>\n McGrath, Mike. Linux in easy steps.<\/u> Southam: Computer Step, 2008.<\/p>\n
\nIn yesterday’s post<\/a> I explained a way to set a file read-only in Windows. Today, I do so for a Linux system.<\/p>\n\n