18817 user 20 0 3075708 2.3g 0 S 392.7 29.6 84:30.28
kdevtmpfsi
As you see above (top output), kdevtmpfsi consumes 2.3g Ram and a lot of
CPU (392%).
What's it then?
Thank you in advance.
On Thu, Mar 13, 2025 at 05:33:41PM +0800, tim wade wrote:
> 18817 user 20 0 3075708 2.3g 0 S 392.7 29.6 84:30.28
> kdevtmpfsi
>
> As you see above (top output), kdevtmpfsi consumes 2.3g Ram and a lot of CPU
> (392%).
> What's it then?
By all means, investigate further. But a fi
On Tue, 2025-03-04 at 10:02 +0200, Anssi Saari wrote:
> Van Snyder writes:
>
> > The nvidia-driver package from non-free apparently doesn't work
> > with a Quadro K2200.
>
> But you didn't check? The release notes tell a different story.
After I installed it,inxi -G reported the nouveau driver
Van Snyder writes:
> The nvidia-driver package from non-free apparently doesn't work with a Quadro
> K2200.
But you didn't check? The release notes tell a different story.
> NVidia recommends the 570 driver.
They always recommend the latest.
> The nvidia-driver package from non-free apparently doesn't work with a
> Quadro K2200. NVidia recommends the 570 driver.
>
> When I first installed the system, the left-hand pane of Evolution
> would spontaneously scroll, even if a different window had keyboard and
> mouse focus, and the mouse
On Sun, 2025-03-02 at 21:35 +0200, Anssi Saari wrote:
> Van Snyder writes:
>
> > I install the driver by running the NVIDIA-Linux-x86_64-
> > 570.124.04.run script at level 3, then rebooting.
>
> Why?
>
> > Is that DKMS?
>
> To be clear, it's a manual installation of drivers from the
> manufac
Van Snyder writes:
> I install the driver by running the NVIDIA-Linux-x86_64-570.124.04.run script
> at level 3, then rebooting.
Why?
> Is that DKMS?
To be clear, it's a manual installation of drivers from the
manufacturer. Definitely not DKMS. You want install stuff manually, you
get to upda
On Sat, 2025-03-01 at 22:38 +, Andy Smith wrote:
> If it's a DKMS, which is what my nvidia driver is, then it will try
> to
> be built for any kernel install and should work as long as you have
> headers installed. Though there have been times that things have
> changed
> and its build is broke
Hi,
On Sat, Mar 01, 2025 at 02:24:04PM -0800, Van Snyder wrote:
> The NVidia kernel module is built by running a bash script. It's not a
> .deb package.
>
> Will it still be automatigically rebuilt?
If it's a DKMS, which is what my nvidia driver is, then it will try to
be built for any kernel in
On Sat, 2025-03-01 at 21:02 +0100, Hans wrote:
> With an upgrade the build of the nvidia-kernel-module should run
> automatically.
The NVidia kernel module is built by running a bash script. It's not a
.deb package.
Will it still be automatigically rebuilt?
On Sat, 01 Mar 2025 11:27:25 -0800
Van Snyder wrote:
>
> If I get the metapackages linux-image-amd64 and limux-headers-amd64,
> will I need to rebuild the NVidia driver every time it loads a new
> kernel?
Probably yes. If you install a fixed kernel version, you'll probably
need only the headers
Am Samstag, 1. März 2025, 20:27:25 CET schrieb Van Snyder:
> On Fri, 2025-02-28 at 22:00 -0800, Van Snyder wrote:
> > That's correct. You're probably missing the metapackage that brings
> > in new kernels automatically. For an amd64 machine, that metapackage
> > is named "linux-image-amd64". (If
On Fri, 2025-02-28 at 22:00 -0800, Van Snyder wrote:
>
> That's correct. You're probably missing the metapackage that brings
> in new kernels automatically. For an amd64 machine, that metapackage
> is named "linux-image-amd64". (If you use DKMS kernel modules,
> you'll
> also want the correspon
On Sat, 2025-03-01 at 04:06 -0500, Timothy M Butterworth wrote:
>
>
> On Sat, Mar 1, 2025 at 4:04 AM Joe wrote:
> > On Fri, 28 Feb 2025 11:27:40 -0800
> > Van Snyder wrote:
> >
> > > On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
> > > > Your kernel is older than your CPU by about a yea
On Sat, Mar 01, 2025 at 04:06:37 -0500, Timothy M Butterworth wrote:
> On Sat, Mar 1, 2025 at 4:04 AM Joe wrote:
>
> > On Fri, 28 Feb 2025 11:27:40 -0800
> > Van Snyder wrote:
> >
> > > On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
> > > > Your kernel is older than your CPU by about a ye
On Sat, Mar 1, 2025 at 4:04 AM Joe wrote:
> On Fri, 28 Feb 2025 11:27:40 -0800
> Van Snyder wrote:
>
> > On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
> > > Your kernel is older than your CPU by about a year, so likely
> > > doesn't have enough
> > > backporting to fully support it prope
On Fri, 28 Feb 2025 11:27:40 -0800
Van Snyder wrote:
> On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
> > Your kernel is older than your CPU by about a year, so likely
> > doesn't have enough
> > backporting to fully support it properly. A newer kernel could be
> > all it takes to
> > make
On Fri, 28 Feb 2025 22:00:41 -0800
Van Snyder wrote:
> On Fri, 2025-02-28 at 12:46 -0800, Van Snyder wrote:
> > On Fri, 2025-02-28 at 14:34 -0500, Greg Wooledge wrote:
> > > On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> > > > "apt update" says everything is up to date, but the k
Am Freitag, 28. Februar 2025, 21:46:35 CET schrieb Van Snyder:
> On Fri, 2025-02-28 at 14:34 -0500, Greg Wooledge wrote:
> > On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> > > "apt update" says everything is up to date, but the kernel is
> > > 6.1.0-18.
> > > I believe there are severa
On Fri, 2025-02-28 at 12:46 -0800, Van Snyder wrote:
> On Fri, 2025-02-28 at 14:34 -0500, Greg Wooledge wrote:
> > On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> > > "apt update" says everything is up to date, but the kernel is
> > > 6.1.0-18.
> > > I believe there are several newer on
Van Snyder composed on 2025-02-28 11:27 (UTC-0800):
> On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
>> Your kernel is older than your CPU by about a year, so likely doesn't
>> have enough
>> backporting to fully support it properly. A newer kernel could be all
>> it takes to
>> make those
On Fri, Feb 28, 2025 at 12:46:35 -0800, Van Snyder wrote:
> On Fri, 2025-02-28 at 14:34 -0500, Greg Wooledge wrote:
> > On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> > > "apt update" says everything is up to date, but the kernel is
> > > 6.1.0-18.
> > > I believe there are several new
On Fri, 2025-02-28 at 14:34 -0500, Greg Wooledge wrote:
> On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> > "apt update" says everything is up to date, but the kernel is
> > 6.1.0-18.
> > I believe there are several newer ones, maybe up to 6.1.0-31?
>
> That's correct. You're probably
Hi,
On Fri, Feb 28, 2025 at 11:27:40AM -0800, Van Snyder wrote:
> What's "mce?"
https://en.wikipedia.org/wiki/Machine-check_exception
> "apt update" says everything is up to date, but the kernel is 6.1.0-18.
> I believe there are several newer ones, maybe up to 6.1.0-31?
You can try a kernel fr
On Fri, Feb 28, 2025 at 11:27:40 -0800, Van Snyder wrote:
> "apt update" says everything is up to date, but the kernel is 6.1.0-18.
> I believe there are several newer ones, maybe up to 6.1.0-31?
That's correct. You're probably missing the metapackage that brings
in new kernels automatically. Fo
On Thu, 2025-02-27 at 22:35 -0500, Felix Miata wrote:
> Your kernel is older than your CPU by about a year, so likely doesn't
> have enough
> backporting to fully support it properly. A newer kernel could be all
> it takes to
> make those MCEs go away.
What's "mce?"
"apt update" says everything i
On Fri, Feb 28, 2025 at 1:12 AM Van Snyder wrote:
>
> While running at level 3 in Debian 12.5, I got the following messages:
>
> mce: {Hardware Error]: CPU: 8 Machine Check: 0 Bank 0: 80440005
> mce: {Hardware Error]: TSC 1838aa435b6d
> mce: {Hardware Error]: PROCESSOR 0: b0671 TIME 140710
Van Snyder composed on 2025-02-27 19:06 (UTC-0800):
> While running at level 3 in Debian 12.5, I got the following messages:
> mce: {Hardware Error]: CPU: 8 Machine Check: 0 Bank 0: 80440005
> mce: {Hardware Error]: TSC 1838aa435b6d
> mce: {Hardware Error]: PROCESSOR 0: b0671 TIME 1407103
While running at level 3 in Debian 12.5, I got the following messages:
mce: {Hardware Error]: CPU: 8 Machine Check: 0 Bank 0: 80440005
mce: {Hardware Error]: TSC 1838aa435b6d
mce: {Hardware Error]: PROCESSOR 0: b0671 TIME 140710368 SOCKET 0 APIC
20 microcode 12b
Motherboard is Micro-Star
On 26.12.2024 14:03, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I think that's the righ
On 2024-12-26, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I have to source it by hand to
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
> > have to create a .profile to include .bashrc? Am I right?
> >
> Yes, I think that's the right way round.
Agreed. Even if
> Sent: Thursday, December 26, 2024 at 5:56 AM
> From: "Chris Green"
> To: debian-user@lists.debian.org
> Subject: Re: bashrc question
>
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I think that's the right way round.
I use ssh a lot and have a 'standard' configuration for all the
systems I ssh into.
On
On 26.12.2024 04:52, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
Hello
I have these settings in .bashrc of my home dir:
$ cat .bashrc
export TF_CPP_MIN_LOG_LEVEL=3
export CUDA_VISIBLE_DEVICES=-1
but every time after i login the system, the settin
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I h
On Thursday, 26-12-2024 at 14:16 hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
> I have
Hello
I have these settings in .bashrc of my home dir:
$ cat .bashrc
export TF_CPP_MIN_LOG_LEVEL=3
export CUDA_VISIBLE_DEVICES=-1
but every time after i login the system, the settings are not activated.
I have to source it by hand to make it work.
what's wrong with me?
Thanks.
On 12/2/24 00:02, Jeffrey Walton wrote:
On Sun, Dec 1, 2024 at 3:47 PM David Christensen
wrote:
On 12/1/24 04:27, Greg wrote:
Hi there,
I'm setting up MD-RAID0 on a top of HW-RAID6 devices (long story). I
would like to confirm the following:
1. The RAID0 chunk size should be the stripe widt
On Sun, Dec 1, 2024 at 3:47 PM David Christensen
wrote:
>
> On 12/1/24 04:27, Greg wrote:
> > Hi there,
> >
> > I'm setting up MD-RAID0 on a top of HW-RAID6 devices (long story). I
> > would like to confirm the following:
> >
> > 1. The RAID0 chunk size should be the stripe width of the
> > underl
I believe it puts it at the
start, rather
than end. In any case, I'd probably be inclined to go with the
default - likely less
confusing for anyone (e.g. even future you) to figure out exactly how
it's laid out,
if/when that becomes a question. In any case, likewise, can test that, e
swer
to my original question.
Regards
Greg
On 12/1/24 04:27, Greg wrote:
Hi there,
I'm setting up MD-RAID0 on a top of HW-RAID6 devices (long story). I
would like to confirm the following:
1. The RAID0 chunk size should be the stripe width of the
underlying RAID6 volumes.
2. The RAID0 metadata should be at the end of the device (meta
Hi there,
I'm setting up MD-RAID0 on a top of HW-RAID6 devices (long story). I
would like to confirm the following:
1. The RAID0 chunk size should be the stripe width of the
underlying RAID6 volumes.
2. The RAID0 metadata should be at the end of the device (metadata ver.
1.0).
3. The strid
On 2024-11-29 03:06, Darac Marjal wrote:
* "systemctl list-units --all" will list all the services installed on
your system. You can search that for something likely looking (e.g.
something beginning with "mysql" or similar).
this works for me. thank you for your help.
mysql it successed finally.
My question is how I can know the installed package name rather than
by guessing?
I can think of a couple of options:
* "dpkg -L mysql-server" will give you a list of files installed by that
package. If you're lucky, one of those will be a .service fi
> They got failed, no package was found.
>
> Then I run systemctl restart mysql it successed finally.
>
> My question is how I can know the installed package name rather than by
> guessing?
$ dpkg -l | grep -i mysql
But that gives you the Debian package name which is not what
question is how I can know the installed package name rather than by
guessing?
Thanks
On Fri, Nov 22, 2024 at 15:25:49 -0500, Roy J. Tellason, Sr. wrote:
> Why would you want to append to a file that some other program is also
> writing to? Sounds messy...
Opening a file in append mode has the following behavior:
O_APPEND
The file is opened in append mode
| sponge -a y
> hobbit:~$ ls -li y
> 6684744 -rw-r--r-- 1 greg greg 13 Nov 21 14:11 y
>
> The inode number changed, because it's a new file. This may be desirable
> or not -- it all depends on your needs. If the file in question is a log
> file that some program may still b
On Sat, 16 Nov 2024, Patrice Duroux wrote:
That's why I ended up with the suffix and letting the sysadmin
(often me, with a different hat on ;-) making that preference
explicit in the APT machinery.
But could it be the a nice feature for apt to have a list apart on the upgrading
(I would say
x | sponge -a y
> hobbit:~$ ls -li y
> 6684744 -rw-r--r-- 1 greg greg 13 Nov 21 14:11 y
>
> The inode number changed, because it's a new file. This may be desirable
> or not -- it all depends on your needs. If the file in question is a log
> file that some program may still be writing to, then this is absolutely
> NOT desirable.
Good point.
Cheers
--
t
signature.asc
Description: PGP signature
tomically when possible.
hobbit:~$ ls -li y
847514 -rw-r--r-- 1 greg greg 8 Nov 21 07:18 y
hobbit:~$ echo quux | sponge -a y
hobbit:~$ ls -li y
6684744 -rw-r--r-- 1 greg greg 13 Nov 21 14:11 y
The inode number changed, because it's a new file. This may be desirable
or not -- it all depen
On Thu, Nov 21, 2024 at 06:44:37PM +, Darac Marjal wrote:
[...]
> If it helps, "sponge" (in the moreutils package) seems to offer the right
> interface here:
[...]
Oh, wow -- thanks for that little gem!
Cheers
--
t
signature.asc
Description: PGP signature
On Thu, Nov 21, 2024 at 01:35:15PM +0100, to...@tuxteam.de wrote:
On Thu, Nov 21, 2024 at 07:22:53AM -0500, g...@wooledge.org wrote:
On Thu, Nov 21, 2024 at 09:48:06 +0100, to...@tuxteam.de wrote:
[...]
> My favourite is actually "sudo dd of=" it hasn't the side effect
> of flooding your std
On 2024-11-21 20:15, Greg Wooledge wrote:
On Thu, Nov 21, 2024 at 08:14:35 +0100, Erwan David wrote:
On Thu, Nov 21, 2024 at 07:39:33AM CET, Bitfox
said:
>
> BTW, what’s the difference between [[ ]] and [ ] here? I know only the
> latter.
IIRC, [[ ]] is a bash/zsh builtin, [ ] is /bin/[ other
g...@wooledge.org (12024-11-21):
> Checking my local Debian man pages now, however, I see that Debian's dd
> (GNU coreutils) *does* offer an append option.
>
> dd oflag=append conv=notrunc of="$file"
>
> So I guess that's another viable choice, as long as your target system
> has GNU coreutil
On Thu, Nov 21, 2024 at 07:22:53AM -0500, g...@wooledge.org wrote:
> On Thu, Nov 21, 2024 at 09:48:06 +0100, to...@tuxteam.de wrote:
[...]
> > My favourite is actually "sudo dd of=" it hasn't the side effect
> > of flooding your stdout (esp. with a larger, uglier thing).
Thanks for all the detai
On Thu, Nov 21, 2024 at 09:48:06 +0100, to...@tuxteam.de wrote:
> On Thu, Nov 21, 2024 at 08:32:30AM +, Michael Kjörling wrote:
> > On 20 Nov 2024 17:49 -0500, from g...@wooledge.org (Greg Wooledge):
> > >> sudo echo "something" >>/etc/postfix/virtual_alias_maps
> > >
> > >> Can you help me wh
On Thu, Nov 21, 2024 at 08:14:35 +0100, Erwan David wrote:
> On Thu, Nov 21, 2024 at 07:39:33AM CET, Bitfox said:
> >
> > BTW, what’s the difference between [[ ]] and [ ] here? I know only the
> > latter.
>
> IIRC, [[ ]] is a bash/zsh builtin, [ ] is /bin/[ other name of
> /bin/test
That's part
On Thu, Nov 21, 2024 at 08:32:30AM +, Michael Kjörling wrote:
> On 20 Nov 2024 17:49 -0500, from g...@wooledge.org (Greg Wooledge):
> >> sudo echo "something" >>/etc/postfix/virtual_alias_maps
> >
> >> Can you help me why the first sudo failed?
> >
> > The redirection >> is being done before
On 20 Nov 2024 17:49 -0500, from g...@wooledge.org (Greg Wooledge):
>> sudo echo "something" >>/etc/postfix/virtual_alias_maps
>
>> Can you help me why the first sudo failed?
>
> The redirection >> is being done before sudo is executed.
Indeed.
The usual pattern if you need to do this in a non-
On Wed, Nov 20, 2024 at 9:42 PM Bitfox wrote:
>
> In my bash shell script, when I say:
>
> sudo echo "something" >>/etc/postfix/virtual_alias_maps
>
> it could not run with the prompts:
>
> bin/mask.sh: line 18: /etc/postfix/virtual_alias_maps: Permission denied
>
>
> but, if I just say:
>
> echo
On Thu, Nov 21, 2024 at 07:39:33AM CET, Bitfox said:
>
> BTW, what’s the difference between [[ ]] and [ ] here? I know only the
> latter.
IIRC, [[ ]] is a bash/zsh builtin, [ ] is /bin/[ other name of
/bin/test
--
Erwan David
On 2024-11-21 13:21, Jeffrey Walton wrote:
On Wed, Nov 20, 2024 at 9:42 PM Bitfox wrote:
In my bash shell script, when I say:
sudo echo "something" >>/etc/postfix/virtual_alias_maps
it could not run with the prompts:
bin/mask.sh: line 18: /etc/postfix/virtual_alias_maps: Permission
denied
On 11/20/24 17:49, Greg Wooledge wrote:
On Thu, Nov 21, 2024 at 06:17:31 +0800, Bitfox wrote:
sudo echo "something" >>/etc/postfix/virtual_alias_maps
https://mywiki.wooledge.org/BashPitfalls#pf53
Can you help me why the first sudo failed?
The redirection >> is being done before sudo is exe
Sounds like making bin/mask.sh executable by root ONLY might help you forget to
use sudo to run it
Sudo chmod /bin/mask.sh x=rshould do it
--
All the best
Keith Bainbridge
keithr...@gmail.com
+61 (0)447 667 468
GMT+ 10:00
Sent from my Aphone. Please excuse my brevity.
On 21 November 2
On Thu, Nov 21, 2024 at 06:17:31 +0800, Bitfox wrote:
> sudo echo "something" >>/etc/postfix/virtual_alias_maps
https://mywiki.wooledge.org/BashPitfalls#pf53
> Can you help me why the first sudo failed?
The redirection >> is being done before sudo is executed.
Hello,
In my bash shell script, when I say:
sudo echo "something" >>/etc/postfix/virtual_alias_maps
it could not run with the prompts:
bin/mask.sh: line 18: /etc/postfix/virtual_alias_maps: Permission denied
but, if I just say:
echo "something" >>/etc/postfix/virtual_alias_maps
and run tha
On Wed, Nov 20, 2024 at 12:04:42PM +, Tim Woodall wrote:
> That's what I do too.
>
> +~tjw12r1
> if I've patched the current version.
> ~tjw12r1 if I've backported a higher version.
>
> I scan for newer versions in debian and auto-rebase my changes (unless
> the rebase fails) so I'm rarely mo
On Sat, 16 Nov 2024, to...@tuxteam.de wrote:
On Sat, Nov 16, 2024 at 11:53:25AM -0600, David Wright wrote:
On Sat 16 Nov 2024 at 15:54:17 (+0100), to...@tuxteam.de wrote:
On Sat, Nov 16, 2024 at 03:11:37PM +0100, Patrice Duroux wrote:
On Sid, building and installing locally modified packages
Patrice Duroux writes:
> But could it be the a nice feature for apt to have a list apart on the
> upgrading
> (I would say then 'replacing') of such cases?
> User can be alerted more easily during apt upgrade that some packages with a
> same version could be replaced by the Debian archive ones.
On Sat, Nov 16, 2024 at 08:41:24PM +0100, Patrice Duroux wrote:
>
> > That's why I ended up with the suffix and letting the sysadmin
> > (often me, with a different hat on ;-) making that preference
> > explicit in the APT machinery.
>
> But could it be the a nice feature for apt to have a list a
> That's why I ended up with the suffix and letting the sysadmin
> (often me, with a different hat on ;-) making that preference
> explicit in the APT machinery.
But could it be the a nice feature for apt to have a list apart on the upgrading
(I would say then 'replacing') of such cases?
User ca
On Sat, Nov 16, 2024 at 11:53:25AM -0600, David Wright wrote:
> On Sat 16 Nov 2024 at 15:54:17 (+0100), to...@tuxteam.de wrote:
> > On Sat, Nov 16, 2024 at 03:11:37PM +0100, Patrice Duroux wrote:
> > >
> > > On Sid, building and installing locally modified packages for testing
> > > at the same ve
On Sat 16 Nov 2024 at 15:54:17 (+0100), to...@tuxteam.de wrote:
> On Sat, Nov 16, 2024 at 03:11:37PM +0100, Patrice Duroux wrote:
> >
> > On Sid, building and installing locally modified packages for testing
> > at the same version as in the archive, I am surprised that apt upgrade
> > will reinst
On Sat, Nov 16, 2024 at 03:11:37PM +0100, Patrice Duroux wrote:
> Hi,
>
> On Sid, building and installing locally modified packages for testing
> at the same version as in the archive, I am surprised that apt upgrade
> will reinstall any of those installed by the one from the archive. I
> did not
Hi,
On Sid, building and installing locally modified packages for testing
at the same version as in the archive, I am surprised that apt upgrade
will reinstall any of those installed by the one from the archive. I
did not remember such a "feature" in the past, unless my memory plays
tricks on me:-
B.M. wrote:
> Thanks a lot for your inputs. In the meantime I disabled zram and added a 2
> GiB swapfile.
>
> What I don't understand: how can the system have not enough memory problems,
> while it's showing ~ 2 GiB cached/buffer? I'd expect it to free some of that
> and be fine again... 2 GiB is
On Montag, 28. Oktober 2024 15:21:02 CET Dan Ritter wrote:
> B.M. wrote:
> > Hi,
> >
> > I have a small server (Raspberry Pi 4 in fact) and since a couple of weeks
> > it repeatedly hangs after some days until I reboot it (after months of
> > uptime without any problem - but I changed a few things
B.M. wrote:
> Hi,
>
> I have a small server (Raspberry Pi 4 in fact) and since a couple of weeks it
> repeatedly hangs after some days until I reboot it (after months of uptime
> without any problem - but I changed a few things in the meantime, so maybe
> load is now higher than before).
>
> At
On 28.10.2024 15:41, B.M. wrote:
Hi,
I have a small server (Raspberry Pi 4 in fact) and since a couple of weeks it
repeatedly hangs after some days until I reboot it (after months of uptime
without any problem - but I changed a few things in the meantime, so maybe
load is now higher than before)
Hi,
I have a small server (Raspberry Pi 4 in fact) and since a couple of weeks it
repeatedly hangs after some days until I reboot it (after months of uptime
without any problem - but I changed a few things in the meantime, so maybe
load is now higher than before).
At least after installing watchd
On 9/17/24 00:12, Andy Smith wrote:
Hi,
On Mon, Sep 16, 2024 at 06:41:28PM +0200, Greg wrote:
1. If I export /dev/md0 via iSCSI would I benefit from memory buffers?
I've very little experience with iSCSI and don't know the answer to
this…
2. Is it possible to export a virtual device (like v
nteresting question... in all environments I ever used it,
network was the bottleneck, so even if there are scenarios where memory
buffers may be useful, you'd need very good connectivity to notice them,
I think.
I'm using ConnectX 3pro Mellanox adapters (56Gbps), it was cheaper than
10
Hi,
On Mon, Sep 16, 2024 at 06:41:28PM +0200, Greg wrote:
> 1. If I export /dev/md0 via iSCSI would I benefit from memory buffers?
I've very little experience with iSCSI and don't know the answer to
this…
> 2. Is it possible to export a virtual device (like vmdk) by iSCSI? This
> would allow sli
Hi Greg,
Am 16.09.2024 um 18:41 schrieb Greg:
Hi there,
I would like ot use Debian box as iSCSI server (target if I'm not
wrong). So I have two questions:
1. If I export /dev/md0 via iSCSI would I benefit from memory buffers?
That's an interesting question... in all environme
Hi there,
I would like ot use Debian box as iSCSI server (target if I'm not
wrong). So I have two questions:
1. If I export /dev/md0 via iSCSI would I benefit from memory buffers?
2. Is it possible to export a virtual device (like vmdk) by iSCSI? This
would allow slight overbooking of the st
Hi Maureen,
On Tue, 10 Sep 2024 20:18:03 -0400
Maureen L Thomas wrote:
> My old HP is not working right and it is very old. I am looking at
> laser printers and have always favored HP. But, in saying that I am
> open to any brand. I always get an all in one model since it does
> come in han
> I am great friend of "Brother" printers. They are cheap and reliable and they
> are well supported by linux. Brother is offering deb packages for installing
> or a linu script, which is downloading and installing these packages
> automatically.
Of course, that means you're at the mercy of Br
Le Tue, Sep 10, 2024 at 08:18:03PM -0400, Maureen L Thomas a écrit :
> Date: Tue, 10 Sep 2024 20:18:03 -0400
> From: Maureen L Thomas
> To: debian-user@lists.debian.org
> Subject: Just a simple question.
>
> My old HP is not working right and it is very old. I am looking at la
Am Mittwoch, 11. September 2024, 02:18:03 CEST schrieb Maureen L Thomas:
> My old HP is not working right and it is very old. I am looking at
> laser printers and have always favored HP. But, in saying that I am
> open to any brand. I always get an all in one model since it does come
> in handy.
ll in one model since it does come
> > in handy. Any advice is welcome. Thanks in advance.
>
> Every time this question comes up at work, the response is always the same:
> to send the latest version of this article:
> "After a full year of not thinking about printers,
. Thanks in advance.
Every time this question comes up at work, the response is always the
same: to send the latest version of this article:
"After a full year of not thinking about printers, the best printer is
still whatever random Brother laser printer that’s on sale."
https://www.theverg
My old HP is not working right and it is very old. I am looking at
laser printers and have always favored HP. But, in saying that I am
open to any brand. I always get an all in one model since it does come
in handy. Any advice is welcome. Thanks in advance.
Maureen
Hans writes:
> What I am exactly want to do:
>
> I have 5 live-build directories. In each I am starting my own script, which
> is
> setting variables and so on for the individual build and does some other
> things (rennamin and copying the resulted ISO and so on).
So you're asking how to do a
What I am exactly want to do:
I have 5 live-build directories. In each I am starting my own script, which is
setting variables and so on for the individual build and does some other
things (rennamin and copying the resulted ISO and so on).
As each build must be started within the live-build dir
Am 06.09.2024 um 12:25 schrieb Hans:
> Dear list,
>
> I am stuck with a little problem and know no one, whom I can ask. So I allow
> me to ask here.
>
> I have several directories, and in each directory there is a shell script,
> which MUST be started within and from its path.
>
> Now I wan
Hi,
On Fri, Sep 06, 2024 at 07:32:41AM -0400, Greg Wooledge wrote:
> On Fri, Sep 06, 2024 at 11:10:16 +, Andy Smith wrote:
> > Is there a reason not to just make these scripts cd to their own
> > directory so the caller doesn't have to care?
> >
> > cd "$(dirname "$0")"
>
> https://mywiki.wo
Andy Smith (12024-09-06):
> cd "$(dirname "$0")"
… || exit
Regards,
--
Nicolas George
1 - 100 of 10172 matches
Mail list logo
