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
Hi Mark,
If you are having trouble with rpm installs and updates in general, the one
thing that has given me problems is that I have a 486-style system. Due to the
way rpm is configured, it would tell me that most all the packages I tried to
install were for a diferent architecture. I mentioned this in a reply to a post
a few days ago, and Axalom Blodstone replied to me with a solution:
You have to hack (edit) the rpmrc file, which is located on my system in the
/usr/lib/rpm folder. Open the file in your favorite text editor, and work your
way through it and make the corresponding lines look like the folowing:
arch_compat: i486: i386 i586
arch_compat: osfmach3_i486: i386 osfmach3_i586
buildarch_compat: i486: i386 i586
When I did this, rpm, Kpackage, and the Mandrake Update tools all were able to
install any package on my system. Now, I made these changes in Mandrake 6.1,
but I bet they will work for 6.0 as well. Give it a day or two, in the event
this is not the case. I am sure AX will jump in with the correct information if
needed.
If this (package for another ardhitecture) is not your problem, the above will
not help. From the changes made in the rpmrc file, it looks like I am telling
rpm that it is ok to install *.586.rpm packages on my 486 system (and perhaps
to make them compatible ?).
If I made a wrong guess about the trouble you are having with
installing/updating packages, shoot a line with more detail, and we all will
try to help.
I usually do fix updates with the Mandrake Update program. It is easy, and I
have found it to be reliable (since the rpmrc hack).
I have updated my kernel from the 2.2.13-4mdk version which came on the
Macmillan 6.5 release of Mandrake 6.1 to the current 2.2.13-7mdk version which
can be found in the Mandrake ftp mirrors. To do this, I downloaded the kernel
package to my personal folder as a regular user. I then ran Kpackage as a
super user.
I have modified the kdelink to allow this by editing the execute tab command
line to:
kdesu -c /usr/bin/kpackage
which pops up a window allowing me to enter my root password, then the program
runs as usual in superuser mode.
The next thing is to change the options > Location of uninstalled packages >
LocationRPM to include your personal folder (just fill in a line in the dialog
box that pops up with the path ex: /home/<foldername> and click the box at the
left of the line). Then select file > reload, and the package(s) in your
personal folder will show up in the tree view (left window) of kpackage.
Now you are finally ready to update the kernel. Navigate the tree to System
Environment > Kernel and click the [+] to expand the Kernel list. Select the
new kernel (it should have a big red U icon next to it), then click the
[Examine] button at the bottom of the screen. This will open a new window, in
which you can select or deselect options at the left (I just let these alone
although it may not hurt to check "replace files"), and click the install
button at the bottom of the window. kpackage will do the rest.
A simpler method is to open a console window, and change to superuser, then run
rpm with:
rpm -Uvh /home/<packagename>
I just like the GUI, it gives me the illusion that I can see more of what's
going on. And besides, once I got Kpackage set up, I can run it without all the
configuration steps.
You can also change the execute command for the Mandrake Update program from
your normal user desktop as well, just use:
kdesu -c MandrakeUpdate
I've probably given you far more than you ever wanted, and most of this may not
apply to your problem. Possibly it may be of use to someone else, though.
Ernie
