Re: hard disk installation method fails
i am sorry link in my last mail may not work outside china
Re: hard disk installation method fails
Thank David Wright very much! i think error msg i report is precise, i use cell phone to record screen, https://pan.baidu.com/s/1a5ADqn1aXo5XmwcDSjVezQ?pwd=1234 this url is valid for 7 days, i am sorry picture isn't very clear. installer search disk for iso file, can't find suitable one, and display "No kernel modules found" screen does your installer find your iso file? or do you really install via http? network connection isn't needed if you use hard disk installation method, with debian-11.6.0-amd64-netinst.iso you can install bare minimal debian system
Re: cpu supported?
On Sat, Feb 18, 2023 at 1:57 AM Tom wrote: > > IsIntel® Core™ i5-10600K Processor > > Is this processor supported? Which release be best. The Core i5-10600K is a 10th gen/IceLake processor. It is supported by the linux kernel. There are no microcode updates (yet?) on my Core i5-1035G1 10th gen: $ grep microcode /proc/cpuinfo microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 microcode : 0xb2 $ dmesg | grep microcode [0.746446] microcode: sig=0x706e5, pf=0x80, revision=0xb2 [0.746479] microcode: Microcode Update Driver: v2.2. $ journalctl -b -k | grep microcode Feb 16 23:18:00 icelake kernel: microcode: sig=0x706e5, pf=0x80, revision=0xb2 Feb 16 23:18:00 icelake kernel: microcode: Microcode Update Driver: v2.2. (Also see https://wiki.debian.org/Microcode ). I'm not sure how to answer "Which release is best". Jeff
Re: cpu supported?
On 18/02/2023 06:17, Tom wrote: Is*Intel® Core™ i5-10600K Processor* Is this processor supported? Which release be best. Hi Tom, This processor from 2020 is very well supported by recent Linux kernels. You can use Debian Stable as Felix suggested. It also has 2 drives one is chip and the other spins. What? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: cpu supported?
Tom composed on 2023-02-18 01:17 (UTC-0500): > IsIntel® Core™ i5-10600K Processor > Is this processor supported? Which release be best. > It also has 2 drives one is chip and the other spins. Your CPU was introduced a bit over a year before Debian 11/Bullseye, so Bullseye as the current stable Debian release is an ideal candidate for your PC. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
cpu supported?
IsIntel® Core™ i5-10600K Processor Is this processor supported? Which release be best. It also has 2 drives one is chip and the other spins. Tom Clark Sent from Mail for Windows
Re: snapd vs apt
On Sat, Feb 18, 2023 at 12:50:12PM +0700, Max Nikulin wrote: [...] > When some application is packaged for Linux distributions it is easier to > rebuild it with a custom patch. I suspect that a developer distributing a > snap package may use specific and not well documented build environment. I think this one is a very important point which hasn't been addressed yet in this thread: Debian packages provide not only their source, but the whole build setup to rebuild that package (and most of them in a reproducible [1] way, i.e. they yield bit-for-bit identical binaries whenever the sources and the build dependencies stay constant). I only know of two "snowflake environments" which can do that, Nix and Guix. But those are in a wholly different category as the ones discussed here. Cheers [1] https://wiki.debian.org/ReproducibleBuilds -- t signature.asc Description: PGP signature
Re: hard disk installation method fails
On Fri 17 Feb 2023 at 22:26:56 (-0700), Charles Curley wrote:
> On Sat, 18 Feb 2023 12:05:11 +0800
> lsg wrote:
>
> > Really? i am afraid vmlinuz and initrd pair in iso file don't include
> > program that search disk for iso file, as pair in hd-media directory
> > does
> >
> > Debian11.6/main/installer-amd64/current/images/hd-media
> >
> > though it's possible to boot iso file with grub, but it's too
> > complicated
> >
> > it seems few users are using hard disk installation method theses days
>
> I haven't been entirely clear about what I do. I do boot d-i using
> grub. The following should make it a bit less opaque.
>
> root@dti386:~# cat /etc/grub.d/50_netinst
> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> menuentry "Install Debian 12 OS (preseeded)" {
> set root='hd0,msdos5'
> set isofile=/firmware-testing-i386-netinst.iso
> insmod part_msdos
> insmod loopback
> loopback loop (hd0,msdos5)$isofile
> linux (loop)/install.386/vmlinuz auto=true file=/media/preseed.cfg
> initrd (loop)/install.386/initrd.gz
> }
> menuentry "Install Debian 12 OS (Expert)" {
> set root='hd0,msdos5'
> set isofile=/firmware-testing-i386-netinst.iso
> insmod part_msdos
> insmod loopback
> loopback loop (hd0,msdos5)$isofile
> linux (loop)/install.386/vmlinuz rescue/enable=true
> initrd (loop)/install.386/initrd.gz
> }
> root@dti386:~#
>
> The key is the loopback module: grub mounts the iso file as a loopback
> device, pulls what it needs from the iso file, and goes from there.
> Using the loopback facility eliminates the necessity of a separate
> initrd and kernel.
>
> The iso file is on /dev/[vs]da5, the first extended partition, with a
> FAT file system. The idea is that the main partitions could get badly
> mangled, but grub and this partition survive. This gives you a rescue
> or re-installation capability without CD-ROMs, USB sticks, etc.
>
> And, yes, these use Testing/Bookworm's weekly build, not Bullseye's.
> The same principle applies to Bullseye.
Ah, that explains the (wrong) advice given earlier. Your method is
completely different from the one in the OP. The latter is the
method documented in the Installation Guide, typically at § 4.4 and
§ 5.1, and dating back at least to lenny (when I stopped buying media).
You have to choose one method or the other, and not mix them.
BTW, in my post, I should have pointed out that the 11.6 hd-media and
ISOs are based on linux-image-5.10.0-20-amd64_5.10.158-2_amd64,
whereas it's likely that linux-image-5.10.0-21-amd64_5.10.162-1_amd64
is installed on most systems.
Cheers,
David.
Re: snapd vs apt
On 17/02/2023 00:48, winnie hw wrote: When both snapd and apt sources are available, which one should I choose for package installation? Though I found the package versions in snapd are a bit newer than apt. With snapd you do not have full control when an application is updated. The daemon decides it for you. It may matter during debugging of some issue. Attempt to reproduce it in a clean environment may fail because on latest version is available in snap. With apt it is possible to setup a custom mirror, e.g. apt-cacher-ng proxy. A proxy for snap must be registered in Canonical and requires network connection to their repository. When some application is packaged for Linux distributions it is easier to rebuild it with a custom patch. I suspect that a developer distributing a snap package may use specific and not well documented build environment.
Re: Partitioning an SSD?
On 16/02/2023 22:25, Joe wrote: Stretch installed perfectly dual-boot with Win 10 on an EFI Acer netbook, but upgrading to Buster broke booting to grub. It actually broke EFI booting completely, but I've been able to restore booting at least to Windows. And yes, I've tried everything the Net can suggest. UEFI implementation by particular vendor may be buggy. E.g. an old HP laptop may be booted up either when it is configured to load a specific .efi file or when directory structures on EFI internal hard drive partition follows layout designed for a removable storage. It ignores most of EFI variables, so e.g. it is better to remove fbx.efi fallback intended to fix boot order. When you have learned such stuff, it is easy to fix boot. Unfortunately pieces of the puzzle was spread over multiple resources. I am not surprised that installer was unable to apply proper workarounds on particular machine. I have heard that vendors may add code intended to ensure booting Windows, but other OSes may be out of luck using the same file layout.
Re: hard disk installation method fails
On Sat, 18 Feb 2023 12:05:11 +0800
lsg wrote:
> Really? i am afraid vmlinuz and initrd pair in iso file don't include
> program that search disk for iso file, as pair in hd-media directory
> does
>
> Debian11.6/main/installer-amd64/current/images/hd-media
>
> though it's possible to boot iso file with grub, but it's too
> complicated
>
> it seems few users are using hard disk installation method theses days
I haven't been entirely clear about what I do. I do boot d-i using
grub. The following should make it a bit less opaque.
root@dti386:~# cat /etc/grub.d/50_netinst
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Install Debian 12 OS (preseeded)" {
set root='hd0,msdos5'
set isofile=/firmware-testing-i386-netinst.iso
insmod part_msdos
insmod loopback
loopback loop (hd0,msdos5)$isofile
linux (loop)/install.386/vmlinuz auto=true file=/media/preseed.cfg
initrd (loop)/install.386/initrd.gz
}
menuentry "Install Debian 12 OS (Expert)" {
set root='hd0,msdos5'
set isofile=/firmware-testing-i386-netinst.iso
insmod part_msdos
insmod loopback
loopback loop (hd0,msdos5)$isofile
linux (loop)/install.386/vmlinuz rescue/enable=true
initrd (loop)/install.386/initrd.gz
}
root@dti386:~#
The key is the loopback module: grub mounts the iso file as a loopback
device, pulls what it needs from the iso file, and goes from there.
Using the loopback facility eliminates the necessity of a separate
initrd and kernel.
The iso file is on /dev/[vs]da5, the first extended partition, with a
FAT file system. The idea is that the main partitions could get badly
mangled, but grub and this partition survive. This gives you a rescue
or re-installation capability without CD-ROMs, USB sticks, etc.
And, yes, these use Testing/Bookworm's weekly build, not Bullseye's.
The same principle applies to Bullseye.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Re: Virtual machine affects client screen resolution
On 18/02/2023 08:57, Albert S. wrote: If you think I issued the xrandr command on the wrong machine, that was not the case: history makes it clear. Behavior depends on the DISPLAY environment value at the moment when xrandr was executed. Likely it was pointed not to vnc Xserver, but to the socket forwarded to your workstation by ssh. Try echo "$DISPLAY" In a local shell, in a ssh session, and from vncviewer.
Re: Partitioning an SSD?
On Thu 16 Feb 2023 at 08:59:58 (+0100), Nicolas George wrote: > pa...@quillandmouse.com (12023-02-15): > > Here's why you would partition a drive. Reinstalling (which I end up > > having to do every time Debian comes out with a new version > > Debian is not Ubuntu, major upgrade do not break the system. Judging by what we read here, they do when inexperienced people try running testing or unstable for one reason or another. (NB I'm casting no aspertions on paulf.) Cheers, David.
Re: hard disk installation method fails
On Sat 18 Feb 2023 at 09:17:43 (+0800), lsg wrote:
> On 2/17/23 22:29, Brian wrote:
> > There isn't much you can do about this. It is usually a temporary
> > issue thats happens after Linux kernel updates. The installer is
> > now out of step. It gets automatically fixed after some time.
> >
> Thanks! i've thought updating iso image and hard disk installer are
> automatic
>
> it's very frustrating, i've never been so disappointed with debian
>
> it will be easier if i can determine if they match by matching file
> name of iso file with that of vmlinuz and initrd pair (their file
> names shall all include same version number)
>
> i have successfully used bullseye hard disk installation method for
> i386 about one month ago, i don't know why it doesn't work this time
I'm not really interested in actually installing an OS at the moment,
so I stopped the debian-installer when it gets to the partitioner.
What I need to know is how far /you/ got before you received the error
you paraphrased as:
"No kernel modules found", probably due to kernel mismatch
(BTW, it really helps to report error messages precisely.)
Here's what I did, and it all worked perfectly (as far as the
partitioner step):
I downloaded the files you did (here with their SHA256):
e482910626b30f9a7de9b0cc142c3d4a079fbfa96110083be1d0b473671ce08d
debian-11.6.0-amd64-netinst.iso
7f161a705077f231d282dc4a8961f17c5d4a6182877ca930eca280958f86dfe9
firmware-11.6.0-amd64-netinst.iso
and these from
http://ftp.us.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/
b00b339f8b1aada1841d86650377dd8e7299eaa7f34d0bbf21deb561467015cd vmlinuz
ab34a60082dee4b18fe3c1e6131cd27e876d6877a3b81c6490814f0a594608ef initrd.gz
Note to Charles: that happens to be the same kernel as on the ISOs,
but you must use the hd-media's initrd. I assume that's because it
knows how to look for the .iso file. You can't just extract it from
the netinst ISO.
OK. I placed these four files into /boot on a regular Debian machine.
I intended to check both ISOs, so I hid one by appending -hidden to
the filename: firmware-11.6.0-amd64-netinst.iso-hidden
Next, I edited the file /boot/grub/grub.cfg and added a few lines at
the end. You can see where they go by the BEGIN/END and 40:
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Install Debian via HTTP" {
search --no-floppy --label --set=root swan05
linux /boot/vmlinuz
initrd /boot/initrd.gz
}
### END /etc/grub.d/40_custom ###
OK, I use LABELs, and this Debian system's root filesystem is on
/dev/sda5 with the LABEL swan05. If you only have a UUID, then that
line will become:
search --no-floppy --fs-uuid --set=root
12345678-abcd-fedc--1234567890ab
or whatever the root filesystem's UUID is.
Then I rebooted the system, and when Grub started (blue screen),
I downarrow'd to Install Debian via HTTP and pressed Return.
A few seconds, and many messages, later I got:
┌───┤ [!!] Select a language
├┐
│
│
│ Choose the language to be used for the installation process. The selected
│
│ language will also be the default language for the installed system.
│
│
│
As I say, I went as far as the partitioner. With no firmware for wifi,
I had to skip out of configuring the network.
I then rebooted to my Debian system, juggled the ISOs' names to:
/boot/debian-11.6.0-amd64-netinst.iso-hidden
/boot/firmware-11.6.0-amd64-netinst.iso
rebooted, and repeated the exercise, with a working wifi network
this time. I stopped again at the partitioner step.
All that took about fifteen or twenty minutes, but that might be
because I've done it before, and the extra grub.cfg lines are in
my backups.
Cleanup: the extra files in /boot do no harm unless you're short of
space. The extra menu will disappear whenever Grub is reconfigured:
kernel update, or grub update. Just ignore it.
Cheers,
David.
Re: ps and AIX field descriptors
On Fri 17 Feb 2023 at 11:30:43 (-0500), Greg Wooledge wrote: > On Fri, Feb 17, 2023 at 09:20:34AM -0600, David Wright wrote: > > On Fri 17 Feb 2023 at 10:05:20 (+0300), Reco wrote: > > > So, to answer your question - currently the only way to restore the > > > behaviour you want is to patch procps and rebuild it. > > Fabulous analysis. > > > Or, depending on the context, you could of course restore > > the appearance of the output with sed: > > > > $ ps -eo '%p %C' | sed -e 's/\([^ ]\+\) /\1|/;' > > PID|%CPU > > 1| 0.0 > > 2| 0.0 > > 3| 0.0 > > 4| 0.0 > > 6| 0.0 > > [ … ] > > Eww, GNUisms. I don't keep a list of differences to hand, but I guess you'd prefer: $ ps -eo '%p %C' | sed -E 's/([^ ]+) /\1|/;' PID|%CPU 1| 0.0 2| 0.0 [ … ] > That aside, a workaround like this is ugly and should > not be needed. The OP wrote: "How can I restore the previous behaviour that allowed other than whitespace separators between fields?" If that's the required format, what are the alternatives? > This sounds like a bug in procps that should be reported, > if it hasn't already. And how long before it's fixed? As for whether it /is/ a bug, I guess that depends on the interpretation of somewhat in "This ps supports AIX format descriptors, which work somewhat like the formatting codes of printf(1) and printf(3)." That's beyond my pay-grade. Cheers, David.
Re: hard disk installation method fails
On 2/18/23 11:12, Charles Curley wrote: That wouldn't help. My method pulls the kernel and initrd from the iso itself. I got the same error you did. I used the weekly build, so I shall wait until the next build and see if that works. Really? i am afraid vmlinuz and initrd pair in iso file don't include program that search disk for iso file, as pair in hd-media directory does Debian11.6/main/installer-amd64/current/images/hd-media though it's possible to boot iso file with grub, but it's too complicated it seems few users are using hard disk installation method theses days
Re: Virtual machine affects client screen resolution
On Fri 17 Feb 2023 at 20:57:38 (-0500), Albert S. wrote: > Running “xrandr --size 800x600” on a virtual machine affected both > monitors on my workstation. That was completely unexpected and I am > wondering how to explain that. > > Below you will find the detailed description. [ … ] > But my real concern is how a xrandr command issued on a VM which is > running on another machine could affect the video of the client > machine used to access that VM. > > I would appreciate an explanation for that. The clue is in your use of the word "client". In fact, the "video of the machine used to access that VM" is the X /server/. The applications that you control on this machine, and others that you connect to, which you thought were servers, are in fact the clients. So, for example, I'm sitting at my All-in-One, running an X server as usual. In a room down the hall, I have a laptop that's booted up, but hasn't been used yet. It's sitting at a VC prompt waiting for someone to log in. There's no X server running on it. I've connected to the laptop with ssh from an xterm here on my A-i-O, and typed into the /laptop/: $ xrandr --output eDP --rotate right and immediately, my screen blanks, comes back a second later, and everything is sideways. When I type: $ xrandr --output eDP --rotate normal then normality is restored. So I ran xrandr on the laptop, but xrandr is not concerned with that machine, but only with the X /server/, running on my A-i-O. https://en.wikipedia.org/wiki/X_Window_System Cheers, David.
Re: hard disk installation method fails
On Sat, 18 Feb 2023 09:17:43 +0800 lsg wrote: > it will be easier if i can determine if they match by matching file > name of iso file with that of vmlinuz and initrd pair (their file > names shall all include same version number) That wouldn't help. My method pulls the kernel and initrd from the iso itself. I got the same error you did. I used the weekly build, so I shall wait until the next build and see if that works. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Partitioning an SSD?
Cindy Sue Causey wrote: ... have you tried refind? i've been using it for several years now and while i do still have grub installed and it gets updated i primarily use refind instead. songbird
Re: versions comparison
Thanks Greg. Good to know that. regards. On Sat, Feb 18, 2023 at 9:08 AM Greg Wooledge wrote: > On Sat, Feb 18, 2023 at 08:38:22AM +0800, winnie hw wrote: > > sorry this is maybe not related to debian directly. > > but how can I compare two versions of a package by programming? > > for instance, v1.24.0.1 should be later than v1.23.99.999. > > Debian's dpkg(1) command has a --compare-versions option. > >--compare-versions ver1 op ver2 >Compare version numbers, where op is a binary operator. dpkg >returns true (0) if the specified condition is satisfied, and > false >(1) otherwise. > > unicorn:~$ if dpkg --compare-versions v1.24.0.1 gt v1.23.99.999; then echo > true; else echo false; fi > dpkg: warning: version 'v1.24.0.1' has bad syntax: version number does not > start with digit > dpkg: warning: version 'v1.23.99.999' has bad syntax: version number does > not start with digit > true > > I wonder if those were the actual version numbers you intended to compare. > Also, your example isn't particularly good, because a simple string > comparison also would have returned true in this case, even though it's > entirely the wrong approach. > > A better example would be something like: > > unicorn:~$ if dpkg --compare-versions 1.24.0.1 gt 1.9.99.999; then echo > true; else echo false; fi > true > > because a string comparison gives a different result here. > > Also, you might be interested in the -V option of GNU sort(1). It > purports to do some kind of version string comparison. I have no idea > whether it handles all the possible Debian versions strings the same > way that dpkg --compare-versions does. > >
Re: versions comparison
On 2023-02-17 at 20:48, Greg Wooledge wrote:
> On Fri, Feb 17, 2023 at 07:42:24PM -0600, John Hasler wrote:
>
>> Also, while Debian uses a sane, consistent version numbering system it
>> is not safe to make assumptions about what non-Debian developers do.
>
> The best thing I can say about Debian's version strings is that they
> are documented.
>
> unicorn:~$ grep ^Version:
> /var/lib/apt/lists/ftp.us.debian.org_debian_dists_bullseye_main_binary-amd64_Packages
> | awk '{print length($0), $0}' | sort -rn | sed 's/.* //' | head
> 1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1.1
> 0.0~git20201031.beca652+really.git20200323.1b35463-2
> 0.0~git20201031.beca652+really.git20200323.1b35463-2
> 7.3.3+dfsg1-1+0.0~git20210225.1e7ef9e+dfsg-4
> 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1
> 0.16.1+20180422git6becd92d7fce3fc411d7c-4+b3
> 6.1.0~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
> 2.0.1~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
> 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1
> 1.1.0~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
>
> Every single piece of that line noise has some meaning... to someone. ;-)
It's really fairly straightforward when you know the pieces involved.
I'm not previously familiar with any of these specific version numbers,
but I could explain exactly what each part of any given one of them
means, if there were need to do so.
(I tried to write up a general explanation that would cover all of them,
but it was starting to develop too many moving parts and sub-clauses for
that to seem to be worthwhile in the immediate context.)
These versions also don't even display one key component of Debian
version numbers that isn't found in versions elsewhere: the epoch.
That's a number which appears at the start of the version, is delimited
from the rest of the version by a colon, and when omitted is
automatically treated as being 0. It's used to allow for the case of a
version-numbering scheme changing, where the new version would not
otherwise sort as greater than the old - e.g., if the old version was
date-based (20230217, for a version referencing today's date) and the
new one uses more traditional version semantics (1.0.0, or the like).
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
Virtual machine affects client screen resolution
Running “xrandr --size 800x600” on a virtual machine affected both monitors on my workstation. That was completely unexpected and I am wondering how to explain that. Below you will find the detailed description. I run KVM on a Debian 11 server, which has no monitor or keyboard attached to it. One of the VMs running on that server is a Ubuntu desktop 22.04 LTS (I needed the desktop version due to the application I was running there). From another machine (a workstation running Debian 11, xfce) with two monitors I access the Ubuntu VM when I need to. I use ssh to the server to establish a ssh tunnel, and then access the Ubuntu machine with the command “/usr/lib/ssvnc/vncviewer localhost:5906 &”. A couple of weeks ago I decided to increase the Ubuntu VM resolution to 1600x1200 to make my work easier, and that initially worked. However, today, after a reboot of the Debian server and all VMs, I noticed that the Ubuntu screen (through VNC) would still have the resolution of 1600x1200 when displayed on my workstation, but it would display as black on the top and gray on the bottom, without any image. The VM console was dead. However, I could still access the VM through ssh. So, I started trying different commands to fix the problem. One of the commands I issued on the VM (through ssh) was “xrandr –size 800x600”. When I issued the xrandr command, one display on my workstation turned off, and the other one went to 800x600 resolution. That was completely unexpected. I am asking myself how can a command issued on a VM which is running on a different machine affect the screen resolution of the workstation used to access that VM. Just to be clear, I was accessing that VM both through ssh and through vncviewer (still back and gray screen image) when that happened. If you think I issued the xrandr command on the wrong machine, that was not the case: history makes it clear. Just to be complete, the solution to the video problem was to make a change on the KVM xml file, from video type=vga to type=virtio. But my real concern is how a xrandr command issued on a VM which is running on another machine could affect the video of the client machine used to access that VM. I would appreciate an explanation for that. Thanks, Albert
build static linked gedit with meson?
I want to compile a statically linked version of gedit using the upstream meson based package. I've got the sources matching my current Debian 11 system and can do a build no problem. What I want to do is statically link the gedit executable. I see the non-static executable is very small and there is a large library file libgedit, and using ldd I see the executable wants to call many system libs. Target is a single statically linked executable which incorporates libgedit as well as parts of all the system libraries they call. Meson doesn't obviously seem to support static linked executables. Any suggestions? Jeremy
Re: Apropos el cron d'usuari ...
On Thu, Feb 16, 2023 at 09:33:35PM +0100, Lluís Gras wrote:
> Missatge de Alex Muntada del dia dl., 13 de febr. 2023 a
> les 21:43:
>
> > Hola, Lluís:
> >
> > > Entenc que es un tema de l'entorn del cron de l'usuari, però
> > > malgrat potinejar al respecte no he trobat com apedaçar-ho.
> >
> > Compte perquè, si no vaig errat, les ordres que s'executen des
> > del cron no veuen l'entorn habitual de l'usuari, és a dir, que el
> > shell que s'executa no té el mateix entorn que el que tindries en
> > un terminal o consola.
> >
>
> Si si, entenc que les coses van per aquí, però de moment, tots els intents
> han estat infructuosos.
>
> [...]
>
> > Em sembla recordar que una estratègia era executar l'ordre que
> > vols dins un bash que sí llegeixi l'entorn, e.g.
> >
> > 40 21 * * * env
> > 41 21 * * * bash -l -c "env"
> >
> > Veuràs que donen resultats diferents.
Jo n'afegiria un més:
# m h dom mon dow command
* * * * * env > /tmp/env0
* * * * * sh -c "env > /tmp/env1"
* * * * * sh -l -c "env > /tmp/env2"
I, clar directament executar directament "env > /tmp/env3"
Veuràs que tots donen entorn distintes. El motiu és que els fitxers que
carreguen no son els mateixos en cada cas.
Amb aquests 4 exemples de variables d'entorns ja tens per a fer les proves que
necessites...
Per a netejar les variables d'entorn actual i carregar les d'un fitxer es pot
fer així (segur que hi ha formes més maques):
| #!/usr/bin/env sh
| env -i sh -c "set -a ; source /tmp/env0 ; set +a; env"
Aquest exemple mostra les variables que ha carregat (hauria de ser quasi
exactament el que diu a /etc/env0). Si canvies el darrer 'env' per
'/usr/bin/xtrlock' aniras veient en quins dels fitxers /tmp/envX funciona i en
quins no. I ja experimentant manipulant els fitxers d'exemple hauries d'arribar
a trobar les variables que necessites.
Altra forma podria ser indagant amb strace o similar, però crec que és massa
complexe pel cas que se t'ha presentat.
I fotre una ullada al manual sovint també ajuda, però no deixis mai que 1 minut
de llegir el manual et privi d'hores de diversió :) [Secció WARNING, per
exemple]
Una abraçada. Salut!
PS: xtrlock.c:122: if (getenv("WAYLAND_DISPLAY"))
--
Antoni Villalonga
https://friki.cat/
Re: versions comparison
On Fri, Feb 17, 2023 at 07:42:24PM -0600, John Hasler wrote:
> Also, while Debian uses a sane, consistent version numbering system it
> is not safe to make assumptions about what non-Debian developers do.
The best thing I can say about Debian's version strings is that they
are documented.
unicorn:~$ grep ^Version:
/var/lib/apt/lists/ftp.us.debian.org_debian_dists_bullseye_main_binary-amd64_Packages
| awk '{print length($0), $0}' | sort -rn | sed 's/.* //' | head
1.31~pre0.8052aabdd159bc9050e7dc264f33782c5acce05f-1.1
0.0~git20201031.beca652+really.git20200323.1b35463-2
0.0~git20201031.beca652+really.git20200323.1b35463-2
7.3.3+dfsg1-1+0.0~git20210225.1e7ef9e+dfsg-4
3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1
0.16.1+20180422git6becd92d7fce3fc411d7c-4+b3
6.1.0~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
2.0.1~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1+deb11u1
1.1.0~1.1.0+~2.0.1~ds+~6.1.0+~0~20180821-1
Every single piece of that line noise has some meaning... to someone. ;-)
Re: versions comparison
Also, while Debian uses a sane, consistent version numbering system it is not safe to make assumptions about what non-Debian developers do. There have been some very original systems used, and developers have been known to change systems in midstream. -- John Hasler j...@sugarbit.com Elmwood, WI USA
Re: hard disk installation method fails
On 2/17/23 22:29, Brian wrote: There isn't much you can do about this. It is usually a temporary issue thats happens after Linux kernel updates. The installer is now out of step. It gets automatically fixed after some time. Thanks! i've thought updating iso image and hard disk installer are automatic it's very frustrating, i've never been so disappointed with debian it will be easier if i can determine if they match by matching file name of iso file with that of vmlinuz and initrd pair (their file names shall all include same version number) i have successfully used bullseye hard disk installation method for i386 about one month ago, i don't know why it doesn't work this time
Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting
Celejar wrote: > The logs show regular deactivate events like the following every 20 > seconds: > > ClientMessage DEACTIVATE: already inactive, resetting activity time > > I saw this: > > https://www.jwz.org/xscreensaver/faq.html#no-blank > > I guess I have to figure out what application is sending these messages? > Firefox? I do tend to keep a lot of tabs open. I recall seeing something several months ago about the Xfce power manager fighting with xscreensaver, though I'm not able to find it right now. If you have the Xfce power manager configured to manage the display, you could try disabling that. mike
Re: versions comparison
On Sat, Feb 18, 2023 at 08:38:22AM +0800, winnie hw wrote: > sorry this is maybe not related to debian directly. > but how can I compare two versions of a package by programming? > for instance, v1.24.0.1 should be later than v1.23.99.999. Debian's dpkg(1) command has a --compare-versions option. --compare-versions ver1 op ver2 Compare version numbers, where op is a binary operator. dpkg returns true (0) if the specified condition is satisfied, and false (1) otherwise. unicorn:~$ if dpkg --compare-versions v1.24.0.1 gt v1.23.99.999; then echo true; else echo false; fi dpkg: warning: version 'v1.24.0.1' has bad syntax: version number does not start with digit dpkg: warning: version 'v1.23.99.999' has bad syntax: version number does not start with digit true I wonder if those were the actual version numbers you intended to compare. Also, your example isn't particularly good, because a simple string comparison also would have returned true in this case, even though it's entirely the wrong approach. A better example would be something like: unicorn:~$ if dpkg --compare-versions 1.24.0.1 gt 1.9.99.999; then echo true; else echo false; fi true because a string comparison gives a different result here. Also, you might be interested in the -V option of GNU sort(1). It purports to do some kind of version string comparison. I have no idea whether it handles all the possible Debian versions strings the same way that dpkg --compare-versions does.
versions comparison
Hello, sorry this is maybe not related to debian directly. but how can I compare two versions of a package by programming? for instance, v1.24.0.1 should be later than v1.23.99.999. Thank you.
Compilar XFCE 4.18 en Debian estable.
Tengo curiosidad de ver la nueva versión de XFCE, pero no he visto otra opción que compilarlo. ¿Alguien que lo haya hecho tiene alguna recomendación? Saludos. Marcos. Delgado.
Re: Partitioning an SSD?
On Fri, 17 Feb 2023 19:33:32 + "Andrew M.A. Cater" wrote: > It's likely that LILO will go with Bookworm - I think it's more or > less unmaintained if I recall correctly, so someone needs to help you > getting this one to work. Is this your only machine? It doesn't seem to be in Bookworm now. > > As ever the Arch Wiki often also has some good tips: maybe we can > get some help from the folks who hang out here first. Cindy, you might also look at refind -- assuming the computer in question is EFI compliant. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: ps and AIX field descriptors
On 2023-02-17 at 15:21, Greg Wooledge wrote: > On Fri, Feb 17, 2023 at 01:49:59PM -0500, The Wanderer wrote: > >> I can't speak to the new version, as I'm still running 3.3.17-7.1 on my >> machine - but I can at least note that the man page from that older >> version also explicitly says "a blank-separated or comma-separated list" >> in the description for the '-o' option, but the given command line (with >> a pipe for a separator) still works. (This may reflect only the same >> thing that you said, above.) >> >> It's entirely possible that this was an intentional change, to bring >> things in line with the documentation, and/or even one required in order >> to be in line with some appropriate specification. > > Hmm... fair point. POSIX says: > >The application shall ensure that the format specification is a list of >names presented as a single argument, or -separated. > > So the behavior of ps in bullseye is an extension of the POSIX requirement, > and apparently only applies to the "AIX format specifiers", which are yet > another extension. FWIW, at least in the 3.3.17-7.1 version I have, the man page claims that ps supports the POSIXLY_CORRECT environment variable. This type of more-strict POSIX compliance, even when it means being less capable, strikes me as the sort of thing that should probably be gated behind a check for that flag. > Nevertheless, this change definitely feels like a regression. Scripts > that are relying on the bullseye behavior, with full output formatting > capability, will no longer work in bookworm. > > I'm not using any such scripts, so I don't have anything to lose here, > but the OP might seriously want to get a bug report in, at least to > learn whether this is an intended regression, or an accidental one. Agreed, -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: ps and AIX field descriptors
On Fri, Feb 17, 2023 at 01:49:59PM -0500, The Wanderer wrote: > I can't speak to the new version, as I'm still running 3.3.17-7.1 on my > machine - but I can at least note that the man page from that older > version also explicitly says "a blank-separated or comma-separated list" > in the description for the '-o' option, but the given command line (with > a pipe for a separator) still works. (This may reflect only the same > thing that you said, above.) > > It's entirely possible that this was an intentional change, to bring > things in line with the documentation, and/or even one required in order > to be in line with some appropriate specification. Hmm... fair point. POSIX says: The application shall ensure that the format specification is a list of names presented as a single argument, or -separated. So the behavior of ps in bullseye is an extension of the POSIX requirement, and apparently only applies to the "AIX format specifiers", which are yet another extension. On bullseye: unicorn:~$ ps -o '%U|%p|%a' USER|PID|COMMAND greg| 1010|bash greg|2023595|ps -o %U|%p|%a unicorn:~$ ps -o 'user|pid|args' error: unknown user-defined format specifier "user|pid|args" [...] Nevertheless, this change definitely feels like a regression. Scripts that are relying on the bullseye behavior, with full output formatting capability, will no longer work in bookworm. I'm not using any such scripts, so I don't have anything to lose here, but the OP might seriously want to get a bug report in, at least to learn whether this is an intended regression, or an accidental one.
Re: Partitioning an SSD?
On Fri, Feb 17, 2023 at 02:11:02PM -0500, Cindy Sue Causey wrote: > > Upgrades are definitely a lot more trouble now, and yes, I do realise > > that each release is bigger and more complicated than the last. > > > Ditto. I can still remember saying (on Debian-User) that if someone > wanted to destroy an operating system, all they had to do was break > its ability to boot. A few weeks later was the last time I was able to > install a Debian release with GRUB that booted. > > LILO was the only thing that worked for me after that. Something went > wrong with mine a few months ago, and I've ended up in all kinds of > other operating systems' LiveDVDs ever since. > Cindy, What machine? What versions have you tried? Does the machine need to dual boot anything? > Even LiveDVD didn't work *for me* with Debian. There was some kind of > a showstopping library issue. Was something like libunistring. > Couldn't keep it up and running long enough to attempt a partition > install. Other systems like Mint have somehow broken the EFI/UEFI > roadblock when installed so I was taking a chance that maybe Debian > could do the same thing. > This is another one of those where the list really needs to know *exactly* what you've done so we can help troubleshoot. A machine that doesn't boot Debian stable with GRUB is in a sorry state. > A partition is currently set up with Sid (Trixie?). It broke my heart > when it didn't boot with GRUB, either. I've tried everything I can > with it with the primary assault being to attempt to duplicate all > GRUB packages that Mint uses to boot from a thumb drive. > It's likely that LILO will go with Bookworm - I think it's more or less unmaintained if I recall correctly, so someone needs to help you getting this one to work. Is this your only machine? As ever the Arch Wiki often also has some good tips: maybe we can get some help from the folks who hang out here first. With every good wish, as ever, Andy Cater > > Cindy :) > -- > Talking Rock, Pickens County, Georgia, USA > * runs with birdseed * >
Re: Partitioning an SSD?
On 2/16/23, Joe wrote: > On Thu, 16 Feb 2023 08:59:58 +0100 > Nicolas George wrote: > >> pa...@quillandmouse.com (12023-02-15): >> > Here's why you would partition a drive. Reinstalling (which I end up >> > having to do every time Debian comes out with a new version >> >> Debian is not Ubuntu, major upgrade do not break the system. >> > > That's the way it used to be, back in the days of sarge, etch, lenny... > > Stretch installed perfectly dual-boot with Win 10 on an EFI Acer > netbook, but upgrading to Buster broke booting to grub. It actually > broke EFI booting completely, but I've been able to restore booting at > least to Windows. And yes, I've tried everything the Net can suggest. > > On another machine, upgrading Buster to Bullseye broke it beyond my > ability to fix, so I installed Bullseye from scratch. > > Upgrades are definitely a lot more trouble now, and yes, I do realise > that each release is bigger and more complicated than the last. Ditto. I can still remember saying (on Debian-User) that if someone wanted to destroy an operating system, all they had to do was break its ability to boot. A few weeks later was the last time I was able to install a Debian release with GRUB that booted. LILO was the only thing that worked for me after that. Something went wrong with mine a few months ago, and I've ended up in all kinds of other operating systems' LiveDVDs ever since. Even LiveDVD didn't work *for me* with Debian. There was some kind of a showstopping library issue. Was something like libunistring. Couldn't keep it up and running long enough to attempt a partition install. Other systems like Mint have somehow broken the EFI/UEFI roadblock when installed so I was taking a chance that maybe Debian could do the same thing. A partition is currently set up with Sid (Trixie?). It broke my heart when it didn't boot with GRUB, either. I've tried everything I can with it with the primary assault being to attempt to duplicate all GRUB packages that Mint uses to boot from a thumb drive. Sid with GRUB is getting one next to the last try before the last one is LILO. An email about EFI flew by me via Linux From Scratch the other day. I'm going to go poke around over there. Maybe there are some tips there that will finally push it over the edge to success. Doing exactly that helped me a couple years ago for something unrelated so I'm laying hope on it based on prior experience. :) Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: ps and AIX field descriptors
On 2023-02-17 at 13:21, debian-u...@howorth.org.uk wrote: > Greg Wooledge wrote: > >> This sounds like a bug in procps that should be reported, if it >> hasn't already. > > It might be a bug if it disagreed with its documentation. But do the > docs say anything about this feature? What they do say is that you > should be able to use comma-separated field decriptions instead of > space-separated I think. Is that true for the new version? I can't speak to the new version, as I'm still running 3.3.17-7.1 on my machine - but I can at least note that the man page from that older version also explicitly says "a blank-separated or comma-separated list" in the description for the '-o' option, but the given command line (with a pipe for a separator) still works. (This may reflect only the same thing that you said, above.) It's entirely possible that this was an intentional change, to bring things in line with the documentation, and/or even one required in order to be in line with some appropriate specification. It might be interesting to dig up the actual commit message from the upstream development commit that made this change, and possibly also any here's-what's-changed-in-the-new-version documentation (whether in Debian or upstream), to see whether there's anything that sheds light on whether this was intentional and if so what the reason was. The answer might, at least, inform the approach to be taken in arguing for the restoration of this functionality in a potential future version. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: xscreensaver fails to activate via "Preview" button or via "Blank after" setting
On Mon, 13 Feb 2023 09:28:23 -0800 Mike Kupfer wrote: > Celejar wrote: > > > I'm running Debian Sid with XFCE. Xscreensaver used to work, but a > > number of months ago, it broke badly: it now fails to fails to activate > > via the "Preview" button or (more importantly) via the "Blank after" > > setting. > > Thank you for bringing this up. I just noticed yesterday that > XScreensaver was not working with Xfce in my Bookworm VM, but I was too > busy to look into it. I could start it by hand after logging in, but > there was an autostart entry for it, so I expected it to already be > running. > > Have you verified that the daemon is running? (Does "pgrep > xscreensaver" produce anything?) It's running: ~$ ps ax | grep screensaver 2727 ?S 0:07 xscreensaver -no-splash 2813 ?S 0:00 xscreensaver-systemd 31876 pts/6S+ 0:00 grep screensaver > Prompted by your email, I added an Xfce autostart command to run > xscreensaver in verbose mode and with logging enabled. The log says > > xscreensaver: 09:09:49: running in process 4072 > xscreensaver: 09:09:49: "cinnamon-screensaver" is already running on > display :0.0 (window 0x121) > > By the time I could look at the log file, though, cinnamon-screensaver > was no longer running. > > The xscreensaver man page does say something about uninstalling other > screensavers. It's in the section "INSTALLING XSCREENSAVER ON GNOME OR > UNITY", but maybe it applies to other DEs? It does seem odd that > cinnamon-screensaver would get started in Xfce. Maybe this is some No cinnamon-screensaver here, as per the output shown above. > side-effect related to using systemd to start screensavers? > > Anyway, if you don't have any other screensavers installed in your VM, > try enabling logging and see if it tells you anything interesting. Thanks for the suggestion. The logs show regular deactivate events like the following every 20 seconds: ClientMessage DEACTIVATE: already inactive, resetting activity time I saw this: https://www.jwz.org/xscreensaver/faq.html#no-blank I guess I have to figure out what application is sending these messages? Firefox? I do tend to keep a lot of tabs open. Anyway, I've updated the bug log with this information: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014782#77 Thank you. -- Celejar
Re: snapd vs apt
On Fri, Feb 17, 2023 at 06:55:52PM +0100, Nicolas George wrote: > Anssi Saari (12023-02-17): > > Seconded. Specifically in the case of programming languages it may make > > sense to install a current version > > Hard disagree on that. You will be tempted to use the latest shiny > features that will be dropped in a few versions because the design was > flawed at its core. > > If you develop, and not just for yourself, then > make sure your developing environment is a Debian stable with only > packages from the main repository [...] When writing software for customers, that's exactly what I do. (Besides: I try to program against a library /documentation/, not a library). Debian stable is my "gold standard". Of course I test-build and test against testing, to have some idea of what's to come. I can't stand those "applications" (Ruby, Python, I'm looking at you) which have to run in some kind of "virtual environment". Cheers -- t signature.asc Description: PGP signature
Re: ps and AIX field descriptors
Greg Wooledge wrote: > This sounds like a bug in procps that should be reported, if it > hasn't already. It might be a bug if it disagreed with its documentation. But do the docs say anything about this feature? What they do say is that you should be able to use comma-separated field decriptions instead of space-separated I think. Is that true for the new version?
Re: snapd vs apt
Anssi Saari (12023-02-17): > Seconded. Specifically in the case of programming languages it may make > sense to install a current version Hard disagree on that. You will be tempted to use the latest shiny features that will be dropped in a few versions because the design was flawed at its core. If you develop, and not just for yourself, then make sure your developing environment is a Debian stable with only packages from the main repository or at least that your testing environment includes such a setup. You can make a tiny few exceptions for very important libraries, if you really must, but only if you install them from sources. Using the latest versions with easy packages might make your life easier, but it will also likely make your software suck. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Re : Re: [HS économie d'énerge] Gestion de l'Idle d'un processeur sous Debian
Bonjour, je pense que tu peux jeter un oeil sur la doc du noyau linux relatif à la gestion d'énergie (lire les pages qui sont en lien, particulièrement "Working-State Power Management", l'autre page "System-Wide Power Management" concernant en gros veille et hibernation) https://docs.kernel.org/admin-guide/pm/strategies.html (note, c'est de la doc en provenance d'Intel mais elle traite aussi des spécificités AMD)
Re: ps and AIX field descriptors
On Fri, Feb 17, 2023 at 09:20:34AM -0600, David Wright wrote: > On Fri 17 Feb 2023 at 10:05:20 (+0300), Reco wrote: > > So, to answer your question - currently the only way to restore the > > behaviour you want is to patch procps and rebuild it. Fabulous analysis. > Or, depending on the context, you could of course restore > the appearance of the output with sed: > > $ ps -eo '%p %C' | sed -e 's/\([^ ]\+\) /\1|/;' > PID|%CPU > 1| 0.0 > 2| 0.0 > 3| 0.0 > 4| 0.0 > 6| 0.0 > [ … ] Eww, GNUisms. That aside, a workaround like this is ugly and should not be needed. This sounds like a bug in procps that should be reported, if it hasn't already.
Re: snapd vs apt
Brian writes: > On Fri 17 Feb 2023 at 05:55:03 +0800, winnie hw wrote: > >> Most versions in snapd are newer than apt. such as ruby, >> >> snap install ruby # version 3.2.1, or >> apt install ruby # version 1:3.0~exp1 > > I cannot better the existing very informative replies. > It comes down to what you want to achieve. Seconded. Specifically in the case of programming languages it may make sense to install a current version and they sometimes provide a convenient way to install from source. Personally I've used Rustup to install current Rust and pyenv to install current Python. Haven't used snaps for a short trial with Firefox but since it didn't work I dumped it. Pyenv especially is pretty neat since it makes easy to install and run different versions of Python. I do wonder about those versions though. Ruby version 1:3.0~exp1??? Doesn't seem to be the current version for any Debian.
Re: lpr hangs on emojis
On 17/02/2023 00:46, Greg Marks wrote: When trying to print a file that contains emojis with the lpr command, not only do the emojis not print, nothing following the first non-printing emoji prints. (This makes it a hassle to print certain e-mails piped to lpr using mutt.) As a small example, after entering the command: echo -e "Hello\n\0360\0237\0230\0212\nGoodbye" > /tmp/test.txt && cat /tmp/test.txt && lpr /tmp/test.txt only the first of the three lines prints. I find it highely unlikely that the printer understands UTF-8, let alone that its built-in fonts contains emoji. Maybe it supports the whole ISO-8859-1 character set, but probably only ASCII. It might be trying to interpret the non-ASCII codes as control sequences, or it just doesn't know what to do with them. Does anyone have a good way of printing text that contains emojis? You can convert it to PDF. Or open the file in word processor and print from there. Even if it's just plain text, it'll be converted to a format that the printer understands, including extra fonts. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: ps and AIX field descriptors
On Fri 17 Feb 2023 at 10:05:20 (+0300), Reco wrote:
> On Fri, Feb 17, 2023 at 07:46:23AM +0100, Andreas Leha wrote:
> > Now my question: How can I restore the previous behaviour that allowed
> > other than whitespace separators between fields?
>
> diff -purw procps-3.3.17/ps/sortformat.c procps-4.0.2/src/ps/sortformat.c
> shows me that:
>
> @@ -128,22 +127,24 @@ static const char *aix_format_parse(sf_n
>items = 0;
>walk = sfn->sf;
>/* state machine */ {
> - int c;
> + int c = *walk++;
>initial:
> -c = *walk++;
> if(c=='%')goto get_desc;
> if(!c)goto looks_ok;
>/* get_text: */
> items++;
> - get_more_text:
> + get_more:
> c = *walk++;
> if(c=='%')goto get_desc;
> -if(c) goto get_more_text;
> +if(c==' ')goto get_more;
> +if(c) goto aix_oops;
> goto looks_ok;
>get_desc:
> items++;
> c = *walk++;
> -if(c) goto initial;
> +if(c&!=' ') goto initial;
> +return _("missing AIX field descriptor");
> + aix_oops:
> return _("improper AIX field descriptor");
>looks_ok:
> ;
>
> If you look at "get_more" label, you'll notice that "old" version of
> procps (bullseye's) checked for any character after "%" block.
> "New" one (bookworm's) explicitly checks for space, and goes to
> "aix_oops" in any other case.
>
> And there is no #ifdefs, no environment variable checks, no options
> etc.
>
> So, to answer your question - currently the only way to restore the
> behaviour you want is to patch procps and rebuild it.
Or, depending on the context, you could of course restore
the appearance of the output with sed:
$ ps -eo '%p %C' | sed -e 's/\([^ ]\+\) /\1|/;'
PID|%CPU
1| 0.0
2| 0.0
3| 0.0
4| 0.0
6| 0.0
[ … ]
Cheers,
David.
Re: lpr hangs on emojis
On 2/16/23 22:46, Greg Marks wrote: When trying to print a file that contains emojis with the lpr command, not only do the emojis not print, nothing following the first non-printing emoji prints. (This makes it a hassle to print certain e-mails piped to lpr using mutt.) As a small example, after entering the command: echo -e "Hello\n\0360\0237\0230\0212\nGoodbye" > /tmp/test.txt && cat /tmp/test.txt && lpr /tmp/test.txt only the first of the three lines prints. One way to at least get all of the text to print is to use pango to convert from UTF-8 to PostScript: cat /tmp/test.txt | paps --paper=letter > /tmp/test.ps && lpr /tmp/test.ps Apart from such commands being a bit unwieldy when trying to print e-mails, it's typically only apparent that an emoji is interfering with lpr when most of the file doesn't print. Also, if the emoji is actually intended to communicate something, it would be nice if it appeared on the printed page. It seems that the enscript command works a bit better than lpr here; the entire file prints along with the octal codes for the included non-printing characters. So there is at least an indication that there is some other character in the text that one might be inclined to go back to the computer screen to view. Does anyone have a good way of printing text that contains emojis? The issue might be with CUPS texttopdf filter: https://github.com/OpenPrinting/cups-filters/issues/254 -- Sarunas Burdulis Dartmouth Mathematics math.dartmouth.edu/~sarunas · https://useplaintext.email · OpenPGP_signature Description: OpenPGP digital signature
Re: CUPS - how to match autodetected printers to physical ones
On Fri 17 Feb 2023 at 09:05:39 -0500, Greg Wooledge wrote: > On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote: [...] > > avahi-browse -rt _ipp._tcp > > avahi-browse -rt _uscan._tcp > > > > (I would find that data useful for my records). > > wooledg:~$ avahi-browse -rt _ipp._tcp 2>&1 | grep -A5 db:c0:d3 > + eno1 IPv4 Canon LBP712Cdn (db:c0:d3)Internet Printer >local > + eno1 IPv4 HP LaserJet P3010 Series [0FCDD7] Internet Printer >local > + eno1 IPv4 hp LaserJet 4250 [621E13] Internet Printer >local > = eno1 IPv4 Canon LBP712Cdn (db:c0:d3)Internet Printer >local >hostname = [dhcp-10-76-173-174.local] >address = [10.76.173.174] >port = [631] >txt = ["mopria-certified=1.2" "print_wfds=T" > "kind=document,envelope,postcard" > "URF=ADOBERGB24,CP255,DM1,FN3,IS1-4,OB10,PQ4,RS300,SRGB24,V1.4,W8-16" "Fax=F" > "Scan=F" "TLS=1.2" "usb_CMD=LIPSLX" > "UUID=15904ba4-fe8c-3bee-5d53-cb5f72ea86b2" "PaperMax=legal-A4" "Punch=0" > "Staple=F" "Sort=T" "Collate=T" "Bind=F" "PaperCustom=T" "Duplex=T" > "Copies=T" "Color=T" "TBCP=F" "Binary=F" "Transparent=F" "usb_MDL=LBP712C UFR > II" "usb_MFG=Canon" "adminurl=https://dhcp-10-76-173-174.local/airprint.html; > "pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf" > "product=(CNLBP712C)" "ty=Canon LBP712C" "priority=10" "qtotal=1" "note=" > "rp=ipp/print" "txtvers=1"] > = eno1 IPv4 hp LaserJet 4250 [621E13] Internet Printer >local Assuming the machine at 10.76.172.100 is identical with this one at 10.76.173.174, it too will have a TXT record with pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf A PDF sent directly to it should print if an open port 9100 exists on the printer: netcat 10.76.172.100 9100 < taxform.pdf > wooledg:~$ time avahi-browse -rt _uscan._tcp > real 1.023 user 0.004 sys 0.004 > > (No other output.) No prolem here. The LBP712Cdn does not have a scanner. It looks like mdns multcasting has been disabled on the printer at 10.76.172.100. This is unfortunate and unnecessary. Perhaps someone should inform your helpful Help Desk that its Bonjour name can be changed to distinguish it from similare devices on the network. -- Brian.
Re: CUPS - how to match autodetected printers to physical ones
Hi. On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote: > So the printer WORKS. It is ON THE NETWORK. I can print TEXT to it > using port 9100. > > What I CANNOT do is find it in CUPS. Or avahi-browse, or driverless, or > any of these other commands that are so allegedly wonderful. > > Is there any way I can tell CUPS "Please set up a queue for a printer > whose IP address is 10.76.172.100 even though you can't discover it with > your fancy tools"? Try this next time you're on site: lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere Reco
Re: hard disk installation method fails
On Fri 17 Feb 2023 at 05:13:34 +0800, lsg wrote: > this is quite unbelievable, it's most widely-used platform: amd64 > > installer says "No kernel modules found", probably due to kernel mismatch > > debian-11.6.0-amd64-netinst.iso is at sdb1, vfat partition, i've checked it > with sha256sum > > vmlinuz and initrd.gz are copied from: > > http://ftp.sunet.se/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/ There isn't much you can do about this. It is usually a temporary issue thats happens after Linux kernel updates. The installer is now out of step. It gets automatically fixed after some time. -- Brian.
Re: CUPS - how to match autodetected printers to physical ones
On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote: > On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote: > > > wooledg:~$ cat /etc/debian_version > > 11.6 > > wooledg:~$ lpstat -l -e > > Canon_LBP712C_UFR_II_ permanent > > ipp://localhost/printers/Canon_LBP712C_UFR_II_ > > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ > > This is a print queue, set up using Canon drivers. > > > Canon_LBP712Cdn_db_c0_d3_ network none > > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ > > This is not a print queue. CUPS has discovered the printer via > mdns/DNS-SD and enumetated it. It should be seen with > > avahi-browse -rt _ipp._tcp > avahi-browse -rt _uscan._tcp > > (I would find that data useful for my records). wooledg:~$ avahi-browse -rt _ipp._tcp 2>&1 | grep -A5 db:c0:d3 + eno1 IPv4 Canon LBP712Cdn (db:c0:d3)Internet Printer local + eno1 IPv4 HP LaserJet P3010 Series [0FCDD7] Internet Printer local + eno1 IPv4 hp LaserJet 4250 [621E13] Internet Printer local = eno1 IPv4 Canon LBP712Cdn (db:c0:d3)Internet Printer local hostname = [dhcp-10-76-173-174.local] address = [10.76.173.174] port = [631] txt = ["mopria-certified=1.2" "print_wfds=T" "kind=document,envelope,postcard" "URF=ADOBERGB24,CP255,DM1,FN3,IS1-4,OB10,PQ4,RS300,SRGB24,V1.4,W8-16" "Fax=F" "Scan=F" "TLS=1.2" "usb_CMD=LIPSLX" "UUID=15904ba4-fe8c-3bee-5d53-cb5f72ea86b2" "PaperMax=legal-A4" "Punch=0" "Staple=F" "Sort=T" "Collate=T" "Bind=F" "PaperCustom=T" "Duplex=T" "Copies=T" "Color=T" "TBCP=F" "Binary=F" "Transparent=F" "usb_MDL=LBP712C UFR II" "usb_MFG=Canon" "adminurl=https://dhcp-10-76-173-174.local/airprint.html; "pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf" "product=(CNLBP712C)" "ty=Canon LBP712C" "priority=10" "qtotal=1" "note=" "rp=ipp/print" "txtvers=1"] = eno1 IPv4 hp LaserJet 4250 [621E13] Internet Printer local wooledg:~$ time avahi-browse -rt _uscan._tcp real 1.023 user 0.004 sys 0.004 (No other output.) > Its URI will be > > ipp://10.76.172.100/ipp/print > > Execute > > lpadmin -p mycanonprinter -v URI -E -m everywhere > > Test printing with > > lp -d mycanonprinter /etc/nsswitch.conf Any physical tests will have to wait, at least a week. Oh, one other thing in case you were confused: the netmask there is /23 not /24. 10.76.172.x and 10.76.173.x are both on that subnet. Each subnet is assigned to one physical floor of a building. That particular subnet covers the 10th floor of building S, which is... not an enormous space, but not small either. At full capacity, there could be a few dozen people working there, and the space is divided into separate sections, each behind its own locked door(s).
Re : Re: [HS économie d'énerge] Gestion de l'Idle d'un processeur sous Debian
Le vendredi 17 février 2023 à 10:40, Basile Starynkevitch a écrit : > La consommation du processeur n'est pas la consommation totale d'un > ordinateur de bureau, dont les ventilateurs consomment, dont l'alimentation > consomment, dont la carte mère consomme, dont l'écran consomme (même pour un > Debian qui est booté, mais ne fait rien, par exemple parce que son > utilisateur est parti prendre un café). Je suis bien d'accord, mais il faut bien commencer quelque part, puis, vient la question du choix du chipset, de la carte mère, de l’alim, de l’écran… En lisant ta réponse j’ai l’impression que je ne pose pas la question dans le bon ordre. Par exemple, dans l’amélioration de la performance énergétique des bâtiments existant, on commence par la toiture. Peut-être que je ne suis pas le bon ordre en commençant par le CPU ? > Peut-être, tout dépend d'une définition de PC de bureau qui ne consomme > presque rien! > >> Genre 1 ou 2 W pour le CPU en idle comme l'indique le la personne qui a posé sur le forum Pour le reste, j'explore le sujet. > Mais la question est curieuse. Le chauffage du bureau (pièce ou chambre où se > trouve l'ordinateur), le coût de sa location ou de son amortissement consomme > probablement plus d'énergie (si on compte le coût en € par jour) que > l'ordinateur. Et l'amortissement du coût à l'achat de l'ordinateur de bureau > (souvent > 600€, amorti sur 4 ans) devrait être aussi prise en compte. Et le > salaire de son utilisateur Le chauffage du bureau (pièce ou chambre où se trouve l'ordinateur), est très bien documenté, on y décrit en détail les dispositions à prendre dans la conception d'un bâtiment bioclimatique ou l'amélioration d'un existant, dans lequel il fait naturellement frais en été sans clim et chaud en hiver avec très peu de chauffage. Si j'avais trouvé autant d'info sur l'optimisation énergétique d'un PC de bureau sous GNU/Linux, je serais comblé et j'aurais déjà fait des expériences. ;-) -- Benoit
Re: snapd vs apt
On Fri 17 Feb 2023 at 05:55:03 +0800, winnie hw wrote: > Most versions in snapd are newer than apt. such as ruby, > > snap install ruby # version 3.2.1, or > apt install ruby # version 1:3.0~exp1 I cannot better the existing very informative replies. It comes down to what you want to achieve. -- Brian.
Re: CUPS - how to match autodetected printers to physical ones
On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote: > wooledg:~$ cat /etc/debian_version > 11.6 > wooledg:~$ lpstat -l -e > Canon_LBP712C_UFR_II_ permanent > ipp://localhost/printers/Canon_LBP712C_UFR_II_ > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ This is a print queue, set up using Canon drivers. > Canon_LBP712Cdn_db_c0_d3_ network none > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ This is not a print queue. CUPS has discovered the printer via mdns/DNS-SD and enumetated it. It should be seen with avahi-browse -rt _ipp._tcp avahi-browse -rt _uscan._tcp (I would find that data useful for my records). It can be printed to with lp -d "Canon_LBP712Cdn_db_c0_d3_" FILE Where the job physically ends up is outside the scope of CUPS. Let's assume the printer you ar interested in is not being multicast. It exists at 10.76.172.100. Let us guess that the resource to access on the printer is ipp/print. This is a pretty good guess because most vendors use it nowadays. Its URI will be ipp://10.76.172.100/ipp/print Execute lpadmin -p mycanonprinter -v URI -E -m everywhere Test printing with lp -d mycanonprinter /etc/nsswitch.conf -- Brian.
Re: Debian Nordic 2022 & 2023 -- Wiki Updated & Matrix Server Move
Removed foss-north 2023 from the Wiki (as i won't have the money) this year to host something Debian related, but if someone else wants to do it feel free to do so On 2/15/23, Luna Jernberg wrote: > Hey! > > Won't go to foss-north 2023 myself this year, got other things to do > that also costs money so sadly can't afford it this year > > On 1/16/23, Petter Reinholdtsen wrote: >> [Luna Jernberg] >>> Hello Debian friends! >>> >>> The Community day for foss-north 2023: https://foss-north.se/2023/ has >>> been announced and is decided to be on Sunday 23th April 2023 in >>> Gothenburg. Any Debian people in the Nordics that want to do anything >>> then? as i did talk about last year or not? >> >> Look like a nice opportunity. I'll see if I can interest some of the >> Norwegian communities. >> >> -- >> Happy hacking >> Petter Reinholdtsen >> >
Re: Debian Nordic 2022 & 2023 -- Wiki Updated & Matrix Server Move
Removed foss-north 2023 from the Wiki (as i won't have the money) this year to host something Debian related, but if someone else wants to do it feel free to do so On 2/15/23, Luna Jernberg wrote: > Hey! > > Won't go to foss-north 2023 myself this year, got other things to do > that also costs money so sadly can't afford it this year > > On 1/16/23, Petter Reinholdtsen wrote: >> [Luna Jernberg] >>> Hello Debian friends! >>> >>> The Community day for foss-north 2023: https://foss-north.se/2023/ has >>> been announced and is decided to be on Sunday 23th April 2023 in >>> Gothenburg. Any Debian people in the Nordics that want to do anything >>> then? as i did talk about last year or not? >> >> Look like a nice opportunity. I'll see if I can interest some of the >> Norwegian communities. >> >> -- >> Happy hacking >> Petter Reinholdtsen >> >
Re: [HS économie d'énerge] Gestion de l'Idle d'un processeur sous Debian
On 17/02/2023 10:09, benoit wrote: Bonjour, Est-il vrai, comme indiqué ci dessous, qu'un processeur (ordinateur allumé qui ne fait rien) en Idle ne consomme que 1 ou 2W ? Traduction : «N'importe quel processeur moderne avec GPU intégré fera l'affaire, vous devrez également vous assurer que la carte mère utilise un minimum d'énergie. Tant que vous disposez d'un support pour les états de sommeil et qu'il n'y a pas de dGPU dans le système pour limiter les états de sommeil plus profonds pour l'ensemble également, n'importe quel CPU Intel à partir de Haswell tournera au ralenti à 1-2W. Cf. https://forums.anandtech.com/threads/cpu-with-low-idle-power-consumption-recommendation.2562703/ La consommation du processeur n'est pas la consommation totale d'un ordinateur de bureau, dont les ventilateurs consomment, dont l'alimentation consomment, dont la carte mère consomme, dont l'écran consomme (même pour un Debian qui est booté, mais ne fait rien, par exemple parce que son utilisateur est parti prendre un café). Si c'est vrai, comment on fait sous Debian pour activer une gestion si pointue de l'économie d'énergie sur un ordinateur de bureau ? Parce que ce qui est important pour économiser, l'énergie, vu que les cœurs passent la majorité du temps à ne rien faire quand on tape du texte, c'est ce que le système consomme à ne rien faire. Le TDP de plus de 100W indiqué pour la plupart de processeurs de bureau, c'est quand tous les cœurs sont à 100% ? Oui, et quand la carte graphique et les disques sont aussi sollicités Suffirait-il d'opter pour une alim 80 PLUS (Gold et supérieure) et un GPU intégré au CPU pour avoir un PC de bureau qui ne consomme presque rien ? Peut-être, tout dépend d'une définition de /PC de bureau qui ne consomme presque rien/! Merci d'avance, -- Benoît Ps. Quand je compile avec make -j1 pour n'avoir qu'un job et que j'affiche l'activité des cœurs on dirait que la job se balade d'un cœur à l'autre qui passe de 0 à 100% d'activité. Oui, c'est le rôle du noyau et du firmware dans le processeur. Je crois que la raison est thermique au niveau de la puce CPU elle-même. Mais la question est curieuse. Le chauffage du bureau (pièce ou chambre où se trouve l'ordinateur), le coût de sa location ou de son amortissement consomme probablement plus d'énergie (si on compte le coût en € par jour) que l'ordinateur. Et l'amortissement du coût à l'achat de l'ordinateur de bureau (souvent > 600€, amorti sur 4 ans) devrait être aussi prise en compte. Et le salaire de son utilisateur. Pour en avoir le coeur net, il faudrait investir (quelques dizaines d'euros) dans un wattmètre. https://www.amazon.fr/Multim%C3%A8tre-Wattm%C3%A8tre-Num%C3%A9rique-Fonctions-Equipements/dp/B07M8JL7HX Librement -- Basile Starynkevitch (only mine opinions / les opinions sont miennes uniquement) 92340 Bourg-la-Reine, France web page: starynkevitch.net/Basile/
Firmowe auto - termin rozmowy
Dzień dobry, czy używane przez Państwa samochody firmowe generują coraz wyższe koszty? Rosnące ceny paliw i utrzymanie firmowych aut to problemy, z jakimi w ostatnim czasie zgłasza się do nas wielu przedsiębiorców. Proste w obsłudze narzędzie pozwoli Państwu zoptymalizować koszty i osiągnąć większą efektywność, dzięki zintegrowaniu danych za pomocą nowych technologii. Z chęcią zadzwonię, aby omówić możliwe do osiągnięcia rezultaty. Jaki termin na krótką rozmowę będzie odpowiedni? Pozdrawiam, Wojciech Wierzba
[HS économie d'énerge] Gestion de l'Idle d'un processeur sous Debain
Bonjour, Est-il vrai, comme indiqué ci dessous, qu'un processeur (ordinateur allumé qui ne fait rien) en Idle ne consomme que 1 ou 2W ? Traduction : «N'importe quel processeur moderne avec GPU intégré fera l'affaire, vous devrez également vous assurer que la carte mère utilise un minimum d'énergie. Tant que vous disposez d'un support pour les états de sommeil et qu'il n'y a pas de dGPU dans le système pour limiter les états de sommeil plus profonds pour l'ensemble également, n'importe quel CPU Intel à partir de Haswell tournera au ralenti à 1-2W. Cf. https://forums.anandtech.com/threads/cpu-with-low-idle-power-consumption-recommendation.2562703/ Si c'est vrai, comment on fait sous Debian pour activer une gestion si pointue de l'économie d'énergie sur un ordinateur de bureau ? Parce que ce qui est important pour économiser, l'énergie, vu que les cœurs passent la majorité du temps à ne rien faire quand on tape du texte, c'est ce que le système consomme à ne rien faire. Le TDP de plus de 100W indiqué pour la plupart de processeurs de bureau, c'est quand tous les cœurs sont à 100% ? Suffirait-il d'opter pour une alim 80 PLUS (Gold et supérieure) et un GPU intégré au CPU pour avoir un PC de bureau qui ne consomme presque rien ? Merci d'avance, -- Benoît Ps.Quand je compile avec make -j1 pour n'avoir qu'un job et que j'affiche l'activité des cœurs on dirait que la job se balade d'un cœur à l'autre qui passe de 0 à 100% d'activité.
