M12 11.9.92

[Brooko]

Thanks Rich - for checking the code.

Still amuses me (over last 12 months or so) when I've seen thread after thread pop up regarding Windows and how bad it is. From a reasonably hard-core Linux user - the step back into "Windows world" actually wasn't too bad - for this kid anyway. Installs are still the worst - Linux makes installing and updating so easy - so Windows is just more time consuming in that manner. But the trade offs for me are:
- software and hardware works and acts the way it's supposed to without workarounds
- being able to go back to MS Office again (personal preference - just do not like Libre Office)
- gaming
- the kids stuff just works without freezing / glitching etc

I do miss the flexibility of Linux though.

And if you think my step back into the 'dark-side' is bad - I've even contemplated jumping the fence from time to time and checking out the OSX eco-system

Time will tell. Hows the golf? My handicap is sadly heading up again. Can't hit it off the tee to save myself at the moment

[Danum]

Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..

I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.

[richb]

Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..

I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.

I did edit the original by adding the one line.

[Danum]

Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..

I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.

I did edit the original by adding the one line.

Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,

Code: Select all

2. As root navigate to /root folder and create new file .bashrc

3. Create new file .bashrc in your own /home/yourusername directory
Add following line -
		

[richb]

Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,

Code: Select all

2. As root navigate to /root folder and create new file .bashrc

3. Create new file .bashrc in your own /home/yourusername directory
Add following line -
		

No I did not since there was already a bashrc I felt it prudent not to overwrite it.

[BurtHulland]

My 64-bit Google Earth problem is solved! The USB key Ihad used to install the OS on all 3 of my systems was failing. It did not create any errors I found except the one in GE. Then I started to wonder if it could be the problem, so I rewrote the key - and was greeted with several errors. I have now bought a new key and written M11.9.92_64 on it. When I used this to reinstall the 64bit M12 OP system, it would then run GE! (I filed the key I had been using in the circular file.)

Burt

[uncle mark]

My 64-bit Google Earth problem is solved! The USB key Ihad used to install the OS on all 3 of my systems was failing. It did not create any errors I found except the one in GE. Then I started to wonder if it could be the problem, so I rewrote the key - and was greeted with several errors. I have now bought a new key and written M11.9.92_64 on it. When I used this to reinstall the 64bit M12 OP system, it would then run GE! (I filed the key I had been using in the circular file.)

I hate it when that happens.

I love it when a bootable USB is working properly, but for me anyway it's easier most of the time to burn a disk.

[zeeone]

Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,

Code: Select all

2. As root navigate to /root folder and create new file .bashrc

3. Create new file .bashrc in your own /home/yourusername directory
Add following line -
		

No I did not since there was already a bashrc I felt it prudent not to overwrite it.

Funny, in my home folder .bashrc in Kubuntu, I found this:


# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes


Uncommented the "force_color_prompt=yes" and magic, the user bash line is green.

Seems that there are a four more bash.bashrc files to look at, that seem to be the system wide settings.

I wonder if the .bashrc in the user folder could be copied into my other Deb distros and work.
This is something to play with later.

[richb]

What was in mine below. I only added the last line.

Code: Select all

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
	# We have color support; assume it's compliant with Ecma-48
	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
	# a case would tend to support setf rather than setaf.)
	color_prompt=yes
    else
	color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi
export PS1="\e[1;32m\u[\w]\\$ \e[m "

[Danum]

What was in mine below. I only added the last line.

Which is a typical Mepis 12 way of doing it, (I know yours is from Kubuntu)
what you are doing is letting the original script setup a color, and then resetting it again, Why? set it up from within the original script then it works as it should, without an extra action,
It is doing things like this that make booting from a Mepis 12 DVD as slow as it is, plus it takes more resources because the system is going round in circles before it finds out just what it should be doing.