-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Heelllp! I decided to upgrade to K3.0.4 through YOU. I began the process, and about 1/2 way through the DL, the circuit quit. I told it go ahead and install what you have, and it did. I restarted the DL, and to my surprise it thought the whole KDE upgrade had been done! So I DLed the whole K3.0.4 from updates and installed it by hand. Worked fine. Anyone know why it can't tell when packages within a subgroup weren't successful? This seems like a pretty basic thing. Anyway, then I decided to try going from 8.0 to 8.1 via the upgrade route, which I'd never tried and was fearful of. I was very careful to select upgrade current system, and update only installed packages. It got to the end of CD1 and made some config changes, but failed with "I need libgcc.so??". I closed this, it wanted to reboot, so I said 'yes'. It rebooted and on init, all I got on the screen was 'LI'. From experience I know this is because a lilo update of the bootblock failed. So I used the 8.1 CD to 'boot to an installed system'. It booted, but it had no idea it was in the middle of an install. It stumbled up to X, but K tripped and bumbled until I ended up at the commandline. I tried 'man', but it wanted libgcc again. So I installed libgcc from the CD, and man worked. I found that in lilo.conf, install had only changed the failsafe option, and added two spurious lines to the end. So I removed the 2 lines, ran lilo and rebooted to failsafe. It came up to X, then K tripped and bumbled until I ended up at the commandline. No continuance of upgrade. I found that it had BACKrevved some KDE files from 3.0.4 to its build of 3.0.3! ONLY SOME! And anyway, how does it dare?! So by hand, I backrevved the KDE files available from the 8.1 CD. Now for the most part it is the - -devel files which are still at 3.0.4. I was able to get K to start, and that's where I am now. I can't compile anything as the headers are not complete. I'm afraid to move, as K (and the system) is here and there at the same time (quantum flux?). And the rest of the system has only the new SW from CD1, not the rest. Does anyone know why the CD update fails? Or at least how to continue the update? I've restarted the update several times, now selecting 'Regular System' instead of 'Installed Packages Only' on the theory that it needs something in the regular system, but no good. Always gets to end of CD1, it does some config updates, then DROPS FROM GRAPHICAL to ncurses and asks if I want to reboot, whereas the first time it stayed in graphical and gave me a countdown. Then always fails to continue update. I think 8.1 uses Grub, but I couldn't find any Grub utility to write the bootblock. There is in fact very little to Grub. Though I've always done a clean install before, I thought it would be OK to update from 8.0 to 8.1 since seems a fairly minor upgrade. I'm resolved that I'll have to DL K3.0.4 again, but that's OK. I just want to finish the 8.1 upgrade. Does anyone know what's wrong/what I can do? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3PydQACgkQnQ18+PFcZJttEgCfWLQCcN4pbWNmTyMxy5ubsJdJ BN8AniaxySdpu0tngp0WOJuq6NC0uwIQ =AKQk -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Does anyone know if Suse8.1 uses Grub? Does anyone know how install chains to CD2? On Monday, 11 November 2002 9:16, Carl wrote:
Heelllp!
I decided to upgrade to K3.0.4 through YOU. I began the process, and about 1/2 way through the DL, the circuit quit. I told it go ahead and install what you have, and it did. I restarted the DL, and to my surprise it thought the whole KDE upgrade had been done! So I DLed the whole K3.0.4 from updates and installed it by hand. Worked fine.
Anyone know why it can't tell when packages within a subgroup weren't successful? This seems like a pretty basic thing.
Anyway, then I decided to try going from 8.0 to 8.1 via the upgrade route, which I'd never tried and was fearful of. I was very careful to select upgrade current system, and update only installed packages. It got to the end of CD1 and made some config changes, but failed with "I need libgcc.so??". I closed this, it wanted to reboot, so I said 'yes'. It rebooted and on init, all I got on the screen was 'LI'. From experience I know this is because a lilo update of the bootblock failed. So I used the 8.1 CD to 'boot to an installed system'.
It booted, but it had no idea it was in the middle of an install. It stumbled up to X, but K tripped and bumbled until I ended up at the commandline. I tried 'man', but it wanted libgcc again. So I installed libgcc from the CD, and man worked. I found that in lilo.conf, install had only changed the failsafe option, and added two spurious lines to the end. So I removed the 2 lines, ran lilo and rebooted to failsafe. It came up to X, then K tripped and bumbled until I ended up at the commandline. No continuance of upgrade.
I found that it had BACKrevved some KDE files from 3.0.4 to its build of 3.0.3! ONLY SOME! And anyway, how does it dare?! So by hand, I backrevved the KDE files available from the 8.1 CD. Now for the most part it is the -devel files which are still at 3.0.4. I was able to get K to start, and that's where I am now.
I can't compile anything as the headers are not complete. I'm afraid to move, as K (and the system) is here and there at the same time (quantum flux?). And the rest of the system has only the new SW from CD1, not the rest.
Does anyone know why the CD update fails? Or at least how to continue the update? I've restarted the update several times, now selecting 'Regular System' instead of 'Installed Packages Only' on the theory that it needs something in the regular system, but no good. Always gets to end of CD1, it does some config updates, then DROPS FROM GRAPHICAL to ncurses and asks if I want to reboot, whereas the first time it stayed in graphical and gave me a countdown. Then always fails to continue update.
I think 8.1 uses Grub, but I couldn't find any Grub utility to write the bootblock. There is in fact very little to Grub.
Though I've always done a clean install before, I thought it would be OK to update from 8.0 to 8.1 since seems a fairly minor upgrade. I'm resolved that I'll have to DL K3.0.4 again, but that's OK. I just want to finish the 8.1 upgrade.
Does anyone know what's wrong/what I can do?
- -- Vila: "I think I have just made the biggest mistake of my life." Orac: "It is unlikely. I would predict there are far greater mistakes waiting to be made by someone with your obvious talent for it." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3P5SgACgkQnQ18+PFcZJs9nACdG1yyFMpbrnB8aAs1FEQnDDBc BXMAn1bEDtAZ9zbBLiJJA4D//IUoYDyc =1PfR -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 11 November 2002 12:26, Johnny Ernst Nielsen wrote:
Good day Carl,
Does anyone know if Suse8.1 uses Grub?
Yes, SuSE 8.1 uses GRUB.
Ah, maybe then the CD2 chaining is buried in Grub. I'll try to supplant Lilo with Grub and see what happens. I'm drinking this afternoon, so it'll have to wait. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3P6skACgkQnQ18+PFcZJuFbQCeOFe1uLXtofCb+l3jYaBnAWsq bE4An1WRWg+PKYtGqaY2/nB1C8qvz7VK =FuLn -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 11 November 2002 11:37, Carl wrote:
On Monday, 11 November 2002 12:26, Johnny Ernst Nielsen wrote:
Good day Carl,
Does anyone know if Suse8.1 uses Grub?
Yes, SuSE 8.1 uses GRUB.
Ah, maybe then the CD2 chaining is buried in Grub. I'll try to supplant Lilo with Grub and see what happens.
OK, tried adding Grub: # grub grub> root (hd0,0) grub> setup (hd0) rebooted, ready to enter commandline boot functions, but still have lilo! Grub is powerless to write a bootblock to my IBM Stinkpad's disk! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3P/S8ACgkQnQ18+PFcZJuODgCZAUPnX4+wljOq9xDvT7m9nrDB KQAAn24NgvKqMcqrO77BVJaSxx2CFipX =UOwR -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HA!, found the problem. Thanks for not lifting fukkin' finger, Suse. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3QR2wACgkQnQ18+PFcZJsSewCfVryYKkIwDvb8cq/t34W8cwgB 5o4An2BlOuskUbRoGNfXfECDoi5tOboR =ytCM -----END PGP SIGNATURE-----
On Monday 11 November 2002 07:12 pm, Carl wrote:
HA!, found the problem.
Thanks for not lifting fukkin' finger, Suse. ================
Carl, Are you off your medication again today? Then again, I think you mentioned earlier today that the all the bottles were empty of their liquor? Still don't have a clue about where to ask your SuSE questions and your KDE questions do you. Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 11 November 2002 18:24, Patrick wrote:
On Monday 11 November 2002 07:12 pm, Carl wrote:
HA!, found the problem.
Thanks for not lifting fukkin' finger, Suse.
================
Carl, Are you off your medication again today? Then again, I think you mentioned earlier today that the all the bottles were empty of their liquor? Still don't have a clue about where to ask your SuSE questions and your KDE questions do you.
Patrick --
--- KMail v1.4.3 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206
WTF are you on about, pissant? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iEYEARECAAYFAj3QS8MACgkQnQ18+PFcZJsq3ACfQX9NUrYoDyhR4UTl8DZgJDMw 4TUAn2xzO4nT58EzUtbtuhNMp8+RPUGm =5l+p -----END PGP SIGNATURE-----
* Carl (quantum@ultra2k.com) [021111 16:16]:
Thanks for not lifting fukkin' finger, Suse.
Have the courtesy to post to the appropriate group and SuSE people are happy to help. Of course, since most SuSE people probably have you killfiled already it might not help in your case. -- -ckm
* Carl (quantum@ultra2k.com) [021111 16:19]: ->-----BEGIN PGP SIGNED MESSAGE----- ->Hash: SHA1 -> ->HA!, found the problem. -> ->Thanks for not lifting fukkin' finger, Suse. How rude. Do you think the people on this list are obligated to answer your questions? Ummm...NOT! If they don't know they answer or are to busy your just out of luck in some instances. And SuSE employee's rarely keep up with the " free to the public provided at no cost to the consumer mailing lists." .. So take your bad language and crappy attitude somewhere else. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
Ben Rosenberg wrote:
* Carl (quantum@ultra2k.com) [021111 16:19]: ->-----BEGIN PGP SIGNED MESSAGE----- ->Hash: SHA1 -> ->HA!, found the problem. -> ->Thanks for not lifting fukkin' finger, Suse.
How rude. Do you think the people on this list are obligated to answer your questions? Ummm...NOT! If they don't know they answer or are to busy your just out of luck in some instances. And SuSE employee's rarely keep up with the " free to the public provided at no cost to the consumer mailing lists." .. So take your bad language and crappy attitude somewhere else.
I second that. These lists ( unless I am mistaken) are primarily set up for users assisting users based on past experience. I for one don't care for your profanity or your profanity disguised as an acronym. I subscribed to this list to learn and hopefully get assistance to problems I encounter. I do not expect help, but it is nice when it is available. Please clean it up or find some one who wants to hear it. D.C.
participants (6)
-
Ben Rosenberg -
Carl -
Christopher Mahmood -
Darrell Cormier -
Johnny Ernst Nielsen -
Patrick