Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
If you are using bash, edit your ~/.bashrc file and add one alias per line. Once you save and close the file, run this to load your new aliases immediately:Alias's are like dos macro's right?
do I need to put my alias in a bash file to run at startup in order to make them work?
I've never used a version of MS/PC-DOS that actually required any filename extension, much less a full 3 characters.*nix has never used 'extensions' as in the DOS/windows world. UNIX and its offspring actually determine a file's type based on its contents, NOT on its 'extension.'
The reason I keep putting 'extension' in quotes is because in *nix there really is no such thing as a file extension. Back in the DOS 8.3 (file names limited to 8 characters, plus a MANDATORY dot-plus-3-character extension), in UNIX we had no such ridiculous limitations.
One thing that you can do that will also help support the development of the FOSS that you enjoy is to order the physical discs to be delivered to you. Doing it this way provides a tiny bit of financial support to these people who often work for free on this stuff, and may end up getting you your software faster than possible by using a slow Internet connection. I used to do that before I got my first DSL circuit.Ubuntu isn't the download i worry about. i only have 128K down and maybe .5K up. it's slow. it was a rather long download on cable at my mom's house. my speed is roughly half that of DSL and 1/3 that of cable. i live in a trailer in the woods, it's a wireless system and i cannot get any faster speed.
First, you must get out of your head the [idiotic] micro$oft way of doing things. Read some of my other comments in this thread about file 'extensions' and how they're basically meaningless in UNIX/Linux.Was asked to associate a program with opening a file. I wanted FX to open it, but FX wasn't in the choice box. What do I use to associate with? In Windows it would be FX.ex- (left the last e off) What's operative in Ubuntu? Still running 11.04, will be changing to Mint, soon.
I understood that DOS couldn't *do* anything with a file unless it had an appropriate extension. For example, a 'batch' file couldn't be executed unless it had a .bat extension, a compiled program couldn't run unless it had .exe as its extension, a JPEG couldn't be displayed unless it had .jpg as its extension, etc. So you're saying this was NOT the case?I've never used a version of MS/PC-DOS that actually required any filename extension, much less a full 3 characters.
The filesystems for earlier versions of UNIX
Hi, another question. when using my Toshiba (ubuntu plus kde) it seems to be a pain to boot up. today i put it in place my the Acer (it died, so i tossed it--was on its last legs anyway--keyboard didn't even work!) and first boot it locked up. second boot it got to KDE then froze. third boot it got stuck in an fsck loop (scanned, fixed errors, reboot, repeat cycle) and the fourth time it froze again, fifth time it finally got in, and worked fine. still works fine. this glitch happened last time too, the fsck loop at least. not sure what is going on. it claims the file system was unclean even though i did a proper shut down prior. also, if i let it try booting with the Kubuntu logo, it freezes during the boot process. i have to hit the 'esc' key to show verbose mode before it will work.
never runs out of RAM, perhaps i should just get into the habit of hibernating it instead of shutting it down?
I'd suggest first looking at the options for mv:lets say i want to move a large amount of folders and files over from one drive to another drive. besides the obvious drag and drop what would be the best way to do this in CLI? would it be to use the mv command and if so what would be the recommended way?
man mv
For the sake of clarity and continuity, let's go back to what I was replying to:I understood that DOS couldn't *do* anything with a file unless it had an appropriate extension. For example, a 'batch' file couldn't be executed unless it had a .bat extension, a compiled program couldn't run unless it had .exe as its extension, a JPEG couldn't be displayed unless it had .jpg as its extension, etc. So you're saying this was NOT the case?
Note that the post "shouted" things like "MANDATORY" that simply aren't true. I was just providing the correct information.*nix has never used 'extensions' as in the DOS/windows world. UNIX and its offspring actually determine a file's type based on its contents, NOT on its 'extension.'
The reason I keep putting 'extension' in quotes is because in *nix there really is no such thing as a file extension. Back in the DOS 8.3 (file names limited to 8 characters, plus a MANDATORY dot-plus-3-character extension), in UNIX we had no such ridiculous limitations. If I wanted to name something my.file.for.work, so be it. The dots were, and are, nothing but characters, like any other standard character. They didn't, and don't, dictate a file's type. *nix basically evolved over the years to accommodate windows users who thought of files as having extensions to dictate what they were.
Don't believe me? Do this: Let's say you have a JPEG file that's named your_pretty_sunset.jpg. Rename it simply your_pretty_sunset. Then fire up your preferred file manager (I use Dolphin), and watch it display the file's preview. Do the same on a windows box and what will happen? Nothing. Without the .jpg extension, it won't recognize it as a JPEG file.
I hope I'm not putting words in Speed's mouth, but I think the point being made is that by ordering discs you're helping [in a small way] to financially support the software you're using. And, of course, getting discs so you don't have to bother with a long download.if i wanted to wait for a few days to have discs delivered then i would not be concerned with an 8 hour download...
One practice that I often preach but don't practice myself is to keep the source file(s) until you're sure that they all made it to their destination intact. So instead of mv, you might do a cp, check to see that the files are there, and then rm the source files. This takes longer and requires more disk space (which may be a problem if your reason to move the files is a full disk). But it's the safest way to do it.lets say i want to move a large amount of folders and files over from one drive to another drive. besides the obvious drag and drop what would be the best way to do this in CLI? would it be to use the mv command and if so what would be the recommended way?
Speed, I respect you too much to want to get into anything ugly.For the sake of clarity and continuity, let's go back to what I was replying to:
<< snip >>
Yes, that and the fact that spending many hours trying to download a large ISO image, only to find that it doesn't work is no fun at all. IME a single disc sent by First Class mail takes 2 days to arrive, which can be faster than several download attempts. And you get a nice silk screened disk to boot!I hope I'm not putting words in Speed's mouth, but I think the point being made is that by ordering discs you're helping [in a small way] to financially support the software you're using. And, of course, getting discs so you don't have to bother with a long download.
I feel the same way. Thanks.Speed, I respect you too much to want to get into anything ugly.
Did you know that you can get a `file' command for DOS and Windows? No it's not provided by default from Microsoft. But by the same token, the `file' utility isn't necessarily installed by default. And in the case of Linux, `file' is one of the many utilities supplied by GNU and other sources.So I'm going to wrap this up with this: If you do what I suggested, i.e., use the file command on a file with *NO* extension, you'll see that *nix accurately analyzes the type of file; I do not believe that any m$ OS has ever been able to do that.
Yes, Microsoft operating systems require file extensions for a file to be executable, just like UNIXI also believe that m$ OSes cannot do anything with a file if it doesn't have an extension telling it what to do. So by "mandatory" I guess I really meant that an extension was mandatory *IF* you wanted to do anything with the file, like execute it.
How 'bout we mutually agree to drop this, and get back to discussing Linux topics in this thread? :shakehands:I feel the same way. Thanks.
Works for me!How 'bout we mutually agree to drop this, and get back to discussing Linux topics in this thread? :shakehands: