Hi Dave, Silviu and James

Dave Plater to opensuse Which yast application did you try online update or software management?

At first, I used the Software Management application I found in the Start Menu. Then I switched to the Command Line tool, zypper.

Silviu Marin-Caea to opensuse Can you copy&paste here the URL of the update repository you have got? It can be seen in YaST Software repositories. If you have something different that this, erase it and add this one: http://download.opensuse.org/update/11.0

This the update repository I have http://download.opensuse.org/update/11.0 same as what you'd recommended.

James Knott to SuSE

...

Silviu Marin-Caea wrote:

Those noarch packages are strange, they don't even exist in the regular update repository.

I thought they were packages that were platform independent.

I don't know where they come from either :-( -- Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Dave, On Thu, Oct 9, 2008 at 10:00 AM, Dave Plater wrote:

Use yast2 online update

Ok so I tried Yast Online Update. I get this, Problems: patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Possible Solutions: [ ] do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed [ ] do not install patch:libxcrypt-109.noarch I guess this'll make sense eventually, but this is all a lot harder than installing Windows :-( --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Dave, On Thu, Oct 9, 2008 at 10:33 AM, Dave Plater wrote:

try do not keep libxcrypt-32bit first and see if you are going to lose something you want. There are so many different packages available that sometimes one is tempted to go overboard.

Just to be clear I didn't install libxcrypt-anything in the first place. At least not on purpose :-(

Do you have packman or videolan repositories enabled?

No, I don't. Trying your suggestion I selected the "do not keep libcrypt-32bit" option, and then followed each of the first next options. It seems to get worse the further along you go. :-( (1) zypper up Reading installed packages... 2 Problems: Problem: patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 Problem: patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Problem: patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 Solution 1: do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed Solution 2: do not install patch:libxcrypt-109.noarch Choose from above solutions by number or skip, retry or cancel [1/2/s/r/C]: 1 Problem: patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Solution 1: do not keep ConsoleKit-32bit-0.2.10-14.1.x86_64 installed Solution 2: do not install patch:ConsoleKit-132.noarch Choose from above solutions by number or skip, retry or cancel [1/2/s/r/C]: 1 Resolving dependencies... 3 Problems: Problem: ConsoleKit-0.2.10-14.2.x86_64 requires ConsoleKit-32bit, but this requirement cannot be provided Problem: pam-32bit-1.0.1-8.1.x86_64 requires libxcrypt.so.2, but this requirement cannot be provided Problem: ConsoleKit-0.2.10-14.2.x86_64 requires ConsoleKit-32bit, but this requirement cannot be provided Problem: ConsoleKit-0.2.10-14.2.x86_64 requires ConsoleKit-32bit, but this requirement cannot be provided uninstallable providers: ConsoleKit-32bit-0.2.10-14.2.x86_64[OS11-update] Solution 1: keep ConsoleKit-32bit Solution 2: architecture change of ConsoleKit-0.2.10-14.2.x86_64 to ConsoleKit-0.2.10-14.2.i586 Solution 3: Ignore some dependencies of ConsoleKit Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/C]: C (2) zypper up Reading installed packages... 2 Problems: Problem: patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 Problem: patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Problem: patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 Solution 1: do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed Solution 2: do not install patch:libxcrypt-109.noarch Choose from above solutions by number or skip, retry or cancel [1/2/s/r/C]: 1 Problem: patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Solution 1: do not keep ConsoleKit-32bit-0.2.10-14.1.x86_64 installed Solution 2: do not install patch:ConsoleKit-132.noarch Choose from above solutions by number or skip, retry or cancel [1/2/s/r/C]: 2 Resolving dependencies... Problem: pam-32bit-1.0.1-8.1.x86_64 requires libxcrypt.so.2, but this requirement cannot be provided uninstallable providers: libxcrypt-32bit-3.0-14.2.x86_64[OS11-update] libxcrypt-3.0-14.2.i586[OS11-update] libxcrypt-3.0-14.1.i586[OS11-oss] Solution 1: keep libxcrypt-32bit Solution 2: Following actions will be done: do not keep pam-32bit-1.0.1-8.1.x86_64 installed do not keep ConsoleKit-32bit-0.2.10-14.1.x86_64 installed deinstallation of pam-32bit-1.0.1-8.1.x86_64 deinstallation of ConsoleKit-32bit-0.2.10-14.1.x86_64 deinstallation of ConsoleKit-0.2.10-14.2.x86_64 deinstallation of PolicyKit-0.8-14.1.x86_64 deinstallation of hal-0.5.11-8.1.x86_64 deinstallation of cups-autoconfig-0.1.0-113.1.x86_64 architecture change of gnome-keyring-2.22.1-22.1.x86_64 to gnome-keyring-2.22.1-22.1.i586 deinstallation of gvfs-backends-0.2.3-29.2.x86_64 architecture change of gvfs-0.2.3-29.2.x86_64 to gvfs-0.2.3-29.2.i586 deinstallation of PolicyKit-doc-0.8-17.1.x86_64 etc etc Solution 3: Following actions will be done: architecture change of libxcrypt-3.0-14.2.x86_64 to libxcrypt-3.0-14.2.i586 architecture change of pam-1.0.1-8.1.x86_64 to pam-1.0.1-8.1.i586 architecture change of pam-modules-11.0-35.1.x86_64 to pam-modules-11.0-35.1.i586 architecture change of pwdutils-3.2.1-12.1.x86_64 to pwdutils-3.2.1-12.1.i586 etc etc --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Dave,

