First Apt upgrade after 3.7 HD install

[Alterscape]

I just performed a Knoppix 3.7 Hard-Disk install. I'd like to start apt-getting new packages, but I remember reading somewhere that the standard Knoppix distro is different enough from vanilla Knoppix that running "apt-get dist-upgrade" will create some troubles. What do I need to check on and be careful of when apt-get upgrading this install..?

[ArtMotion]

This one is also puzzling me!

Can somebody provide some infos please?

[shah]

My experience:
Don't do "apt-get dist-upgrade" while KDM is running.....might cause you to unable to log in.
Lots of unnecessary script be added to your startup (rc.d).....tends to slow down booting.
Tends to break your system.....not all files will be successfull installed.

My advice:
Don't do "apt-get dist-upgrade".
Do package by package upgrade.

[Alterscape]

Thanks, Shah! Will apt-get upgrade break anything in the knoppix install? It makes me nervous..

[Durand Hicks]

I've never had problems doing apt-get update, apt-get upgrade followed by apt-get dist-upgrade. But that's just me.
I do know one thing, when upgrading the desktop environment packages such as KDE or GNOME, it is better to log out of the desktop, and then kill the kdm or wdm processes.
You can do this two ways:
1) press ctl-alt-f1 and log in as root
2a) type init 3 to kill the wdm or kdm processes. or
2b)
b1) type ps ax to find the process number of the wdm or kdm process
b2) type kill -9 (process number) of the kdm or wdm process
3) type apt-get upgrade
4) type aptitude (I prefer this tool when upgrading enmasse)
5) highlight upgradable packages and press shift-+ (all of the upgradable packages will be marked to be upgraded)
6) press g once to see the list of packages that are going to be upgraded.
If there are any broken packages, they will automatically be umarked to protect the integrity of the remaining packages.
You can also revert some of the package back to the previous version simply by highlighting the package and pressing enter.
Scroll down to the bottom where the version numbers are listed and highlight the previous version and press shift-+ to revert back.
Press q to get back to previous screen.
Repeat above steps as necessary for all packages you want to revert to previous version before upgrading.
Press q again to get back to the original screen.
Press g to see the updated list of packages you want download with your choices.
Once satisfied with your selections, go to next step...
7) press g again to begin downloading and after the downloads are complete, press enter to install the packages.
When done installing, press continue.
8) press q followed by 'y' followed by enter
9) you can check for any remaining packages that weren't upgraded by typing apt-get -s dist-upgrade
If there are a few you missed from above, and the output shows no errors, then press the up arrow and remove the -s from the line followed by enter
You should be totally dist-upgraded by now. I do want to point out some notes:

If during the install phase you see any references about upgrading your scripts, always say no. This keeps your (custom) scripts as is.
You may find some services being stopped and started, if you know you had the services running at the time of the upgrade, then leave that service alone, but any that you saw as being started but wasn't configured to start, then you'll need to stop those services and then follow up with "update-rc.d -f (service) remove" to keep them from starting when you reboot.
You can reboot if you want, but it's not really necessary unless you installed a new kernel and/or upgraded lilo. Basically you would just type init 5 to restart your x window system and go about your business as usual.
That's my basic procedure in a nutshell. but feel free to comment and/or add/subtract any steps i might have missed.

HTH,

Durand

[CrashedAgain]

I'm with shah on this one, don't do apt-get upgrade or dist-upgrade, especially if you have done other than 'debian style' HD install. I have had a 'knoppix-style' install survive an apt-get upgrade but only once.

If you do try it; NEVER NEVER NEVER chose 'upgrade to package maintainer's version' when asked if you want to change a configuration script (always keep your existing); expect at least a couple of packages to fail to upgrade & need special attention and expect that the upgrade will set up to start every known service in all runlevels by default. So look at what services you have now in runlevel 5 & be prepared to manually use sys-v-init to restore that configuration after upgrade. The service that causes the most problem is nis so apt-get remove nis before you upgrade (unless you happen to actually need nis).

Also, localepurge & apt-get remove any packages you don't want before you upgrade.

[GreyGeek]

I just performed a Knoppix 3.7 Hard-Disk install. I'd like to start apt-getting new packages, but I remember reading somewhere that the standard Knoppix distro is different enough from vanilla Knoppix that running "apt-get dist-upgrade" will create some troubles. What do I need to check on and be careful of when apt-get upgrading this install..?

I did a Knoppix 3.7 install this last weekend.
When I ran knoppix-installer as root I selected install option 3, the 'debian' installer, so that I could select ReiserFS.
After the install was complete I entered the following commands as root
apt-get update
apt-get upgrade
apt-get dist-upgrade
apt-get autoclean
auto-apt updatedb

The next day I realized that KPackage in Debian works differently than the package of the same name in SUSE or Mandrake. Sunday after noon I used KPackage to install dozens of apps. Amazing tool!. Installing PostgreSQL was always a manual pain, as was Bibletime. Not wth Debian.