Subject: Re: Compiling Kernel (long!)
To: NetBSD/Atari mailing list <port-atari@NetBSD.ORG>
From: Waldi Ravens <waldi@moacs.indiv.nl.net>
List: port-atari
Date: 02/07/1996 22:12:27
Hallo Andreas,
> ps won't work. /netbsd no such file ... a ll /gemdos say
> ls: q???????.??? no such file ...
[ ... ]
> ---------- /etc/fstab ----------
> /dev/sd0a / ffs rw 1 1
> /dev/sd0j /usr ffs rw 1 2
> /dev/sd0k /usr/local ffs rw 1 2
> /dev/sd0d /gemdos msdos rw 1 2 =
>
> ---------- end /etc/fstab ----------
The msdosfs driver has changed. You will need a new mount_msdos
and add the -G option in /etc/fstab.
A couple of weeks ago the change was announced by Leo. I guess
it's important enough to repost for those who joined in later:
Message-Id: <m0te1Mx-0000ABC@waux11.wau.mis.ah.nl>
From: leo@wau.mis.ah.nl (Leo Weppelman)
To: port-atari@NetBSD.ORG
Subject: msdosfs-changes
Hallo,
For those of you that compile kernels from the -current sources, there
is a pitfall in the msdosfs-changes I committed to the cvs-tree this week.
Up until now, the atari kernel treated the msdosfs like it was a gemdos
made filesystem automatically. The msdosfs kernel code contained a bunch
of '#ifdef atari' statements to accomplish this. As this was:
1) 'Could be done better' programming
2) Did not permit you to use the 'real' msdosfs
I decided to change the '#ifdef's to testing a mount-settable flag. The
latest mount_msdos has a '-G' option to tell the kernel the filesystem
mounted is the gemdos flavour of msdosfs.
In practice, this means that you should add the '-G' flag when you mount
an msdosfs that was created by GEM, and leave it out when mounting filesystems
created by msdos or tools that create filesystems compliant to it (like
newdosfs).
So when you decide to update to the latest -current, please get the
latest sources of mount_msdos _and_ sys/mount.h.
Leo.
> /dev/fd0a wont work, while mount_msdos /dev/fd0a /mnt there is a I/O error
> Device not configured. What is to do to get the floppy working?
fd?a => single sided floppy (80 tracks, 9 sectors/track)
fd?b => double sided floppy (2*80 tracks, 9 sectors/track)
fd?c => double sided, high density (2*80 tracks, 18 sectors/track)
(extra density is not supported)
You probably inserted a dsdd or dshd floppy. Try a different floppy,
or use the appropriate device.
Regards,
Waldi