Printable View
I experienced the same thing Cuddles as did a few others. We posted it at http://www.knoppix.net/forum/viewtopic.php?t=8382 but never really got an answer. I am glad to finally see an explanation. I agree with Markus about this being the price for running unstable. I myself switched to debian/woody, there is something to be said for stability and dependability.
Hmmmmm, starting from newest to oldest posts...
First, Glad to see Knoppix.Net back alive again -=- I got "topic repliy notifications" through my email, but all day today, had no luck getting to the site -=- You never know how much you use/need something, until you don't have it... ( and, besides, I always get "withdrawl" symtoms if I can't get my "daily fix" of this forum :D ) -=- Glad to see it back (whoever you are :!:)
Nmcphillips and Markus, I don't think its "knoppix's" fault, really. I think its the simple fact that: "A person decides to either want, or doesn't know how to change it, to remain on the 'edge' with using the testing, experimental, or unstable, versions as they become available." I am quite sure that a majority of my problems are stemming from the fact that in my 'sources.list' I allow these packages to be "seen", and thus, Knoppix is only doing what I asked of it... If my sources.list has entries for 'give me the newest thing out there', it is doing what it is being asked to do. From what I know, just don't know how to do it, my sources.list states to look for 'unstable', 'testing', 'experimental', etc... packages. I am sure that if you took a distro like "woody", added 'unstable', 'testing', and 'experimental' to your sources.list - in no time, you would be in the same boat as someone who doesn't change the sources.list (like myself) from a Knoppix install. (my bad)
A. Jorge Garcia, I like your idea. So, considering that I am at v3.3, I would do a apt-get dist-upgrade to get to v3.4 - which I hear has hit the world already? (did I understand your theory correctly?) -=- I realize that v3.3 is old news now, but in the world of Windows - you didn't call upon the "Great God Of Microsoft" to do any "Windows" upgrades as far as your OS was concerned, unless, your life depended on it - no one deserves to deal with that hell, unless those conditions were necessary. -=- I am not sure what to do here. I hate to have all the hell that breaks loose when I do a apt-get upgrade, but, don't want to miss new things untill a new version of the complete OS comes out. I think I might take a combination of what Stephen stated, and you did... View what "would" be upgraded, decide if I need it, or wait till a new version comes out... (?)
Stephen, OH HOW COOL :!: "pointers!", or I guess they would be called "remote 'links'" in a Windows world (?) ALIASES - never thought of it... You would create this as a text file right? And the placement of this file would be under the /root/ home directory, under a folder [dot]bashrc ??? Do I add it to a specific "existing" file, or create my own? I am missing your statement, or explaination, on this somewhat though -=- it only runs every-other time??? (btw - I like your "Sherlock Holmes" way of dealing with upgrades, and very well explained, but, in practice, its kind of hard to always do it though - in my case, and what usually gets me into this trouble is, I take the "quick and dirty" FAST way out. It is only after I do the upgrade do I pay the price for my "easy way out"...
This whole "scare" of this past upgrade was simply because, I never realized that when xdm installed, it added a "new" display server to my list on logins - thus my <default> that I always used, was no longer a valid deafult, I needed to choose. I just didn't realize what had changed, or how it had changed on me. I know now. (DUH :!:)
Thanks for this forum, for if not, I am sure I would have sat at the login screen wondering what I had done, or how I would get 2.x gig of OS back after the upgrade - never realizing that it was simply another option on the login screen...
Cuddles
This is bizarre. I do apt-get upgrade quite frequently and really never have problems. What gives? I usually stick with old config files if a packages wants to replace them.
Ok I'll have to admit that I did have the same problem with X that Cudles had when upgrding to KDE 3.2. I fixed it by uncommenting "set e" from /etc/X11/Xsession. Of course I wouldn't have had this problem if I hadn't gone out of my way to add 3.2 before it got put in unstable (Though I can't tell if the same thing would have happened afterward or not).
Adam
I seem to have been a bit unclear (again).
I don't blame Knoppix, I like it immensely having used Mandrake and Suse in the past. Having a bit of trouble once in a while is really a price I'm willing to pay, at least for now. Perhaps when I tire of fixing things, I'll change to woody or sarge, but for the time being unstable is a great way of getting to know debians little quirks. Each time I have to fix a small thing, and the bugs are usually smallish, I learn a little.
It is a . file so you either need to create or edit the file that may already exist and the /root/.profile file should already be reading it when you login the command I suggested after the editing is necessary because you made a change to the file and had to re-read to be able to use the new aliases in the current shell any new shell would have the aliases every time after this when you login as root the file should be read as long as the section for this is in the /root/.profile file. I have included both of them this time in case you do not have them.Quote:
Originally Posted by Cuddles
Code:HappyTux:/home/stephen/archives/deb# cat /root/.profile
# ~/.profile: executed by Bourne-compatible login shells.
# Source the .bashrc if it exists.
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# Set path.
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
export PATH
mesg n
HappyTux:/home/stephen/archives/deb# cat /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
export PS1='\h:\w\$ '
umask 022
# You may uncomment the following lines if you want `ls' to be colorized:
export LS_OPTIONS='--color=auto -h'
eval `dircolors`
alias ls='ls $LS_OPTIONS'
alias ll='ls $LS_OPTIONS -l'
alias l='ls $LS_OPTIONS -lA'
#
# Some more alias to avoid making mistakes:
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
# Allows me to run an X program as root
export XAUTHORITY=/home/stephen/.Xauthority
# Stops bash from overwriting file.
#i.e. bob@sonic:~> cat > todo-list.txt
# bash: todo-list.txt: cannot overwrite existing file
set -o noclobber
# Some aliases added by me for convenience
alias agi="apt-get install"
.... {SNIP}
# Set pager to most for color man pages
PAGER=most ; export $PAGER
#Added to let less view .gz doc files
eval `lesspipe`