On Wed, 2002-12-25 at 15:59, [EMAIL PROTECTED] wrote:
I did what you suggested, i.e., manually mount the CDROM with:
# mount /dev/hdd /mnt/cdrom
and I got the following:
/dev/hdd: Input/output error
mount: block device /dev/hdd is write-protected, mounting read-only
/dev/hdd: Input/output error
mount: you must specify the filesystem type
By the way, # ls /mnt
shows me:
cdrom cdrw floppy
As of right now, I am going to stop messing with it so as to limit the
number of variables. I will gladly provide one and all any information
necessary to further troubleshoot this.
Thank you.
Send redhat-list mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://listman.redhat.com/mailman/listinfo/redhat-list
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of redhat-list digest..."
Today's Topics:
1. Re: software (Alan Harding)
2. next question on kernels -- the config files (Robert P. J. Day)
3. Re: CDROM CDRW Not Accessible (Alan Harding)
4. Re: Anyone on product life span? (Ben Russo)
5. Re: next question on kernels -- the config files (Michael Schwendt)
6. VoIP Telephony (Henry The BIG)
7. Happy Holidays! (Christopher Henderson)
8. Re: Unable to build a custom kernel since 2.4.18-5 (Michael H. Warfield)
9. Re: Unable to build a custom kernel since 2.4.18-5 (Michael H. Warfield)
10. Re: Unable to build a custom kernel since 2.4.18-5 (Robert P. J. Day)
11. Re: CDROM CDRW Not Accessible (Mike Burger)
--__--__--
Message: 1
Subject: Re: software
From: Alan Harding <[EMAIL PROTECTED]>
To: Redhat List <[EMAIL PROTECTED]>
Organization:
Date: 25 Dec 2002 17:22:50 +0000
Reply-To: [EMAIL PROTECTED]
On Sun, 2002-12-22 at 17:30, Andrew Pasquale wrote:
> On Sun, Dec 22, 2002 at 12:13:01PM -0500 or thereabouts, Dave Eells wrote:
> > Are there websites where I can go to download freeware for RH 8.0?
> > Ex:gnucash is the financial software that comes with 8.0 but it is not
> > an acceptable software to me. Is there freeware financial software that
> > would equal quicken? Thanks
> >
>
> There are lots of sites to download software. Google is your friend :)
>
> Try searches like "linux money management" and see what you can find. There
seem to be quite a few options. Personally, I like gnuCash alright, though it takes
some getting used to.
>
> If you must have quicken, check out Crossover Office from CodeWeavers.
Reportedly, quicken now runs on linux:
>
> http://desktoplinux.com/articles/AT2282537026.html
>
> HTH
>
> --
> Andrew Pasquale
As a slight Aside, try http://www.google.com/linux all the searches
you make are then related to linux information automatically.
(ps there is also a /microsoft, /mac, /bsd as well)
Enjoy
--
Alan & Jan Harding
Tel: 07715 539272
"One by one the penguins are stealing my sanity"
--__--__--
Message: 2
Date: Wed, 25 Dec 2002 12:09:02 -0500 (EST)
From: "Robert P. J. Day" <[EMAIL PROTECTED]>
To: redhat mailing list <[EMAIL PROTECTED]>
Subject: next question on kernels -- the config files
Reply-To: [EMAIL PROTECTED]
some of this has come up before, but i wanted to make dead
sure i got it right.
occasionally, someone asks "where is the config file for
the currently running kernel?", and the answer is that a
number of config files reside in the kernel directory
/usr/src/linux-???/configs. you just have to choose the
one that corresponds to how your machine was installed.
but there are more config files than prebuilt binary
kernel RPMs, which leads one to ask:
1) for the config files that appear to match a binary
kernel RPM, is this *exactly* the config file that
was used to build the corresponding RPM?
2) what are the other config files for? just suggestions
or starting points if someone wants help getting going?
i've also noticed the config file .../arch/i386/defconfig
in the kernel source directory. what does this represent?
it's part of the actual kernel-source RPM, so i would guess
it's the config file to be used for a kernel configuration
if there is no .config file. is that correct?
and finally, for those who hadn't noticed, there is a
kernel config option to actually build the config file
into the new kernel itself. that config file can (allegedly)
be extracted with the script .../scripts/extract-ikconfig,
again in the kernel source directory. (i say "allegedly"
since i bugzilla'ed it once for not working, and i'm just
about to check if it's better).
rday
--__--__--
Message: 3
Subject: Re: CDROM CDRW Not Accessible
From: Alan Harding <[EMAIL PROTECTED]>
To: Redhat List <[EMAIL PROTECTED]>
Organization:
Date: 25 Dec 2002 17:32:17 +0000
Reply-To: [EMAIL PROTECTED]
On Wed, 2002-12-25 at 15:08, Thomas A. Hulslander wrote:
> OK. I found vi tutorial on line and found our that saving is done with
> ZZ. Who would have guessed. I think that I have successfully added the
> following to fstab:
>
> /dev/hdc /mnt/cdrw iso9660 noauto,owner,kudzu,ro 0 0
> /dev/hdd /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
>
> Now, however, when I try to access the CDROM I get the following:
>
> Could not mount device.
> The reported error was:
> mount: wrong fs type, bad option, bad superblock on /dev/hdd,
> or too many mounted file systems
>
> And in webmin I get this:
>
> mount -t iso9660 -o "user,owner,ro,mode=444,kudzu" /dev/hdd /mnt/cdrom :
> mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too
> many mounted file systems
>
> One other thing that worries me and may be contributing to this is the
> fact that when I run vi to access fstab I get messages about multiple
> fstab swaps being found. hmmm ??
>
> Any suggestions? I'd really like to get this cleaned up and feel good
> about the system again. It's feeling sloppy and really bothering me.
> Excruciating detail is very much appreciated.
>
> Thanks all!
one thing you could look at is mounting by hand from the console.
First check that /mnt/cdrom and /mnt/cdrw exist ( ls /mnt )
if they do then just try the basic
#> mount /dev/hdd /mnt/cdrom
#> mount /dev/hdc /mnt/cdrw
see if that works. We are all assuming that hdd, and hdc are the devices
in the dev folder, but that may not be true. Can you give a listing of
Dmesg??
#> dmesg (at the console prompt
Have a good one
--
Alan & Jan Harding
Tel: 07715 539272
"One by one the penguins are stealing my sanity"
--__--__--
Message: 4
Subject: Re: Anyone on product life span?
From: Ben Russo <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: 25 Dec 2002 13:18:24 -0500
Reply-To: [EMAIL PROTECTED]
On Mon, 2002-12-23 at 13:49, Leonard den Ottolander wrote:
> Hi,
>
> I am a little surprised that I haven't heard anyone on the new "product end
> of life" policy. Maybe I haven't been looking to well though...
RedHat is trying to make money.
I don't disparage RedHat for what they are doing.
They are not being "bad" or "evil" or anything like that....
No one should be expected to give things away for free.
For my personal uses of RedHat, (my home firewall and PC)
it is no big deal to upgrade my boxes to a new version once a year
or so. And I couldn't afford buying Windows 2000/XP and all the
software to set up firewalling/DHCP Cacheing DNS, Web Server, Mail
Server, Security programs, VPN services...
((( Not to mention the problems with consistency, stability
and PRIVACY/FREEDOM )))
I also would find
it expensive to pay about $800/yr to have AS on my boxes...
Also it would cramp my style to not have something closer to
the latest and greatest versions of toys that the 'base' distributions
offer.
Heck I usually have upgraded my personal boxes more than once
every 18 months anyway. I used to use Slackware in the
old days, but security wasn't as much of a concern back then.
The last few years I have skipped 7.0 and 7.1 went
straight from 6.2 to 7.2, then skipped 7.3 on my firewall and
went to 8.0 just last month. I upgraded my workstation from 7.3
to 8.0 in one day. (Yesterday)
Professionally it is a total different equation...
It is not practical to migrate our Web Services, NMS systems and
database applications to new versions of PHP/PERL/Apache/libc/binutils
and it is not feasible to ignore known security
vulnerabilities in servers that are used for business.
So what are the options? How do we cope with this?
If we only had a few servers (1-10) I would say that the Cost-Benefit
comparison of RH Advanced Server when compared to Solaris/HP-UX/Win with
the corresponding lock-ins of HW/SW and/or the TCO of possibly
maintaining our own tarball'd dists of Open Source packages for Solaris
or HP (or dealing with the variable quality of the packages from
Sunfreeware/HPPD, or the stability/support/security of Windows)
would still favor RH Advanced Server at a cost of 700-800 per year for
support.
However when we are talking about 30-50 servers that we need to keep
up2date and maintained, then the economy of scale kicks in, and RedHat
can't have their cake and eat it too. RedHat, *MUST* continue (AFAIK)
to distribute the SOURCE RPM's for the bundled binary RPM's of Open
Source packages that they ship out with Advanced server.
So, with 30-50 servers to maintain we will probably start maintaining
our own RH Advanced Server "rpbbuild" box. Where we keep downloading
and building Source RPM's as they are released, and with SSH and shared
keys we will be able (with a little scripting) to make a secure package
distribution system that will be a lot more work than up2date and rhn,
but worth less than 30 X 800 $/year
I explained to my RedHat Salesman that if we could pay for Advanced
Server in a way that reflected our alternative cost of scale....
full price for servers 1-5
80% for servers 5-10
70% for servers 10-15
60% for servers 15-20
50% for servers 20-25
and 40% for all servers over 25
That we would definitely buy and maintain support contracts on all
our Linux Servers that we need RedHat advanced server on.
This makes sense for RedHat to do as well. Because the cost of doing
good quality testing and packaging is fixed. After they make the
updates for Advanced server packages they are only paying for bandwidth.
And even that doesn't scale linearly, because most people with more than
a dozen servers will have a caching proxy server and with GPG key
checking on the packages and UseNOSSLForPackages turned on in up2date
I only download the packages once per office site.
I think that RedHat will probably do that...
If they don't, then I will be building a set of scripts to distribute
my rpmbuild'd Source Rpms that I will download for free from Redhat.
What are the downsides of this??? Well for one, I will have trouble
getting Support from Dell/Oracle/Veritas/Peregrine Systems/HighDeal
NetCool... However I get better support from the user groups for those
products than I do from the traditional support mechanisms anyway!
And, when you get to the *tough* support issues that are real bugs or
problems the "expert" support technicians aren't as by-the-book as the
on-the-phone help desk guys anyway. So I don't really see a downside.
-Ben.
--__--__--
Message: 5
Date: Wed, 25 Dec 2002 19:52:53 +0100
From: Michael Schwendt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: next question on kernels -- the config files
Reply-To: [EMAIL PROTECTED]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 25 Dec 2002 12:09:02 -0500 (EST), Robert P. J. Day wrote:
> some of this has come up before, but i wanted to make dead
> sure i got it right.
>
> occasionally, someone asks "where is the config file for
> the currently running kernel?", and the answer is that a
> number of config files reside in the kernel directory
> /usr/src/linux-???/configs. you just have to choose the
> one that corresponds to how your machine was installed.
Another answer is to use the config file in:
/boot/config-$(uname -r)
> but there are more config files than prebuilt binary
> kernel RPMs, which leads one to ask:
>
> 1) for the config files that appear to match a binary
> kernel RPM, is this *exactly* the config file that
> was used to build the corresponding RPM?
Yes.
> 2) what are the other config files for? just suggestions
> or starting points if someone wants help getting going?
Which ones exactly?
> i've also noticed the config file .../arch/i386/defconfig
> in the kernel source directory. what does this represent?
Hmm, architecture-dependent defaults? Try:
cd /usr/src/linux-2.4
grep defconfig * -R
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+Cf6F0iMVcrivHFQRAkZpAJ9bJckLP+Xcy9CxfqhBdQhg8/AhBwCfaAcy
mAXP6bzfymEE1eF4YvZukxQ=
=040o
-----END PGP SIGNATURE-----
--__--__--
Message: 6
From: "Henry The BIG" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: VoIP Telephony
Date: Wed, 25 Dec 2002 14:01:55 -0500
Reply-To: [EMAIL PROTECTED]
Hi,
Where can I find a free VoIP Telephony server on Internet?
Thank you,
Henry
--__--__--
Message: 7
Subject: Happy Holidays!
From: Christopher Henderson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Organization:
Date: 25 Dec 2002 13:02:39 -0600
Reply-To: [EMAIL PROTECTED]
Happy holidays to everyone on the list!
~Christopher
--__--__--
Message: 8
Date: Wed, 25 Dec 2002 14:02:36 -0500
From: "Michael H. Warfield" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Unable to build a custom kernel since 2.4.18-5
Reply-To: [EMAIL PROTECTED]
--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Dec 24, 2002 at 11:51:46PM -0800, Jack Bowling wrote:
> On Wed, Dec 25, 2002 at 12:27:14AM -0500, Michael H. Warfield wrote:
> > Hello all,
> >=20
> > Bad day... Bad week, and more... Last several kernel updates
> > from RedHat have been impossible to use to build custom kernel builds.
> >=20
> > I swear I must be doing something fundamental wrong but a proceedure
> > I've been using to build custom kernels from the RedHat kernel source
> > rpm just isn't working any more (and a backup proceedure is even worse).
> <snip>
> I agree with your final statement, Michael - if this were common, we
> would have heard about it by now. Seems to be user error somehow. Since
> this occurs on different boxes and with both 7.3 and 8.0 versions, that
> would tend to rule out different gcc versions being the problem. An easy
> test for RH kernels being the culprit would be to see if you could
> compile a minaline kernel. I can't see this being the root problem,
> though, knowing the usual solidness of RH kernels. I would
> check to make sure you have the proper glibc-kernheader rpms installed.
What I see in the 7.3 i386 updates directory is this:
[root@canyon i386]# ls *kern*
glibc-kernheaders-2.4-7.16.i386.rpm kernel-doc-2.4.18-18.7.x.i386.rpm
kernel-2.4.18-18.7.x.i386.rpm kernel-doc-2.4.18-19.7.x.i386.rpm
kernel-2.4.18-19.7.x.i386.rpm kernel-source-2.4.18-18.7.x.i386.rpm
kernel-BOOT-2.4.18-18.7.x.i386.rpm kernel-source-2.4.18-19.7.x.i386.rpm
kernel-BOOT-2.4.18-19.7.x.i386.rpm
What I have on this 7.3 system is this:
glibc-kernheaders-2.4-7.16
kernel-wlan-ng-0.1.14-4
kernel-wlan-ng-modules-%{linvers}-0.1.14-4
kernel-utils-2.4-8.20
kernel-source-2.4.20-2.2
kernel-wlan-ng-modules-rh73.5-0.1.14-4
kernel-pcmcia-cs-3.1.27-18
kernel-2.4.18-19.7.x
(The source is from Phoebe trying it out. I also had 2.4.18-19.7.x
on there as well - both same result).
What I have now done (or attempted) on this one system with
no other changes:
2.4.18-5 Builds 2.4.18-5custom successfully.
2.4.18-18.* Fails building modules
2.4.18-19.* Fails building modules
2.4.20-2.2 Fails building modules
Generic Builds...
Untared linux-2.4.18.tar.bz2 from redhat/SORUCES directory,
copied the .config file from the 2.4.18-19.x into the resulting directory.
"make oldconfig ; make dep bzImage ; make modules" successfully builds
a complete kernel and modules for 2.4.18.
Untared linux-2.4.20.tar.bz2 from redhat/SORUCES directory,
copied the .config file from the 2.4.20-2.2 directory into the resulting
directory. "make oldconfig ; make dep bzImage ; make modules" successfully
builds a complete kernel and modules for 2.4.20.
So...
2.4.18-5 builds fine
2.4.18 generic builds fine
2.4.20 generic builds fine
2.4.18-18.* Blows chunks building modules
2.4.19-19.* Blows chunks building modules
2.4.20-2.2 Blows chunks building modules.
All on same system, no other changes.
Next.
> --=20
> Jack Bowling
> mailto: [EMAIL PROTECTED]
Mike
--=20
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
/\/\|=3Dmhw=3D|\/\/ | (678) 463-0932 | http://www.wittsend.com/=
mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
--opJtzjQTFsWo+cga
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iQCVAwUBPgoAzOHJS0bfHdRxAQHXdwQAvm4/+qJIzKIaUOkQzBbAeMk9JHOf/xmz
RcNT522D2xQ/Fai9iazdLARwwM2GvuhdqSf4fxU2nrGJQFgJTyU1pnMyval4Q5Bx
MfGUCe4ukd5ZLBaiCDAXBfV6tulI/LKq6usMyFGm1biv/7i1Za4LExumzIN8FYGE
kYZpekaFVpE=
=bypH
-----END PGP SIGNATURE-----
--opJtzjQTFsWo+cga--
--__--__--
Message: 9
Date: Wed, 25 Dec 2002 14:08:10 -0500
From: "Michael H. Warfield" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Unable to build a custom kernel since 2.4.18-5
Reply-To: [EMAIL PROTECTED]
--eJnRUKwClWJh1Khz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Dec 25, 2002 at 01:48:01PM +0100, Michael Schwendt wrote:
> On Wed, 25 Dec 2002 00:27:14 -0500, Michael H. Warfield wrote:
> > Bad day... Bad week, and more... Last several kernel updates
> > from RedHat have been impossible to use to build custom kernel builds.
> >=20
> > I swear I must be doing something fundamental wrong but a
> > proceedure
> > I've been using to build custom kernels from the RedHat kernel source
> > rpm just isn't working any more (and a backup proceedure is even
> > worse).
> >=20
> > I need a custom kernel to add some options and add some drivers
> > (usbvision for one - mods to a kernel driver I MAINTAIN for another).=
=20
> > The proceedure I HAVE been using is to install the kernel "source" RPM
> > from the install CD's and then gone to /usr/src/linux-2.4 and copied
> > the appropriate configs/kernel{whatever} to .config and then "make
> > oldconfig ; make deps clean bzImage ; make modules" etc... Worked
> Drop "make clean" because it is obsolete. Change "make deps" to
> "make dep". And execute "make mrproper" once at the very beginning.
No harm from the "make clean". I'm in that habit since having been
a kernel developer and driver maintainer from the olden days (0.x days, my
first distro was SLS). There never WAS a need for it when building a
fresh build, anyways, and defeated some of the purpose of "makefiles".
But, there was a time when the dependencies couldn't be fully trusted so
I'm in the habit. I'll just forget about it...
That "make deps" was obviously a typo or it wouldn't have gotten
even that far! (No target for "deps" so it would have blown up immediately=
.)
Only ran "make mrproper" once, so that checks.
> > I also tried doing a "make mrproper" followed by a "make
> > xconfig"
> > where I "loaded" a "configs/kernel-2.4.18-i386.config" config file and
> > saved it. That was even WORSE! Then I couldn't even build bzImage!
> > That blew up with this error:
> Which is a known one somewhere in bugzilla. Don't use "make xconfig",
> but "make menuconfig" which doesn't suffer from that error.
Funny... That seems to work perfectly fine with the stock kernel
tarballs. I know that were WAS a problem with a couple of rev clicks,
but I haven't seen any problems with it. But noted and will be double
checked and verified.
Mike
--=20
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
/\/\|=3Dmhw=3D|\/\/ | (678) 463-0932 | http://www.wittsend.com/=
mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
--eJnRUKwClWJh1Khz
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iQCVAwUBPgoCGuHJS0bfHdRxAQFDHQQAp8g0lNHsvriBoqU45UPDFofhatX2DQQw
R5fw9glLkkMf3hrefTE+6KwLRZjLPjwUqt5XH2igfSkDgMDLElhTN3SOe9Ilh1F0
I0jVG1sp04tRFoPM3EqzZbr6qTKglh+hzxpPoGqTjeC2BDHAod0GCZluXwtuihYg
GFmgdUq+VJM=
=aILA
-----END PGP SIGNATURE-----
--eJnRUKwClWJh1Khz--
--__--__--
Message: 10
Date: Wed, 25 Dec 2002 14:47:55 -0500 (EST)
From: "Robert P. J. Day" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Unable to build a custom kernel since 2.4.18-5
Reply-To: [EMAIL PROTECTED]
On Wed, 25 Dec 2002, Michael H. Warfield wrote:
(snip)
> 2.4.18-18.* Fails building modules
> 2.4.18-19.* Fails building modules
(snip)
i'm seeing *exactly* the same thing here -- failure on
"make modules". i wasn't going to say anything since i
figured i must have done *something* wrong, but i
*completely* re-installed the source tree and tried to
build from the default config file, and "make modules"
still failed.
i'm going to poke around a bit longer, but which
kernel-source RPM is the preferred one? the
2.4.18-19 one?
rday
--__--__--
Message: 11
Date: Wed, 25 Dec 2002 15:57:18 -0500 (EST)
From: Mike Burger <[EMAIL PROTECTED]>
To: Redhat List <[EMAIL PROTECTED]>
Subject: Re: CDROM CDRW Not Accessible
Reply-To: [EMAIL PROTECTED]
He's already noted that he's put the CDRW as secondary master, and the
CDROM as secondary slave. Those are, by definition, /dev/hdc and/dev/hdd,
respectively.
On 25 Dec 2002, Alan Harding wrote:
> On Wed, 2002-12-25 at 15:08, Thomas A. Hulslander wrote:
> > OK. I found vi tutorial on line and found our that saving is done with
> > ZZ. Who would have guessed. I think that I have successfully added the
> > following to fstab:
> >
> > /dev/hdc /mnt/cdrw iso9660 noauto,owner,kudzu,ro 0 0
> > /dev/hdd /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
> >
> > Now, however, when I try to access the CDROM I get the following:
> >
> > Could not mount device.
> > The reported error was:
> > mount: wrong fs type, bad option, bad superblock on /dev/hdd,
> > or too many mounted file systems
> >
> > And in webmin I get this:
> >
> > mount -t iso9660 -o "user,owner,ro,mode=444,kudzu" /dev/hdd /mnt/cdrom :
> > mount: wrong fs type, bad option, bad superblock on /dev/hdd, or too
> > many mounted file systems
> >
> > One other thing that worries me and may be contributing to this is the
> > fact that when I run vi to access fstab I get messages about multiple
> > fstab swaps being found. hmmm ??
> >
> > Any suggestions? I'd really like to get this cleaned up and feel good
> > about the system again. It's feeling sloppy and really bothering me.
> > Excruciating detail is very much appreciated.
> >
> > Thanks all!
>
>
> one thing you could look at is mounting by hand from the console.
>
> First check that /mnt/cdrom and /mnt/cdrw exist ( ls /mnt )
> if they do then just try the basic
>
> #> mount /dev/hdd /mnt/cdrom
> #> mount /dev/hdc /mnt/cdrw
>
> see if that works. We are all assuming that hdd, and hdc are the devices
> in the dev folder, but that may not be true. Can you give a listing of
> Dmesg??
>
> #> dmesg (at the console prompt
>
> Have a good one
>
--
Mike Burger
http://www.bubbanfriends.org
Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000
--__--__--
__
redhat-list mailing list
Unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
End of redhat-list Digest
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
