Re: With Fedora Core 4 ---- how to access CD during post installation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Mogens,

Thank you very much for your reply and I tried the
following things according to your suggestions:

1)
mount -t iso9660 /dev/hda /tmp/one >/root/mounta.log >
2>&1
mount -t iso9660 /dev/hdb /tmp/one >/root/mountb.log >
2>&1
mount -t iso9660 /dev/hdc /tmp/one >/root/mountc.log >
2>&1
mount -t iso9660 /dev/hdd /tmp/one >/root/mountd.log >
2>&1
mount -t iso9660 /dev/hde /tmp/one >/root/mounte.log >
2>&1
mount -t iso9660 /dev/hdf /tmp/one >/root/mountf.log >
2>&1

mount -t iso9660 /dev/sda /tmp/one >/root/mountaa.log
> 2>&1
mount -t iso9660 /dev/sdb /tmp/one >/root/mountbb.log
> 2>&1
mount -t iso9660 /dev/sdc /tmp/one >/root/mountcc.log
> 2>&1
mount -t iso9660 /dev/sdd /tmp/one >/root/mountdd.log
> 2>&1
mount -t iso9660 /dev/sde /tmp/one >/root/mountee.log
> 2>&1
mount -t iso9660 /dev/sdf /tmp/one >/root/mountff.log
> 2>&1

mounta.log shows: mount: special device /dev/hda does
not exist
mountb.log shows: mount: special device /dev/hdb does
not exist

mountc.log, mountd.log, mounte.log, mountf.log,
mountbb.log, mountcc.log, mountdd.log, mountee.log and
mountff.log all show similar info as mounta.log and
mountb.log, complain special device /dev/hdx /dev/sdx
does not exist.

only mountaa.log shows: mount: /dev/sda already
mounted or /tmp/one busy.

which means only /dev/sda is recognized by Fedora Core
4 at post the installation time. all the rest devices
are not recognized by Fedora Core 4 during that time.

2) df >/root/df.log 2>&1

the content of df.log is as follows:

Filesystem           1K-blocks      Used Available
Use% Mounted on
/dev/sda3             74921528   2041844  69012440  
3% /
/dev/sda1               248895     13523    222522  
6% /boot

no info about cdrom during post installation time.

3) cat /etc/fstab |grep cd >/root/fs.log 2>&1

fs.log is an empty file, which means at the post
installation time, fstab has no information about
CDROM.

So my problem is: I have a tarball on CDROM which is
needed to be moved to hard drive, how can I copy this
tarball to hard drive?

RedHat 9.0 doesn't have this problem, RedHat 9.0 can
recognize cdrom at the post installation time, But
Fedora Core 4 seems not. This doesn't make sense, for
Fedora Core 4 suppose to be improved based on RedHat
9.0, My head is hurt a lot.

Any further suggestions will be highly appreciated!


jing




 

--- Mogens Kjaer <mk@xxxxxx> wrote:

> jing han wrote:
> ...
> > 
> > I found "mount -t iso9660 /dev/hda /tmp/one
> >/dev/null
> > 2>&1" doesn't work for me, which means I cannot
> copy
> > myCustom.tgz to hard drive.
> 
> I use a mount in %post in my kickstart file,
> however,
> this is for mounting an NFS drive during a network
> install.
> 
> It works fine.
> 
> Could you change the line into:
> 
> mount -t iso9660 /dev/hda /tmp/one >/root/mount.log
> 2>&1
> 
> and look into /root/mount.log after reboot and see
> if there's an error
> message?
> 
> Maybe it's because /dev/hda is already mounted?
> 
> Try adding a
> 
> df >/root/df.log 2>&1
> 
> and see which mounts are available.
> 
> Mogens
> 
> -- 
> Mogens Kjaer, Carlsberg A/S, Computer Department
> Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
> Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
> Email: mk@xxxxxx Homepage: http://www.crc.dk
> 
> -- 
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
> 



		
__________________________________________ 
Yahoo! DSL ? Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux