Bug#172244: Problem using ext3
* Pete Ryland
| My system has 2 realteks. I wasn't phased by needing to manually select the
| module, but it will be nice when it works perfectly.
Will be fixed with discover 2.
| 'Load installer modules' would be confusing to a newbie. IMO, this should
| be made simpler to understand - maybe even removed. I didn't need any
| modules anyway. :)
Huh? You did have to download the extra modules to be able to mkfs,
partition and such?
| I was able to partition my drives to ext3 and mount them, but what I failed
| to realise for a bit was that they weren't actually mounted since ext3
| wasn't in the kernel and wasn't there as a module. HOWEVER, the
| installation still proceeded to install without having the devices mounted!
This is bad, but I wonder why the kernel didn't pick up the ext3.
Perhaps this is the cause of some strange errors I've seen where ext3
hasn't worked. It seems like the default kernel doesn't support ext3,
a bug has been filed to correct this.
Also, di-utils-mount-partitions should fail if it can't mount the
partition; I don't know why this didn't happen; mount failing should
have caused the postinst to fail. (We should probably say something
like «We tried to mount $partition, but failed, perhaps the kernel
doesn't support the file system».)
| Another thing is that I didn't need to look for a cdrom, but it kept making
| that the default option, even when I was up to the later stages of the
| install. Otherwise the default options were nicely done.
Known problem; will be fixed once we have the correct priorities in
the archive. A bug has already been filed.
| Anyway, it has worked with ext2 now, and it's just booted nicely into my new
| install. :) You forgot to tell me to take the floppy out though! :)
Yup, should probably do that.
--
Tollef Fog Heen ,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
`. `'
`-
Reply to: