Follow-up: FreeBSD box can't access CD ROM??

Sun Dec 30 13:31:25 GMT 2001

This is a multi-part message in MIME format.

------=_NextPart_000_0022_01C19136.4731EBC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks to Joe, Martin and Andrew for the helpful suggestions.

I've tried to answer your follow-ups below:

The "mount /cdrom" command is given while logged in as "root" from the =
/root directory.

"mount" on its own gives:

/dev/ad0s1a on / (ufs, local, writes: sync 6 async 18, reads: sync 192 =
async 0)
/dev/ad0s1f on /usr (ufs, local, writes: sync 5 async 31, reads: sync =
395 async 96)
/dev/ad0s1e on /var (ufs, local, writes: sync 115 async 137, reads: sync =
29 async 0)
procfs on /proc (procfs, local)

The "Cheap*Bytes" FreeBSD 4.0 CD is one I bought from The Linux Emporium =
in Wallingford. As far as I'm aware there's no intrinsic problem with =
it. Yes, Andrew, I've used the CD to install FreeBSD in a dual-boot =
configuration with Win98 on my laptop and that runs fine, yet as far as =
I'm aware there's nothing out-of-the-ordinary about the CD ROM drive in =
the desktop FreeBSD box which is having the probs. The drive was working =
fine when that machine was an MS Windows box. I could try the drive in =
another machine, but not without some disruption to the family's =
computing habits, so I'll try other approaches first!

Your suggestion, Martin, of doing a cvsup sounds like it may be worth a =
try. I know (in theory) how to go about it, but I've yet to bite the =
bullet and actually do it.=20

Many thanks for your help

Cheers
Charles Brewster

------=_NextPart_000_0022_01C19136.4731EBC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks to Joe, Martin and Andrew for =
the helpful=20
suggestions.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I've tried to answer your follow-ups=20
below:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The "mount /cdrom" command is given =
while logged in=20
as "root" from the /root directory.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>"mount" on its own gives:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>/dev/ad0s1a on / (ufs, local, writes: =
sync 6 async=20
18, reads: sync 192 async 0)<BR>/dev/ad0s1f on /usr (ufs, local, writes: =
sync 5=20
async 31, reads: sync 395 async 96)<BR>/dev/ad0s1e on /var (ufs, local, =
writes:=20
sync 115 async 137, reads: sync 29 async 0)<BR>procfs on /proc (procfs,=20
local)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The "Cheap*Bytes" FreeBSD 4.0 CD is one =
I bought=20
from The Linux Emporium in Wallingford. As far as I'm aware there's no =
intrinsic=20
problem with it. Yes, Andrew, I've used the CD to install FreeBSD in a =
dual-boot=20
configuration with Win98 on my laptop and that runs fine, yet as far as =
I'm=20
aware there's nothing out-of-the-ordinary about the CD ROM drive in the =
desktop=20
FreeBSD box which is having the probs. The drive was working fine when =
that=20
machine was an MS Windows box. I could try the drive in another machine, =
but not=20
without some disruption to the family's computing habits, so I'll try =
other=20
approaches first!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Your suggestion, Martin, of doing a =
cvsup sounds=20
like it may be worth a try. I know (in theory) how to go about it, but =
I've yet=20
to bite the bullet and actually do it. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Many thanks for your help</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Cheers<BR>Charles Brewster</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0022_01C19136.4731EBC0--