Date: Thu, 19 Oct 2006 21:57:11 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Martin McCormick <martin@dc.cis.okstate.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Why csh on Root? Message-ID: <20061019185710.GA57678@gothmog.pc> In-Reply-To: <200610191649.k9JGmxOl017063@dc.cis.okstate.edu> References: <200610191649.k9JGmxOl017063@dc.cis.okstate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-10-19 11:48, Martin McCormick <martin@dc.cis.okstate.edu> wrote:
> RW writes:
> > There is an alternative uid 0 user called toor which you can use if you
> > want
> > to use bash as root. OTOH hand there is a school of thought that you
> > shouldn't be too comfortable as root.
>
> My thanks to all. On all the systems in question, bash
> ends up on the same partition as root, but the points are
> well-taken.
>
> One thing I was trying to accomplish is to have a bell in
> the root prompt. In the .cshrc file is a string
>
> set prompt="\007\!# "
>
> I have also tried replacing the \007 with the actual
> Control-G and even a \a. All produce an attempt to render a bell
> but what is sent to the remote terminal is ^G1#
> as in the actual ASCII characters ^ and G.
>
> I am not sure what to do to correct this problem as I do not get
> it in bash. A \a or \007 is sent literally.
This is easy to do with tcsh:
set prompt = '%{^G%}%n@%m:%/%# '
Note the %{ ... %} around the literal ^G character :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061019185710.GA57678>