LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-21-2004, 11:17 PM   #16
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15

Quote:
Originally posted by WMD
Well...if you have Windoze XP, just format the drive with that. It'll let you select FAT32.
Oh you mean from boot? Lol, I thought of that a while ago, but I can't seem to find my windows xp cd.....
 
Old 08-21-2004, 11:24 PM   #17
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
Quote:
Originally posted by linuxnubx
and lsmod:
Code:
Module                  Size  Used by
nls_cp437               5760  0
vfat                   12544  0
fat                    40224  1 vfat
snd_pcm_oss            48680  0
snd_mixer_oss          17408  3 snd_pcm_oss
ipv6                  245764  10
sbp2                   22024  1
intel_mch_agp           8208  1
uhci_hcd               29328  0
ehci_hcd               25732  0
snd_intel8x0           29576  3
snd_ac97_codec         64516  1 snd_intel8x0
snd_pcm                84228  2 snd_pcm_oss,snd_intel8x0
snd_timer              22148  1 snd_pcm
snd_page_alloc          9224  2 snd_intel8x0,snd_pcm
snd_mpu401_uart         6656  1 snd_intel8x0
snd_rawmidi            20772  1 snd_mpu401_uart
snd_seq_device          6792  1 snd_rawmidi
snd                    45156  11 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               7776  3 snd
ohci1394               31876  0
ieee1394               93368  2 sbp2,ohci1394
ntfs                  131444  1
agpgart                28076  1 intel_mch_agp
[/B]
Looking at that output ...

You sure that it's being picked up as sda1? There's no
sign of usb-storage or the commonly necessary scsi-
modules ... I'm quite confused. Or is all that stuff compiled
into your kernel? And if so, why is half the other USB
stuff not? :)

Cheers,
Tink
 
Old 08-21-2004, 11:38 PM   #18
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
Shouldn't be detected as /dev/sda1? I wouldn't be able to do mkdosfs -F 32 /dev/sda1 successfully if it wasn't detecting as sda1 right?

Code:
ieee1394               93368  2 sbp2,ohci1394
I'm using firewire at the moment. That should be it right there.

The FAT32 really is detected under Windows XP, just for some reason, does not want to mount at all under Linux.

It still gives me:
Code:
root@gHost:~# mount /dev/sda1
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       or too many mounted file systems

Last edited by linuxnubx; 08-21-2004 at 11:40 PM.
 
Old 08-21-2004, 11:43 PM   #19
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
I have NO experience with firewire devices. I have
had lots of dealings with usb, though. And I can say
that a usb hdd won't do anything if the scsi-bits
and usb-storage isn't loaded.

Can you post the output of dmesg?


Cheers,
Tink
 
Old 08-21-2004, 11:49 PM   #20
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
dmesg:
Code:
root@gHost:~# dmesg
cket received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
ieee1394: unsolicited response packet received - no tlabel match
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda.
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found
NTFS-fs warning (device hda1): ntfs_fill_super(): Atime updates are not implemen ted yet.  Disabling them.
Unable to load NLS charset utf8
NTFS volume version 3.1.
Looks like I've got some problems, but this might help me find out how to fix it.
 
Old 08-21-2004, 11:53 PM   #21
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
Doesn't look too happy, indeed. Are using
Pat's kernel, or did you roll one yourself?


Cheers,
Tink
 
Old 08-22-2004, 12:24 AM   #22
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
I'm using con kolivas. In the kernel options for VFAT FS Support there are two options

1) (437) Default codpage for FAT
2) Default IO charset for FAT: iso8859-1

What values should replace the 437 and the iso8859-1? Those are the default values given...

Last edited by linuxnubx; 08-22-2004 at 12:31 AM.
 
Old 08-22-2004, 02:04 AM   #23
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
Fixed!!! I reinstalled Slack 10, so now I'm using kernel version 2.4.26... It was the 2.6.8.1 ck3 kernel... Well anyways, I noticed that

1) (437) Default codpage for FAT
2) Default IO charset for FAT: iso8859-1

options were not in the menuconfig, so it has to be those options that are messing everything up. You guys know how to work this?
 
