On Tuesday 13 July 2004 10:16 am, Reid Priedhorsky wrote:
> I suppose Googling may help. The man page on Debian is not so helpful.
Not very helpful at all. I get it now. Thanks.
--
Michael McIntyre Silvan <[EMAIL PROTECTED]>
Linux fanatic, and certified Geek; registered Linux user #2
On Tue, 13 Jul 2004 09:30:18 +0200, Silvan wrote:
>
>> Also look into the tput program. You tell it what you want (bold,
>> green, etc.) and it outputs appropriate magic for your current
>> terminal.
>
> Sounds interesting, but any syntax examples? I couldn't make heads or
> tails of it.
Here'
> It's a matter of a 3-way merge, as cvs does it. The three files are:
> 1) Old package version original config file
> 2) New package version config file
> 3) The installed config file (with your changes).
>
> This would mean changing dpkg to keep pristine copies of installed
> conffiles (fi
Once upon a time Silvan said...
>
> It would be cool if this process could use a CVS-style merge instead. I
> wonder how hard it would be to do this in practice?
>
> I guess it's not such a simple matter as merging two source files, really.
It's a matter of a 3-way merge, as cvs does it. The
On Monday 12 July 2004 06:31 pm, Monique Y. Mudama wrote:
> > remote, etc. It helps when you have as many different terminal
> > sessions open at one time as I do.
>
> Great minds must think alike ... root is red for me, too =)
Hard to argue with that. Great minds indeed. :)
Incidentally, on
> Also look into the tput program. You tell it what you want (bold, green,
> etc.) and it outputs appropriate magic for your current terminal.
Sounds interesting, but any syntax examples? I couldn't make heads or tails
of it.
--
Michael McIntyre Silvan <[EMAIL PROTECTED]>
Linux fanati
On Tue, 13 Jul 2004 01:10:06 +0200, Monique Y. Mudama wrote:
>
> > Wow, how could you do that? Can you share your code with us? I use
> > colored xterms to distinguish those -- easier to do. :-)
>
> In my root .bashrc I have this:
>
> export PS1='\e[31;1m\h:\w\$\e[0m '
Also look into the tput p
On 2004-07-10, * Tong* penned:
> On Sat, 10 Jul 2004 00:55:08 -0400, Silvan wrote:
>
>> anyway. One thing I've done to help me keep track of where I am is
>> to use colorized prompts. Red is root, cyan is local user, purple is
>> local user with developer environment variables, green is remote,
>
On 2004-07-10, Silvan penned:
>
> One thing I've done to help me keep track of where
> I am is to use colorized prompts. Red is root, cyan is local user,
> purple is local user with developer environment variables, green is
> remote, etc. It helps when you have as many different terminal
> sessio
On Fri, Jul 09, 2004 at 10:31:02AM -0400, Ken Long wrote:
> I have a question that I hope someone can help me with.
>
> As some background, we had a problem where every once in a very long
> while, someone (usually me O:) ) would get a little ahead of themselves
> and issue a shutdown command to s
> > use colorized prompts. Red is root, cyan is local user, purple is local
> > user with developer environment variables, green is remote, etc. It
> > helps when you have as many different terminal sessions open at one time
> > as I do.
>
> Wow, how could you do that? Can you share your code wi
On Sat, 10 Jul 2004 00:55:08 -0400, Silvan wrote:
> anyway. One thing I've done to help me keep track of where I am is to use
> colorized prompts. Red is root, cyan is local user, purple is local user
> with developer environment variables, green is remote, etc. It helps when
> you have as m
> /sbin/shutdown file, or better yet, redirect the new /sbin/shutdown file
> to /sbin/shutdown.real instead? Is that possible?
You already have the answer you seek about dpkg-divert. It works well.
While your problem is certainly solved, I thought I'd throw out a suggestion
anyway. One thing
Ken Long wrote:
I have a question that I hope someone can help me with.
As some background, we had a problem where every once in a very long
while, someone (usually me O:) ) would get a little ahead of themselves
and issue a shutdown command to shut down the system they were logged in
on. Problem
--- Ken Long <[EMAIL PROTECTED]> wrote:
> So, I had this bright idea to replace shutdown with a script that
> would take an additional parameter of the hostname of the system. The
> script would then check the hostname given on the commandline against
> the hostname of the system it was bein
On Fri, 09 Jul 2004 10:31:02 -0400
Ken Long <[EMAIL PROTECTED]> wrote:
> So, here is my question. How can I make it so that if I upgrade the
> sysvinit package on a system, it will either just not touch the
> /sbin/shutdown file, or better yet, redirect the new /sbin/shutdown
> file to /sbin/shu
I have a question that I hope someone can help me with.
As some background, we had a problem where every once in a very long
while, someone (usually me O:) ) would get a little ahead of themselves
and issue a shutdown command to shut down the system they were logged in
on. Problem was, the person
17 matches
Mail list logo
