Re: [gentoo-user] Re: mount and exfat
On Tue, 2012-10-30 at 06:40 +0100, Francesco Talamona wrote: > On Tuesday 30 October 2012, Bill Kenworthy wrote: > > Any idea how I can get the mount command to recognise exfat? It > > works as root but not via fstab for users. > > > > bunyip ~ # mount /dev/sdc1 /mnt/tmp > > mount: unknown filesystem type 'exfat' > > bunyip ~ # mount.exfat /dev/sdc1 /mnt/tmp > > FUSE exfat 0.9.8 > > bunyip ~ # > > > > > > BillK > > http://forums.debian.net/viewtopic.php?f=30&t=85873 > > Never used exfat myself, but I think you should include "exfat-fuse" in > fstab > > HTH > Francesco > Ah, I was using exfat! Seems like all the newer high capacity usb thumb drives are exfat so it will become more common I am sure. BillK
[gentoo-user] Re: mount and exfat
On Tuesday 30 October 2012, Bill Kenworthy wrote: > Any idea how I can get the mount command to recognise exfat? It > works as root but not via fstab for users. > > bunyip ~ # mount /dev/sdc1 /mnt/tmp > mount: unknown filesystem type 'exfat' > bunyip ~ # mount.exfat /dev/sdc1 /mnt/tmp > FUSE exfat 0.9.8 > bunyip ~ # > > > BillK http://forums.debian.net/viewtopic.php?f=30&t=85873 Never used exfat myself, but I think you should include "exfat-fuse" in fstab HTH Francesco -- Linux Version 3.6.2-gentoo, Compiled #3 SMP Sat Oct 20 09:46:59 CEST 2012 Two 2.9GHz AMD Athlon 64 X2 Processors, 8GB RAM, 11659 Bogomips Total aemaeth
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
On Mon, 21 Jul 2008 02:35:44 +0300, Nikos Chantziaras wrote: > Anyway, you don't need to add something to remind you > of the partition's position; /etc/mtab will use regular device names, > so you can see what's going on with 'cat /etc/mtab' or simply 'mount' > without parameters. cfdisk also shows the labels against the partition names. -- Neil Bothwick Don't use a long word if a diminutive one will do. signature.asc Description: PGP signature
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Mick wrote: On Sunday 20 July 2008, Nikos Chantziaras wrote: The labels are part of the file system; they're always there. For example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, meaning /dev/hd* instead of /dev/sd*) the labels are there and I can mount /dev/disk/by-label/GentooRoot just fine. Yes, labels . . . been thinking of doing this for the last two years! I guess I will have to use reiserfstune for my reiserfs partitions. What about xfs - will xfsprogs do it? The xfs_admin is used to change the label of XFS partitions: http://linux.die.net/man/8/xfs_admin Thanks for the tip. The thing with the conventional device numbering system is that you know which one is first, which second, etc. With Labels I'll have to add something to it to remind myself that this is the first partition, etc. Can I have blank spaces in the Label name? I don't think spaces are allowed. But you can use underscores or capitalization. Anyway, you don't need to add something to remind you of the partition's position; /etc/mtab will use regular device names, so you can see what's going on with 'cat /etc/mtab' or simply 'mount' without parameters. On my system, even though I use labels, I get this with 'mount': /dev/sdc1 on / type ext3 (rw,noatime) /dev/sda1 on /windows/C type fuseblk (rw,noatime,allow_other,blksize=4096)
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Dale wrote: Dale wrote: True but I have trouble remembering which partition is home and which is portage, until I mount them anyway. It's obvious then. I guess according to another reply that I will have to use something else for resierfs. I guess it can't hurt to much. Worst thing is to have to boot and edit fstab back to the old way. :/ Well bummer, you have to umount it first. O_O That sucks. Somebody tell me it ain't so. It is so ;P Best simply boot from the live CD and change the labels there, mount the root partition, change fstab right there and reboot.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Dale wrote: True but I have trouble remembering which partition is home and which is portage, until I mount them anyway. It's obvious then. I guess according to another reply that I will have to use something else for resierfs. I guess it can't hurt to much. Worst thing is to have to boot and edit fstab back to the old way. :/ Dale :-) :-) Well bummer, you have to umount it first. O_O That sucks. Somebody tell me it ain't so. Dale :-) :-)
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Nikos Chantziaras wrote: Dale wrote: Nikos Chantziaras wrote: Dale wrote: [...] Question, if I were to label mine and then boot from a Gentoo or any other bootable CD, would those labels still be there? The labels are part of the file system; they're always there. For example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, meaning /dev/hd* instead of /dev/sd*) the labels are there and I can mount /dev/disk/by-label/GentooRoot just fine. Kwl. Now to see what I can screw up. o_O I should mention here the old Indian* saying: "If it ain't broke, don't fix it." *OK, it's not Indian, but you get the idea. True but I have trouble remembering which partition is home and which is portage, until I mount them anyway. It's obvious then. I guess according to another reply that I will have to use something else for resierfs. I guess it can't hurt to much. Worst thing is to have to boot and edit fstab back to the old way. :/ Dale :-) :-)
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Dale wrote: Nikos Chantziaras wrote: Dale wrote: [...] Question, if I were to label mine and then boot from a Gentoo or any other bootable CD, would those labels still be there? The labels are part of the file system; they're always there. For example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, meaning /dev/hd* instead of /dev/sd*) the labels are there and I can mount /dev/disk/by-label/GentooRoot just fine. Kwl. Now to see what I can screw up. o_O I should mention here the old Indian* saying: "If it ain't broke, don't fix it." *OK, it's not Indian, but you get the idea.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
On Sunday 20 July 2008, Nikos Chantziaras wrote: > Dale wrote: > > Nikos Chantziaras wrote: > >> Mick wrote: > >>> [...] > >>> What would be the recommended way of upgrading from the /dev/hd to > >>> /dev/sd then? I have held back doing this because I didn't have the > >>> time to mess about with it. If I were to configure a new kernel > >>> without legacy ATA drivers, how would I know what my devices will be > >>> seen as in advance, so that I can change my /etc/fstab before I reboot? > >> > >> The way I do it, is to label my partitions. If your partitions aren't > >> labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your > >> root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label > >> them with: > >> > >> tune2fs -L GentooRoot /dev/hda1 > >> tune2fs -L GentooHome /dev/hda2 > >> mkswap -L GentooSwap /dev/hda3 > >> [...] > > > > Question, if I were to label mine and then boot from a Gentoo or any > > other bootable CD, would those labels still be there? > > The labels are part of the file system; they're always there. For > example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, > meaning /dev/hd* instead of /dev/sd*) the labels are there and I can > mount /dev/disk/by-label/GentooRoot just fine. Yes, labels . . . been thinking of doing this for the last two years! I guess I will have to use reiserfstune for my reiserfs partitions. What about xfs - will xfsprogs do it? Thanks for the tip. The thing with the conventional device numbering system is that you know which one is first, which second, etc. With Labels I'll have to add something to it to remind myself that this is the first partition, etc. Can I have blank spaces in the Label name? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Alan Mackenzie wrote: On Sun, Jul 20, 2008 at 12:29:19AM +0300, Nikos Chantziaras wrote: The CD/DVD-ROM can show up as /dev/sd* even with the old legacy drivers if you have enable "SCSI Emulation" for it. In any event, try to build a new kernel using the new drivers. The old legacy driver you're using will probably get declared "deprecated" at some point (if it didn't happen already). [...] In a philosophical mood, one might say that the new "unified", "enhanced", "better" IDE support is inadequate for my setup. What I actually said, I'm not going to repeat in a public mailing list. I must admit that I'm not affected much by this since, as I mentioned in another post, I use labels and don't look at what /dev/sd* my drive is mapped. For unpartitioned drivers where I'm not sure which /dev/sd* entry to use, I simply use /dev/disk/by-id instead ;) So the kernel guys have decided that nobody would ever want more than 15 partitions on a drive. It's a bit like the old MS-DOS restriction to 512 MB all over again. Hey, guys, hard drives nowadays are like 200 gig, not 512meg. What's so wrong about having partitions with sizes 1Gb, 2Gb, 4Gb, with maybe 100Mb for a boot partition? Unlike the above, this one is a real problem. Fortunately, as long as the new drivers are still labeled "experimental" there's little chance of the legacy drivers being removed from the kernel. Performance-wise, I don't think you're missing much by not using the new drivers (though that's just a guess; don't take my word on it :P) If some day the legacy drivers are kicked out, you might have to go the LVM route by force :P But I guess this isn't like to happen anytime soon now, since not all hardware seems supported by the new drivers. Both of these created /dev/sdc and /dev/sdc1, but no /dev/sdd. When I tried # mount -t iso9660 /dev/sdc /cdrom, I got the "something's gone wrong, but we're not telling you what" error message. Trying to mount /dev/sdc1 gave exactly the same result. Actually, thinking about it, this was probably my USB stick it was trying to access. I know that everyone is using his/her own system as he/she sees fit, but I don't mount CD/DVD and USB drives by hand anymore. And no entries at all in fstab either. I just plug it in and let dbus (+ HAL if you're on KDE/Gnome) handle the rest :P Nikos, do you happen to know the appropriate kernel mailing list where I could express the opinion that restricting the number of partitions on a drive to 15 isn't a good tradeoff? LKML should be OK. At least last time I checked, regulars there are against directing people to "more appropriate" lists, meaning that LKML is the most appropriate of all if the issue is about things that are officially in the kernel. In any event, I remember this issue being raised back in 2004, so I guess it has been discussed to death by now. (And I did not follow the discussion, so I can't give you a summary, I'm afraid. Google is your friend.) All in all, I really amn't impressed with this "modern" drive support. Besides quartering the max number of partitions on a drive, it confuses IDE and SCSI drives, thus confusing me, too. Previously, when I attached devices to the IDE1 socket, I knew they would appear at /dev/hd[cd]. Now, it would seem, the kernel assigns drives at random to /dev/sd[abcd...], so you can only determine by experiment which devices are at which "device". Nothing personal, Nikos. ;-) I'm on PATA+SATA+USB here, so I know what you mean. However, I found the /dev/disk/ tree to be very helpful here.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Nikos Chantziaras wrote: Dale wrote: Nikos Chantziaras wrote: Mick wrote: [...] What would be the recommended way of upgrading from the /dev/hd to /dev/sd then? I have held back doing this because I didn't have the time to mess about with it. If I were to configure a new kernel without legacy ATA drivers, how would I know what my devices will be seen as in advance, so that I can change my /etc/fstab before I reboot? The way I do it, is to label my partitions. If your partitions aren't labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label them with: tune2fs -L GentooRoot /dev/hda1 tune2fs -L GentooHome /dev/hda2 mkswap -L GentooSwap /dev/hda3 [...] Question, if I were to label mine and then boot from a Gentoo or any other bootable CD, would those labels still be there? The labels are part of the file system; they're always there. For example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, meaning /dev/hd* instead of /dev/sd*) the labels are there and I can mount /dev/disk/by-label/GentooRoot just fine. Kwl. Now to see what I can screw up. o_O Dale :-) :-)
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Dale wrote: Nikos Chantziaras wrote: Mick wrote: [...] What would be the recommended way of upgrading from the /dev/hd to /dev/sd then? I have held back doing this because I didn't have the time to mess about with it. If I were to configure a new kernel without legacy ATA drivers, how would I know what my devices will be seen as in advance, so that I can change my /etc/fstab before I reboot? The way I do it, is to label my partitions. If your partitions aren't labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label them with: tune2fs -L GentooRoot /dev/hda1 tune2fs -L GentooHome /dev/hda2 mkswap -L GentooSwap /dev/hda3 [...] Question, if I were to label mine and then boot from a Gentoo or any other bootable CD, would those labels still be there? The labels are part of the file system; they're always there. For example, when booting the 2007.0 LiveDVD (which uses the legacy drivers, meaning /dev/hd* instead of /dev/sd*) the labels are there and I can mount /dev/disk/by-label/GentooRoot just fine.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Nikos Chantziaras wrote: Mick wrote: [...] What would be the recommended way of upgrading from the /dev/hd to /dev/sd then? I have held back doing this because I didn't have the time to mess about with it. If I were to configure a new kernel without legacy ATA drivers, how would I know what my devices will be seen as in advance, so that I can change my /etc/fstab before I reboot? The way I do it, is to label my partitions. If your partitions aren't labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label them with: tune2fs -L GentooRoot /dev/hda1 tune2fs -L GentooHome /dev/hda2 mkswap -L GentooSwap /dev/hda3 Then edit /etc/fstab and change the mount points from: /dev/hda1 ... /dev/hda2 ... /dev/hda3 ... to: /dev/disk/by-label/GentooRoot /dev/disk/by-label/GentooHome /dev/disk/by-label/GentooSwap As reference, here the relevant entries in my own /etc/fstab: /dev/disk/by-label/GentooRoot / ext3noatime 0 1 /dev/disk/by-label/GentooSwap none swapsw 0 0 /dev/disk/by-label/Suckage/windows/C ntfs-3g noatime 0 0 As you can see this even works for NTFS; you use the label you gave the drive in Windows. After you've done these changes, it doesn't matter the least anymore what the actual device name is. You can even move the harddisk to another computer (actually I'm doing exactly that) that totally results in a re-ordering of /dev/sd* entries and it will still mount correctly. Question, if I were to label mine and then boot from a Gentoo or any other bootable CD, would those labels still be there? Dale :-) :-)
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Mick wrote: [...] What would be the recommended way of upgrading from the /dev/hd to /dev/sd then? I have held back doing this because I didn't have the time to mess about with it. If I were to configure a new kernel without legacy ATA drivers, how would I know what my devices will be seen as in advance, so that I can change my /etc/fstab before I reboot? The way I do it, is to label my partitions. If your partitions aren't labeled yet, you can do so with 'tune2fs'. If your /dev/hda1 is your root (/), /dev/hda2 your /home and /dev/hda3 your swap, you can label them with: tune2fs -L GentooRoot /dev/hda1 tune2fs -L GentooHome /dev/hda2 mkswap -L GentooSwap /dev/hda3 Then edit /etc/fstab and change the mount points from: /dev/hda1 ... /dev/hda2 ... /dev/hda3 ... to: /dev/disk/by-label/GentooRoot /dev/disk/by-label/GentooHome /dev/disk/by-label/GentooSwap As reference, here the relevant entries in my own /etc/fstab: /dev/disk/by-label/GentooRoot / ext3noatime 0 1 /dev/disk/by-label/GentooSwap none swapsw 0 0 /dev/disk/by-label/Suckage/windows/C ntfs-3g noatime 0 0 As you can see this even works for NTFS; you use the label you gave the drive in Windows. After you've done these changes, it doesn't matter the least anymore what the actual device name is. You can even move the harddisk to another computer (actually I'm doing exactly that) that totally results in a re-ordering of /dev/sd* entries and it will still mount correctly.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Hi, Mick,
On Sun, Jul 20, 2008 at 06:22:23PM +0100, Mick wrote:
> On Sunday 20 July 2008, Alan Mackenzie wrote:
> > So the kernel guys have decided that nobody would ever want more than 15
> > partitions on a drive.
> From memory I recall that this has always been the limit for SATA/SCSI
> drives. For ATA drives I think it is 63?
If I do # ls -l /dev/hd[gh], I get:
brw-rw 1 root disk 34, 0 2005-02-26 06:43 /dev/hdg
brw-rw 1 root disk 34, 64 2005-02-26 06:43 /dev/hdh
, which does indeed suggest a max of 63. However, there's nothing on the
disk partition structure (which is basically a chain of extended
partitions across the entire disk) to limit this.
> Not sure if this is a Linux OS kernel restriction - what is the maximum
> number
> that MSWindows see?
What's MSWindows? ;-)
Proabably a lot less than 63.
However, the limit of 15 (which I didn't know about before) is a good
reason for me not to migrate to SATA disks. I _like_ having lots of
partitions ~1 - 4 Gb. It was trivial for me to clear a 4 Gb partition
for a trial installation of Gentoo (which, by the way, I'm expecting to
expand into my prime system - my Debian Sarge is beginning to feel very
tired).
Shoe horning IDE disks into the S{ATA,CSI}'s 15 partition limit seems an
unkind thing to do.
> Mick
--
Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
On Sun, 20 Jul 2008 15:05:10 +, Alan Mackenzie wrote: > So the kernel guys have decided that nobody would ever want more than 15 > partitions on a drive. It's a bit like the old MS-DOS restriction to > 512 MB all over again. Hey, guys, hard drives nowadays are like 200 > gig, not 512meg. What's so wrong about having partitions with sizes > 1Gb, 2Gb, 4Gb, with maybe 100Mb for a boot partition? Nothing, which is why the kernel includes LVM, allowing you to have many more filesystems on a disk. -- Neil Bothwick c:>Press Enter to Exit signature.asc Description: PGP signature
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
On Sunday 20 July 2008, Alan Mackenzie wrote: > So the kernel guys have decided that nobody would ever want more than 15 > partitions on a drive. From memory I recall that this has always been the limit for SATA/SCSI drives. For ATA drives I think it is 63? Not sure if this is a Linux OS kernel restriction - what is the maximum number that MSWindows see? I would think it is the same. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Hi, Nikos!
On Sun, Jul 20, 2008 at 12:29:19AM +0300, Nikos Chantziaras wrote:
> Alan Mackenzie wrote:
> >>The default in new kernels is to only use /dev/sd*.
> >I'm totally confused. Doesn't "sd*" mean "SCSI disk drive"? When I was
> >installing Gentoo from the CD, I had to mount my main hard drive as
> >/dev/sdb5. When I built my own kernel, it needed /dev/hdh5.
> >This seems crazy. Is it documented anywhere in Gentoo?
> Not sure. But if you have /dev/hd* instead of /dev/sd*, it means you
> configured your kernel with the legacy IDE drivers instead of the new
> (P)ATA drivers. The new drivers use /dev/sd* (for IDE/PATA/SATA and
> SCSI alike; there's no difference anymore.)
This was indeed the case.
> The CD/DVD-ROM can show up as /dev/sd* even with the old legacy drivers
> if you have enable "SCSI Emulation" for it.
> In any event, try to build a new kernel using the new drivers. The old
> legacy driver you're using will probably get declared "deprecated" at
> some point (if it didn't happen already).
[ Detailed instructions snipped - but they were appreciated and followed
:-]
Did this. It mapped my two hard drives (previously /dev/hd[gh]) to
/dev/sd[ab], and created /dev/sda, dev/sda1, . So far, so good.
However, it hadn't created /dev/sda16 or /dev/sda17 for some reason. A
quick # ls -l /dev/sd{a15,b} gives:
... 8, 15 /dev/sda15
... 8, 16 /dev/sdb
In a philosophical mood, one might say that the new "unified",
"enhanced", "better" IDE support is inadequate for my setup. What I
actually said, I'm not going to repeat in a public mailing list.
So the kernel guys have decided that nobody would ever want more than 15
partitions on a drive. It's a bit like the old MS-DOS restriction to 512
MB all over again. Hey, guys, hard drives nowadays are like 200 gig, not
512meg. What's so wrong about having partitions with sizes 1Gb, 2Gb, 4Gb,
with maybe 100Mb for a boot partition?
>< > Generic ATA support
> unless you can't find a native driver for your chipset (I doubt you have
> some extremely rare/exotic mainboard ;)
The HPT370A UDMA100 chip (with my two hard drives) was no problem. For
the VIA VT82C586A/B/VT82C686/A/B/VT823x/A/C "ordinary" IDE chip (the one
with my two DVD drives attached), I tried configuring "VIA", which
didn't work. Then I rebuilt the kernel again with "Generic ATA
support", which didn't work either.
Both of these created /dev/sdc and /dev/sdc1, but no /dev/sdd. When I
tried # mount -t iso9660 /dev/sdc /cdrom, I got the "something's gone
wrong, but we're not telling you what" error message. Trying to mount
/dev/sdc1 gave exactly the same result. Actually, thinking about it,
this was probably my USB stick it was trying to access.
Nikos, do you happen to know the appropriate kernel mailing list where I
could express the opinion that restricting the number of partitions on a
drive to 15 isn't a good tradeoff?
All in all, I really amn't impressed with this "modern" drive support.
Besides quartering the max number of partitions on a drive, it confuses
IDE and SCSI drives, thus confusing me, too. Previously, when I
attached devices to the IDE1 socket, I knew they would appear at
/dev/hd[cd]. Now, it would seem, the kernel assigns drives at random to
/dev/sd[abcd...], so you can only determine by experiment which devices
are at which "device". Nothing personal, Nikos. ;-)
I think I need to go back to the traditional IDE handling.
None of the Gentoo kernels I've built have even seen my two DVD drives,
yet. I'll get there, somehow.
Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
On Saturday 19 July 2008, Nikos Chantziaras wrote:
> Alan Mackenzie wrote:
> >> The default in new kernels is to only use /dev/sd*.
> >
> > I'm totally confused. Doesn't "sd*" mean "SCSI disk drive"? When I was
> > installing Gentoo from the CD, I had to mount my main hard drive as
> > /dev/sdb5. When I built my own kernel, it needed /dev/hdh5.
> >
> > This seems crazy. Is it documented anywhere in Gentoo?
>
> Not sure. But if you have /dev/hd* instead of /dev/sd*, it means you
> configured your kernel with the legacy IDE drivers instead of the new
> (P)ATA drivers. The new drivers use /dev/sd* (for IDE/PATA/SATA and
> SCSI alike; there's no difference anymore.)
>
> The CD/DVD-ROM can show up as /dev/sd* even with the old legacy drivers
> if you have enable "SCSI Emulation" for it.
>
> In any event, try to build a new kernel using the new drivers. The old
> legacy driver you're using will probably get declared "deprecated" at
> some point (if it didn't happen already).
>
> To enable the new drivers, first disable the legacy drivers. ("Device
> Drivers" section):
>
> < > ATA/ATAPI/MFM/RLL support --->
>
> Now enable the new drivers:
>
> <*> Serial ATA (prod) and Parallel ATA (experimental) drivers --->
>
> Enter that section and pick your chipset. Don't enable the:
>
> < > Generic ATA support
>
> unless you can't find a native driver for your chipset (I doubt you have
> some extremely rare/exotic mainboard ;)
What would be the recommended way of upgrading from the /dev/hd to /dev/sd
then? I have held back doing this because I didn't have the time to mess
about with it. If I were to configure a new kernel without legacy ATA
drivers, how would I know what my devices will be seen as in advance, so that
I can change my /etc/fstab before I reboot?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Alan Mackenzie <[EMAIL PROTECTED]> writes: > There's /dev/sda and /dev/sda1, and no other /dev/sd*. That's where my > UBS stick gets mounted. What about any /dev/sr*?
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Alan Mackenzie wrote:
The default in new kernels is to only use /dev/sd*.
I'm totally confused. Doesn't "sd*" mean "SCSI disk drive"? When I was
installing Gentoo from the CD, I had to mount my main hard drive as
/dev/sdb5. When I built my own kernel, it needed /dev/hdh5.
This seems crazy. Is it documented anywhere in Gentoo?
Not sure. But if you have /dev/hd* instead of /dev/sd*, it means you
configured your kernel with the legacy IDE drivers instead of the new
(P)ATA drivers. The new drivers use /dev/sd* (for IDE/PATA/SATA and
SCSI alike; there's no difference anymore.)
The CD/DVD-ROM can show up as /dev/sd* even with the old legacy drivers
if you have enable "SCSI Emulation" for it.
In any event, try to build a new kernel using the new drivers. The old
legacy driver you're using will probably get declared "deprecated" at
some point (if it didn't happen already).
To enable the new drivers, first disable the legacy drivers. ("Device
Drivers" section):
< > ATA/ATAPI/MFM/RLL support --->
Now enable the new drivers:
<*> Serial ATA (prod) and Parallel ATA (experimental) drivers --->
Enter that section and pick your chipset. Don't enable the:
< > Generic ATA support
unless you can't find a native driver for your chipset (I doubt you have
some extremely rare/exotic mainboard ;)
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Hi, Miernik, On Sat, Jul 19, 2008 at 09:13:09PM +0200, Miernik wrote: > Alan Mackenzie <[EMAIL PROTECTED]> wrote: > > # mknod /dev/hdc b 22 0 > > This didn't help one iota. I had a look at dmesg, but there was no > > mention of hdc in it. (It did mention hdg, hdh, where my main hard > > drives are (don't ask!)). > Maybe there was some /dev/sda /dev/sdb or something similar? There's /dev/sda and /dev/sda1, and no other /dev/sd*. That's where my UBS stick gets mounted. > Why do you assume your drive is under /dev/hdx and not /dev/sdx ? Er, because it's an IDE drive, and on my old Debian system it appears at /dev/hdc. My HDD is at /dev/hdh on both old Debian and new Gentoo. When I do an lspci -v, on my Gentoo system, this shows up for hd[cd]: 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE Flags: bus master, medium devsel, latency 32 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] I/O ports at a400 [size=16] Capabilities: [c0] Power Management version 2 This suggests that the IDE controller has been initialised properly, but the kernel has ignored it. > -- > Miernik > http://miernik.name/ -- Alan Mackenzie (Nuremberg, Germany)
Re: [gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Hi, Nikos, On Sat, Jul 19, 2008 at 10:06:15PM +0300, Nikos Chantziaras wrote: > Alan Mackenzie wrote: > >However, I can't access my DVD drives. I know at least one of them > >works, because I installed Gentoo from it. > >When I do > > mount -tiso9660 /dev/hdc /cdrom > >, it comes back with "special device /dev/hdc does not exist". And yes, > >there was a CD in the drive, and /cdrom exists. > >What does "special device" mean here? Does it mean the physcial > >hardware, the controller chip, the directory entry /dev/hdc, the driver > >in the kernel, or what? What is "special" about my DVD writer? > /dev/hdc (and other files in /dev) are not called "files", they're > called "special devices"). Ah! I really wish they weren't. Didn't they used to be called "device files"? > >Well, to answer some of my questions, I was missing a /dev/hdc, so I > >made one with > ># mknod /dev/hdc b 22 0 > >. This didn't help one iota. I had a look at dmesg, but there was no > >mention of hdc in it. (It did mention hdg, hdh, where my main hard > >drives are (don't ask!)). > Use /dev/sdc instead of /dev/hdc. I booted up in to the kernel, did # ls /dev/sd*, and the only things displayed were /dev/sda and /dev/sda1. That is the place where my USB stick gets mounted. > The default in new kernels is to only use /dev/sd*. I'm totally confused. Doesn't "sd*" mean "SCSI disk drive"? When I was installing Gentoo from the CD, I had to mount my main hard drive as /dev/sdb5. When I built my own kernel, it needed /dev/hdh5. This seems crazy. Is it documented anywhere in Gentoo? -- Alan Mackenzie (Nuremberg, Germany).
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Alan Mackenzie <[EMAIL PROTECTED]> wrote: > # mknod /dev/hdc b 22 0 > > This didn't help one iota. I had a look at dmesg, but there was no > mention of hdc in it. (It did mention hdg, hdh, where my main hard > drives are (don't ask!)). Maybe there was some /dev/sda /dev/sdb or something similar? Why do you assume your drive is under /dev/hdx and not /dev/sdx ? -- Miernik http://miernik.name/ -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] Re: mount: "special device /dev/hdc does not exist". What does this mean?
Alan Mackenzie wrote: Hi, Gentoo? I've a newly installed system, now working with my own special optimiesed keyboard layout. :-) However, I can't access my DVD drives. I know at least one of them works, because I installed Gentoo from it. When I do mount -tiso9660 /dev/hdc /cdrom , it comes back with "special device /dev/hdc does not exist". And yes, there was a CD in the drive, and /cdrom exists. What does "special device" mean here? Does it mean the physcial hardware, the controller chip, the directory entry /dev/hdc, the driver in the kernel, or what? What is "special" about my DVD writer? /dev/hdc (and other files in /dev) are not called "files", they're called "special devices"). Well, to answer some of my questions, I was missing a /dev/hdc, so I made one with # mknod /dev/hdc b 22 0 . This didn't help one iota. I had a look at dmesg, but there was no mention of hdc in it. (It did mention hdg, hdh, where my main hard drives are (don't ask!)). Use /dev/sdc instead of /dev/hdc. The default in new kernels is to only use /dev/sd*. -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] Re: mount -t cifs doesn't accept //hostname/share?
On 2008-03-17, Rik Koenig <[EMAIL PROTECTED]> wrote: > On Mon, Mar 17, 2008 at 11:44 AM, Grant Edwards <[EMAIL PROTECTED]> wrote: > >> According to the docs at >> http://gentoo-wiki.com/HOWTO_Setup_Samba#Using_CIFS, >> the following command should work: >> >> mount -t cifs /// / \ >> -o >> "username=,uid=,iocharset=cp850,dir_mode=0770,file_mode=660" >> >> That doesn't work for me. I get this error: >> >> mount -t cifs //sidewinder/temp_xfer /mnt/tmp -o [...] >> mount error: improperly formatted UNC name. /sidewinder/temp_xfer does not >> begin with \\ or // >> mount error 22 = Invalid argument >> >> mount.cifs works fine. The only way I can get mount to work is >> to use backslashes for the UNC path. When support for >> forward-slahses in UNC paths get broken? >> >> -- >> Grant >> >> >> -- >> gentoo-user@lists.gentoo.org mailing list >> > > This error is actually described in the gentoo-wiki page just under that > command example: '*Warning:* Recent versions of "mount" don't support > forward slashes in UNC path names as shown above -- you must use > backslashes.' I know, I added that warning. > However, forward slashes are working for me with samba 3.0.28 and util-linux > 2.13-r2. I've got samba 3.0.28 and util-linux 2.13-r2, and forward slashes don't work for me. I pasted in the command from the wiki page almost exactly as shown (changed the hostname and sharename), and it didn't work. I also found a number of reports of the exact same problem in various other places (Ubunto forums for example). Perhaps I should edit the warning on the wiki page to say that sometimes backslashes work, and sometimes they don't. -- Grant -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Re: mount cdrom: No buffer space available
On Tuesday 27 November 2007, Joost Roeleveld wrote: > > On Mon, 26 Nov 2007 07:53:40 +0100, Dirk Heinrichs wrote: > >> There is no need to do so. However, a fuse based filesystem for mounting > >> audio CDs exists, see http://castet.matthieu.free.fr/cddfs/. > > > > Oh, thank you all for your input -- I've been a bit obsessed with rails > > and let this go to the back burner a bit. > > > > However, I did notice that when I click on "CDROM" from nautilus there's > > a message about HAL; again, though, it cannot be a hardware issue as > > these particular discs and drives work in another distro on the same > > machine. > > If the discs and drives work on the same machine with a different distro, > then I agree, the hardware should work. > > Also, as the /dev/ entries exist and it doesn't complain about that, the > drives are probably detected correctly. > > > I believe it to be a driver issue (HAL is a hardware driver? Hardware > > Abstraction Layer? But isn't it more BIOS than OS?). I'll double check > > things with some data discs on the other distro in the next few days and > > do some more googling (and wikipedia-ing). > > Can you also check with datadiscs on the Gentoo installation? > I agree with the others that audio-discs are generally not mountable. > The FUSE-driver for Audio-discs might be installed on your other distro > (Redhat?), but is not installed by default with Gentoo. > > > If this sheds any light: > > > > > > arrakis ~ # > > arrakis ~ # dmesg | grep 'cd' > > ehci_hcd :00:03.3: EHCI Host Controller > > > > When I do the above command, it only shows me the cd/dvd writer, not the > cdrom drive. > Can you post the full output of "dmesg" after you booted the system? > > > I think it's more on shutdown that I notice lotsa weird messages about > > the cdrom drive(s) since futzing with /etc/fstab. > > Can you also give us the contents of your "/etc/fstab" file? Haven't followed up all of this thread, but it may well be a clash between hald/dbus trying to control your media devices and your fstab. Entries in the latter are only applicable if you want to be mounting such devices manually. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: mount cdrom: No buffer space available
> On Mon, 26 Nov 2007 07:53:40 +0100, Dirk Heinrichs wrote: > > >> There is no need to do so. However, a fuse based filesystem for mounting >> audio CDs exists, see http://castet.matthieu.free.fr/cddfs/. > > Oh, thank you all for your input -- I've been a bit obsessed with rails > and let this go to the back burner a bit. > > However, I did notice that when I click on "CDROM" from nautilus there's > a message about HAL; again, though, it cannot be a hardware issue as > these particular discs and drives work in another distro on the same > machine. If the discs and drives work on the same machine with a different distro, then I agree, the hardware should work. Also, as the /dev/ entries exist and it doesn't complain about that, the drives are probably detected correctly. > I believe it to be a driver issue (HAL is a hardware driver? Hardware > Abstraction Layer? But isn't it more BIOS than OS?). I'll double check > things with some data discs on the other distro in the next few days and > do some more googling (and wikipedia-ing). Can you also check with datadiscs on the Gentoo installation? I agree with the others that audio-discs are generally not mountable. The FUSE-driver for Audio-discs might be installed on your other distro (Redhat?), but is not installed by default with Gentoo. > If this sheds any light: > > > arrakis ~ # > arrakis ~ # dmesg | grep 'cd' > ehci_hcd :00:03.3: EHCI Host Controller When I do the above command, it only shows me the cd/dvd writer, not the cdrom drive. Can you post the full output of "dmesg" after you booted the system? > I think it's more on shutdown that I notice lotsa weird messages about > the cdrom drive(s) since futzing with /etc/fstab. Can you also give us the contents of your "/etc/fstab" file? Kind regards, Joost Roeleveld -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: mount cdrom: No buffer space available
On Mon, 26 Nov 2007 07:53:40 +0100, Dirk Heinrichs wrote: > There is no need to do so. However, a fuse based filesystem for mounting > audio CDs exists, see http://castet.matthieu.free.fr/cddfs/. Oh, thank you all for your input -- I've been a bit obsessed with rails and let this go to the back burner a bit. However, I did notice that when I click on "CDROM" from nautilus there's a message about HAL; again, though, it cannot be a hardware issue as these particular discs and drives work in another distro on the same machine. On boot, and I think shutdown, there are messages about failing to access the CDROM -- this is post POST and after GRUB -- I think; maybe it's on shutdown only. I believe it to be a driver issue (HAL is a hardware driver? Hardware Abstraction Layer? But isn't it more BIOS than OS?). I'll double check things with some data discs on the other distro in the next few days and do some more googling (and wikipedia-ing). If this sheds any light: arrakis ~ # arrakis ~ # dmesg | grep 'cd' ehci_hcd :00:03.3: EHCI Host Controller ehci_hcd :00:03.3: new USB bus registered, assigned bus number 1 ehci_hcd :00:03.3: irq 17, io mem 0xe1102000 ehci_hcd :00:03.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ohci_hcd :00:03.0: OHCI Host Controller ohci_hcd :00:03.0: new USB bus registered, assigned bus number 2 ohci_hcd :00:03.0: irq 18, io mem 0xe1104000 ohci_hcd :00:03.1: OHCI Host Controller ohci_hcd :00:03.1: new USB bus registered, assigned bus number 3 ohci_hcd :00:03.1: irq 19, io mem 0xe110 ohci_hcd :00:03.2: OHCI Host Controller ohci_hcd :00:03.2: new USB bus registered, assigned bus number 4 ohci_hcd :00:03.2: irq 20, io mem 0xe1101000 usb 4-1: new low speed USB device using ohci_hcd and address 2 sl811: driver sl811-hcd, 19 May 2005 arrakis ~ # I think it's more on shutdown that I notice lotsa weird messages about the cdrom drive(s) since futzing with /etc/fstab. thanks, Thufir -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: mount cdrom: No buffer space available
On Fri, 23 Nov 2007 09:11:06 + Neil Bothwick <[EMAIL PROTECTED]> wrote: > On Fri, 23 Nov 2007 08:15:48 + (UTC), Thufir wrote: > > > In this case, the discs are fine, as are the drives. The drives > > mount fine in Fedora and read these particular discs fine (music > > CD's). > > You don't mount audio CDs. > > Not to listen to them, or to get any sort of valuable information off them. But can't you mount them? I vaguely remember being confused when the files (TOC) i copied off a music CD wouldn't play by themselves... -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: mount cdrom: No buffer space available
On Fri, 23 Nov 2007 08:15:48 + (UTC), Thufir wrote: > In this case, the discs are fine, as are the drives. The drives mount > fine in Fedora and read these particular discs fine (music CD's). You don't mount audio CDs. -- Neil Bothwick Procrastinate now! signature.asc Description: PGP signature
[gentoo-user] Re: mount cdrom: No buffer space available
On Fri, 23 Nov 2007 07:36:44 +0100, Dirk Heinrichs wrote: > I also found (with Google) one forum posting where it was stated that > the cause was a bad, self-burned disk in the drive. When the poster > changed the disk, the problem disapeared. In this case, the discs are fine, as are the drives. The drives mount fine in Fedora and read these particular discs fine (music CD's). What other things effect mounting devices? can I test the /dev/ configuration? how about mtab? Just shots in the dark... thanks, Thufir -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: mount cdrom: No buffer space available
On Thu, 22 Nov 2007 15:20:43 +, Stroller wrote: > A Google seems to suggest that "mount: No buffer space available" is > commonly returned when the device is already mounted. Oh, I wasn't finding that or didn't know how to interpret it. > The manpage for `mount` indicates that `mount -a` will mount all devices > listed in /etc/fstab, so your output suggests to me that the CD drives > are mounted when you issue this command - no wonder they fail when you > try to mount them again separately! Yes, I concur with everything above. However, I guess I left out the fact that there's a disc in each drive; the discs are readable. arrakis ~ # arrakis ~ # mount -a arrakis ~ # arrakis ~ # mount /dev/hdb3 on / type ext3 (rw,noatime) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec) udev on /dev type tmpfs (rw,nosuid) devpts on /dev/pts type devpts (rw,nosuid,noexec) /dev/hdb1 on /boot type ext2 (rw) none on /dev/shm type tmpfs (rw) /dev/mapper/VolGroup00-LogVol00 on /mnt/VolGroup00/LogVol00 type ext3 (rw,noexec,nosuid,nodev) usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85) arrakis ~ # arrakis ~ # mount -va && df && mount -v /mnt/cdrom mount: /dev/hdb1 already mounted on /boot mount: none already mounted on /dev/shm mount: /dev/VolGroup00/LogVol00 already mounted on /mnt/VolGroup00/ LogVol00 mount: proc already mounted arrakis ~ # arrakis ~ # ll /mnt/ total 20 drwxr-xr-x 3 root root 4096 Oct 7 00:17 VolGroup00 drwx-- 2 root root 4096 Jul 26 02:54 cdrom drwxr-xr-x 2 root root 4096 Nov 22 00:37 cdrom1 drwxr-xr-x 2 root root 4096 Nov 21 23:54 cdrw1 drwx-- 2 root root 4096 Jul 26 02:54 floppy arrakis ~ # arrakis ~ # ll /mnt/cdrom total 0 arrakis ~ # arrakis ~ # ll /mnt/cdrom1 total 0 arrakis ~ # arrakis ~ # ll /mnt/cdrw1 total 0 arrakis ~ # arrakis ~ # thanks, Thufir -- [EMAIL PROTECTED] mailing list
[gentoo-user] Re: Mount and write ntfs (natively)
[EMAIL PROTECTED] writes: Yikes ... looks like my literacy level is greviously low.. > First, sorry this got somewhat disjointed. > > I think you may have already ansered what I wanted to know but for the > sake of clarity. > > The `puppy' live cd described in my quotation says it can create a > file on ntfs and this write withing that space. In other words it > isn't normal read/write as we normally think of it. That gibberish above should say: The `Puppy' live CD described in my quotation in earlier post, says it can create a file on ntfs and THEN write WITHIN that space. In other words it isn't normal read/write as we normally think of it. > My question to you was if ntfs-g3 can read/write in a normal way to > ntfs. That is could one do: >echo data >file > > and then >rm -f file > > or vim file in the normal way? > > I think you've already said you think it can. I was unable to tell > from the man page installed with ntfs-3g, and wanted to know for sure > before getting myself into a bind. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Mount and write ntfs (natively)
Harry Putnam wrote: Harry Putnam <[EMAIL PROTECTED]> writes: Alexander, Do you know if the system described above is what ntfs-g3 does too? One could never determine something that basic from the man page supplied with it. After reading it, I still know nothing about how it works. With a disk mounted under this tool can one simply say `echo data >file' and `file' appears and can be edited? With "this tool", you mean ntfs-3g? If so, then yes, creating files and "resizing" (ie. making them larger or smaller) should be possible, according to what I read. I haven't checked this, as I don't have NTFS file systems on my Linux boxes ;) Alexander Skwar -- I wasn't recommending that we make the links for them, only provide them with the tools to do so if they want to take the gamble (or the gambol). -- Larry Wall in <[EMAIL PROTECTED]> -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: Mount and write ntfs (natively)
Harry Putnam <[EMAIL PROTECTED]> writes: > Alexander, Do you know if the system described above is what ntfs-g3 > does too? One could never determine something that basic from the man page supplied with it. After reading it, I still know nothing about how it works. With a disk mounted under this tool can one simply say `echo data >file' and `file' appears and can be edited? -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: Mount and write ntfs (natively)
Gian Domeni Calgeer <[EMAIL PROTECTED]> writes: >> > Or does anyone know if any of the Live CDs `knoppix' style have this >> > tool on board? >> >> ntfs3g is *VERY* *VERY* new. I don't think that a "knoppix style" >> CD already has it. But I *bet*, that they'll have it quite soon. > > Hi > > On > http://sourceforge.net/mailarchive/forum.php?thread_id=29233640&forum_id=2697 > Szakacsits Szabolcs mentions a LiveCD called Puppy which has ntfs-3g > installed. See > http://www.puppyos.net/. I haven't tried it, though. PS a not to Alexander below this quote: Looking thru those pages a bit I find that puppys support ntfs is a system where it creates a file and then can write only inside that file. ie, no ability to freely write to ntfs, like create/delete files. http://www.puppyos.com/faq.htm Q: NTFS partition I have Windows XP installed on my computer, and the hard drive is partitioned with a single NTFS partition. When I boot up with the Puppy live-CD, the "home" file is not created on /root, so I can't have any permanent storage. Why doesn't Puppy work with NTFS? A: When the live-CD boots up, Puppy looks for a vfat, ext2/3 or reiserfs partition, in that order, and if found creates a 256M file on it, named "pup001". This file is actually a complete ext2 filesystem, and Puppy mounts this on /root, and it becomes your home folder and keeps all your personal files and settings. This is a very safe technique and is unlikely to mess up your hard drive as no partitions are being created or modified, just a file created. Anyway, this technique has a problem when it comes to NTFS. Linux support for NTFS is not yet complete, and currently an NTFS partition can be mounted read-only but not written (safely) to. When Puppy boots up, if he can't find a vfat, ext2/3 or reiserfs partition, he gives up and only uses the ramdisk. HOWEVER, Puppy version 0.9.7+ does have limited NTFS write support. That is, the Linux NTFS driver can safely write to a file if it already exists, but cannot safely create or resize a file. SOLUTION: bootup Windows XP, download pup001.zip from the Puppy download site, unzip it (and you will then have a single file called pup001) and move it to C:\ (the top-level in the C: drive). Now reboot the Puppy live-CD and Puppy will use the pre-existing pup001 file as your home data file. Simple! = Alexander, Do you know if the system described above is what ntfs-g3 does too? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Mount and write ntfs (natively)
> > Or does anyone know if any of the Live CDs `knoppix' style have this > > tool on board? > > ntfs3g is *VERY* *VERY* new. I don't think that a "knoppix style" > CD already has it. But I *bet*, that they'll have it quite soon. Hi On http://sourceforge.net/mailarchive/forum.php?thread_id=29233640&forum_id=2697 Szakacsits Szabolcs mentions a LiveCD called Puppy which has ntfs-3g installed. See http://www.puppyos.net/. I haven't tried it, though. Gian -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Mount and write ntfs (natively)
[EMAIL PROTECTED] schrieb: Peter Ruskin <[EMAIL PROTECTED]> writes: Yes. It's called ntfs3g. There's an ebuild for it. Thanks for that tip, Alexander - it works well here. Peter or Alexander, can you give a few details of what you are able to do with it? I don't use it - I just read about it. Can I put that on a live CD and boot with the cd, then be able to mount an ntfs disk and write to it? Yes, you should be able to do so. The great thing is, that you don't need no Windows libraries, in contrast to the "Captive approach". And you're able to write to NTFS. Or does anyone know if any of the Live CDs `knoppix' style have this tool on board? ntfs3g is *VERY* *VERY* new. I don't think that a "knoppix style" CD already has it. But I *bet*, that they'll have it quite soon. Alexander Skwar -- "What you end up with, after running an operating system concept through these many marketing coffee filters, is something not unlike plain hot water." (By Matt Welsh) -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: Mount and write ntfs (natively)
Peter Ruskin <[EMAIL PROTECTED]> writes: >> Yes. It's called ntfs3g. There's an ebuild for it. >> > Thanks for that tip, Alexander - it works well here. Peter or Alexander, can you give a few details of what you are able to do with it? Can I put that on a live CD and boot with the cd, then be able to mount an ntfs disk and write to it? Or does anyone know if any of the Live CDs `knoppix' style have this tool on board? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: mount: unknown filesystem type 'ext2'
> > Hello, I'm trying to upgrade my server to the latest hardened-sources > > kernel. I'm trying to mount my /dev/hda1 partition to /boot but I'm > > getting the error: > > > > mount: unknown filesystem type 'ext2' > > > > It's true that I don't have ext2 support compiled into my kernel, but I > > never have. My /etc/fstab looks like this: > > > > /dev/hda1 /boot ext3 noauto,noatime 1 2 > > > should it be ext2 above? The filesystem is ext3 as notated in fstab. > > Does anyone know what's going on here? > > > do you have an initrd loading? Without some kernel support, it can't load > at all? Check your lilo or grub configuration and make sure you have some > kind of initrd with ext2 loading. I don't think I have anything like that going. Here's my grub.conf: --- timeout 2 default 0 fallback 1 title Gentoo Linux 2.6.14-hardened-r2 root (hd0,0) kernel /kernel-2.6.14-hardened-r2 root=/dev/hda3 video=vesafb,mtrr vga=0x318 title Gentoo Linux 2.6.14-hardened-r1 (Fallback) root (hd0,0) kernel /kernel-2.6.14-hardened-r1_fallback root=/dev/hda3 video=vesafb,mtrr vga=0x318 --- Maybe this is a bug in one of the packages I've updated recently? - Grant -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: mount: unknown filesystem type 'ext2'
On Wed, 28 Dec 2005 09:15:14 -0800, Grant wrote: > Hello, I'm trying to upgrade my server to the latest hardened-sources > kernel. I'm trying to mount my /dev/hda1 partition to /boot but I'm > getting the error: > > mount: unknown filesystem type 'ext2' > > It's true that I don't have ext2 support compiled into my kernel, but I > never have. My /etc/fstab looks like this: > > /dev/hda1 /boot ext3 noauto,noatime 1 2 > should it be ext2 above? > Does anyone know what's going on here? > do you have an initrd loading? Without some kernel support, it can't load at all? Check your lilo or grub configuration and make sure you have some kind of initrd with ext2 loading. > - Grant Probably something really dumb! Inasmuch as it _had_ been working! -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: mount umount and xterm freeze
Harry Putnam <[EMAIL PROTECTED]> writes: > Still I can't get to those shares without a reboot of gentoo it seems. > That reboot must clear something that probably can be cleared manually > without a reboot Even the above referenced reboot was frozen at the point of umounting local fs. Requiring a hard reboot. Any ideas whats behind this persistent mount problem? -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: mount umount and xterm freeze
Neil Bothwick <[EMAIL PROTECTED]> writes: > On Fri, 21 Oct 2005 06:02:07 -0500, Harry Putnam wrote: > >> So far I've used the old MS refrain `reboot, reboot, and reboot' to >> clear up the mounts but I'm sure there is some better way or maybe a >> way to prevent this from the start. > > umount -l /mount/point Using that I see the problem mnts disappear from `mount' output alright. But those shares cannot be remounted following that command. Trying to mount them following the umount -l (1 hr later). Just hangs the command. However it isn't such a persistent hang and the normal ^c will kill it. Still I can't get to those shares without a reboot of gentoo it seems. That reboot must clear something that probably can be cleared manually without a reboot -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: mount mac disks?
On 10/15/05, Mark Knecht <[EMAIL PROTECTED]> wrote: I found HFS & HFSPLUS file system support in the kernel so I'mbuilding that now. Actually OS X disks are formated HFS+ so no need to build HFS support. There are also hfsutils and hfsplusutils but the later seems to bemasked in a way that I don't know how to get around: Hack the ebuild :-) (and submit the patch). lightning linux # emerge -pv hfsutils hfsplusutilsThese are the packages that I would merge, in order: Calculating dependencies -!!! All ebuilds that could satisfy "hfsplusutils" have been masked.!!! One of the following masked packages is required to complete your request:- sys-fs/hfsplusutils- 1.0.4 (masked by: missing keyword)- sys-fs/hfsplusutils-1.0.4-r1 (masked by: missing keyword)For more information, see MASKED PACKAGES section in the emerge man page orsection 2.2 "Software Availability" in the Gentoo Handbook. -- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationLinux, because reboots are for installing hardware. "In a world without walls and fences, who needs windows and gates?"
[gentoo-user] Re: mount mac disks?
I found HFS & HFSPLUS file system support in the kernel so I'm building that now. There are also hfsutils and hfsplusutils but the later seems to be masked in a way that I don't know how to get around: lightning linux # emerge -pv hfsutils hfsplusutils These are the packages that I would merge, in order: Calculating dependencies - !!! All ebuilds that could satisfy "hfsplusutils" have been masked. !!! One of the following masked packages is required to complete your request: - sys-fs/hfsplusutils-1.0.4 (masked by: missing keyword) - sys-fs/hfsplusutils-1.0.4-r1 (masked by: missing keyword) For more information, see MASKED PACKAGES section in the emerge man page or section 2.2 "Software Availability" in the Gentoo Handbook. lightning linux # emerge -pv hfsutils These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N] sys-fs/hfsutils-3.2.6-r4 +tcltk 202 kB Total size of downloads: 202 kB lightning linux # Thanks, Mark On 10/15/05, Mark Knecht <[EMAIL PROTECTED]> wrote: > Good afternoon, >Not a topic I see come up a lot. I finally bought my first Mac - a > Mac Mini - and I'm fiddling around with external 1394 drives. If I use > MSDOS as a file system for the drive then I have no trouble mounting > the drive on any of my systems, but it made me wonder if I can format > the drive using an Apple native partition type and mount that under > Gentoo? > >Is it possible? > >I had been assuming that since OS X is based on BSD Linux that it > would be happy mounting ext3 drives but it doesn't mount them at all, > at least using their default tools that recognized a 1394 drive when > it's plugged in. > >Thanks in advance for info in this area. I've never used a Mac and > bought this one on a whim after selling my x86 laptop. Not sure if I'm > going to continue running OS X on it or whether I might try Gentoo. > > Cheers, > Mark > > -- gentoo-user@gentoo.org mailing list
[gentoo-user] Re: mount
On Thursday 14 April 2005 22:12, Al Bayrouni wrote: > Hello all, > > I want to mount an iso file ont /mnt/iso directorie. > I have this message when I run this command: > > > mount /mnt/packages-x86-2005.0.iso /mnt/iso -o loop=/dev/loop0, > > /dev/loop0: no such file or directorie mount -o loop /mnt/packages-x86-2005.0.iso /mnt/iso Ciao Francesco -- Linux Version 2.6.11.5, Compiled #1 Wed Mar 30 07:26:00 CEST 2005 One 1.53GHz AMD Athlon XP Processor, 2.5GB RAM, 3022.84 Bogomips Total macula -- gentoo-user@gentoo.org mailing list
