From: Dominik Vogt <dominik.vogt@gmx.de>
To: zsh-users@zsh.org
Subject: Re: Bug: Losing .zsh_history
Date: Thu, 6 Oct 2022 11:30:29 +0100 [thread overview]
Message-ID: <Yz6uRU7d1OwnTzOK@localhost> (raw)
In-Reply-To: <CAH+w=7YmLcwXSj4nGFDRAOweqVvwJcSQt7SFkSTd4qmNHAZNvQ@mail.gmail.com>
On Wed, Oct 05, 2022 at 09:34:15PM -0700, Bart Schaefer wrote:
> On Wed, Oct 5, 2022 at 4:03 PM Dominik Vogt <dominik.vogt@gmx.de> wrote:
> > Actually, what's really strange is that the shell should not be
> > started at all in this situation: The display only ever fails
> > when powering on; once it works it keeps working.
>
> It's possible that the window manager has started even though it can't
> use the display, so you can't see it.
No, the box boots to the console and X is started from the command
line.
> Is it possible that a shell is starting on a different virtual
> terminal (console)?
Can't think of a way to get into an _interactive_ zsh without typing
a password sowmewhere. The loss must have occured when shutting
down the machine in the previous session.
> Incidentally, everything I've seen with publication dates in the last
> 7 years says that it's no longer worthwhile to worry about SSD wear
> from repeated writes. Any recently-manufactured SSD will probably
> outlast an HDD.
> I suppose you did mention that you have an old
> machine, so maybe you're trying to preserve a very old drive?
Yeah. But I've just taken a look at the output of the smartmon
tools and it looks like even the ancient disk will be safe for
many more years. Leaving 1/3 of the disk space unpartitioned
seems to be good enough for the rest of my life, without having to
worry about additional measures.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
next prev parent reply other threads:[~2022-10-06 10:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:55 Dominik Vogt
2022-10-05 20:01 ` Eric Cook
2022-10-05 20:20 ` Dominik Vogt
2022-10-05 21:05 ` Wesley
2022-10-05 21:24 ` Dominik Vogt
2022-10-05 22:31 ` Bart Schaefer
2022-10-05 23:03 ` Dominik Vogt
2022-10-06 4:34 ` Bart Schaefer
2022-10-06 9:40 ` Peter Stephenson
2022-10-06 10:52 ` Dominik Vogt
2022-10-06 10:30 ` Dominik Vogt [this message]
2022-10-05 20:26 ` Dominik Vogt
2022-10-05 22:16 ` Bart Schaefer
2022-10-05 22:32 ` Dominik Vogt
2022-10-06 10:31 ` Dominik Vogt
2022-10-07 11:45 ` Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yz6uRU7d1OwnTzOK@localhost \
--to=dominik.vogt@gmx.de \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).