Mailinglist Archive: opensuse (3254 mails)
| < Previous | Next > |
update.tar.gz not expanded during install
- From: "Houghton, Chris" <chris.houghton@xxxxxxxxx>
- Date: Wed, 11 Sep 2002 11:13:14 -0700
- Message-id: <0DCC27458EB5D51181840002A507069E034489BB@xxxxxxxxxxxxxxxxxxxxxx>
I'm trying to add a driver during installation following the instructions at
http://sdb.suse.de/de/sdb/html/hmeyer_driver_update.html.
During install the update.tar.gz and update.post files are copied over to
/update/install and the update.post file runs, apparently inside a 'chroot
/mnt' command but the tar file hasn't been extracted into the installed
system tree so the driver .o isn't there and the mkinitrd fails.
The directory names in the tar archive do not include the leading slash.
I've tried extracting the file in the update.post script but that doesn't
seem to work either.
Are there any known problems with the update method that I just haven't
found documented?
Thanks,
Chris Houghton
Intel Corp
>From http://sdb.suse.de/de/sdb/html/hmeyer_driver_update.html
Description of the boot sequence during the installation
The installation workflow performs the following steps:
The system boots from the installation CD or floppy disk
syslinux/isolinux starts up
The user presses the "ALT" key (optional, if a medium change is
necessary)
syslinux prompts the user for an "update medium" (e.g. floppy or
CD-ROM)
The user inserts the medium and presses the "Enter" key
syslinux boots into the "update" mode of linuxrc
linuxrc mounts the medium
linuxrc copies all files from /linux/suse/<arch>-<version>/install
into a directory install in a RAM disk mounted below /update (max. 8MB), all
files will be flagged as "executable"
linuxrc loads all driver modules below /linux/suse/<arch>-<version>/
modules by first unloading all modules with the same name and loading the
new modules from this directory (in the order the modules have been
installed on the medium! Take care of this if your driver modules depend on
other modules being loaded first)
linuxrc unmounts the update medium
now linuxrc kicks back and starts YaST1 or YaST2 to continue the
installation
before starting the installation of packages, YaST1/YaST2 first
execute /update/install/update.pre
after the initial installation, YaST1/YaST2 extract
/update/install/update.tar.gz in the root directory of the installed system
and run /update/install/update.post afterwards.
http://sdb.suse.de/de/sdb/html/hmeyer_driver_update.html.
During install the update.tar.gz and update.post files are copied over to
/update/install and the update.post file runs, apparently inside a 'chroot
/mnt' command but the tar file hasn't been extracted into the installed
system tree so the driver .o isn't there and the mkinitrd fails.
The directory names in the tar archive do not include the leading slash.
I've tried extracting the file in the update.post script but that doesn't
seem to work either.
Are there any known problems with the update method that I just haven't
found documented?
Thanks,
Chris Houghton
Intel Corp
>From http://sdb.suse.de/de/sdb/html/hmeyer_driver_update.html
Description of the boot sequence during the installation
The installation workflow performs the following steps:
The system boots from the installation CD or floppy disk
syslinux/isolinux starts up
The user presses the "ALT" key (optional, if a medium change is
necessary)
syslinux prompts the user for an "update medium" (e.g. floppy or
CD-ROM)
The user inserts the medium and presses the "Enter" key
syslinux boots into the "update" mode of linuxrc
linuxrc mounts the medium
linuxrc copies all files from /linux/suse/<arch>-<version>/install
into a directory install in a RAM disk mounted below /update (max. 8MB), all
files will be flagged as "executable"
linuxrc loads all driver modules below /linux/suse/<arch>-<version>/
modules by first unloading all modules with the same name and loading the
new modules from this directory (in the order the modules have been
installed on the medium! Take care of this if your driver modules depend on
other modules being loaded first)
linuxrc unmounts the update medium
now linuxrc kicks back and starts YaST1 or YaST2 to continue the
installation
before starting the installation of packages, YaST1/YaST2 first
execute /update/install/update.pre
after the initial installation, YaST1/YaST2 extract
/update/install/update.tar.gz in the root directory of the installed system
and run /update/install/update.post afterwards.
| < Previous | Next > |