Old 08-22-2004, 02:16 AM   #24
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
OK. This is getting extremely ANNOYING. Now that my external hdd is working, I can't copy files onto it WTF. And the error this time is!!!

"The destination disk is read-only."

Amazing... Really, just fcuking great... How do I allow WRITE enabled on my FAT32??? Man, what the fcuk do I have to do to get this shiet going? It says WRITE is enabled under permissons, so WTF. I can't even change the options under permissions because "Couldn't change the permissions of "fat32" because it is on a read-only disk."
 
Old 08-22-2004, 02:20 AM   #25
major.tom
Member
 
Registered: Jun 2003
Location: Canada
Distribution: Slackware (current); Gentoo (newbie)
Posts: 142

Rep: Reputation: 15
I don't know for sure, but this link might help. It was great for teaching me to create Fat32 ZIP disks that I could read from my windoze machine. I believe it tells how to create Fat16, but it's only one small change in step 3 (hit L and it will list the correct code for Fat32). (oh, and don't use partition 4 -- that is specific to ZIP disks)

http://docs.cs.byu.edu/docs/ziplinux/1.php

Good luck,

Garry

Last edited by major.tom; 08-22-2004 at 02:21 AM.
 
Old 08-22-2004, 03:34 AM   #26
Tinkster
Moderator
 
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928Reputation: 928
Quote:
Originally posted by linuxnubx
OK. This is getting extremely ANNOYING. Now that my external hdd is working, I can't copy files onto it WTF. And the error this time is!!!

"The destination disk is read-only."

Amazing... Really, just fcuking great... How do I allow WRITE enabled on my FAT32??? Man, what the fcuk do I have to do to get this shiet going? It says WRITE is enabled under permissons, so WTF. I can't even change the options under permissions because "Couldn't change the permissions of "fat32" because it is on a read-only disk."
And again the output of
mount
and knowledge of your fstab and the commandline you're
using to mount it would be helpful in diagnosing the problem.

If you just want to vent go talk at a parking meter.



Cheers,
Tink
 
Old 08-22-2004, 03:42 AM   #27
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
Sorry about that. Anyways, I don't know what happened... But it works now... shiet.
 
Old 08-22-2004, 01:20 PM   #28
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
Okay, a bit of the same trouble. It was working fine in 2.4.26, but when I moved back up to the 2.6.8.1 ck3, it doesn't work anymore and gives me:

Code:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       or too many mounted file systems
I'm thinking it has to do with those two extra options that are now included with the new kernel:

1) (437) Default codpage for FAT
2) Default IO charset for FAT: iso8859-1

Anybody know what values I should use for these two kernel options? The default ones don't seem to work... Or maybe the problem is coming from elsewhere, but I do know that moving from 2.4.26 to 2.6.8.1 ck3 creates the problem.
 
Old 08-22-2004, 01:41 PM   #29
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 244Reputation: 244Reputation: 244
Assuming your kernel source directory is in /usr/src, what is your output for :

cat /usr/src/linux-2.6.8.1/.config | grep -i fat
 
Old 08-22-2004, 01:47 PM   #30
linuxnubx
Member
 
Registered: Jul 2004
Posts: 92

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by Cedrik
Assuming your kernel source directory is in /usr/src, what is your output for :

cat /usr/src/linux-2.6.8.1/.config | grep -i fat
Code:
# CONFIG_X86_MCE_NONFATAL is not set
# DOS/FAT/NT Filesystems
CONFIG_FAT_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"

These are the two new options that come with 2.6.8.1... And I think they might be messing up my fat32 access. I can't turn them off; I can only change the values.

Last edited by linuxnubx; 08-22-2004 at 01:48 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
making FAT32 partition reakinator Linux - Newbie 5 10-14-2005 08:51 PM
Having trouble making Fat32 Partition eggoz Linux - Hardware 1 09-18-2005 10:12 PM
making a fat32 partition tintilin Slackware 19 12-05-2004 12:45 PM
Making mounted FAT32 partition writable by all jrittvo Fedora 14 06-07-2004 02:39 AM
Making FAT32 partitions larger than 32GB's syzygy_eolith Linux - Newbie 5 04-23-2004 12:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:14 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration