Brian King said :
> > > I was wondering...is puredyne meant to be run from a cd/dvd?
> > > and if you install it to your hd, is it just an image of the cd/dvd?
> >
> > you can choose to either have a full install using ubiquity, or turn
> > your HD in a liveHD with a persistence setting using make-live-device.sh
> >
> >
> Ok i installed via menu option on live cd so assume I used ubiquity?
yes.
> > > Knoppix was like that the last time I tried it (years ago now)
> > > A copy of the loopback filesystem.
> > >
> > > I friend suggested it might be as I was having some issues.....like bash
> > > doesn't seem to work well with the ~/.bashrc file.
> > > I tried to add alias's to it and source them with . ~/.bashrc but no
> > go...i
> > > get this creepy prompt "\[\e]0;\...@\h:
> > > \w\a\]${debian_chroot:+($debian_chroot)}...@\h:\w\$" and my alias ref's
> > in
> > > ~/.bashrc aren't installed?? What's the story hory?
> >
> > mm...
> > Puredyne uses zsh for the shell, not bash ... did you change that
> > yourself?
> >
>
> hmmm....i replaced xterm with gnome-terminal so that's me problem then?
well could be.
The terminal is used to interface with the shell, and you can make any
combinaison you like.
Except that.. our shell, ZSH, is configured to deal with 256 colors
enables terminals and by default, in Puredyne, xterm is configured to
understand that.
But probably not gnome-terminal, which is probably why you see all these
escape codes. To be sure this is the source of the problem, go in your
terminal preferences and tell it to set its TERM name to:
xterm-256color
Then restart and it should work.
a.
PS: This 256 color prettification is bringing more troubles than
goodness BTW, and it will be changed to a less intrusive customisation
in a future release.
https://bugs.launchpad.net/puredyne-live/+bug/496296
---
[email protected]
http://identi.ca/group/puredyne
irc://irc.goto10.org/puredyne
