On 2024-01-26, Nicolas George wrote:
> Curt (12024-01-26):
>> A play-sound.timer unit file in /usr/lib/systemd/system-generators/initrd
>> directory.
>
> I see no mention of this directory on the web. Where did yo find the
> idea of using it, I want to check the doc.
I guess that path should've
On Sat, Jan 27, 2024 at 02:16:52PM +0100, Paul van der Vlis wrote:
> Op 27-01-2024 om 00:00 schreef Richard Lucassen:
> > On Wed, 24 Jan 2024 15:15:37 +0100 Paul van der Vlis wrote:
> >
> > > Op een vers geinstalleerde Debian12 heb ik een raar probleem met
> > > LetsEncrypt certificaten. (Ik
On Sat, 27 Jan 2024 14:16:52 +0100
Paul van der Vlis wrote:
> > Ik neem aan dat de user wel lid is van de groep ssl-cert. Eerst
> > uitloggen en weer inloggen voordat de user echt tot de groep hoort.
> > Misschien is dat het?
>
> Alles in /etc/letsencrypt was root:root.
> Dan helpt het niet als
Curt (12024-01-27):
> (Anyway, this is what my personal robot explained to me and may be subject to
> imperfection and error.)
I started explaining all the ways this answer is obviously nonsensical,
but I got fed up and deleted it.
If I wanted the answers from a stupid AI, I could have asked
On Sat, Jan 27, 2024 at 01:56:57PM -0500, Dotfiles wrote:
> If I make changes to the config files in /etc/zsh, do I have to worry about
> them getting overwritten if I do an upgrade to the next major Debian release?
If that release comes with a new config file, you will be
asked at installation
On Sat, Jan 27, 2024 at 02:31:07PM -0500, Dotfiles wrote:
> >
> > Debian always does this with configuration files.
> >
>
> OK, thanks. I’ve seen those prompts before with other config files but I
> wasn’t sure if it also happened with zsh. But it sounds like this is standard
> behavior for
On Fri, Jan 26, 2024 at 01:50:38PM -0600, David Wright wrote:
On Fri 26 Jan 2024 at 07:25:13 (-0500), Dan Ritter wrote:
Greg Wooledge wrote:
> On Thu, Jan 25, 2024 at 07:32:38PM -0500, Thomas George wrote:
> > The current PSI works perfectly but I don't like the pale green prompt.
> >
> > Tried
If I make changes to the config files in /etc/zsh, do I have to worry about
them getting overwritten if I do an upgrade to the next major Debian release?
On Sat, Jan 27, 2024 at 02:32:57PM +, Albretch Mueller wrote:
> apt-get installation logs (in --dry-run mode) show lines like:
> ...
> Inst libvncclient1 (0.9.14+dfsg-1 Debian:12.4/stable [amd64])
> Inst vlc-bin (3.0.20-0+deb12u1 Debian:12.4/stable [amd64])
> Inst vlc-plugin-qt
On Sat, Jan 27, 2024 at 06:07:28PM +0100, Geert Stappers wrote:
> On Sat, Jan 27, 2024 at 02:16:52PM +0100, Paul van der Vlis wrote:
> > Op 27-01-2024 om 00:00 schreef Richard Lucassen:
> > > On Wed, 24 Jan 2024 15:15:37 +0100 Paul van der Vlis wrote:
> > >
> > > > Op een vers geinstalleerde
>
> Debian always does this with configuration files.
>
OK, thanks. I’ve seen those prompts before with other config files but I wasn’t
sure if it also happened with zsh. But it sounds like this is standard behavior
for all config files. Good to know.
On Sat, 27 Jan 2024 14:16:52 +0100
Paul van der Vlis wrote:
> > Ik neem aan dat de user wel lid is van de groep ssl-cert. Eerst
> > uitloggen en weer inloggen voordat de user echt tot de groep hoort.
> > Misschien is dat het?
>
> Alles in /etc/letsencrypt was root:root.
> Dan helpt het niet als
David Wright (12024-01-26):
> It looks as if the root directory is decrypted by
> /usr/share/initramfs-tools/scripts/local-top/cryptroot
> and, from its prereqs, that this script makes sure it
> is the last to run from scripts/local-top, by actually
> being run from scripts/local-block/cryptroot.
I have installed Windows 10 on a notebook Asus F552M. Then I installed Debian
12, but no Grub at reboot only Windows. If I use SuperGrub cd by manual booting
I can access to debian and boot it. So I used Boort Repair Disk 64 to try to
repair, but it gave me a report advicing me to ask online
On Sat, Jan 27, 2024 at 05:07:37PM -, Curt wrote:
> On 2024-01-26, Nicolas George wrote:
> > Curt (12024-01-26):
> >> A play-sound.timer unit file in /usr/lib/systemd/system-generators/initrd
> >> directory.
> >
> > I see no mention of this directory on the web. Where did yo find the
> > idea
Hi Hans,
On Sat, Jan 27, 2024 at 10:23:09AM +0100, Hans wrote:
> I see this exactly as you and are watching this list for may years.
I'm not sure who you're replying to as you've removed those details,
though I may guess from your In-Reply-To header which doesn't point
to a list message. You
Good afternoon
Thank You
There is only one password.
The problem was created until
the update to DEBIAN 11 created panic.
Before
sudo
su
su -
did work.
Regards
Sophie
Von: Gareth Evans
Gesendet: Mittwoch, 24. Januar 2024 04:31
An: debian-user@lists.debian.org
Hi,
Andy Smith wrote:
> It is hard to understand how what Michael/Sophie/Tobias does can in
> any way be "fun" for them, though maybe that is just our lack of
> understanding.
I expressed my suspicion of a "Hurz" performance in
https://lists.debian.org/debian-user/2023/05/msg00100.html
Have
Hello,
On Sat, Jan 27, 2024 at 11:05:30AM +0100, Thomas Schmitt wrote:
> Andy Smith wrote:
> > It is hard to understand how what Michael/Sophie/Tobias does can in
> > any way be "fun" for them, though maybe that is just our lack of
> > understanding.
>
> I expressed my suspicion of a "Hurz"
On Fri, 2024-01-26 at 16:11 +0100, hw wrote:
> I've never had issues with any UPS due to self tests. The batteries
> need to be replaced when they are worn out. How often that is
> required depends on the UPS and the conditions it is working in,
> usually every 3--5 years.
It was with some
Hi,
I typically have logcheck send me anomalous logs. In the last week,
all Debian 10 machines (I know, I know, upgrade needed) started
logging this whenever I logged in from a particular other host by
SSH:
2024-01-27T07:59:42.003881+00:00 t.example.com sshd[12319]: Postponed publickey
for root
>> On Fri, Jan 26, 2024 at 07:42:30AM -0500, Dan Ritter wrote:
> Might be time for a new font. I like Inconsolata, but l1I!
> should never look similar, nor O0@ or S$.
My eyesight sucks like a black hole with daddy issues, so I like fonts
that are a bit larger than most. My favorites on
Op 27-01-2024 om 00:00 schreef Richard Lucassen:
On Wed, 24 Jan 2024 15:15:37 +0100
Paul van der Vlis wrote:
Op een vers geinstalleerde Debian12 heb ik een raar probleem met
LetsEncrypt certificaten. (Ik gebruik certbot, weet niet of dat van
belang is.)
Eerder was het zo dat gebruikers die
On 1/19/24, David Wright wrote:
> On Fri 19 Jan 2024 at 22:19:21 (+), Albretch Mueller wrote:
>> Package dependencies to me are just DAGs,
> Are they? No circular dependencies?
The way I see them, "circular dependencies" are "cultural".
"organizational" issues not essentially technical
On Fri, 26 Jan 2024, David Wright wrote:
On Fri 26 Jan 2024 at 19:03:33 (+0100), Roger Price wrote:
I currently have two Eaton Ellipse ECO 1600's. ... The four screws are deeply
recessed and difficult to see. They have different heads: some are Torx 10,
others are a star.
20/20 hindsight
apt-get installation logs (in --dry-run mode) show lines like:
...
Inst libvncclient1 (0.9.14+dfsg-1 Debian:12.4/stable [amd64])
Inst vlc-bin (3.0.20-0+deb12u1 Debian:12.4/stable [amd64])
Inst vlc-plugin-qt (3.0.20-0+deb12u1 Debian:12.4/stable [amd64])
...
you can get most parts of the suffix:
I see this exactly as you and are watching this list for may years.
However, I wanted not to be so directly because I want not to blame anyone on
this list.
But since the beginning, I had the suspicion, that someone just wants to make
fun with us.
Aleady from the beginning I checked after the
On 27 Jan 2024 08:12 +, from a...@strugglers.net (Andy Smith):
> 2024-01-27T07:59:42.003881+00:00 t.example.com sshd[12319]: Postponed
> publickey for root from 2001:db8:1f1:f0c2::2 port 37032 ssh2 [preauth]
> 2024-01-27T07:59:42.01+00:00 t.example.com sshd[12319]: Accepted
> publickey
Hi,
On Sat, Jan 27, 2024 at 09:55:16AM +, Michael Kjörling wrote:
> On 27 Jan 2024 08:12 +, from a...@strugglers.net (Andy Smith):
> > This only happens when I log in as root using a public key, i.e.
> >
> > ssh -i /path/to/pubkey r...@t.example.com
>
> According to
On 1/27/24, Andrew M.A. Cater wrote:
> I am consistently *puzzled* by what you are trying to do: I think that
> that is just effectively recording the repository that the package comes
> from. What does your /etc/sources.list consist of - and if it references
> bookworm, in what way does 12.4
30 matches
Mail list logo
