On Wed, 26 Nov 2008, Boyd Stephen Smith Jr. wrote:
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
I've been going thru a number of bash related web sites looking for the
way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export HISTCONTROL=ignoredups:era
Am 2008-11-26 15:28:47, schrieb Robert Holtzman:
> I've been going thru a number of bash related web sites looking for the
> way to eliminate duplicates in ~/.bash_history. So far I've turned up
>
> export HISTCONTROL=ignoredups
> export HISTCONTROL=erasedups
> awk '!x[$0]++' .bash_history > .bas
On Wednesday 2008 November 26 16:28, Robert Holtzman wrote:
> I've been going thru a number of bash related web sites looking for the
> way to eliminate duplicates in ~/.bash_history. So far I've turned up
I use:
export HISTCONTROL=ignoredups:erasedups
My .bash_history doesn't have any adjacent d
On Wed, Nov 26, 2008 at 5:28 PM, Robert Holtzman <[EMAIL PROTECTED]> wrote:
> I've been going thru a number of bash related web sites looking for the way
> to eliminate duplicates in ~/.bash_history. So far I've turned up
>
> export HISTCONTROL=ignoredups
> export HISTCONTROL=erasedups
> awk '!x[$0
Eduard Bloch, 07/08/07 16:40:
>> Hi Anna.
>>
>> Anna Machens, 08.07.2007 15:48:
>> That’s really odd; I experienced the same thing yesterday. Suddenly
>> there was no
>> history anymore but since then, the file has been growing normally like
>> before.
>
> I have seen this several times in the pa
Quoting Eduard Bloch <[EMAIL PROTECTED]>:
I have seen this several times in the past, still having no idea how
this happens. For a while I suspected bash_completion but I think I
saw this also without bash_completion. Finally I am suspecting the
filesystem journaling doing weird thin
Eduard Bloch wrote:
Hi Anna.
Anna Machens, 08.07.2007 15:48:
(i'm using debian unstable )
i am totally confused. suddenly, my .bash_history file for root did not
exist
anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly
there was no
history anymore but
> Hi Anna.
>
> Anna Machens, 08.07.2007 15:48:
> > (i'm using debian unstable )
> > i am totally confused. suddenly, my .bash_history file for root did not
> > exist
> > anymore.
>
> That’s really odd; I experienced the same thing yesterday. Suddenly
> there was no
> history anymore but sinc
Hi Anna.
Anna Machens, 08.07.2007 15:48:
> (i'm using debian unstable )
> i am totally confused. suddenly, my .bash_history file for root did not
> exist
> anymore.
That’s really odd; I experienced the same thing yesterday. Suddenly there was no
history anymore but since then, the file has be
On Monday 21 November 2005 06:07 pm, Adam Hardy wrote:
> Roberto C. Sanchez on 21/11/05 22:30, wrote:
> > On Mon, Nov 21, 2005 at 10:00:33PM +, Adam Hardy wrote:
> >>thanks for the tips about C-r Is there some sort of documentation on
> >> this? I'd like to see how much history it keeps. It's a
C. Chad Wallace on 22/11/05 02:38, wrote:
Stephen Rueger wrote:
Adam Hardy <[EMAIL PROTECTED]> writes:
This used to work until recently when I found that the .bash_history
had been transformed into a data file, instead of the ASCII text that
I was used to.
How exactly did you find that ou
Stephen Rueger wrote:
Adam Hardy <[EMAIL PROTECTED]> writes:
This used to work until recently when I found that the .bash_history had
been transformed into a data file, instead of the ASCII text that I was
used to.
How exactly did you find that out? If it's merely because grep says
something
Adam Hardy <[EMAIL PROTECTED]> writes:
>This used to work until recently when I found that the .bash_history had
>been transformed into a data file, instead of the ASCII text that I was
>used to.
How exactly did you find that out? If it's merely because grep says
something like "binary file .ba
Roberto C. Sanchez on 21/11/05 22:30, wrote:
On Mon, Nov 21, 2005 at 10:00:33PM +, Adam Hardy wrote:
thanks for the tips about C-r Is there some sort of documentation on this? I'd
like to see how much history it keeps. It's a seperate program from history,
right?
HISTSIZE
On Mon, Nov 21, 2005 at 10:00:33PM +, Adam Hardy wrote:
>
> thanks for the tips about C-r Is there some sort of documentation on this?
> I'd
> like to see how much history it keeps. It's a seperate program from history,
> right?
>
HISTSIZE
The number of commands to rem
Clive Menzies on 21/11/05 10:23, wrote:
On (20/11/05 21:41), Ralph Katz wrote:
On 11/20/2005 05:20 PM, Adam Hardy wrote:
I rely on .bash_history alot to remind me what command syntax to use - I
don't scroll back thro the history with the up button, I just grep the
.bash_history file for the co
On Sun, 2005-11-20 at 23:45 +, Oliver Lupton wrote:
> On Sun, 20 Nov 2005 22:17:59 +
> Adam Hardy <[EMAIL PROTECTED]> wrote:
>
> > I rely on .bash_history alot to remind me what command syntax to use - I
> > don't scroll back thro the history with the up button, I just grep the
> > .bash
On (20/11/05 21:41), Ralph Katz wrote:
> On 11/20/2005 05:20 PM, Adam Hardy wrote:
> > I rely on .bash_history alot to remind me what command syntax to use - I
> > don't scroll back thro the history with the up button, I just grep the
> > .bash_history file for the command I want to run.
> >
> > T
On 11/20/2005 05:20 PM, Adam Hardy wrote:
> I rely on .bash_history alot to remind me what command syntax to use - I
> don't scroll back thro the history with the up button, I just grep the
> .bash_history file for the command I want to run.
>
> This used to work until recently when I found that t
On Sun, 20 Nov 2005 22:17:59 +
Adam Hardy <[EMAIL PROTECTED]> wrote:
> I rely on .bash_history alot to remind me what command syntax to use - I
> don't scroll back thro the history with the up button, I just grep the
> .bash_history file for the command I want to run.
>
> This used to work
Sent: Sunday, October 22, 2000 12:16 AM
Subject: Re: bash_history
> I think you can turn saving of the history on/off, see man bash:
>
> ...
>HISTSIZE
> The number of commands to remember in the command
> history (see HISTORY below
t; Sent: Friday, October 20, 2000 10:30 PM
> Subject: Re: bash_history
>
> "Matthias Mann" <[EMAIL PROTECTED]> writes:
>
> > Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
> > system the bash don´t save anything to /root/bash_histor
Yes this is a typo! Do you have any answere of my questions?
- Original Message -
From: Moritz Schulte <[EMAIL PROTECTED]>
To:
Sent: Friday, October 20, 2000 10:30 PM
Subject: Re: bash_history
"Matthias Mann" <[EMAIL PROTECTED]> writes:
> Is there a bug in
"Matthias Mann" <[EMAIL PROTECTED]> writes:
> Is there a bug in bash (Debian 2.2.0 potato)? When i go as root into my
> system the bash don´t save anything to /root/bash_history.
Is this a typo? Bash's history should be in ~/.bash_history.
moritz
--
/* Moritz Schulte <[EMAIL PROTECTED]>
Joey Hess wrote:
> Let's cut it down some..
>
> > cc anatomy.c -o anatomy
> > cc kod.c -o kofd
> > cp kofd kod
> > rm kofd
>
> According to google, kod and kofd are related to the oracle database.
> It's possible this is a cooincidence, or he was using these names to try
> to appear innocous (wei
"Dzuy M. Nguyen" wrote:
> This linux box was plugged into the same LAN as our company NT Network.
> It wasn't setup to access the NT Network or be involved in it. It just
> get's
> it's TCP/IP signal from the LAN.
And what about the internet connection? Are all of your NT boxes
connected directly
ave scanned the ports of the computers physically
connected on this LAN? Should I be concerned with the security of the
whole office now?
- Original Message -
From: w trillich <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 02, 2000 6:58 PM
Subject: Re: bash_history from Cracked Computer
Dzuy M. Nguyen wrote:
> Can someone help me figure out this "/.bash_history" from my
> computer that someone cracked into and did some damage.
>
> I'll probably re-install the box, but I'd like to see what they did
> before I destroy it. I've attached the "/.bash_history".
Let's cut it down some
if you run updatedb via cron (or run it from the shell by hand
recently) it'll tell you if you have any of the evil files
on your computer:
locate pscan
locate wuftp
locate bnc2
locate .shit
locate anatomy
locate kod
locate '/b$'
if you find a
That's an awesome trail your cracker left there...!
Does anyone know what 'anatomy' and 'kofd/kod' are? Perhaps the source
is still on the machine in /root/.dead/home/.dead/dead/ (or something
like that)
It looks like he was performing port scans from your machine (./pscan IP
PORT entries). Don't
Many thanks to all for help with this.
Patrick
> On Wed, 14 Jul 1999, Patrick Kirk wrote:
>
> > Hi all,
> >
> > I love the ability to get at previous commands just by flicking the up
> >arrow. But if the last 15 commands were mutt, its a little less
> >conenient. Is there a way that if the last 15 commands were ls preceded
> >by 10 mutts
Something that might help:
bash has both emacs and vi key bindings, and I think it defaults to emacs,
SO if you know that you used 'ls -stuFF' many commands ago, you can
type
ls
and bash will search backwards in the history list for the last time you
used ls and instantly take you there.
I use th
On Wed, Jul 14, 1999 at 09:23:12AM -0400, Michael E. Touloumtzis wrote:
> On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> > ... Is there a way that if the last 15 commands were ls preceded
> > by 10 mutts amd preceded by three tops, then the uparrow would
> > first show ls, then mu
Many thanks. I edited /etc/skel/.bash_profile and it is much easier now.
Patrick
On Wed, Jul 14, 1999 at 09:23:12AM -0400, Michael E. Touloumtzis wrote:
> On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> > ... Is there a way that if the last 15 commands were ls preceded
> > by 10
On Wed, Jul 14, 1999 at 02:05:27PM +0100, Patrick Kirk wrote:
> ... Is there a way that if the last 15 commands were ls preceded
> by 10 mutts amd preceded by three tops, then the uparrow would
> first show ls, then mutt and then top?
man bash
export HISTCONTROL=ignoredups
36 matches
Mail list logo
