Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ive read lots of threads and HowTo's on this topic but they are either not for my OS or Im just to new to this to understand (probably more the latter).
Ive plugged my USB memory stick (MSI 256 mega stick) into the port on the front panel. On its screen ready is displayed.
I have Fedora Core 2 kernel release 2.6.5-1.358smp and a Foxconn motherboard.
In XP the stick is automatically detected but not in FC2
What do I have to do to transfer files to and from it? I really want to be able to do this so I don't have to go back to W****** or partition my drive which might not be possible because I have a Seagate serial HHD and I had trouble trying to get W****** to install on it (No trouble with Linux though).
open a console, plug in the usb-stick and type:
- dmesg
you should see something like this:
usb 1-1.1: new full speed USB device using address 5
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: SOMEUSBDEVICE FROM SOMEVENDOR
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
USB Mass Storage device found at 5
SCSI device sda: 256001 512-byte hdwr sectors (131 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
That was so interesting all sorts of great info came up about my system im lucky ive been reading some stuff cause I only just learnt how to open a console in the Terminal or that there was even a difference. Here is the bottom part of my log. Also I tryed to type the - in the comand you told me to enter so I was lucky to get it to go at all now what do I do next
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 4-2: USB disconnect, address 2
usb 4-2: new full speed USB device using address 3
scsi3 : SCSI emulation for USB Mass Storage devices
Vendor: MSI Model: MS-551X Rev: 0100
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 503552 512-byte hdwr sectors (258 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
sdb: sdb1
Attached scsi removable disk sdb at scsi3, channel 0, id 0, lun 0
USB Mass Storage device found at 3
atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0x88 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
usb 4-2: USB disconnect, address 3
usb 4-2: new full speed USB device using address 4
scsi4 : SCSI emulation for USB Mass Storage devices
Vendor: MSI Model: MS-551X Rev: 0100
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 503552 512-byte hdwr sectors (258 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
sdb: sdb1
Attached scsi removable disk sdb at scsi4, channel 0, id 0, lun 0
USB Mass Storage device found at 4
open a console and become root with:
su -l
(enter the password)
goto /mnt with:
cd /mnt
make a directory:
mkdir usb
edit your /etc/fstab file:
kwrite /etc/fstab &
append the following line:
/dev/sdb1 /mnt/usb auto noauto,owner,sync 0 0
after saving the fstab file try to mount the usb-device-filesystem with:
mount /mnt/usb
list your contents:
ls -la /mnt/usb
[leith@localhost leith]$ su
Password:
[root@localhost leith]# cd /mnt
[root@localhost mnt]# mkdir usb
[root@localhost mnt]# kwrite /etc/fstab &
[1] 3900
[root@localhost mnt]# QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...
okay.
There is a file in your folder /etc (/etc is a little bit like the registry of windows) called "fstab" (or filesystem table).
in this file you can see or edit all (storage-)device that linux (possibly) mount on startup.
Appending an entry for you usb-device makes linux know about it and howto handle it as a storage device.
You can browse with your filemanager (as root) to your "/etc" directory and open the "fstab" with an text-editor. you must be "root" to edit or more exactly save the file after editing.
then append the line:
/dev/sdb1 /mnt/usb auto noauto,owner,sync 0 0
where:
- /dev/sdb1 is your usb-device
- /mnt/usb is the folder where linux mount the device in
- auto is for auto-detecting the devices filesystem. (You can set it to "vfat" if you have a windows fat filesystem on the stick)
- noauto,owner,sync -> noauto means that linux does not mount it on startup
-> owner means that the person who mounts it is the owner
-> sync means that linux directly writes data on the device (if you copy something on it)
with this entry you should be able to mount the device.
You can add on the KDE-desktop an icon with:
- right-click on the desktop
-> new -> device -> harddisk (don't know exactly the name in EN (localisation))
after this there comes up a new dialog. you can set a name for your new icon and specify which device you want to use.
you specify it on the "device"-tab. there should be an entry with: /dev/sdb1 (/mnt/usb).
Originally posted by KiwiPingu ..
[root@localhost mnt]# kwrite /etc/fstab &
[1] 3900
[root@localhost mnt]# QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...
..
this is it.
you can ignore the QPixmap messages.
know append the line to your fstab as shown in the other posts.
The document could not be saved, as it was not possible to write to file:/etc/fstab.
Check that you have write access to this file or that enough disc space is available.
I have about 110Gb available so it must be that i don't have the write access. Is write access like root. How do I get it.
I am the root user and know the root password.
your devicefile "/dev/sdb1" is owned by root.
i solved it by changing the ownerchip of "/dev/sdb1" to my user.
it is not the best way (it's a evil workaround), but for a home(-mostly one-user)-machine it doesn't matter.
go to your "root" console. (sorry i am only talking about the console but if you get used to it, many things are faster)
type:
chown -c YOURUSER /dev/sdb1
the "chown" command changes the ownerchip of files
YOURUSER is the user who wants to mount the device
with this command you set the new ownerchip. after this try mounting again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.