accessing jump drive in a console

Hannahpj · #1 20th December 2008, 09:36 PM

Hi everyone,

I'm trying to get comfortable with working in a terminal and it's going well. However, can someone please tell me how to access my jump (usb) drive in terminal? I can only get so close to it. If I navigate to /media, I can see 'USB DISK', but I can't do 'ls' to get to the files so I can open them in an editor like vi.

PabloTwo · #2 21st December 2008, 01:06 AM

Try: ls /media/USB\ DISK/

You have to 'escape' the SPACE character using the back slant.
Also, you can let the terminal help you with 'auto completion'.

Type: ls /media/USB

then hit the TAB key. It should complete using the back slant, space, and DISK/

Hannahpj · #3 21st December 2008, 01:55 AM

PabloTwo,

Thank you very much!!! I can now access all of my files and have learned something about using escape characters in a shell and the auto-completion. Again, thanks much for your help!

Hannahpj · #4 21st December 2008, 02:12 AM

PabloTwo,

now that I can get to my files, I found my .java files on my thumb drive. When I try to open TictacGame.java in the vi editor, I see no code but I know there's code in the file. It brings up a blank screen with 'TictacGame.java [New File]' at the bottom, uh, could you advise please, I'd be most grateful

PabloTwo · #5 21st December 2008, 10:00 PM

Are you giving vi the full path to the file? If the file you want to open in vi isn't in the current directory that you are in, then typing just "vi TictaGame.java" will open a new (blank) file with the name you gave it.

Try: vi /media/USB\ DISK/TictaGame.java

That assumes that the file you want to open and edit isn't in some sub directory of ..../USB\ DISK\. Or, you could first "cd" to that directory:

cd /media/USB\ DISK/
vi TictaGame.java

Also be very aware that Linux is case sensitive. And on the TAB auto completion thing, if there is more than one file or directory name that would match the text you had entered so far, you need to hit TAB twice. It will then show you all the choices you have.

If you haven't used vi before, be sure and read the manual first. "man vi" at the command prompt. You might want to start out with the "nano" text editor rather than "vi", as it's much simpler to figure out and use. vi is very powerful, but it has a somewhat steep learning curve.

Hannahpj · #6 22nd December 2008, 02:11 AM

thanks for your patience PabloTwo, I can get to all of my files, including the java ones, it wasn't working because I wasn't giving the full path, I'll also take your suggestion about the 'nano' editor. I started with vi because it was recommended as it's found on practically every unix and linux system. They told me if I learn it, I can pretty much rely on it being present if I ever have to work with other unix and linux based system.

sidebrnz · #7 22nd December 2008, 06:27 AM

What they tell you is true, but what they don't tell you is that, without a cheat sheet and a tutorial, it's very hard to learn. It was written back when all you had was either a teletype or a screen that imitated one, so it's basically what's called a "line editor." Very terse, no help function. Frankly, I'd not wish it on my worst enemy, but there are people who love it. That's one of the beauties of Linux: there are editors to fit anybody's taste.

Hannahpj · #8 23rd December 2008, 11:43 PM

I think I'll eventually come to really like the vi/vim editor. Yea, it's pretty cryptic but because it's on almost all unix based systems, I consider it most valuable to learn. I've started the built in tutor in Fedora 9 (vimtutor) and I plan to get the books the tutor recommends. If I force myself to do real work with it on a regular basis, even in small dosis, I'll learn it. After all, that's exactly how I had to ease into Linux from Windows and now I wouldn't go back.