This is how I keep a long-term record of bash commands from different
sessions:
https://www.reddit.com/r/bash/comments/ak9c3r/
HTH
--
Karl Vogel I don't speak for anyone but myself
Comment: I use a screwdriver a lot
Reply: I'm all out of orange juice. Will straight vodka
On Sun, Jul 28, 2024 at 5:16 AM songbird wrote:
> not that i would want that,
>
> but it would be possible for various terminals to save to
> their own unique history files based upon terminal pty or
> tty or anything else you'd like and to reload those upon
>
On Sat, Jul 27, 2024 at 11:23 PM Jeffrey Walton wrote:
> On Sun, Jul 28, 2024 at 12:25 AM Mike Castle wrote:
> > * I keep history under source control (currently git) and regularly
> > (well, for some definition of "regularly"), merge them across machines
>
> Thi
On Sat, Jul 27, 2024 at 11:04 PM mick.crane wrote:
> If I've "su'd" I type "exit".
> To close the terminal I click that X in the virtual terminal's top right
> hand corner.
Depending on settings, that may or may not save that invocation's
histo
On 2024-07-28 at 09:29, Yassine Chaouche wrote:
> Le 7/28/24 à 12:19, songbird a écrit :
>
>> to keep my own setup consistent and to not keep certain things in
>> history i actually do the opposite of what you want because i want
>> certain commands already preload
Le 7/28/24 à 12:19, songbird a écrit :
[...]
to keep my own setup consistent and to not keep certain
things in history i actually do the opposite of what you
want because i want certain commands already preloaded in
my history for all windows when i start up and then i adjust
my environment
mick.crane wrote:
> In debian bookworm, xfce desktop, different virtual terminals have a
> different history if same user presses "up key" in different virtual
> terminals ?
> Is this something that can be changed so history is shared between
> virtual terminals?
&
Le 7/28/24 à 05:24, Mike Castle a écrit :
On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote:
Is this something that can be changed so history is shared between
virtual terminals?
Yes.
[...]
From my .bashrc file, I have the following history related settings:
# No limit on running
On 2024-07-27 23:58, Greg Wooledge wrote:
You need to specify *exactly* what you're doing.
"exactly" is at mickiwiki.com
I can take the ridicule of my coding understanding.
Whenever I need to reboot my computer (kernel update or the like), I
decide which shells I want to reta
On Sun, Jul 28, 2024 at 12:25 AM Mike Castle wrote:
>
> On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote:
> > Is this something that can be changed so history is shared between
> > virtual terminals?
>
> [...]
> For me, I see up bash with the following features:
> *
see the history
in a new terminal, where I "cd'd" to for example.
stuff like that.
No, I mean *how did you close the terminal*? And what terminal is it?
one of these
1826 ?Sl 0:00 xfce4-terminal
1854 pts/0Ss 0:00 bash
If I've "su'd" I type
On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote:
> Is this something that can be changed so history is shared between
> virtual terminals?
Yes.
There are all sorts of settings that can control how shells save
history. Most shells are capable of doing whatever you want, but the
d
On 28/07/2024 08:01, mick.crane wrote:
Sometimes I forget where I was after closing a virtual terminal and it
would be handy to see the history
in a new terminal, where I "cd'd" to for example.
help history
less ~/.bash_history
On Sun, Jul 28, 2024 at 02:01:04 +0100, mick.crane wrote:
> On 2024-07-27 23:58, Greg Wooledge wrote:
> > You need to specify *exactly* what you're doing.
> Sometimes I forget where I was after closing a virtual terminal and it
> would be handy to see the history
> in
her directories that
I"ll use bits of.
Mainly using different windows Ctrl+Alt+arrows in Xfce with their own
virtual terminals.
Sometimes I forget where I was after closing a virtual terminal and it
would be handy to see the history
in a new terminal, where I "cd'd" to for
On 2024-07-27 22:50:17 +0100, mick.crane wrote:
> In debian bookworm, xfce desktop, different virtual terminals have a
> different history if same user presses "up key" in different virtual
> terminals ?
> Is this something that can be changed so history is shared betwe
On 2024-07-27 at 18:44, mick.crane wrote:
> On 2024-07-27 23:08, Greg Wooledge wrote:
>
>> On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote:
>>
>>> In debian bookworm, xfce desktop, different virtual terminals
>>> have a different history if same us
On Sat, Jul 27, 2024 at 23:44:08 +0100, mick.crane wrote:
> On 2024-07-27 23:08, Greg Wooledge wrote:
> > On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote:
> > > In debian bookworm, xfce desktop, different virtual terminals have a
> > > different history if sa
On 2024-07-27 23:08, Greg Wooledge wrote:
On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote:
In debian bookworm, xfce desktop, different virtual terminals have a
different history if same user presses "up key" in different virtual
terminals ?
As your subject says, this is &qu
Hi,
On Sat, Jul 27, 2024 at 10:50:17PM +0100, mick.crane wrote:
> Is this something that can be changed so history is shared between virtual
> terminals?
You may be interested in "atuin" to aggregate shell history from
multiple logins and machines in a searchable interface. It ca
On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote:
> In debian bookworm, xfce desktop, different virtual terminals have a
> different history if same user presses "up key" in different virtual
> terminals ?
As your subject says, this is "bash history". And y
In debian bookworm, xfce desktop, different virtual terminals have a
different history if same user presses "up key" in different virtual
terminals ?
Is this something that can be changed so history is shared between
virtual terminals?
mick
On Mon 05/02/2024 at 00:45, Greg Wooledge wrote:
...
> If you're one of these "I want every command I ever run to be in my
> shell history, retained forever, and I don't care how much space it
> takes" people, then there are web pages out there that can help you.
>
(Re)posting the below as requested, and can confirm
history -r
seems to have the desired effect.
Thanks.
- Original message -
From: Will Mengarini
To: Gareth Evans
Cc: debian-user@lists.debian.org
Subject: Re: script/history
Date: Monday, 5 February 2024 01:02
* Gareth Evans [24
* Gareth Evans [24-02/04=Su 09:46 +]:
> Re the script command, does anyone know of a way to make
> commands run during a script session appear in bash history too?
You want the 'history -r' command, "explained" by `help history`.
After you end the script, you&#x
On Mon, Feb 05, 2024 at 12:28:38AM +, Gareth Evans wrote:
> I was trying to view the history of commands run during a script session.
>
> user@qwerty:~$ script foo
> Script started, output log file is 'foo'.
> user@qwerty:~$ date
> Mon 5 Feb 00:21:16 GMT 2024
On Sun 04/02/2024 at 19:45, David Wright wrote:
...
> According to this man page for csh (but includes tcsh):
>
> https://linux.die.net/man/1/csh
>
> the "a" that modifies modifiers is a "[feature] of tcsh not found
> in most csh(1) implementations (specifically, the 4.4BSD csh)". It
> appears t
On Sun 04/02/2024 at 17:33, Greg Wooledge wrote:
...
> The script(1) utility has NOTHING to do with running ordinary shell
> scripts.
I understand that.
I was trying to view the history of commands run during a script session.
user@qwerty:~$ script foo
Script started, output log file i
On Sun, Feb 04, 2024 at 01:45:27PM -0600, David Wright wrote:
> SCRIPT(1) User Commands SCRIPT(1)
> [ … ]
> HISTORY
>The script command appeared in 3.0BSD.
>
> I have no idea why "the history mechanism" is even mentioned
>
gt; >> "SEE ALSO
> >> csh(1) (for the history mechanism)"
My take on this is that the man page was originally written for
BSD, which lies on the csh side of the "great divide" rather
than the sh/bash side.
SCRIPT(1) User Commands
On Sun, Feb 04, 2024 at 04:01:29PM +, Gareth Evans wrote:
> It seemed to me initially (as I should perhaps have stated) that man script
> was suggesting that csh was a component or depedency (of script), which
> seemed to be contradicted by it not being installed. On reflection,
> possibly,
On Sun 04/02/2024 at 13:24, Max Nikulin wrote:
> On 04/02/2024 16:46, Gareth Evans wrote:
>> Re the script command, does anyone know of a way to make commands run during
>> a script session appear in bash history too?
> [...]
>> man script says
>>
>> "SE
date
> > Sun 4 Feb 09:44:00 GMT 2024
> > $ exit
> > exit
> > Script done.
> > $ history|tail -n2
> > 30797 2024-02-04 09:43:57 script foo.txt
> > 30798 2024-02-04 09:44:21 history|tail -n2
> >
> > I did try to search on this but just got lots o
On 04/02/2024 16:46, Gareth Evans wrote:
Re the script command, does anyone know of a way to make commands run during a
script session appear in bash history too?
[...]
man script says
"SEE ALSO
csh(1) (for the history mechanism)"
but
$ man csh
No manual entry for csh
On Sun, Feb 04, 2024 at 09:46:09AM +, Gareth Evans wrote:
> man script says
>
> "SEE ALSO
> csh(1) (for the history mechanism)"
>
> but
>
> $ man csh
> No manual entry for csh
I'm so glad that we're entering an era where it's norm
> $ script foo.txt
> Script started, output log file is 'foo.txt'.
> $ date
> Sun 4 Feb 09:44:00 GMT 2024
> $ exit
> exit
> Script done.
> $ history|tail -n2
> 30797 2024-02-04 09:43:57 script foo.txt
> 30798 2024-02-04 09:44:21 history|tail -n2
>
On Sun, 2024-02-04 at 09:46 +, Gareth Evans wrote:
> Re the script command, does anyone know of a way to make commands
> run during a script session appear in bash history too?
Maybe this:
https://serverfault.com/questions/16204/how-to-make-bash-scripts-print-out-every-command-bef
Re the script command, does anyone know of a way to make commands run during a
script session appear in bash history too?
$ script foo.txt
Script started, output log file is 'foo.txt'.
$ date
Sun 4 Feb 09:44:00 GMT 2024
$ exit
exit
Script done.
$ history|tail -n2
30797 2024-02-0
I’m comforted by this friendly discussion about the old days versus the
modern generation by fellow old folks of pre-PC days.
Sort of like an afternoon gathering at the Elks or the VFW.
Thank you all.
Blessings.
-Tom
On Fri, Nov 03, 2023 at 12:57:39PM -0500, John Hasler wrote:
> tomas writes:
> > See my other reply. My whole point is about making lives of curious
> > users easier by sticking to the terminology they'll find should they
> > dare (yes,please!) to open that door to the cellar.
>
> The people at Xe
On Fri, Nov 03, 2023 at 08:25:20AM -0500, John Hasler wrote:
> tomas writes:
> > Small anecdote: there was an old Linux distro (ISTR it was SuSE) where
> > something below /etc/init.d (or was it /etc/rc.d? It's a long while
> > ago) was a symlink to the parent directory, creating an infinite
> > hi
tomas writes:
> Small anecdote: there was an old Linux distro (ISTR it was SuSE) where
> something below /etc/init.d (or was it /etc/rc.d? It's a long while
> ago) was a symlink to the parent directory, creating an infinite
> hierarchy (or a circular reference, depending on how you squint).
On Sys
tomas writes:
> See my other reply. My whole point is about making lives of curious
> users easier by sticking to the terminology they'll find should they
> dare (yes,please!) to open that door to the cellar.
The people at Xerox PARC and SRI who came up with the desktop metaphor
in the early years
On 2023-11-06, Nicolas George wrote:
> Loris Bennett (12023-11-06):
>> I beg to differ. I think you are confusing the precise definition of
>> something with the label used to refer to it. When the transistor was
>> invented, so was a new word to describe it. When this particular
>> concept of
Loris Bennett (12023-11-06):
> I beg to differ. I think you are confusing the precise definition of
> something with the label used to refer to it. When the transistor was
> invented, so was a new word to describe it. When this particular
> concept of how to organise data on a computer, about wh
Nicolas George writes:
>> Surely 'directory' is also just a more or
>> less apt metaphor
>
> You missed the point: directory is not a metaphor at all, it is a
> precise term for what is actually being talked about.
I beg to differ. I think you are confusing the prec
Hi,
Nicolas George wrote:
> > Ear, ear!
Curt wrote:
> An ear c'est une oreille.
C'est probablement because les frenchais ne cannot pas prononcer le "H".
Have a nice day :)
Thomas
On Fri, Nov 03, 2023 at 11:33:55AM -0400, Stefan Monnier wrote:
> > Regarding Tomas' assertion, I'm not sure I buy into the argument
> > regarding dumbing-down [...]
> I guess in a sense what's going on here is that these words act as kinds
> of "dog whistle". I don't think the argument that "dir
On Fri, Nov 03, 2023 at 03:46:38PM +0100, Loris Bennett wrote:
> Nicolas George writes:
>
> > to...@tuxteam.de (12023-11-03):
> >> The other is related: folder has become the culture of those
> >> who want to "sell you knowledge", i.e. of those whose business
> >> model is based on keeping you du
On 2023-11-03, Nicolas George wrote:
> to...@tuxteam.de (12023-11-03):
>> The other is related: folder has become the culture of those
>> who want to "sell you knowledge", i.e. of those whose business
>> model is based on keeping you dumb.
>
> Ear, ear!
https://fr.wikipedia.org/wiki/Hear,_hear
A
On 11/3/23 11:17, Nicolas George wrote:
Loris Bennett (12023-11-03):
If I think of the main non-digital directory I have dealt with in my
life it was a telephone directory. That also did not contain further
directories within itself.
On the other hand, scholarly articles usually contain a bib
t;directory" is better
technically than "folder" is really strong, so I can totally imagine
a different version of the world's history where those two terms end up
used in exactly reversed ways where Unix (and win32) ends up using
"folder" while Windows's user-fac
Loris Bennett (12023-11-03):
> If I think of the main non-digital directory I have dealt with in my
> life it was a telephone directory. That also did not contain further
> directories within itself.
On the other hand, scholarly articles usually contain a bibliography
section, i.e. a directory of
Nicolas George writes:
> to...@tuxteam.de (12023-11-03):
>> The other is related: folder has become the culture of those
>> who want to "sell you knowledge", i.e. of those whose business
>> model is based on keeping you dumb.
>
> Ear, ear!
>
> Also, that metaphor is easy, but it is very shaky. In
On Fri, Nov 03, 2023 at 08:46:36AM +0100, Nicolas George wrote:
> to...@tuxteam.de (12023-11-03):
> > The other is related: folder has become the culture of those
> > who want to "sell you knowledge", i.e. of those whose business
> > model is based on keeping you dumb.
>
> Ear, ear!
>
> Also, tha
to...@tuxteam.de (12023-11-03):
> The other is related: folder has become the culture of those
> who want to "sell you knowledge", i.e. of those whose business
> model is based on keeping you dumb.
Ear, ear!
Also, that metaphor is easy, but it is very shaky. In the physical
world, I have *sometim
On Thu, Nov 02, 2023 at 11:17:01PM -0400, Greg Wooledge wrote:
> On Thu, Nov 02, 2023 at 12:16:54PM -0500, John Hasler wrote:
> > This was in the 1970s when the graphical UI was being invented. The
> > idea was that the screen was to look like an actual desktop which might
> > have actual file fol
The culprit is MAME (mame_0.206+dfsg.1-1 in my buster machine). I deleted
the directory, ran MAME thru the menu and voila, it showed up again.
changing .mame/io.ini so that the key historypath starts with .mame/ is
enough to make the problem disappear for me.
HTH,
--
[]s; Massa⠠⠵
via GMail Inbo
On Sat, 18 Apr 2020 at 22:15, wrote:
> On Saturday, April 18, 2020 07:00:53 AM David wrote:
> > On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> > > I can see any *ONE* previous commands by using the up-arrow key.
> > > But I need to see the *comple
On 18/4/20 10:14 pm, rhkra...@gmail.com wrote:
On Saturday, April 18, 2020 07:00:53 AM David wrote:
On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obv
On Sat 18 Apr 2020 at 09:31:10 (-0400), songbird wrote:
> David wrote:
> > On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> >>
> >> I can see any *ONE* previous commands by using the up-arrow key.
> >> But I need to see the *complete* history. F1 is no &q
David wrote:
> On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
>>
>> I can see any *ONE* previous commands by using the up-arrow key.
>> But I need to see the *complete* history. F1 is no "Help".
>> Obviously its stored in a file. Where?
>
> Read
On Saturday, April 18, 2020 07:52:23 AM Richard Owlett wrote:
> On 04/18/2020 05:19 AM, Richard Owlett wrote:
> > I can see any *ONE* previous commands by using the up-arrow key.
> > But I need to see the *complete* history. F1 is no "Help".
> > Obviously its s
On Saturday, April 18, 2020 07:00:53 AM David wrote:
> On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
> > I can see any *ONE* previous commands by using the up-arrow key.
> > But I need to see the *complete* history. F1 is no "Help".
> > Obviously its stored
On Sat, Apr 18, 2020 at 06:52:23AM -0500, Richard Owlett wrote:
[...]
> There's one thing I don't understand - erasure of previous history.
> https://mywiki.wooledge.org/BashFAQ/088 states it as:
> >... it overwrites the existing history with the new version.
That&
On 04/18/2020 05:19 AM, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
Using 'cat ~/.bash_history' gives desired format (i.e. witho
On Sat, 18 Apr 2020 at 20:20, Richard Owlett wrote:
>
> I can see any *ONE* previous commands by using the up-arrow key.
> But I need to see the *complete* history. F1 is no "Help".
> Obviously its stored in a file. Where?
Reading https://mywiki.wooledge.org/BashFAQ/08
On 18/04/2020 11:19, Richard Owlett wrote:
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
Well, for Bash, the file is at ~/.bash_history (as set in $HISTF
On Sat, 18 Apr, 2020 at 05:19:40 -0500, Richard Owlett wrote:
> I can see any *ONE* previous commands by using the up-arrow key.
> But I need to see the *complete* history. F1 is no "Help".
> Obviously its stored in a file. Where?
> TIA
Use the 'history' command, o
I can see any *ONE* previous commands by using the up-arrow key.
But I need to see the *complete* history. F1 is no "Help".
Obviously its stored in a file. Where?
TIA
On Fri, Dec 27, 2019 at 2:58 PM Sven Joachim wrote:
> On 2019-12-27 12:20 -0700, Keith Christian wrote:
>
> > It seems at one point there was a debian documentation package that
> > contained either text or HTML versions of the project's history as
> > seen
On 2019-12-27 12:20 -0700, Keith Christian wrote:
> It seems at one point there was a debian documentation package that
> contained either text or HTML versions of the project's history as
> seen on this page:
>
> https://www.debian.org/doc/manuals/project-history
It seems at one point there was a debian documentation package that
contained either text or HTML versions of the project's history as
seen on this page:
https://www.debian.org/doc/manuals/project-history/ch-releases.en.html
Unable to find anything on packages.debian.org containin
ectory to a
backup disk. That's been running for several years without any changes.
I periodically run rsync manually as well.
> Are they open by some process? Check with lsof.
The commands "lsof | grep history" and "sudo lsof | grep 'history.db'"
return noth
On Fri 09 Aug 2019 at 14:53:32 (-0500), Greg Marks wrote:
> On a computer running Debian 10, in a number of directories a
> subdirectory "history" has mysteriously appeared containing a
> file history.db. There are 11 of these history.db files in various
> places in my home
On 10/08/19 7:53 AM, Greg Marks wrote:
> On a computer running Debian 10, in a number of directories a
> subdirectory "history" has mysteriously appeared containing a
> file history.db. There are 11 of these history.db files in various
> places in my home directory; cmp rev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 10/8/19 1:32 pm, David wrote:
> I don't know the answer, but you might find some clues here:
> https://codesearch.debian.net/search?q=history.db&literal=1 Note
> the list of package names at the top of the page.
Why is it not accessible vi
Do you have some kind of backup, sync, or versioning application running?
On Fri, Aug 9, 2019, 22:01 Greg Marks wrote:
> On a computer running Debian 10, in a number of directories a
> subdirectory "history" has mysteriously appeared containing a
> file history.db. Th
On Sat, 10 Aug 2019 at 13:01, Greg Marks wrote:
>
> On a computer running Debian 10, in a number of directories a
> subdirectory "history" has mysteriously appeared containing a
> file history.db.
[...]
> Does anyone know what might be causing this?
I don't know
On a computer running Debian 10, in a number of directories a
subdirectory "history" has mysteriously appeared containing a
file history.db. There are 11 of these history.db files in various
places in my home directory; cmp reveals that they are all identical.
Each is an "SQLi
On Friday 10 May 2019 03:45:49 am Curt wrote:
> On 2019-05-09, Gene Heskett wrote:
> > On Thursday 09 May 2019 12:51:24 pm Curt wrote:
> >> On 2019-05-09, Gene Heskett wrote:
> >> > Greetings all;
> >> >
> >> > I have a need to transfer all the prefs -"saved logins" from a
> >> > wheezy install
On 2019-05-09, Gene Heskett wrote:
> On Thursday 09 May 2019 12:51:24 pm Curt wrote:
>
>> On 2019-05-09, Gene Heskett wrote:
>> > Greetings all;
>> >
>> > I have a need to transfer all the prefs -"saved logins" from a
>> > wheezy install to a stretch install, separate drives. And obviously
>> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
rhkra...@gmail.com wrote:
> On Thursday, May 09, 2019 03:54:33 PM Dan Purgert wrote:
>> Gene Heskett wrote:
>> > On Thursday 09 May 2019 12:00:56 pm john doe wrote:
>> >> I would say the 'profile' that you want to move.
>> >
>> > That does not exist
On Thursday 09 May 2019 07:53:44 pm David Wright wrote:
> On Thu 09 May 2019 at 16:26:10 (-0400), Gene Heskett wrote:
> > On Thursday 09 May 2019 12:51:24 pm Curt wrote:
> > > On 2019-05-09, Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > > I have a need to transfer all the prefs -"saved
On Thu 09 May 2019 at 16:26:10 (-0400), Gene Heskett wrote:
> On Thursday 09 May 2019 12:51:24 pm Curt wrote:
>
> > On 2019-05-09, Gene Heskett wrote:
> > > Greetings all;
> > >
> > > I have a need to transfer all the prefs -"saved logins" from a
> > > wheezy install to a stretch install, separat
On Thursday 09 May 2019 12:51:24 pm Curt wrote:
> On 2019-05-09, Gene Heskett wrote:
> > Greetings all;
> >
> > I have a need to transfer all the prefs -"saved logins" from a
> > wheezy install to a stretch install, separate drives. And obviously
> > the stretch firefox is about 20 versions newe
On Thursday, May 09, 2019 03:54:33 PM Dan Purgert wrote:
> Gene Heskett wrote:
> > On Thursday 09 May 2019 12:00:56 pm john doe wrote:
> >> I would say the 'profile' that you want to move.
> >
> > That does not exist in my $home dir on the src drive. Any idea where it
> > may be?
>
> Should be s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> On Thursday 09 May 2019 12:00:56 pm john doe wrote:
>
>> On 5/9/2019 5:32 PM, Gene Heskett wrote:
>> > Greetings all;
>> >
>> > I have a need to transfer all the prefs -"saved logins" from a
>> > wheezy install to a stretch inst
On Thursday 09 May 2019 12:00:56 pm john doe wrote:
> On 5/9/2019 5:32 PM, Gene Heskett wrote:
> > Greetings all;
> >
> > I have a need to transfer all the prefs -"saved logins" from a
> > wheezy install to a stretch install, separate drives. And obviously
> > the stretch firefox is about 20 vers
s I visit with that browser. (I save usernames
but not passwords.) IIRC it's cookies that prevent security questions
being asked all the time.
I think places is the file that contains history, along with bookmarks
and other stuff.
I don't believe I have a profile dating from wheezy so I don
On 2019-05-09, Gene Heskett wrote:
> Greetings all;
>
> I have a need to transfer all the prefs -"saved logins" from a wheezy
> install to a stretch install, separate drives. And obviously the
> stretch firefox is about 20 versions newer. What file do I copy from the
> wheezy drive to the stre
On 5/9/2019 5:32 PM, Gene Heskett wrote:
> Greetings all;
>
> I have a need to transfer all the prefs -"saved logins" from a wheezy
> install to a stretch install, separate drives. And obviously the
> stretch firefox is about 20 versions newer. What file do I copy from the
> wheezy drive to the st
Greetings all;
I have a need to transfer all the prefs -"saved logins" from a wheezy
install to a stretch install, separate drives. And obviously the
stretch firefox is about 20 versions newer. What file do I copy from the
wheezy drive to the stretch drive so my bank knows its me?
Cheers, Gen
On 2018-12-03, rhkra...@gmail.com wrote:
>> >
>> > The logs are gzipped periodically (gibberish for less).
>>
>> But not for zless.
>
> Hmm, I might have found / committed a [p]ebkac, it now seems that, for
> example:
>
> cat /var/log/dpkg.log.* | less
>
> ... works fine. Not sure what I did w
On Mon 03 Dec 2018 at 12:01:51 (-0500), rhkra...@gmail.com wrote:
> On Monday, December 03, 2018 10:21:44 AM Brian wrote:
> > On Mon 03 Dec 2018 at 14:57:53 +, Curt wrote:
> > > On 2018-12-03, rhkra...@gmail.com wrote:
> > > > On Monday, December 03, 2018 06:02:05 AM Steve Kemp wrote:
> > > >>
; > > The logs are gzipped periodically (gibberish for less).
>> >
>> > But not for zless.
>>
>> Hmm, I might have found / committed a [p]ebkac, it now seems that, for
>> example:
>>
>> cat /var/log/dpkg.log.* | less
>>
>> ... works fi
at, for
> example:
>
> cat /var/log/dpkg.log.* | less
>
> ... works fine. Not sure what I did wrong earlier. (And they apparently
> are
> not gzipped (on my Wheezy system).
>
I created a script to browse apt history:
https://twitter.com/CiudadanosCs/status/1069505851340349440?s=19
Maybe can be useful for you
>
On Monday, December 03, 2018 10:21:44 AM Brian wrote:
> On Mon 03 Dec 2018 at 14:57:53 +, Curt wrote:
> > On 2018-12-03, rhkra...@gmail.com wrote:
> > > On Monday, December 03, 2018 06:02:05 AM Steve Kemp wrote:
> > >> > Is there anywhere else I should look?
> > >> >
> > >> Take a look at /
On Mon, 3 Dec 2018, Curt wrote:
> Date: Mon, 3 Dec 2018 09:57:53
> From: Curt
> To: debian-user@lists.debian.org
> Subject: Re: Package install history - logs etc ?
> Resent-Date: Mon, 3 Dec 2018 15:00:24 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
&
On Mon 03 Dec 2018 at 14:57:53 +, Curt wrote:
> On 2018-12-03, rhkra...@gmail.com wrote:
> > On Monday, December 03, 2018 06:02:05 AM Steve Kemp wrote:
> >> > Is there anywhere else I should look?
> >>
> >> Take a look at /var/log/dpkg.log* too.
> >
> > (I am not the OP.) Is there a speci
1 - 100 of 435 matches
Mail list logo
