On Tue, 26 Oct 1999,mshirley wrote:
| -----Original Message-----
| From: Ernest N. Wilcox Jr. [mailto:[EMAIL PROTECTED]]
| Sent: Tuesday, October 26, 1999 12:23 PM
| To: [EMAIL PROTECTED]
| Subject: Re: [newbie] Way to make an updated 6.0 CD?
|
|
| On Tue, 26 Oct 1999,Thomas J. Hamman wrote:
| | On Tue, 26 Oct 1999, mshirley wrote:
| |
| | > With all the problems with 6.1, is there a way to
| | > make an updated 6.0 CD so that all the updates are
| | > installed automagically? IE, I put the CD in, and
| | > run install, etc, and get the new kernal, initscripts,
| | > and heck even the new 2.2.13 kernal and XFree86 even.
| | > Is there a file used for installation that says what files
| | > are on the CD?
| |
| | Technically you could, yes. You'd just remove the packages you're
| replacing
| | from Mandrake/RPMS, put the newer packages you want to use in
| Mandrake/RPMS,
| | and then from the base of the distribution tree run:
| |
| | ./misc/genhdlist .
| |
| | To update the hdlist with the new packages.
| |
| | That's what I did when I made an updated M6.0 CD (with the updates
| specifically
| | for 6.0). I can foresee you possibly having dependency problems when
| trying to
| | mix 6.1 packages in, though; it's quite likely that there are slightly
| newer
| | versions for some libraries (like gtk, qt, etc.) in 6.1 that some
| packages in
| | 6.1 depend on, so you would need to add them too (and might as well toss
| in the
| | newer development packages while you're at it). But THEN you MIGHT (or
| might
| | not, your guess is as good as mine) break some of the 6.0 packages that
| are
| | linked with slightly older libraries from 6.0.
| |
| | If you haven't actually tried 6.1 yet, I'd suggest giving it a try. It
| works
| | great for me, and my impression of it is that it's less buggy than 6.0.
| There
| | were some updates for 6.0 that ya just HAD to get, but I didn't even
| bother
| | getting the 6.1 updates until I was burning a CD for a friend and
| figured I
| | might as well put the existing updates on it.
| |
| | > Secondly, once I get this ready, can it be burnt in *GAK*
| | > Windows, or do I actually need to figure out XCDroast?
| |
| | As far as I know, burning in Windows should be fine. Though I don't
| know if
| | Windows burning programs allow you to use Rock Ridge extensions? I'd
| think you
| | would want a Linux CD burned with Rock Ridge extensions (it's like the
| Linux
| | version of Windows' Joliet).
| |
| | -Tom
|
| Mandrake 6.1 works great here. The only problem I have found is that there
| apears to be a conflict between the kcmclock package and the kdelibs
| package.
| If you have this problem, remove the kcmclock package, and install the
| kdelibs
| package in kpackage. Problem solved!
|
| Ernie
|
|
| I have been following the banter from Steve Philps and Axalon about how
| broken 6.1 is,
| and don't even want to touch it until the SECOND bug fix is out. 6.0 works
| well for me,
| but have been unable to get the fix packages to install correctly, and
| thought that since
| I am still learning, and hence, screwing up my installs bad enough that I
| need to reinstall
| every now and then, that I would make an updated 6.0 CD, that way I have one
| less step every
| time I reinstall.
|
| On that note, when updating the kernal and initscripts for instance, how do
| I get the package
| to install? De-install the kernal and then reinstall the new one, then
| update lilo? or the other
| way around? Secondly, how do you update lilo that is on a floppy? I don't
| have lilo on the MBR.
|
| Know-nothing,
| Mark
Oops! Almost forgot! After you install the new kernel, you need to edit the
/etc/lilo.conf file to use the new kernel. I recommend you add a new section
for the new kernel (temporarily), and keep the old setup available for a while,
just in case <grin>. I have put a copy of my lilo.conf in as an example. The
part you need to duplicate starts with the "image = " line, and includes any
indented lines below it until the next unindented line. Simply insert a new
section under the existing one, but refering to the new kernel, and with a new
label (lilo must have a unique key sequence for each entry). For example, my
previous image = line was "image = /boot/vmlinuz-2.2.13-4mdk", and for the temp
section I used "image = vmlinuz-2.2.13-7mdk", "append = "mem=80""and "label =
k". Save the file, and run lilo from a console. This will add the new settings
to the lilo boot loader. I think the lilo.conf file will have a boot = line
something like "boot = /dev/fd0". If this is the case, you will need the boot
floppy in the floppy drive when you run lilo. I think the boot = line tells
lilo where to put the boot loader with the new information. Then when you
restart the system to try out the new kernel, use the key sequence used in the
label line (in my case, "k") to start the new kernel. If all is well, you can
then edit the /etc/lilo.conf file again to remove the temporary entry, and set
up the permanent entry for the new kernel. And finally re run lilo as before to
install the new settings, and you are done.
boot = /dev/hda
timeout = 50
prompt
message = /boot/StartMessage.txt
default = w
vga = normal
read-only
map=/boot/map
install=/boot/boot.b
image = /boot/vmlinuz-2.2.13-7mdk
label = l
append = "mem=80M"
root = /dev/hda3
other = /dev/hda1
label = w
table=/dev/hda
Note that each lilo.conf file is specific to the machine and user. Yours will
not have the same information as mine, but the image =, label =, and root =
lines will exist. They will contain information specific to your machine and
configuration. The append = line in my lilo.conf file is a hold over from when
I used RedHat 5.2, it was needed to let the system know to use all 80 Meg of
ram (Linux used by default only 64 Meg then). Since I do not know if this has
changed, and the setting improved performance on my old 486-style box, I keep
it. It's not doing any harm.
It's a good thing I didn't get all this on one message! I do go on, don't I ?
Ernie
