problem with hostname

[Fred Roller]

On Mon, 2009-07-13 at 17:27 -0700, NoOp wrote:
> On 07/12/2009 05:06 AM, pkaplan1 at comcast.net wrote:
> 
> > 
> > This problem started about two weeks ago and there have been no
> > references in the syslog files to "wlsdev18-2" since June 29. I
> > assume I did something at that I did something on that date to cause
> > this, but I have no idea what (could have been some mucking with
> > Samba while attached to the AD network at work).
> 
> Open up synaptic: File|History and see what else you may have installed
> on the 29th. Perhaps something that you installed in the process may be
> causing it. You could also 'purge' samba and related packages, test, and
> then reinstall Samba. Be sure to purge the packages (or use 'Mark for
> Complete Removal' in synaptic) rather than just remove them, otherwise
> the suspect config files will remain.
> 
> 
> 
> 

His PS1 variables are intact and his hostname file is good.  I had a
hostname issue when I connected to a Win network that stated the
hostname exceeded the netbios 8 character limit.  (trying to dig up from
memory)  For SnG, shorten your hostname to "test" or some such if you
haven't already tried.  Something is not assign the \n variable it's
value.  Find this and I think we can fix this.

-- 
Fred R.
www.fwrgallery.com

"Life is like Linux, simple.  If you are fighting it, you are doing
something wrong."