Stephen P. Molnar wrote:
>
>
> On 03/01/2024 11:08 AM, Markus Schönhaber wrote:
> >
> > [1] Look at /etc/apache2/mods-enabled/userdir.conf line 11
> > there you should see something like
> > [2] "ExecCG" which probably should read "ExecCGI" instead.
> >
> That was the problem. Many thanks.
If
On 03/01/2024 11:08 AM, Markus Schönhaber wrote:
01.03.24, 16:36 +0100, Stephen P. Molnar:
I am running up to date Bookworm and get the 'Failed to start Apache2
service on boot' error message.
I searched Google and found
https://forums.debian.net/voew.top9c,php?t=14419s which didn't solve t
01.03.24, 16:36 +0100, Stephen P. Molnar:
> I am running up to date Bookworm and get the 'Failed to start Apache2
> service on boot' error message.
>
> I searched Google and found
> https://forums.debian.net/voew.top9c,php?t=14419s which didn't solve the
> problem.
>
> I then tried sudo systemct
Zithro : And yet you continue trying to compile (possibly) incompatible
softwares from source, instead of following the user guides, and despite
our warnings. You essentially say "I want to do some complicated stuff
without understanding how it works, and quick please".
Are you reading my mind ? H
Seems you also don't read and/or learn ...
Don't top post please, it's a matter of respect.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On 30 Aug 2023 10:50, Ma
Not a useful suggestion for me. I'm not a coder,such as I'm not a pro
system admin : this is only a hobby for me. I try to do the best I can,but
I can't solve bugs for which a solution has not been found yet and that
involves the writing of a piece of code.
On Wed, Aug 30, 2023 at 4:45 AM zithro
On 29 Aug 2023 23:48, Mario Marietto wrote:
I'm running Debian bookworm [...]
No you're not.
You're running a MODIFIED Debian version with a (rather old) MODIFIED
kernel :
$ uname -r
5.4.244-stb-cbe
>
[removed mostly copy/paste from old posts]
Can someone give me some suggestions to
On 26 Jul 2023 07:43 -0400, from s.mol...@sbcglobal.net:
> I just tried to boot
> into the new OS and it booted!!! After bumbling luck on my part, but I'll
> take it.
In that case, you may want to run `sudo update-grub` from within the
system that boots. Doing so will rewrite the GRUB configuratio
-Original Message-
From: Greg Wooledge
Sent: Wednesday, July 26, 2023 7:15 AM
To: debian-user@lists.debian.org
Subject: Re: Error: no such device
On Wed, Jul 26, 2023 at 06:46:31AM -0400, s.mol...@sbcglobal.net wrote:
> I installed Debian 12.0.0 on my Linux platform form the
On 26 Jul 2023 06:46 -0400, from s.mol...@sbcglobal.net:
> I installed Debian 12.0.0 on my Linux platform form the net install iso
> without any warning or error messages. The initial boot of the system booted
> the system came to a halt father quickly with the message:
>
>
>
> GRUB loading
>
On Wed, Jul 26, 2023 at 06:46:31AM -0400, s.mol...@sbcglobal.net wrote:
> I installed Debian 12.0.0 on my Linux platform form the net install iso
> The computer has been in service since the last time I upgraded the system
...???
Did you *reinstall* Debian, or did you *upgrade* it? Those are tw
Is it possible that the CPU or motherboard could cause the problem ?
On 6/2/23 09:09, gene heskett wrote:
On 6/2/23 06:27, David wrote:
On Thu, 1 Jun 2023 at 18:43, Mick Ab
wrote:
Recently, Hardware error messages such as the following have
appeared every few weeks :-
Hi, given that you say these sympoms appear and disappear, the first
and easy thing
I woul
On 02/06/2023 13:36, Charles Curley wrote:
On Fri, 2 Jun 2023 12:01:10 +0100
Mick Ab wrote:
Ram :-
I don't know the make of the Ram - someone built the PC for me.
16GB DDR4-3200MHz RAM (2 x 8GB sticks, I understand
You may be able to get the make of the RAM (and more) with:
dmidecode | l
On 6/2/23 06:27, David wrote:
On Thu, 1 Jun 2023 at 18:43, Mick Ab wrote:
Recently, Hardware error messages such as the following have
appeared every few weeks :-
Hi, given that you say these sympoms appear and disappear, the first
and easy thing
I would try, is to re-seat (ie disconnect and
On Fri, 2 Jun 2023 12:01:10 +0100
Mick Ab wrote:
> Ram :-
>
> I don't know the make of the Ram - someone built the PC for me.
>
> 16GB DDR4-3200MHz RAM (2 x 8GB sticks, I understand
You may be able to get the make of the RAM (and more) with:
dmidecode | less
then search ('/') on Memory Devi
On Fri, 2 Jun 2023 at 11:01, Mick Ab wrote:
>
> Thanks for all the replies to the Error Messages.
>
> I don't know how you find which disk is referred to by ata5.
ls -l /dev/disk/by-path | grep 'ata-5'
> I think dm-0 is a reference to a Raid setup.
To get the UUID:
sudo dmsetup info /dev/dm-0
Hi Mick,
Can you please give result of this command? (install inxi if you don't
have it)
sudo inxi -Fm
Also, please run Memtest86+ on your machine (for several hours) to check
memory for errors. You can find it there:
https://memtest.org/
It can be also found in Debian packages, but booting to
Thanks for all the replies to the Error Messages.
I don't know how you find which disk is referred to by ata5.
I think dm-0 is a reference to a Raid setup.
Other information about my hardware and rebooting :-
I have two 1 TB hard drives arranged as a RAID 1 array.
The power supply :-
Corsair
On Thu, 1 Jun 2023 at 18:43, Mick Ab wrote:
> Recently, Hardware error messages such as the following have
> appeared every few weeks :-
Hi, given that you say these sympoms appear and disappear, the first
and easy thing
I would try, is to re-seat (ie disconnect and reconnect) every SATA connect
On Fri, 2 Jun 2023 06:32:51 +0200
wrote:
> >
> > That sounds like your hard drive has run out of space. Running free
> > should tell you which one(s)? are out of space.
>
> Probably typo: "free" tells you about RAM. Try "df", best with option
> "-h":
>
> df -h
Yes, a mis-remembering. Apol
On Thu, Jun 01, 2023 at 01:11:55PM -0600, Charles Curley wrote:
> On Thu, 1 Jun 2023 19:42:27 +0100
> Mick Ab wrote:
>
> > May 27 13:58:08 piglit kernel: [2083218.337088] EXT4-fs warning
> > (device dm-0): ext4_dirblock_csum_verify:400: inode #53: comm opera:
> > No space for directory leaf check
Mick Ab wrote:
> I run a desktop PC with Debian 11, Ryzen 5 5600x CPU and
> MSI-B550 A Pro motherboard.
>
> Recently, Hardware error messages such as the following have
> appeared every few weeks :-
>
> And around the time of the error messages on the 22nd May, the
> syslog extracts say:
>
> Ma
On Thu, 1 Jun 2023 19:42:27 +0100
Mick Ab wrote:
> May 27 13:58:08 piglit kernel: [2083218.337088] EXT4-fs warning
> (device dm-0): ext4_dirblock_csum_verify:400: inode #53: comm opera:
> No space for directory leaf checksum. Please run e2fsck -D.
> May 27 13:58:08 piglit kernel: [2083218.337091]
On 01/06/2023 19:42, Mick Ab wrote:
Any thoughts about why the above is happening, please ?
Everything is failing, from CPU caches, hard drive SATA link, to
checksum errors in the filesystem. Could be failing PSU, what make and
model is it, how old? Also it could be RAM issues.
Motherboard bio
Le 20/02/2023 à 13:18, Greg Wooledge a écrit :
On Mon, Feb 20, 2023 at 06:30:36AM +0100, to...@tuxteam.de wrote:
On Sun, Feb 19, 2023 at 03:13:40PM -0700, 43i3 Adam wrote:
The error :
ake[5]: *** [scripts/Makefile.build:500: drivers/media] Error 2
make[5]: *** Waiting for unfinished jobs
On Mon, Feb 20, 2023 at 06:30:36AM +0100, to...@tuxteam.de wrote:
> On Sun, Feb 19, 2023 at 03:13:40PM -0700, 43i3 Adam wrote:
> > The error :
> > ake[5]: *** [scripts/Makefile.build:500: drivers/media] Error 2
> > make[5]: *** Waiting for unfinished jobs
> > CC [M] drivers/staging/qlge/qlge
On Sun, Feb 19, 2023 at 03:13:40PM -0700, 43i3 Adam wrote:
> hi, please a need help i never had this kind of error compile my own
> kernel. please you can find there the version of kernel and the command
> line a use for that. thanks ...
>
> kernel version: linux-6.1.12
> os type: 64-bit
> process
On Tue, Oct 4, 2022 at 2:32 AM Anssi Saari wrote:
> Dave Parker writes:
>
> > So, I copied /lib/systemd/system/nftables.service to
> /etc/systemd/system/nftables.service, set
> > ProtectHome=false, ran "systemctl daemon-reload", and now it works!
>
> Well, good, buy why not put configuration dat
Hello,
On Mon, Oct 03, 2022 at 10:36:53PM -0400, Dave Parker wrote:
> So, I copied /lib/systemd/system/nftables.service to
> /etc/systemd/system/nftables.service, set ProtectHome=false, ran "systemctl
> daemon-reload", and now it works!
This overrides the entire file with your copy in /etc. That
Dave Parker writes:
> So, I copied /lib/systemd/system/nftables.service to
> /etc/systemd/system/nftables.service, set
> ProtectHome=false, ran "systemctl daemon-reload", and now it works!
Well, good, buy why not put configuration data in /etc instead of /root
where it belongs and keep the serv
On Mon, Oct 3, 2022 at 5:42 PM Andy Smith wrote:
> Hello,
>
> On Mon, Oct 03, 2022 at 05:36:19PM -0400, Greg Wooledge wrote:
> > On Mon, Oct 03, 2022 at 05:01:21PM -0400, Dave Parker wrote:
> > > Oct 03 16:48:55 host systemd[1]: Starting nftables...
> > > Oct 03 16:48:55 host nft[926]: /etc/nftab
Hello,
On Mon, Oct 03, 2022 at 05:36:19PM -0400, Greg Wooledge wrote:
> On Mon, Oct 03, 2022 at 05:01:21PM -0400, Dave Parker wrote:
> > Oct 03 16:48:55 host systemd[1]: Starting nftables...
> > Oct 03 16:48:55 host nft[926]: /etc/nftables.conf:4:1-37: Error: File not
> > found: /root/nftables/rul
On Mon, Oct 03, 2022 at 05:01:21PM -0400, Dave Parker wrote:
> Oct 03 16:48:55 host systemd[1]: Starting nftables...
> Oct 03 16:48:55 host nft[926]: /etc/nftables.conf:4:1-37: Error: File not
> found: /root/nftables/ruleset.txt
Sounds like the service might be chrooted.
On Tue, 14 Jun 2022 02:55:04 +
"Russell L. Harris" wrote:
Hello Russell,
>I've gotten lazy because I seldom have a problem with Synaptic.
IKWYM. Despite Synaptic being looked down on in some quarters, I find
it very capable. Especially when it comes to dependency issue
resolution.
>enoug
On Mon, 13 Jun 2022 18:46:02 -0500
David Wright wrote:
Hello David,
>While I would generally concur, I would not advise, for example,
>performing the monthly firefox upgrade while the browser is running.
I've never had issues doing that (admittedly, not with ff, but other
browsers); The browse
On Mon, Jun 13, 2022 at 06:46:02PM -0500, David Wright wrote:
> On Mon 13 Jun 2022 at 12:38:37 (+0100), Brad Rogers wrote:
> > On Mon, 13 Jun 2022 07:24:07 -0400 Greg Wooledge wrote:
> > >On Mon, Jun 13, 2022 at 04:58:44AM +, Russell L. Harris wrote:
> > >> I suppose I should have shut down som
On Mon, Jun 13, 2022 at 06:46:02PM -0500, David Wright wrote:
On Mon 13 Jun 2022 at 12:38:37 (+0100), Brad Rogers wrote:
On Mon, 13 Jun 2022 07:24:07 -0400 Greg Wooledge wrote:
>On Mon, Jun 13, 2022 at 04:58:44AM +, Russell L. Harris wrote:
>> I suppose I should have shut down some of proces
On Mon 13 Jun 2022 at 12:38:37 (+0100), Brad Rogers wrote:
> On Mon, 13 Jun 2022 07:24:07 -0400 Greg Wooledge wrote:
> >On Mon, Jun 13, 2022 at 04:58:44AM +, Russell L. Harris wrote:
> >> I suppose I should have shut down some of processes before running
> >> Synaptic.
> >That shouldn't be ne
On Mon, 13 Jun 2022 07:24:07 -0400
Greg Wooledge wrote:
Hello,
>On Mon, Jun 13, 2022 at 04:58:44AM +, Russell L. Harris wrote:
>> I suppose I should have shut down some of processes before running
>> Synaptic.
>That shouldn't be necessary.
Indeed. It seems more likely that the problems a
On Mon, Jun 13, 2022 at 04:58:44AM +, Russell L. Harris wrote:
> That occurred to me when I first typed "su", but then I forgot to go
> back and try. Now I can sleep tonight without worrying about it.
If you want more details (and more options):
https://wiki.debian.org/NewInBuster#Changes
>
On Sun, Jun 12, 2022 at 11:27:04PM -0500, David Wright wrote:
The fact that your working directory is a user's (yours?), and
???sbin directories are not in your $PATH suggests you might have
become root using "su" and not "su -" or "su --login". Try one
of these instead. (The change to su's seman
On 6/13/22 00:29, David Wright wrote:
On Mon 13 Jun 2022 at 03:22:29 (+), Russell L. Harris wrote:
Debian 11 AMD
At the end of my weekly UPGRADE session using synaptic, the system
hung. I restarted using the hardware RESET button. The system
booted and found a number of orphaned nodes.
On Mon 13 Jun 2022 at 03:22:29 (+), Russell L. Harris wrote:
> Debian 11 AMD
>
> At the end of my weekly UPGRADE session using synaptic, the system
> hung. I restarted using the hardware RESET button. The system
> booted and found a number of orphaned nodes.
>
> When I started synaptic a me
On 6/6/22 22:17, Felix Miata wrote:
Bob Crochelt composed on 2022-06-06 17:02 (UTC-0700):
Running updated Debian on a pretty old iMac. Seeing messages that complain
about sda, only drive in the system:
190 Airflow_Temperature_Cel 0x0022 045 037 045Old_age Always
FAILING_NOW
Bob Crochelt composed on 2022-06-06 17:02 (UTC-0700):
> Running updated Debian on a pretty old iMac. Seeing messages that complain
> about sda, only drive in the system:
> 190 Airflow_Temperature_Cel 0x0022 045 037 045Old_age Always
> FAILING_NOW 55 (255 255 60 26 0)
> 194 Temper
On 6/6/22 20:27, David wrote:
On Tue, 7 Jun 2022 at 10:03, Bob Crochelt wrote:
9 Power_On_Hours 0x0032 045 045 000Old_age Always
- 48690
Assuming the raw value is hours, that's about 5.5 years of power on time.
190 Airflow_Temperature_Cel 0x0022 045
On Tue, 7 Jun 2022 at 10:03, Bob Crochelt wrote:
> 9 Power_On_Hours 0x0032 045 045 000Old_age Always
> - 48690
Assuming the raw value is hours, that's about 5.5 years of power on time.
> 190 Airflow_Temperature_Cel 0x0022 045 037 045Old_age Always
On 6/6/22 17:02, Bob Crochelt wrote:
Hi:
Running updated Debian on a pretty old iMac. Seeing messages that complain
about sda, only drive in the system:
> I think this means its time to replace the hard drive, any other
thoughts?
Interpreting smartctl output is tough. Try to find manufa
On 27.03.2022 18:12, Nicholas Geovanis wrote:
On Sun, Mar 27, 2022, 7:31 AM Reiner Buehl wrote:
Hi all!
I am trying to build an amd64 Debian package from sources but the
command dpkg-buildpackage -us -uc fails with a number of the
following
error messages:
ERROR: ld.
On Sun, Mar 27, 2022, 7:31 AM Reiner Buehl wrote:
> Hi all!
>
> I am trying to build an amd64 Debian package from sources but the
> command dpkg-buildpackage -us -uc fails with a number of the following
> error messages:
>
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
> p
On Sun, Feb 20, 2022, 2:21 AM Christian Britz wrote:
>
>
> On 2022-02-20 03:35 UTC+0100, Nicholas Geovanis wrote:
>
> > Probably you should be using the pip3 command instead. It may not be
> > installed,
> > so I think this will install it:
> > sudo apt-get install python3-pip
>
> python3-pip is
On 2022-02-20 03:35 UTC+0100, Nicholas Geovanis wrote:
> Probably you should be using the pip3 command instead. It may not be
> installed,
> so I think this will install it:
> sudo apt-get install python3-pip
python3-pip is installed. I think it came with the Debian installer.
It makes no di
On Sat, Feb 19, 2022 at 3:00 PM Christian Britz wrote:
> Hello Debian users,
>
> I would like to update the Python3 packages which I installed for my
> local user via pip.
>
> The command "pip list --user --outdated" gives the following error
> messages. This is on Debian stable. Any ideas?
>
Pr
It happens also when I run sudo pip list --outdated, so I think it is
not related to my user profile.
On 2022-02-19 21:59 UTC+0100, Christian Britz wrote:
> Hello Debian users,
>
> I would like to update the Python3 packages which I installed for my
> local user via pip.
>
> The command "pip lis
El lun, 18 oct 2021 a las 9:07, Andrei POPESCU
() escribió:
>
> On Vi, 15 oct 21, 10:39:54, Victor Hugo Muñoz wrote:
> >
> > Actually, yes. Why? Due to confinement, my home PC has also been my
> > office PC. And
> > since I had a working machine, decided to upgrade packages only if
> > strictly nec
On Vi, 15 oct 21, 10:39:54, Victor Hugo Muñoz wrote:
>
> Actually, yes. Why? Due to confinement, my home PC has also been my
> office PC. And
> since I had a working machine, decided to upgrade packages only if
> strictly necessary.
As you found out (the hard way), the "strictly necessary" isn't
On 10/15/21, Andrei POPESCU wrote:
> On Jo, 14 oct 21, 13:19:09, Victor Hugo Muñoz wrote:
>>
>> Yes, I know the risks :-) My office computer is in stable for that
>> reason. This is my home computer. Anyway,
>> I'm extremely conservative with upgrades, and do not upgrade if I
>> think I'm going to
El vie, 15 oct 2021 a las 10:20, Greg Wooledge () escribió:
>
> On Fri, Oct 15, 2021 at 10:56:25AM +0300, Andrei POPESCU wrote:
> >
> > Packages are not allowed to use dpkg features that are not present in
> > stable.
> >
> > In this particular case, according to the changelog 'dpkg' introduced
> >
On Fri, Oct 15, 2021 at 10:56:25AM +0300, Andrei POPESCU wrote:
> On Jo, 14 oct 21, 13:47:22, Greg Wooledge wrote:
> > On Thu, Oct 14, 2021 at 01:51:07PM -0300, Victor Hugo Muñoz wrote:
> > > And it looks that this worked! You were right, I had not the latest
> > > version, so I upgraded dpkg, and
On Jo, 14 oct 21, 13:19:09, Victor Hugo Muñoz wrote:
>
> Yes, I know the risks :-) My office computer is in stable for that
> reason. This is my home computer. Anyway,
> I'm extremely conservative with upgrades, and do not upgrade if I
> think I'm going to break something important, This may
> be
On Jo, 14 oct 21, 13:47:22, Greg Wooledge wrote:
> On Thu, Oct 14, 2021 at 01:51:07PM -0300, Victor Hugo Muñoz wrote:
> > And it looks that this worked! You were right, I had not the latest
> > version, so I upgraded dpkg, and yes, texlive-base passed the
> > installation without errors.
>
> Is th
On Thu, Oct 14, 2021 at 01:51:07PM -0300, Victor Hugo Muñoz wrote:
> And it looks that this worked! You were right, I had not the latest
> version, so I upgraded dpkg, and yes, texlive-base passed the
> installation without errors.
Is this considered a bug in texlive-base, i.e. that it should cont
15 Oct 2021, 02:41 by victor_mu...@uchile.cl:
> El jue, 14 oct 2021 a las 13:35, Andrew M.A. Cater
> () escribió:
>
>>>
>>>
>> It might be worth checking what packages you have installed. If you
>> can manage to, uninstall them (or use dpkg --purge to purge texlive-base
>> then retry.
>>
>
> Tha
El jue, 14 oct 2021 a las 13:46, David Wright
() escribió:
>
> I'm still running buster, but what that /looks/ like to me is that
> you're running a version of dpkg that is, as yet, ignorant of the
> ?new flags in packages' lists of conffiles.
>
> I say flags, but the only one defined is exactly th
On Thu 14 Oct 2021 at 13:19:09 (-0300), Victor Hugo Muñoz wrote:
> El jue, 14 oct 2021 a las 12:46, The Wanderer ()
> escribió:
> > On 2021-10-14 at 10:57, Victor Hugo Muñoz wrote:
> > >
> > > I'm having problems installing texlive in my PC. I'm using unstable
> > > here.
> >
> > That may be the r
El jue, 14 oct 2021 a las 13:35, Andrew M.A. Cater
() escribió:
>>
> It might be worth checking what packages you have installed. If you
> can manage to, uninstall them (or use dpkg --purge to purge texlive-base
> then retry.
Thanks for the idea. It didn't work. texlive-base is not installed, so
p
El jue, 14 oct 2021 a las 12:46, The Wanderer () escribió:
>
> On 2021-10-14 at 10:57, Victor Hugo Muñoz wrote:
>
> > Hello, everyone.
> >
> > I'm having problems installing texlive in my PC. I'm using unstable
> > here.
>
> That may be the root problem, or at least, the best place to solve it.
> T
On Thu 14 Oct 2021 at 11:57:05 (-0300), Victor Hugo Muñoz wrote:
>
> I'm having problems installing texlive in my PC. I'm using unstable
> here.
>
> Everything started a couple of days ago, when I needed the package
> physics.sty. I had to install texlive-science. But dependences came
> in, and s
On 2021-10-14 at 10:57, Victor Hugo Muñoz wrote:
> Hello, everyone.
>
> I'm having problems installing texlive in my PC. I'm using unstable
> here.
That may be the root problem, or at least, the best place to solve it.
The basic rule of running unstable is "if it breaks, you get to keep all
the
On Thu, Oct 14, 2021 at 11:57:05AM -0300, Victor Hugo Muñoz wrote:
> Hello, everyone.
>
> I'm having problems installing texlive in my PC. I'm using unstable
> here.
>
> Everything started a couple of days ago, when I needed the package
> physics.sty. I had to install texlive-science. But depende
Yes, unfortunately, this is necessary to use SEV. Please take a look at these
instructions.
https://libvirt.org/kbase/launch_security_sev.html
https://developer.amd.com/sev/
The settings memtune, uefi, iommu are required to use launchSecurity = sev
The use for secured KVM using AMD Secure Encry
There is no need to PM me. I am subscribed to the mailinglist.
On Tue, Aug 10, 2021 at 02:06:04PM +0200, Office onFocus wrote:
> these are my iso files:
>
[...]
> wget
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.10.0-amd64-netinst.iso
> wget
> https://get.debian.org/
On Mon, Aug 09, 2021 at 02:04:49PM +0200, Office onFocus wrote:
> I cannot start an installation of a debian * .iso (install, live, ..) from
> any installation medium.
>
> This problem affects all Debian images. There are no problems with Ubuntu or
> CentOS! As soon as you
> boot the ISO and cl
On 04-04-2021 15:40, Orlando Canchola wrote:
> Yes, I am installing Debian boster
It's unlikely to be the desktop environment.
It could be a dirty disc, or any number of other issues.
What was the installation step immediately before you received that
message?
Cheers!
Harry
> El sáb., 3 de abril
On 04-04-2021 15:25, Orlando Canchola wrote:
> Hi! The error is: "Installation step failed
>
> An installation step failed. You can try to run the failing item again
> from the
> menu, or skip it and choose something else"
>
> The environment desktop I tried to install is xfce
Try to keep your
On 04-04-2021 15:12, Orlando Canchola wrote:
> Hi I am trying to install Debian buster but when I choose a desktop
> environment and wait, an error occurs, so what could I do?
Hullo, Orlando,
Describe the error.
Is there any message involved?
Which desktop environment are you trying to install?
C
On 11/11/20 10:00 PM, pe...@easthope.ca wrote:
> More about wicd later. This is a more immediate problem.
>
> An attempt to install a package begins as expected.
> For example apt-get install exim4 retrieves exim4-base and
> etc. Then preconfigures.
>
> Then this.
>
> Selecting previously unse
On Sun, Oct 25, 2020 at 4:36 PM didier gaumet
wrote:
> Hello,
>
> reading
> http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#programfiles-usr-bin-spacefm-auth
> ,
> Perhaps you should use the spacefm executable rather than the spacefm-auth
> one?
>
You are absolutely right. When I wa
On Sun, Oct 25, 2020 at 04:17:03AM -0400, Gene Heskett wrote:
[...]
> Probably its gfx commands are expecting x11 for a gui, and buster uses
> wayland, not x11. synaptic is in that same sinking boat. Spit...
This is a guesss, I guess. Could you substantiate it?
Having looked at synaptic's depe
Hello,
reading
http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#programfiles-usr-bin-spacefm-auth
,
Perhaps you should use the spacefm executable rather than the spacefm-auth one?
On Sunday 25 October 2020 01:10:43 kaye n wrote:
> Hello Friends!
>
> Firstly, if it matters, my system is:
>
> Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4
> Distro: Debian GNU/Linux 10 (buster)
> Machine:
> Type: Desktop Mobo: MSI model: H81M-P33 (MS-7817) v: 1.0 serial: N/A
>
On Mon, 12 Oct 2020 at 12:36, Marc Shapiro wrote:
> I had not thought that there was any real difference between the two
> formats, and this may well be the only instance where there is, but I'm
> going to use the '/dev/mapper/vgname-lvname' format in all locations
> from here on out.
I notice t
> '/dev/vgname/lvname' instead of '/dev/mapper/vgname-lvname'.
Indeed, I have found that `/dev//` doesn't work as argument to
`root=` on the kernel command line, whereas `/dev/mapper/-`
works fine.
Maybe it merits a bug report. Maybe it'll be hard/inconvenient to make
the kernel accept the `
On 10/11/20 2:04 PM, Marc Shapiro wrote:
On 10/11/20 6:34 AM, Stefan Monnier wrote:
That did it. I am assuming that the system was just in the process of
changing from the initrc to the actual running system? But how do I
get the
boot sequence to activate the LVs automatically each time bef
On 10/11/20 6:34 AM, Stefan Monnier wrote:
That did it. I am assuming that the system was just in the process of
changing from the initrc to the actual running system? But how do I get the
boot sequence to activate the LVs automatically each time before attempting
to mount the / filesystem?
AF
> That did it. I am assuming that the system was just in the process of
> changing from the initrc to the actual running system? But how do I get the
> boot sequence to activate the LVs automatically each time before attempting
> to mount the / filesystem?
AFAIK you don't need to do anything spe
On 10/10/20 7:42 PM, Stefan Monnier wrote:
I am attempting to mount an LVM Logical Volume as root, but I am getting an
error in the boot sequence when it attempts to mount the root filesystem.
The error is saying that it can not find /dev/block/254:15, which is the LV
that I am trying to mount.
> I am attempting to mount an LVM Logical Volume as root, but I am getting an
> error in the boot sequence when it attempts to mount the root filesystem.
> The error is saying that it can not find /dev/block/254:15, which is the LV
> that I am trying to mount. Then it falls into a shell.
>
> When
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
[...]
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
Strictly speaking
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
The whole design is built around "you can do this with systemctl commands,
or b
On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> > On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > > Seriously?
> > >
> > > Yes seriously. This is
On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > Seriously?
> >
> > Yes seriously. This is a pain point that could be avoided. I'm not a
> > systemd hater.
On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > Seriously?
>
> Yes seriously. This is a pain point that could be avoided. I'm not a
> systemd hater. I do some quite advanced things with it. But I don't
> think it's above cri
On Fri, Jul 24, 2020 at 09:52:29AM -0400, Greg Wooledge wrote:
[...]
> I don't know of any specific term for a directory's physical
> manifestation, other than "directory".
>
> In the olden days, a directory was basically a series of 16-byte
> records (14 bytes for the filename, 2 bytes for the
On Fri, Jul 24, 2020 at 09:56:27AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
[...]
> Since writing that, I've had occasion to remember the term 'dirent',
> which I think is more the in-memory representation of a directory than
> the on-disk representation, but m
On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
Seriously?
Yes seriously. This is a pain point that could be avoided. I'm not a
systemd hater. I do some quite advanced things with it. But I don't
think it's above criticism, and this is an area I feel is worthy of
criticism.
Co
On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
>
> On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
>
>> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>>> Nitpick: the directory entry is the one carrying the name.
>>
>> I had the impression that even a directory is stored in/as
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
Sounds like a case where directly editing the underlying
1 - 100 of 1133 matches
Mail list logo
