On Tue, Oct 15, 2024 at 03:12:30PM -0700, Mike Kupfer wrote:
> wrote:
>
> > > Richard Owlett wrote:
> > >
> > > > Wandering a chain of links starting at https://wiki.mate-desktop.org/
> > > > leads me to _suspect_ the configuration information I seek is in
> > > > /home/richard/.config/dconf/use
wrote:
> > Richard Owlett wrote:
> >
> > > Wandering a chain of links starting at https://wiki.mate-desktop.org/
> > > leads me to _suspect_ the configuration information I seek is in
> > > /home/richard/.config/dconf/user .
[...]
> Besides, it might be a bad idea to change the file while the de
On Tue, Oct 15, 2024 at 10:06:42AM -0700, Mike Kupfer wrote:
> Richard Owlett wrote:
>
> > Wandering a chain of links starting at https://wiki.mate-desktop.org/
> > leads me to _suspect_ the configuration information I seek is in
> > /home/richard/.config/dconf/user .
>
> You can dump the setting
Richard Owlett wrote:
> Wandering a chain of links starting at https://wiki.mate-desktop.org/
> leads me to _suspect_ the configuration information I seek is in
> /home/richard/.config/dconf/user .
You can dump the settings that are in dconf with
gsettings list-recursively
and redirecting the
On Thu, Aug 22, 2024 at 08:17:36AM -0400, Greg Wooledge wrote:
> On Thu, Aug 22, 2024 at 14:33:22 +0300, Dmitrii Odintcov wrote:
> > Hi Greg,
> >
> >
> > This has occurred to me, but seemed like a bit of a hack and less
> > convenient to transfer to other machines...
> >
> > > do it manually, no
On Thu, Aug 22, 2024 at 14:33:22 +0300, Dmitrii Odintcov wrote:
> Hi Greg,
>
>
> This has occurred to me, but seemed like a bit of a hack and less
> convenient to transfer to other machines...
>
> > do it manually, not with update-alternatives
> Why so? Could I not feed the script path to update
Hi Greg,
This has occurred to me, but seemed like a bit of a hack and less
convenient to transfer to other machines...
> do it manually, not with update-alternatives
Why so? Could I not feed the script path to update-alternatives install?
Thanks
On Thu, 22 Aug 2024 at 14:02, Greg Wooledge wr
On Thu, Aug 22, 2024 at 13:09:06 +0300, Dmitrii Odintcov wrote:
> Let's say I want to install VS Code / Codium as an alternative for
> `/usr/bin/editor`, but I want it to always run with `--wait
> --reuse-window` so that other software can rely on the editor
> returning after the file is saved (lik
On Mon, Jul 22, 2024 at 04:06:55PM CEST, Michael Kjörling
said:
> On 22 Jul 2024 05:47 +0800, from cor...@free.fr:
> > I have been running an old debian 11 for many days.
> > is it safe to run 'apt upgrade' and 'apt update' periodically?
> > for example put them into crontab.
>
> `apt update` (a
On Sun 21 Jul 2024 at 22:01:58 (-0600), Charles Curley wrote:
> On Sun, 21 Jul 2024 18:43:28 -0500
> David Wright wrote:
>
> > I run the following from root's crontab:
> >
> > apt-get -qq -o Acquire::http::Proxy="http://192.168.1.14:3142/";
> > update && apt-get -qq -d -o
> > Acquire::http::
On 22 Jul 2024 05:47 +0800, from cor...@free.fr:
> I have been running an old debian 11 for many days.
> is it safe to run 'apt upgrade' and 'apt update' periodically?
> for example put them into crontab.
`apt update` (and `apt-get update`) will only update the package
database. That should be abo
On Mon, 22 Jul 2024 05:47:58 +0800
cor...@free.fr wrote:
> I have been running an old debian 11 for many days.
> is it safe to run 'apt upgrade' and 'apt update' periodically?
> for example put them into crontab.
I suggest you do the next update manually. Then you can automate the
process with th
On Sun, 21 Jul 2024 18:43:28 -0500
David Wright wrote:
> I run the following from root's crontab:
>
> apt-get -qq -o Acquire::http::Proxy="http://192.168.1.14:3142/";
> update && apt-get -qq -d -o
> Acquire::http::Proxy="http://192.168.1.14:3142/"; dist-upgrade && find
> /var/cache/apt/archi
Hi,
On Mon, Jul 22, 2024 at 05:47:58AM +0800, cor...@free.fr wrote:
> is it safe to run 'apt upgrade' and 'apt update' periodically?
> for example put them into crontab.
I prefer to use apticron to download updates daily and tell me about
them, and then for me to install them manually. The reason
On Mon 22 Jul 2024 at 05:47:58 (+0800), cor...@free.fr wrote:
> I have been running an old debian 11 for many days.
> is it safe to run 'apt upgrade' and 'apt update' periodically?
> for example put them into crontab.
I run the following from root's crontab:
apt-get -qq -o Acquire::http::Proxy=
On Mon, Jul 22, 2024 at 07:34:29 +0800, Bret Busby wrote:
> One thing to remember, regarding automated upgrades, is that, if an upgrade
> involves a kernel upgrade, then you can have a need for immediate rebooting,
> which may be problematic.
It's also rare, but NOT unheard of, for a stable releas
On 22/7/24 07:34, Bret Busby wrote:
On 22/7/24 05:47, cor...@free.fr wrote:
Hi list,
I have been running an old debian 11 for many days.
is it safe to run 'apt upgrade' and 'apt update' periodically?
for example put them into crontab.
I ask this question because I am worried that some software
On 22/7/24 05:47, cor...@free.fr wrote:
Hi list,
I have been running an old debian 11 for many days.
is it safe to run 'apt upgrade' and 'apt update' periodically?
for example put them into crontab.
I ask this question because I am worried that some software updates may
conflict with each othe
On 7/21/24 17:47, cor...@free.fr wrote:
Hi list,
I have been running an old debian 11 for many days.
is it safe to run 'apt upgrade' and 'apt update' periodically?
for example put them into crontab.
I wouldn't have the upgrade run automatically, because maybe there's a
package you wouldn't wan
Pocket writes:
On Dec 14, 2023, at 2:23 PM, Linux-Fan wrote:
> Pocket writes:
[...]
> > Should the suffix of the file be .pem as the certs that are referenced by
> > the conf file seem to be in PEM format?
>
> Stick to what the program expects and use .crt
Ok what format DER, PEM or some
Sent from my iPad
> On Dec 14, 2023, at 2:23 PM, Linux-Fan wrote:
>
> Pocket writes:
>
>>> On 12/14/23 08:11, Henning Follmann wrote:
>>> On Wed, Dec 13, 2023 at 09:47:41PM -0500, Jeffrey Walton wrote:
On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
> What formats does certs need to
Pocket writes:
On 12/14/23 08:11, Henning Follmann wrote:
On Wed, Dec 13, 2023 at 09:47:41PM -0500, Jeffrey Walton wrote:
On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
What formats does certs need to be to work with update-ca-certificates?
PEM or DER?
PEM
Well lets look at man update-ca-c
On 12/14/23 08:11, Henning Follmann wrote:
On Wed, Dec 13, 2023 at 09:47:41PM -0500, Jeffrey Walton wrote:
On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
What formats does certs need to be to work with update-ca-certificates?
PEM or DER?
PEM
Well lets look at man update-ca-certificates, sh
On Wed, Dec 13, 2023 at 09:47:41PM -0500, Jeffrey Walton wrote:
> On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
> >
> > What formats does certs need to be to work with update-ca-certificates?
> >
> > PEM or DER?
>
> PEM
Well lets look at man update-ca-certificates, shall we?
"Certificates must
Hello,
On Wed, Dec 13, 2023 at 07:50:00PM -0700, Charles Curley wrote:
> On Thu, 14 Dec 2023 09:34:37 +0800
> jeremy ardley wrote:
>
> > You don't have to be your own CA. It's very easy to use letsencrypt
> > to generate valid certificates for hosts even if they are not
> > directly connected to
On Wed, Dec 13, 2023 at 10:52 PM Jeffrey Walton wrote:
>
> On Wed, Dec 13, 2023 at 9:58 PM Pocket wrote:
> >
> > On 12/13/23 21:47, Jeffrey Walton wrote:
> > > On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
> > >> What formats does certs need to be to work with update-ca-certificates?
> > >>
> >
On Wed, Dec 13, 2023 at 9:58 PM Pocket wrote:
>
> On 12/13/23 21:47, Jeffrey Walton wrote:
> > On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
> >> What formats does certs need to be to work with update-ca-certificates?
> >>
> >> PEM or DER?
> > PEM
>
> Ok since I am using an intermediate cert to s
On 12/13/23 21:50, Charles Curley wrote:
On Thu, 14 Dec 2023 09:34:37 +0800
jeremy ardley wrote:
You don't have to be your own CA. It's very easy to use letsencrypt
to generate valid certificates for hosts even if they are not
directly connected to the internet.
Oooh, is there a writeup som
On 12/13/23 21:47, Jeffrey Walton wrote:
On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
What formats does certs need to be to work with update-ca-certificates?
PEM or DER?
PEM
Ok since I am using an intermediate cert to sign, I am creating a
combined PEM with the root CA and the intermed
On Thu, 14 Dec 2023 09:34:37 +0800
jeremy ardley wrote:
> You don't have to be your own CA. It's very easy to use letsencrypt
> to generate valid certificates for hosts even if they are not
> directly connected to the internet.
Oooh, is there a writeup somewhere on how to do that? The last time
On Wed, Dec 13, 2023 at 7:55 PM Pocket wrote:
>
> What formats does certs need to be to work with update-ca-certificates?
>
> PEM or DER?
PEM
> I have just finished writing some scripts to generate certs for my email
> server and nginx server.
>
> [...]
> Will pem format type certs work?
Yes.
On 12/13/23 20:25, Roberto C. Sánchez wrote:
On Wed, Dec 13, 2023 at 07:54:45PM -0500, Pocket wrote:
What formats does certs need to be to work with update-ca-certificates?
PEM or DER?
I have just finished writing some scripts to generate certs for my email
server and nginx server.
The scrip
On 12/13/23 20:34, jeremy ardley wrote:
On 14/12/23 08:54, Pocket wrote:
I have just finished writing some scripts to generate certs for my
email server and nginx server.
The scripts allow me to become my own CA.
You don't have to be your own CA. It's very easy to use letsencrypt to
On 14/12/23 08:54, Pocket wrote:
I have just finished writing some scripts to generate certs for my
email server and nginx server.
The scripts allow me to become my own CA.
You don't have to be your own CA. It's very easy to use letsencrypt to
generate valid certificates for hosts even
On Wed, Dec 13, 2023 at 07:54:45PM -0500, Pocket wrote:
> What formats does certs need to be to work with update-ca-certificates?
>
> PEM or DER?
>
> I have just finished writing some scripts to generate certs for my email
> server and nginx server.
>
> The scripts allow me to become my own CA.
On 10/5/23 05:01, Steve Matzura wrote:
On 10/4/2023 2:32 PM, David Christensen wrote:
On 10/4/23 05:03, Steve Matzura wrote:
On 10/3/2023 6:06 PM, David Christensen wrote:
On 10/3/23 12:03, Steve Matzura wrote:
I gave up on the NFS business and went back to good old buggy
but reliable SAMBA (
On 10/4/23 05:03, Steve Matzura wrote:
On 10/3/2023 6:06 PM, David Christensen wrote:
On 10/3/23 12:03, Steve Matzura wrote:
I gave up on the NFS business and went back to good old buggy
but reliable SAMBA (LOL), ...
I have attempted to document the current state of Samba on my
SOHO, below.
On 10/3/23 12:03, Steve Matzura wrote:
I gave up on the NFS business and went back to good old buggy but
reliable SAMBA (LOL), which is what I was using when I was on Debian 8,
and which worked fine. Except for one thing, everything's great.
In /etc/fstab, I have:
//192.168.1.156/BigVol1 /m
On 03/10/2023 20:03, Steve Matzura wrote:
I gave up on the NFS business
Why?
and went back to good old buggy but reliable SAMBA (LOL)
:o
Sorry but I think you created bigger problem that you already had. NFS
works great, I've been using it for years and it never failed me. I
cannot image w
On Thu 13 Apr 2023 at 14:39:18 (-0600), Charles Curley wrote:
> On Thu, 13 Apr 2023 13:57:04 -0500
> David Wright wrote:
>
> > https://lists.debian.org/debian-user/2023/04/msg00405.html
> >
> > I was left with a system whose Grub menu only contained entries for
> > the new system, because os-pro
On Thu, Apr 13, 2023 at 01:57:04PM -0500, David Wright wrote:
os-prober no longer scours all the other
partitions for OSes any more.¹
Which is wonderful--that was one of the most annoying misfeatures to
have ever been enabled.
On Thu, 13 Apr 2023 13:57:04 -0500
David Wright wrote:
> https://lists.debian.org/debian-user/2023/04/msg00405.html
>
> I was left with a system whose Grub menu only contained entries for
> the new system, because os-prober no longer scours all the other
> partitions for OSes any more.¹ To get b
On Thu 13 Apr 2023 at 04:14:46 (+0200), Michel Verdier wrote:
> Le 12 avril 2023 David Wright a écrit :
>
> > the menu/ is moot. I would maintain that this failure mode is rare
> > enough for a reasonable penalty of having to type a few characters
> > editing the Grub menu.
> >
> > The last time I
Le 12 avril 2023 David Wright a écrit :
> the menu/ is moot. I would maintain that this failure mode is rare
> enough for a reasonable penalty of having to type a few characters
> editing the Grub menu.
>
> The last time I booted a kernel that was on a different partition
> from my installed Grub,
On Wed 12 Apr 2023 at 07:50:33 (-0400), The Wanderer wrote:
> On 2023-04-12 at 07:44, Michel Verdier wrote:
> > Le 12 avril 2023 The Wanderer a écrit :
> >
> >> Without anything more, wouldn't that just result in an extra
> >> GRUB-menu entry pointing to the same copy of the kernel/etc.?
> >
> >
On 2023-04-12 at 07:44, Michel Verdier wrote:
> Le 12 avril 2023 The Wanderer a écrit :
>
>> Without anything more, wouldn't that just result in an extra
>> GRUB-menu entry pointing to the same copy of the kernel/etc.?
>
> Of course he can change menuentry to point to another kernel/initram
Fro
Le 12 avril 2023 The Wanderer a écrit :
> Without anything more, wouldn't that just result in an extra GRUB-menu
> entry pointing to the same copy of the kernel/etc.?
Of course he can change menuentry to point to another kernel/initram
> As I think I understand matters, the goal is to have a dup
On 2023-04-11 at 22:30, Michel Verdier wrote:
> Le 11 avril 2023 davidson a écrit :
>> I believe the OP just wants an extra entry in his grub menu that
>> will boot a redundant copy of his latest working kernel. (But that
>> is only my understanding, which might be wrong. OP can speak for
>> hims
On Wed, 12 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 davidson wrote:
I haven't tried booting yet with my "5.10.0-21-amd63-kg" initrd,
though. I'll leave that to you, if you want to try.
Boot went fine, but it is worth mentioning that grub-update
*update-grub
decided that the "5.10.0-21-
On Tue, 11 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 Marc Auslander wrote:
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four f
Le 11 avril 2023 davidson a écrit :
> # update-initramfs -u
> # update-initramfs: Generating /boot/initrd.img-5.10.0-21-amd64-kg
> W: missing /lib/modules/5.10.0-21-amd64-kg
Of course : /lib/modules/ is installed via package. You
have to do it manually to get rid of this error. And without it you
On Tue 11 Apr 2023 at 22:14:18 (+0200), zithro wrote:
> I thought :
>
> - you can install as many kernel packages as you want, whether built
> or downloaded
> - updates don't automatically remove old kernels/initrd by default
>
> So I wonder, why handling it manually ?
> What is the advantage, ex
I thought :
- you can install as many kernel packages as you want, whether built or
downloaded
- updates don't automatically remove old kernels/initrd by default
So I wonder, why handling it manually ?
What is the advantage, except for adding -confusion- ?
On Tue 11 Apr 2023 at 10:51:19 (-0400), Marc Auslander wrote:
> On 4/10/2023 11:00 PM, David Wright wrote:
> > On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
> > > I'm on Buster.
> > >
> > > In /boot I keep a copy of the current working linux named by appending
> > > -knowngood to t
On Tue, 11 Apr 2023 davidson wrote:
On Tue, 11 Apr 2023 Michel Verdier wrote:
Le 11 avril 2023 davidson a écrit :
Experiment #2: see if I could tweak OP's practice enough so that
update-grub would not care.
...and so that "update-initramfs -u" would not notice.
--
Sometimes it pays to ha
On Tue, 11 Apr 2023 Michel Verdier wrote:
Le 11 avril 2023 davidson a écrit :
The first experiment simply tried to replicate your observations (as I
understood them). Basically, I added "-kg" suffix to all the files in
/boot corresponding to latest installed kernel, so that I had
unsuffixed cop
Le 11 avril 2023 davidson a écrit :
> The first experiment simply tried to replicate your observations (as I
> understood them). Basically, I added "-kg" suffix to all the files in
> /boot corresponding to latest installed kernel, so that I had
> unsuffixed copies and "*-kg" ("knowngood") copies,
On Tue, 11 Apr 2023 Marc Auslander wrote:
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update f
On 11 Apr 2023 16:43, Marc Auslander wrote:
On 4/11/2023 9:30 AM, zithro wrote:
The solution is in "man update-initramfs" :
update-initramfs -c -k $KERNEL_VERSION
-c creates a new initramfs
-k specifies the version of the kernel
This breaks when package update tries to update-initramfs. My cop
On 4/10/2023 11:00 PM, David Wright wrote:
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This
On 4/11/2023 9:30 AM, zithro wrote:
On 11 Apr 2023 02:17, Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This is different from vmlin
On 11 Apr 2023 02:17, Marc Auslander wrote:
I'm on Buster.
In /boot I keep a copy of the current working linux named by appending
-knowngood to the four files. My idea is that if an update fails, I
have a recent working linux. This is different from vmlinuz.old which
is the previous kernel
On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote:
> I'm on Buster.
>
> In /boot I keep a copy of the current working linux named by appending
> -knowngood to the four files. My idea is that if an update fails, I
> have a recent working linux. This is different from vmlinuz.old which
On Sat 01 Oct 2022 at 20:07:13 +0200, Erwan David wrote:
> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> >
> > > My /boot is 235 MB (from deb 10 installer), however in testing I now
> > > have 56MB initramfs files and update-initramfs cann
> Le 01/10/2022 à 18:25, Felix Miata a écrit :
> > Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> >
> >> My /boot is 235 MB (from deb 10 installer), however in testing I
> >> now have 56MB initramfs files and update-initramfs cannot work for
> >> the 3rd kernel to install (and apt autorem
> I alreaady have compres=zstd (should be better than lzma).
I'd be surprised if `zstd` compresses better than `lzma` (which itself
should compress about the same as `xz`). I just tested here and I get
zstd => 11049378
xz => 9989884
lzma => 9965122
Maybe with more control over t
Le 01/10/2022 à 18:25, Felix Miata a écrit :
Erwan David composed on 2022-10-01 16:21 (UTC+0200):
My /boot is 235 MB (from deb 10 installer), however in testing I now
have 56MB initramfs files and update-initramfs cannot work for the 3rd
kernel to install (and apt autoremove keeps 2 kernels, th
Erwan David composed on 2022-10-01 16:21 (UTC+0200):
> My /boot is 235 MB (from deb 10 installer), however in testing I now
> have 56MB initramfs files and update-initramfs cannot work for the 3rd
> kernel to install (and apt autoremove keeps 2 kernels, thus at upgrade
> there are temporarily 3
On 2022-10-01 17:26 +0200, Erwan David wrote:
> Le 01/10/2022 à 17:16, Stefan Monnier a écrit :
>>> My /boot is 235 MB (from deb 10 installer), however in testing I now have
>>> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
>>> install (and apt autoremove keeps 2 kern
Le 01/10/2022 à 17:16, Stefan Monnier a écrit :
My /boot is 235 MB (from deb 10 installer), however in testing I now have
56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
install (and apt autoremove keeps 2 kernels, thus at upgrade there are
temporarily 3 kernels).
> My /boot is 235 MB (from deb 10 installer), however in testing I now have
> 56MB initramfs files and update-initramfs cannot work for the 3rd kernel to
> install (and apt autoremove keeps 2 kernels, thus at upgrade there are
> temporarily 3 kernels).
MODULES=dep
and
COMPRESS=lzma
in `
On Sat, 19 Mar 2022 07:31:04 -0700
Peter Ehlert wrote:
> I now have both needrestart and needrestart-session installed.
>
> Question: do either run in the background?
Apt calls needrestart, so it isn't necessary to run it in the
background.
Unattended upgrades will inform you of which processe
On 3/19/22, Peter Ehlert wrote:
>
> On 3/19/22 06:32, piorunz wrote:
>> On 19/03/2022 10:02, songbird wrote:
>>
>>>there is also package debian-goodies which has the
>>> command checkrestart. i'm not sure which is better.
>>>
>>
>> All I know is that needrestart works for me, it correctly prom
On 3/19/22, piorunz wrote:
> On 19/03/2022 02:32, Lee wrote:
>> How to tell if I need to reboot the machine after updating the software?
>
> install "needrestart" package.
>
> Description: needrestart checks which daemons need to be restarted after
> library upgrades.
> It is inspired by checkres
On Sat, 19 Mar 2022 10:15:27 -0400
Cindy Sue Causey wrote:
Hello Cindy,
>admin emails sent to them as a potential remedy. It's on my to-do to
>play around with those emails to see if that catches those upgrade
>messages..
What they include is advisory notices that get thrown up (when using
syna
On Sat, Mar 19, 2022 at 10:04:59AM -0500, Nicholas Geovanis wrote:
> On Fri, Mar 18, 2022 at 9:35 PM Greg Wooledge wrote:
>
> > On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
> > > How to tell if I need to reboot the machine after updating the software?
> >
> > Reboots are needed if you got
On Fri, Mar 18, 2022 at 9:35 PM Greg Wooledge wrote:
> On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
> > How to tell if I need to reboot the machine after updating the software?
>
> Reboots are needed if you got a new kernel, or new firmware, or new
> microcode, or a new version of the dbu
On 3/19/22 06:32, piorunz wrote:
On 19/03/2022 10:02, songbird wrote:
there is also package debian-goodies which has the
command checkrestart. i'm not sure which is better.
songbird
All I know is that needrestart works for me, it correctly prompts for
computer reboot after kernel u
On 3/19/22, Greg Wooledge wrote:
> On Sat, Mar 19, 2022 at 10:55:03AM +0100, Toni Mas Soler wrote:
>> I restart Dbus from time to time. Actually, I stop Dbus if i don't
>> need, that is when I do not use X (almost allways).
>> Do you mean my action is not effective?
>
> The fact that you're "almos
On 19/03/2022 10:02, songbird wrote:
there is also package debian-goodies which has the
command checkrestart. i'm not sure which is better.
songbird
All I know is that needrestart works for me, it correctly prompts for
computer reboot after kernel upgrade; and offers to restart variou
On Sat, Mar 19, 2022 at 10:55:03AM +0100, Toni Mas Soler wrote:
> I restart Dbus from time to time. Actually, I stop Dbus if i don't
> need, that is when I do not use X (almost allways).
> Do you mean my action is not effective?
The fact that you're "almost always" not using X is probably relevant
piorunz wrote:
> On 19/03/2022 02:32, Lee wrote:
>> How to tell if I need to reboot the machine after updating the software?
>
> install "needrestart" package.
>
> Description: needrestart checks which daemons need to be restarted after
> library upgrades.
> It is inspired by checkrestart from th
Hi,
19 mars 2022, 12:16 de edua...@kalinowski.com.br:
> The needrestart package will offer to restart services affected when there'a
> a library update, and it also warns you when the kernel has been udpated (and
> a reboot is necessary). It just doesn't warn you about microcode updates,
> AFA
On 18/03/2022 23:47, Lee wrote:
So
it would be nice if there was some program that would just say that I
needed to reboot
The needrestart package will offer to restart services affected when
there'a a library update, and it also warns you when the kernel has been
udpated (and a reboot is nece
I restart Dbus from time to time. Actually, I stop Dbus if i don't
need, that is when I do not use X (almost allways).
Do you mean my action is not effective?
Toni Mas
Missatge de piorunz del dia ds., 19 de març 2022 a les 5:55:
>
> On 19/03/2022 02:32, Lee wrote:
> > How to tell if I need to r
On 19/03/2022 02:32, Lee wrote:
How to tell if I need to reboot the machine after updating the software?
install "needrestart" package.
Description: needrestart checks which daemons need to be restarted after
library upgrades.
It is inspired by checkrestart from the debian-goodies package.
On 3/18/22 19:47, Lee wrote:
On 3/18/22, Greg Wooledge wrote:
On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
How to tell if I need to reboot the machine after updating the software?
Reboots are needed if you got a new kernel, or new firmware, or new
microcode, or a new version of the d
On 3/18/22, Greg Wooledge wrote:
> On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
>> How to tell if I need to reboot the machine after updating the software?
>
> Reboots are needed if you got a new kernel, or new firmware, or new
> microcode, or a new version of the dbus package (because dbu
On Fri, Mar 18, 2022 at 10:32:49PM -0400, Lee wrote:
> How to tell if I need to reboot the machine after updating the software?
Reboots are needed if you got a new kernel, or new firmware, or new
microcode, or a new version of the dbus package (because dbus cannot
be restarted).
On Ma, 14 dec 21, 14:59:56, Thanos Katsiolis wrote:
> Kent thank you for your response.
>
>
> I also had to install the GNOME, although using dpkg I saw related
> packages, so I thought that it was installed.
> Is there a way to verify that something like DM (gdm) or GNOMe is
> installed, in orde
Kent thank you for your response.
I also had to install the GNOME, although using dpkg I saw related
packages, so I thought that it was installed.
Is there a way to verify that something like DM (gdm) or GNOMe is
installed, in order to know what to do?
Thank you all for your help.
On Mon, Dec 1
On Mon, Dec 13, 2021 at 10:14 AM Thanos Katsiolis
wrote:
> The Display Manager was missing (gdm3), I installed it and the login works
> fine.
>
> Now when I log in there is a blue screen and the cursor, nothing else is
> displayed.
> Is there a problem with GNOME?
>
Probably.
You might try rei
The Display Manager was missing (gdm3), I installed it and the login works
fine.
Now when I log in there is a blue screen and the cursor, nothing else is
displayed.
Is there a problem with GNOME?
Thank you all.
On Thu, Dec 9, 2021 at 4:39 PM Thanos Katsiolis
wrote:
> Hello,
>
> I followed the
On Mon, Dec 13, 2021 at 12:04:32PM +0200, Thanos Katsiolis wrote:
> Thank you Piotr for your response.
>
> As I responded to Andrei lower in the thread, neither DM nor DE must have
> been installed.
>
> I would like to get GNOME, so I will try to install it. Does this affect
> the DM somehow?
If
Thank you Piotr for your response.
As I responded to Andrei lower in the thread, neither DM nor DE must have
been installed.
I would like to get GNOME, so I will try to install it. Does this affect
the DM somehow?
On Fri, Dec 10, 2021 at 8:54 PM piorunz wrote:
> On 10/12/2021 16:24, Thanos Kat
Andrei sorry for my late response,
> More precisely, no Display Manager (DM). Even if you do have a Desktop
> Environment installed, the DM is responsible for automatically starting
> it.
>
> Please try to log in on the console and run:
>
> startx
>
>
>
startx ha the output:
/etc/X11/xinit/x
[this appears to have been meant for the list]
On Vi, 10 dec 21, 20:25:26, Thanos Katsiolis wrote:
> > Yes, it's possible, e.g. in case there was a conflict and APT decided it
> > > should remove remove your Desktop Environment to resolve the conflict.
> >
> > > This should be visible in the logs
On 10/12/2021 16:24, Thanos Katsiolis wrote:
I verified that Debian 10.10 was installed , ran cleaning commands,
reboot again but again I can only access ttys and not the Graphical
Interface.
What DE you are using?
1. Check if your DE is still installed.
dpkg -l | grep /your-de/name/
2. Instal
So I have to install a Desktop Environment.
I am thinking of using tasksel to install GNOME.
Thank you for your help.
I though about that too, that the video card somehow could have affected
the update somehow regarding DE.
The VGA compatible controller entry of lspci is NVIDIA Corporation GP107GL
[Quadro P400] (rev a1)
I don't remember anything about firmware during the installation.
On Fri, Dec 10, 2021 at 7:
1 - 100 of 970 matches
Mail list logo