You must have at least one ConsoleKit package and at least one libxcrypt because your system depends on them.

Well ok. Kind of hoping then that the "system" would know what to DO with them :-(

I would recommend using Yast2 Online update to resolve the problem

According to this bug report (http://lists.opensuse.org/opensuse-bugs/2007-06/msg00641.html) from what I read "Yast2 Online" *uses* zypper by default, so shouldn't the results be the same?

but first use zypper clean next zypper ref and then post the output of zypper lr

zypper clean All repositories have been cleaned up. zypper ref Repository 'OS11-update' is up to date. Repository 'OS11-oss' is up to date. Repository 'OS11-non-oss' is up to date. zypper lr # | Alias | Name | Enabled | Refresh ---+------------------+------------------+---------+-------- 1 | OS11-update | OS11-update | Yes | Yes 2 | OS11-oss | OS11-oss | Yes | Yes 3 | OS11-non-oss | OS11-non-oss | Yes | Yes yast2 online_update Problems───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ │ │patch:libxcrypt-109.noarch conflicts with libxcrypt-32bit.x86_64 < 3.0-14.2 provided by libxcrypt-32bit-3.0-14.1.x86_64 │ │ │ │patch:ConsoleKit-132.noarch conflicts with ConsoleKit-32bit.x86_64 < 0.2.10-14.2 provided by ConsoleKit-32bit-0.2.10-14.1.x86_64 Possible Solutions─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ │ │[ ] do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed │ │ │ │[ ] do not install patch:libxcrypt-109.noarch If I try to "resolve" by Check-ing [X] do not keep libxcrypt-32bit... Then [OK -- Try Again] etc etc, the results & offered solutions are EXACTLY the same as the output from Zypper on the command line.

Another question, which gui(s) do you have and which one are you using?

I originally installed KDE 35, and had this problem. Someone told me that I should use Gnome. So I reinstalled everything with that installed. I had the same problem. Some posts have suggested that the GUI is the problem. So I reinstalled a GUI-less system. And am trying everything at the "Console GUI" (Do you call it ncurses, or something?), hoping that the problem gets solved so then I can install the GUI on top of asystem that works. So far, the results are the same no matter which GUI I seem to use. I was searching around and found this discussion, https://bugzilla.novell.com/show_bug.cgi?id=336678 It's completely over my head, and I'm pretty sure it SHOULD be. It seems to be talking about some of this stuff. It also looks like "they" have know about this for a long time; since October of last year? The discussion ends with ------- Comment #83 From Ladislav Slezak 2008-06-04 05:13:43 MDT -------I'll remove the yast workaround after 11.0 is out.------- Comment #84 From Ladislav Slezak 2008-06-04 05:24:39 MDT -------The workaround was removed in SVN trunk (for 11.1), later it will be includedin yast2-packager-2.17.0. Apparently the 11 version I have installed has yast2-packager-2.16.53-3.1. And the "Roadmap" for "11.1" says it will take until Dec to be released. So, what am I supposed to do in the meantime? I just want to get up & running on a system that works. Should I replace this with a different flavor of Linux? Ubuntu's supposed to be "friendly" to normal users. --Mil

Hi Carlos, On Thu, Oct 9, 2008 at 12:30 PM, Carlos E. R. wrote:

Yes, but zypper is harder to use. You come from windows, so a graphical solution should be easier on you.

Navigating an interface, GUI or otherwise, is not what makes it hard. Consistenly confusing results regardless of interface is what makes it hard.

[X] do not keep libxcrypt-32bit...

I'd better wait for a solution, removing a needed library could render your system useless. No body so far seems to know why you are having that conflict.

I'm not following through with any changes. I was asked earlier to "try and see", which is all I'm doing here too.

Do you have a PPC machine? You said:

]> I bought a new PC with an AMD cpu,

...so you don't have a PPC machine (PowerPC hardware) and that Bugzilla is not related to your problem, which was for 10.3 and you have 11.0

Well at leasst one of the people in THAT posted has posted here too, https://bugzilla.novell.com/show_bug.cgi?id=412794, and it seems there's some discussion about that.

Meanwhile, as you like reinstalling

That couldn't be farther from the truth. I "like" having a working system and no installation problems, like my old box was. --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Dave, On Thu, Oct 9, 2008 at 12:34 PM, Dave Plater wrote:

Have you tried the system repair tool on the dvd

Yes, in both the KDE & Gnome "states" of my adventures. It doesn't matter if it's a new installation or a repaired on. The first "update" (yast or zypper, gui or not) gets these conflicting errors.

that should at least get your system back to square one

It seems to do that just fine. Unfortunately it's "square one" that's the problem. :-( --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dave,

You need to have the opensuse 11.0 dvd as one of your repositories.

I saw your comment earlier, and installed the DVD repository as you suggested. With that set up there upgrade errors are still the same as I've been reporting so far. --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-10-09 at 22:43 +0200, Dave Plater wrote:

Then I suggest you back up any data you may need and start a new kde 3 install from scratch, after the install completes update immediately with yast 2 online update.

Reinstalling doesn't solve things, this is not windows. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjue2oACgkQtTMYHG2NR9UNwgCeP0J77lzzWXAEhpbwWjG6DoOh YfQAn1j5/wiMYEjMh718jg3OgJqtS17z =V0Ws -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-10-09 at 15:07 -0700, Kai Ponte wrote:

On Thursday 09 October 2008 02:45:13 pm Carlos E. R. wrote:

...

...

Then I suggest you back up any data you may need and start a new kde 3 install from scratch, after the install completes update immediately with yast 2 online update.

Reinstalling doesn't solve things

Oh, I beg to differ. I've had several occasions where I've mucked something up and found the only way to fix it is to reinstall.

Rebooting often works as well.

Rebooting might, but resinstalling... I don't do that in years. And he solved the problem at last without reinstalling. In this case he had already reinstalled several times and each time he bumped into the same exact problem. Reinstalling once more wouldn't solve anything more. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjuhqUACgkQtTMYHG2NR9VbAwCfYqiEfbuoHdPxV0QgpO/kUnud L9MAniQoOgL7R6oR052V42W7RFl+gtRV =pQPT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

On Thursday, 2008-10-09 at 15:07 -0700, Kai Ponte wrote:

...

Rebooting often works as well.

Rebooting might, but resinstalling... I don't do that in years.

And he solved the problem at last without reinstalling. In this case he had already reinstalled several times and each time he bumped into the same exact problem. Reinstalling once more wouldn't solve anything more.

Well, Carlos, I can agree with both of you. I'm sure that in principle, re-installation is not needed. But, like Mil, and, I'm sure, Kai, I've managed to skip a step in the original install, or not understood one of the steps, or fouled it up somehow, and lost a piece that caused the errors and lost dependencies to snowball to a frightening extent. Sure, I could have solved the problem if I'd known the innards of the system well enough to find the one or two real problems, but I don't. It's much easier (especially now that my system software is on its own dedicated partition) to re-install and get the process right. And if it then works, I don't have any doubts about whether I've left another installation error buried in there to bite me later. John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Don, On Thu, Oct 9, 2008 at 1:59 PM, Don Raboud wrote:

Perhaps you could initially upgrade just those two packages individually and after that try the online update again. I don't know if that would work, but it might be worth a try.

Well your suggestion, despite the counterintuitive nonsense below, worked. rpm -q libxcrypt-32bit ConsoleKit-32bit libxcrypt-32bit-3.0-14.1 ConsoleKit-32bit-0.2.10-14.1 zypper se -s libxcrypt-32bit\* ConsoleKit-32bit\* Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------+---------+-------------+--------+------------ v | ConsoleKit-32bit | package | 0.2.10-14.2 | x86_64 | OS11-update i | ConsoleKit-32bit | package | 0.2.10-14.1 | x86_64 | OS11-oss v | libxcrypt-32bit | package | 3.0-14.2 | x86_64 | OS11-update i | libxcrypt-32bit | package | 3.0-14.1 | x86_64 | OS11-oss zypper in -f libxcrypt-32bit Reading installed packages... Problem: cannot install both libxcrypt-32bit-3.0-14.1.x86_64 and libxcrypt-32bit-3.0-14.2.x86_64 Solution 1: do not keep libxcrypt-32bit-3.0-14.1.x86_64 installed Solution 2: do not install libxcrypt-32bit-3.0-14.2.x86_64 Choose from above solutions by number or cancel [1/2/C]: 1 Resolving dependencies... Problem: conflicting requests Solution 1: keep libxcrypt-32bit Solution 2: do not install libxcrypt-32bit-3.0-14.2.x86_64 Choose from above solutions by number or cancel [1/2/C]: 1 Resolving dependencies... The following package is going to be upgraded: libxcrypt-32bit Overall download size: 38.0 K. No additional space will be used or freed after the operation. Continue? [YES/no]: yes Downloading package libxcrypt-32bit-3.0-14.2.x86_64 (1/1), 38.0 K (137.0 K unpacked) Downloading: libxcrypt-32bit-3.0-14.2.x86_64.rpm [done] Installing: libxcrypt-32bit-3.0-14.2 [done] zypper in -f ConsoleKit-32bit Reading installed packages... Problem: cannot install both ConsoleKit-32bit-0.2.10-14.1.x86_64 and ConsoleKit-32bit-0.2.10-14.2.x86_64 Solution 1: do not keep ConsoleKit-32bit-0.2.10-14.1.x86_64 installed Solution 2: do not install ConsoleKit-32bit-0.2.10-14.2.x86_64 Choose from above solutions by number or cancel [1/2/C]: 1 Resolving dependencies... Problem: conflicting requests Solution 1: keep ConsoleKit-32bit Solution 2: do not install ConsoleKit-32bit-0.2.10-14.2.x86_64 Choose from above solutions by number or cancel [1/2/C]: 1 Resolving dependencies... The following package is going to be upgraded: ConsoleKit-32bit Overall download size: 13.0 K. No additional space will be used or freed after the operation. Continue? [YES/no]: yes Downloading package ConsoleKit-32bit-0.2.10-14.2.x86_64 (1/1), 13.0 K (20.0 K unpacked) Downloading: ConsoleKit-32bit-0.2.10-14.2.x86_64.rpm [done] Installing: ConsoleKit-32bit-0.2.10-14.2 [done] rpm -q libxcrypt-32bit ConsoleKit-32bit libxcrypt-32bit-3.0-14.2 ConsoleKit-32bit-0.2.10-14.2 zypper se -s libxcrypt-32bit\* ConsoleKit-32bit\* Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------+---------+-------------+--------+------------ i | ConsoleKit-32bit | package | 0.2.10-14.2 | x86_64 | OS11-update v | ConsoleKit-32bit | package | 0.2.10-14.1 | x86_64 | OS11-oss i | libxcrypt-32bit | package | 3.0-14.2 | x86_64 | OS11-update v | libxcrypt-32bit | package | 3.0-14.1 | x86_64 | OS11-oss Now, zypper upzypper up Reading installed packages... Nothing to do. Finally. Thank you! --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 09 October 2008 04:30:43 pm Mil T wrote:

Hi Don,

On Thu, Oct 9, 2008 at 1:59 PM, Don Raboud wrote:

...

Perhaps you could initially upgrade just those two packages individually and after that try the online update again. I don't know if that would work, but it might be worth a try.

Well your suggestion, despite the counterintuitive nonsense below, worked. ... zypper upzypper up Reading installed packages... Nothing to do.

Finally. Thank you!

If you get similar problem with next update, check versions of zypper and libzypp. There was problem with version from DVD with exactly the same symptoms. YaST Online Update would report conflict, when you select solution and press OK it will check and ask the same question, offering the same solution. To get out of circle one has to use YOU deselect all updates except zypper or/and libzypp (I can't recall exact file) and after that is done YOU will restart and update much more packages. Current versions are: linux:~ # zypper --version zypper 0.11.10 linux:~ # rpm -qa libzypp libzypp-4.27.1-0.1 -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

On Friday, 2008-10-10 at 16:31 -0500, Rajko M. wrote:

...

If you get similar problem with next update, check versions of zypper and libzypp. There was problem with version from DVD with exactly the same symptoms. YaST Online Update would report conflict, when you select solution and press OK it will check and ask the same question, offering the same solution. To get out of circle one has to use YOU deselect all updates except zypper or/and libzypp (I can't recall exact file) and after that is done YOU will restart and update much more packages.

Argh. :-( Too bad we all had forgotten or did not know.

-- Cheers, Carlos E. R.

The strange thing is, I told the OP of a zypper update after installation and I kept telling him to use yast online update but I think by then he was using command line. I remember the immediate update of libzypp after installation and I still can't work out what went wrong in his case. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. wrote:

On Saturday 11 October 2008 05:25:16 am Dave Plater wrote:

...

The strange thing is, I told the OP of a zypper update after installation and I kept telling him to use yast online update but I think by then he was using command line. I remember the immediate update of libzypp after installation and I still can't work out what went wrong in his case.

The point is to check for update only 1 or 2 package management related. Any other will make YOU (YaST Online Update) chase his tail.

BTW, I agree with Silviu, that few recent problems (zypper and/or Network Manager) repelled for sure a bunch of people that would otherwise use openSUSE.

IIRC the manual version of yast online update (not the applet version) updates the package managements first and then restarts to complete the other pending updates. Maybe the applet version was the root cause of the problem, I have only ever used it as an indicator. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 09 October 2008 08:00:54 pm Dave Plater wrote:

Mil T wrote:

...

Hi Dave, Silviu and James

...

Dave Plater to opensuse Which yast application did you try online update or software management?

At first, I used the Software Management application I found in the Start Menu.

Then I switched to the Command Line tool, zypper.

This the update repository I have

http://download.opensuse.org/update/11.0

-- Mil

Use yast2 online update for system updates software management doesn't install patches. IIRC there is a zypper update after a clean 11.0 install, if you use yast2 online update it should update your system properly. Software management is for adding and removing packages mainly. Regards Dave P

I Installed suse 11 a while ago yet to another laptop. The experience was horrible, but only because I forgot to do the system update immediately after install from DVD. .. I tried to install ati drivers before kernel update, so you can imagine.. The system started to install all kinds of weird kernel versions (pae, etc.). So, I think it would be a good idea that after a clean DVD install, the system automatically pops up a gigantic banner saying: Go to Yast => Online Update Cheers, Sampsa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Kai, On Thu, Oct 9, 2008 at 12:53 PM, Kai Ponte wrote:

NT?

Wow - how old was it?

Older that someone of my age can remember exactly! :-) I also just retired my old Compuserve dial-up account. $9.95 month, with easy access around the world.

(We just retired an eight year old NT box running as our PDC a few months back.)

It's good to know there are still "Average Joes & Janes" out there with a dose of old-fashioned common sense. If it ain't broke, don't fix it! :-D Honestly, it ran fine & did what I needed. Word Processing, Presentations, Spreadsheet, Page Layout, EMail, Internet. Noone was ever able to clearly explain to me why I needed a "Ribbon" in my WP, or Words-with-Wings flying faster across my presentations, let alone get me to waste money on it! It's getting harder to find floppy disks, though. --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Kai, On Thu, Oct 9, 2008 at 2:08 PM, Kai Ponte wrote:

LOL! Got rid of my compuserve sometime in the early '90s. :P

And, as a result, "Are you better off than you were 15 years ago?" :-)

Well, it has been "broken" for years and I could easily hack the SAM, but it sufficed for the 1500 or so of us until we could get Active Directory running.

That hardly qualifies as broken. I live on a farm. It's not broken until the rust holding the chicken-wire together blows away.

...

It's getting harder to find floppy disks, though. What are those?

Smart aleck. ;-)

Seriously, since you're an NT guy

Gal, thank you very much. New great-grandma, actually. But how would you know? :-)

I'd suggest a re-install.

The forced individual installs seem to have done the trick.

I converted over from NT/XP a few years ago

Have you managed to install Opensuse successfully yet? :-)

it is a LOT easier being a SUSE guy in a Microsoft shop. etc.

I'm sure that's all true. None of which, I want to do. I just want to get back to my business (You may have guessed that it's NOT computers!), and stop wasting time on things that aren't my knitting.

such an archaic notion as drive letters.

Watch it, "sonny!" I'm more archaic than drive letters. Thank you. --Mil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org