Re: Q: Gnome network odd

2024-02-01 Thread Tixy
On Wed, 2024-01-31 at 22:12 -0600, David Wright wrote:
> > I also have a more vague memory that you could put config into
> > /etc/network/interfaces then in some circumstance NetworkManager
> > would
> > not try and manage that interface, and in others it would take
> > over.
> > (Perhaps selected by allow hotplug option in the ifupdown config?)
> 
> That seems unlikely. Perhaps you're thinking of NM's ifupdown plugin
> that allows you to use the configuration in /e/n/i. I'm assuming the
> OP has not installed that in their sleep.

They wouldn't need to because it looks like it's shipped with the main
network-manage package which contains various files with 'plugin' in
their name, including libnm-settings-plugin-ifupdown.so.

As we've seen from the OPs latest reply, the plugin is configured to
not manage interfaces.

-- 
Tixy



Re: Debian/Xen on ARM: How to identify source of an unhandled SMC call during boot?

2024-01-31 Thread Tixy
On Wed, 2024-01-31 at 21:59 +0100, hw wrote:
> On Wed, 2024-01-31 at 08:02 +0100, Paul Leiber wrote:
> > Am 25.01.2024 um 22:28 schrieb Paul Leiber:
> > [...]
> > > Some people on xen-devel pointed out to me two unhandled SMC calls in 
> > > the boot logs which could be the root of the problem. I am now trying to 
> > > find out where these calls come from to get closer to the root cause. 
> > > The suspected calls are the following ones:
> > > 
> > > (XEN) d0v0 Unhandled SMC/HVC: 0x8450
> > > (XEN) d0v0 Unhandled SMC/HVC: 0x8600ff01
> > > 
> > > These calls happen during the Dom0 boot process, so it's something from 
> > > inside Linux and nothing Xen related, I've been told. The current 
> > > working hypothesis is that the calls are trying to find some module not 
> > > emulated by Xen and are therefore failing, leading to Linux waiting for 
> > > the reply, and subsequently to the Xen watchdog triggering and rebooting.
> > > 
> > >  From what I could find out in ARM documentation, the unhandled SMC 
> > > calls probably have the following purpose:
> > > 
> > > 0x8450 = TRNG_VERSION, returns the implemented TRNG (True Random 
> > > Number Generator) ABI version [2]
> > > 0x8600ff01 = Call UID Query for Vendor Specific Hypervisor Service, 
> > > Returns a unique identifier of the service provider [3]
> > > 
> > > The more likely cause is the second call to the address 0x8600ff01.
> > > 
> > > Now I simply have no idea how to find out where in the Linux boot 
> > > process these calls are made. I tried poking into the Linux sources a 
> > > bit, and I couldn't find an exact match for these call addresses, so I 
> > > assume these addresses are assembled from different parts. There are 
> > > some matches for "0x8600" and for "ff01", but I couldn't identify if 
> > > these matches are relevant.
> > > 
> > > I tried to find out if strace could help, but from what I understand, 
> > > this is related to commands coming from userspace, so I am not sure that 
> > > strace helps during the boot process.
> > > 
> > > I'd appreciate it if somebody more knowledgeable would point me in the 
> > > right direction. If more information is needed, I can provide it.
> 
> I would search for the message 'Unhandled SMC/HVC' itself, or even for
> 'Unhandled', not for the address.  The address is probably determined
> at runtime and not hardcoded.

I sure those hex values aren't 'addresses' but the ID's for the secure
monitor calls Paul already identified.

Looking at the Linux sources I found the header for constructing these
monitor calls: include/linux/arm-smccc.h

So it might be worth looking at the files that include that. There are
various drivers for firmware, and a watchdog driver amongst other
things... drivers/watchdog/arm_smc_wdt.c

-- 
Tixy



Re: Q: Gnome network odd

2024-01-29 Thread Tixy
On Mon, 2024-01-29 at 23:49 -0600, David Wright wrote:
> I would tend to think that:
> 
> . The debian-installer installs ifupdown by default when you don't
>   install a Desktop Manager like Gnome,
> 
> . The debian-installer installs NetworkManager by default if you do
>   install a Desktop Manager like Gnome,
> 
> . It shouldn't do both.
> 

My experience, admittedly from a few releases ago, is that ifupdown is
always installed but that the installer doesn't populate it's config
files with the found network interfaces, only the loopback interface.

I also have a more vague memory that you could put config into
/etc/network/interfaces then in some circumstance NetworkManager would
not try and manage that interface, and in others it would take over.
(Perhaps selected by allow hotplug option in the ifupdown config?)

-- 
Tixy



Re: Home UPS recommendations

2024-01-26 Thread Tixy
On Fri, 2024-01-26 at 15:37 +, Michael Kjörling wrote:
> On 26 Jan 2024 15:17 +, from a...@strugglers.net (Andy Smith):
> > Out of interest what brand of UPS do you recommend for home use that
> > has easily-replaceable batteries every 3–5 years? For a load of
> > about 300W.
> 
> I would suggest to look at the free-standing floor-/tower-model APC
> _Back-UPS Pro_ series.

I have had a couple of those, never had any problems with them. Though
replacement batteries cost more than half the price of a new UPS so I
ended up just buying a a second UPS when the original batteries got
rather feeble. (After 7 years).

I've now stopped using it though because of the cost of the electricity
it uses. It uses 18W when just sitting there ready for action, which 
worked out at 40GBP a year!

-- 
Tixy



Re: SOLVED: Re: Chromium oops: libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so

2024-01-23 Thread Tixy
On Tue, 2024-01-23 at 13:34 -0700, Charles Curley wrote:
> I went to shut down the machine, and it got stuck trying to shut down
> wpa_supplicant and Network Manager. Ten minutes into the shutdown, I
> finally pulled the plug. A few reboots and shutdowns later, I decided
> to try another kernel. I had recently installed Bookworm from the 12.0
> netinst CD image, so I had the 12.0 kernel, linux-image-6.1.0-9-amd64,
> 6.1.27-1, as my fall-back kernel. I rebooted to that, and was able to
> shut down and boot in quick order.
> 
> So I purged the newer kernel, inux-image-6.1.0-15-amd64, leaving the
> older one in place.

As you've already found out, that's not the latest one, and if I'm not
mistaken is the one that introduce a wifi bug [1], so that could
explain it getting stuck in the wifi stuff during shutdown.

You would probably be OK with the latest Debian 6.1 kernel if you don't
explicitly want the 6.5 one from backports.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057969

-- 
Tixy



Re: No Release file for Security Update

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 18:51 +, Tixy wrote:
> > On Thu, 2024-01-18 at 18:16 +, Tixy wrote:
> > > > On Thu, 2024-01-18 at 12:06 -0600, John Hasler wrote:
> > > > > > Tixy writes:
> > > > > > > > Where could your machine be getting this IP address from?  It's 
> > > > > > > > the
> > > > > > > > same IP address shown in your output when you used the incorrect
> > > > > > > > address 'ftp.security.debian.org' and for me that doesn't 
> > > > > > > > resolve to
> > > > > > > > any IP address.
> > > > > > 
> > > > > > > > From here both security.debian.org and ftp.security.debian.org 
> > > > > > > > resolve
> > > > > > to 57.128.81.193.  Happens both with Unbound and with 8.8.8.8.
> > > > > > 
> > > > > > toncho/~ 22 dig  ftp.security-debian.org
> > > > 
> > > > That's a different address (you're using a '-') and works for me too.
> > > > 
> > > > I was using the address that George _said_ he used in his email,
> > > > obviously he was wrong and just mis-typing emails rather than copy and
> > > > pasting in what he was actually using :-(
> > 
> > Of course you're also guilty John ;-) saying 'ftp.security.debian.org'
> > resolved, but at least you pasted a command showing what you really
> > used :-)

And now you can all point out that it was me that was misquoting the
address and using a dot where in fact everyone else was using a hyphen
in 'debian-security'. I'll now slink away red faced and try and find a
hole big enough to crawl into...

-- 
Tixy



Re: No Release file for Security Update

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 18:16 +, Tixy wrote:
> On Thu, 2024-01-18 at 12:06 -0600, John Hasler wrote:
> > Tixy writes:
> > > Where could your machine be getting this IP address from?  It's the
> > > same IP address shown in your output when you used the incorrect
> > > address 'ftp.security.debian.org' and for me that doesn't resolve to
> > > any IP address.
> > 
> > > From here both security.debian.org and ftp.security.debian.org resolve
> > to 57.128.81.193.  Happens both with Unbound and with 8.8.8.8.
> > 
> > toncho/~ 22 dig  ftp.security-debian.org
> 
> That's a different address (you're using a '-') and works for me too.
> 
> I was using the address that George _said_ he used in his email,
> obviously he was wrong and just mis-typing emails rather than copy and
> pasting in what he was actually using :-(

Of course you're also guilty John ;-) saying 'ftp.security.debian.org'
resolved, but at least you pasted a command showing what you really
used :-)

-- 
Tixy



Re: No Release file for Security Update

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 12:06 -0600, John Hasler wrote:
> Tixy writes:
> > Where could your machine be getting this IP address from?  It's the
> > same IP address shown in your output when you used the incorrect
> > address 'ftp.security.debian.org' and for me that doesn't resolve to
> > any IP address.
> 
> > From here both security.debian.org and ftp.security.debian.org resolve
> to 57.128.81.193.  Happens both with Unbound and with 8.8.8.8.
> 
> toncho/~ 22 dig  ftp.security-debian.org

That's a different address (you're using a '-') and works for me too.

I was using the address that George _said_ he used in his email,
obviously he was wrong and just mis-typing emails rather than copy and
pasting in what he was actually using :-(

-- 
Tixy



Re: No Release file for Security Update

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 10:48 -0500, Thomas George wrote:
> On 1/17/24 20:52, Greg Wooledge wrote:
> > On Wed, Jan 17, 2024 at 08:40:58PM -0500, Thomas George wrote:
> > > deb http://ftp.security-debian.org/debian-security/ bookworm-security main
> > > non-free non-free-firmware
> > Stop guessing, and *read* what you were told to use.
> > 
> > https://lists.debian.org/debian-user/2024/01/msg00778.html
> > 
> >  Your source is incorrect. The security repo is at
> >  "http://security.debian.org/debian-security;;.
> > 
> > There are other lines that also work, but you can't just guess randomly
> > until you stumble across one.  Read a trusted source, and copy what
> > they tell you to use.  Don't put "ftp." in front of things that don't
> > need it.
> I typed the above line exactly. apt-get update searches for 
> security.debian.org:80 [57.128.81.193] and times out, no connection

Where could your machine be getting this IP address from?
It's the same IP address shown in your output when you used the
incorrect address 'ftp.security.debian.org' and for me that doesn't
resolve to any IP address.

-- 
Tixy



Re: nftables: Clamping mss size to lower mtu (on PPPoE connection does not work)

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 14:16 +0100, Ralph Aichinger wrote:
> On Thu, 2024-01-18 at 12:51 +0000, Tixy wrote:
> > 
> > I have the same options in the forward chain except that I haven't
> > qualified them with an interface name. Didn't occur to me that I
> > would
> > need to do that as there are only two networks my LAN and 'the
> > internet'.
> 
> You probably don't need to, I just copied the example from the nftables
> wiki. For my setup it might in theory make a difference because maybe
> it could interfere with the use of jumbo frames on my lan,

I'm not a network expert, but surely machines on your LAN are sending
packets direct to each other, not using this machine as a gateway?
Isn't that what the sub-net mask about? Identifying IP addresses that
are directly accessible and for any other addresses packets are sent to
the 'gateway'.

>  but as the
> machine in question is a lowly Rasbperry Pi 4, it is a rather
> theoretical aspect.

Not as lowly as my SheevPlug ;-) Though to be fair, the SoC's inbuilt
ethernet and SATA devices do make it good for the use-cases it was
designed for, e.g. a NAS, or router.

-- 
Tixy



Re: nftables: Clamping mss size to lower mtu (on PPPoE connection does not work)

2024-01-18 Thread Tixy
On Thu, 2024-01-18 at 12:31 +0100, Ralph Aichinger wrote:
[...]
> So it seems clamping the mss on the NAT/PPPoE-Machine running Debian no
> longer works. For this I use/used the follwing rules:
> 
> iifname "ppp0" tcp flags syn tcp option maxseg size set rt mtu;
> oifname "ppp0" tcp flags syn tcp option maxseg size set rt mtu;
> 
> setting a specific mtu as a constant instead of "rt mtu" does not help
> either.

I have the same options in the forward chain except that I haven't
qualified them with an interface name. Didn't occur to me that I would
need to do that as there are only two networks my LAN and 'the
internet'.

In case it helps, my complete forward chain is below. From the comments
with links to Stack Exchange it's obvious I hit the MTU size problem
and had to fix it...

chain forward {
type filter hook forward priority 0; policy drop;

# Count packets
iifname $DEV_PRIVATE counter name cnt_forward_out
iifname $DEV_WORLD counter name cnt_forward_in

# Allow traffic from established and related packets, drop invalid
ct state vmap { established : accept, related : accept, invalid : drop }

# Fix some sites not working correctly by hacking MTU size
# See 
https://unix.stackexchange.com/questions/658952/router-with-nftables-doesnt-work-well
# Also 
https://unix.stackexchange.com/questions/672742/why-mss-clamping-in-iptables-nft-seems-to-take-no-effect-in-nftables
tcp flags syn tcp option maxseg size set rt mtu

# connections from the internal net to the internet or to other
# internal nets are allowed
iifname $DEV_PRIVATE accept

    # the rest is dropped by the above policy
}

-- 
Tixy



Re: man page for cut

2024-01-17 Thread Tixy
On Wed, 2024-01-17 at 17:26 +, Richmond wrote:
> In the man page for cut it says:
> 
>  -b, --bytes=LIST
>   select only these bytes
> 
> But there is no equals sign in the actual syntax:
> 
> echo hello|cut -b 2-5
> ello
> 
> echo hello|cut -b=2-5
> cut: invalid byte/character position ‘=2-5’
> Try 'cut --help' for more information.
> 
> Why is this?
> 

The equals sign only applies to the 'long form' of the option...

$echo hello|cut --bytes=2-5
ello

This is standard behaviour for a lot of utilities.

A hyphen and single letter is the 'short form' and there is an optional
space between the letter and it's arguments.

A double hyphen and and option name has an '=' separating it from and
arguments.

For the short form, you can often (usually?) merge multiple option
letters and any argument at the end applies to the last option letter.

$echo hello|cut -zb2-5
ello$

(the 'z' option says use NUL byte for line terminator so in this case
it didn't output the newline and my '$' command prompt got printed
straight after the 'ello'.

-- 
Tixy



Re: How to prevent rtkit from giving firefox higher priority?

2024-01-17 Thread Tixy
On Wed, 2024-01-17 at 11:19 +0100, hw wrote:
> On Tue, 2024-01-16 at 08:41 -0500, Greg Wooledge wrote:
> > On Tue, Jan 16, 2024 at 02:17:05PM +0100, hw wrote:
> > > On Tue, 2024-01-16 at 08:03 -0500, Greg Wooledge wrote:
> > > > On Tue, Jan 16, 2024 at 01:43:23PM +0100, hw wrote:
> > > > > There's only a bunch of links in that directory, apparently all
> > > > > pointing to files that don't exist.  Don't you have that?
> > > > 
> > > > unicorn:~$ ls -l /run/user/1000/systemd/units
> > > > total 0
> > > > lrwxrwxrwx 1 greg greg 32 Jan  4 10:33 
> > > > invocation:at-spi-dbus-bus.service -> bfec6466520a4586b8c9205c235ccc92
> > > > [...]
> > > > I guess that's normal, then.  It seems they're using the symlink target
> > > > as the actual *data*, not a link to another file that contains the data.
> > > > Why?  I have no idea.  I seem to recall one of the BSDs doing something
> > > > like this, but I never fully understood the rationale.  Something about
> > > > atomic operations, maybe?
> > > > 
> > > 
> > > I consider it as alarming rather than normal when I can't access data
> > > on my own computer.
> > 
> > You can access it just fine.  You just don't *understand* it.  (Neither
> > do I.)
> 
> If I could access it, I could display the file.  If there is no file,
> then these directory entries shouldn't exist.

Filesystem directories entries hold more than file and directory
objects. As well as symbolic links, there's named FIFOs, named sockets,
and devices.

E.g.

$ mkfifo a-fifo
$ nc -lkU a-socket&
$ ln -T target -s a-link

$ ls -l a-*
prw-r--r-- 1 tixy tixy 0 Jan 17 12:07 a-fifo
lrwxrwxrwx 1 tixy tixy 6 Jan 17 12:08 a-link -> target
srwxr-xr-x 1 tixy tixy 0 Jan 17 12:07 a-socket

-- 
Tixy



Re: Seeking a Terminal Emulator on Debian for "Passthrough" Printing

2024-01-12 Thread Tixy
On Fri, 2024-01-12 at 06:08 -0500, Dan Ritter wrote:
> Would it be correct to say that you don't care about the
> "terminal emulator" at all, and merely need a way for the Linux
> server to send data over the network to a serial port on a
> remote Debian machine which is attached to a printer?
> 
> If so, I direct you to the sredird package.

I've always used 'ser2net' for that for of thing, mostly with single-
board computers attached via serial ports on a remote machine. But it
doesn't matter what the device is, it's a dumb pipe to transfer bytes
to/from a serial port on another computer.


-- 
Tixy



Re: 1 Currently unreadable (pending) sectors How worried should I be?

2024-01-02 Thread Tixy
On Tue, 2024-01-02 at 17:47 -0500, Dan Ritter wrote:
> > root@tiassa:~# journalctl -u smartmontools.service | grep unreadable
> > Jan 02 13:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently 
> > unreadable (pending) sectors
> > Jan 02 13:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently 
> > unreadable (pending) sectors
> > Jan 02 14:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently 
> > unreadable (pending) sectors
> > Jan 02 14:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently 
> > unreadable (pending) sectors
> > Jan 02 15:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently 
> > unreadable (pending) sectors
> 
> These are logged at suspiciously even times, like something is
> looking at the disk every 30 minutes exactly.

Perhaps 'smartd' the "SMART Disk Monitoring Daemon" ;-)

-- 
Tixy



Re: Firefox Warning [SOLVED]

2023-12-27 Thread Tixy
On Wed, 2023-12-27 at 11:05 -0600, Mike McClain wrote:
> If I recall correctly, Firefox used to have a checkbox in the
> preferences to permit or deny auto updates. In this version 121.0 for
> the Raspberry PI, that's no longer so and I'm quite sure that FF
> updated itself without asking.

Debian's Firefox is the latest ESR version, i.e. 115, not 121, so it
seems like you've not been talking about a Debian package but something
you originally download and installed from somewhere else e.g. from
Mozilla's site or installed some flatpack or something. That might
explain why it didn't play nicely with your Debian desktop and wants to
update itself to new versions. (Non-ESR versions don't get security
updates so I assume whoever built the software you installed wanted
users to keep up-to-date and included a mechanism to ensure that.)

-- 
Tixy



Re: difference in seconds between two formatted dates ...

2023-12-25 Thread Tixy
On Sun, 2023-12-24 at 23:05 +, Albretch Mueller wrote:
[...]
> Why would %S be in the range second (00..60), instead of (00..59)?:

To support leap seconds [1].

[1] https://en.wikipedia.org/wiki/Leap_second

-- 
Tixy



Re: Test

2023-12-22 Thread Tixy
On Fri, 2023-12-22 at 12:15 -0500, Pocket wrote:
> This is a test of the emergency broadcast system

Please stop spamming the 1000 or so people subscribed to this list.

-- 
Tixy



Re: differences among amd64 and i386

2023-12-16 Thread Tixy
On Thu, 2023-12-14 at 18:19 -0500, Greg Wooledge wrote:
> https://en.wikipedia.org/wiki/Sandy_Bridge
> 
> Instruction set x86-64
> Instructions    x86, x86-64
> 
> You could run amd64 on this machine.  Right now, you have a choice
> between the two, but some distributions have already dropped support
> for i386.  amd64 would be the more future-proof choice.

Just announced today [1] it looks like Debian will drop i386 installs
for the next release.

[1] https://lists.debian.org/debian-devel-announce/2023/12/msg3.html

-- 
Tixy



Re: The bug

2023-12-13 Thread Tixy
On Wed, 2023-12-13 at 10:10 -0500, Greg Wooledge wrote:
> If it's a remote server to which you have limited
> or no physical access, booting a kernel that may "just be unusable"
> (enough to prevent editing GRUB menus and rebooting) could be a disaster.

Which is what happened a few years ago to me when an update broke
kernels running under the Xen hypervisor, which the VPS running my
email was.

-- 
Tixy



Re: quick alpine config question?

2023-11-25 Thread Tixy
On Sat, 2023-11-25 at 13:49 +, Tixy wrote:
> On Sat, 2023-11-25 at 11:46 +, Tim Woodall wrote:
> > OK. This is weird! Something is joining those two lines.
> 
> Not at this end it isn't. For me, all 3 of your diffs look the same on
> screen and are binary the same apart from the space you deleted in the
> third one.
> 
> Perhaps your MUA is treating it as being in quoted-printable encoding?

I've just looked at the message on the web archive [1] and see that
shows the lines joined before you removed the space after the '=',
perhaps that's what you were looking at?

[1] https://lists.debian.org/debian-user/2023/11/msg00898.html 

-- 
Tixy



Re: quick alpine config question?

2023-11-25 Thread Tixy
On Sat, 2023-11-25 at 11:46 +, Tim Woodall wrote:
> OK. This is weird! Something is joining those two lines.

Not at this end it isn't. For me, all 3 of your diffs look the same on
screen and are binary the same apart from the space you deleted in the
third one.

Perhaps your MUA is treating it as being in quoted-printable encoding?
Though looking at the RFC for that, it looks like deleting the trailing
space should have caused the problem (by turning it into a soft line
break) not fixed it. So it's perhaps some other quirk.

-- 
Tixy

 



Re: IMAP vs POP was Thunderbird vs Claws Mail

2023-11-20 Thread Tixy
On Mon, 2023-11-20 at 10:15 -0600, Mike McClain wrote:
> Seeing several messages complaining about fetching messages from
> gmail.com I'd like to point out that gmail can be set to forward all
> messages to a gmail account to another account on a different server.
> I saw a message making that point several years ago,

I'm sure I've mentioned that here before. I did it in my last job as my
employer used Google for mail, so I just forwarded everything to an
email account on my email server at home.

-- 
Tixy



Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"

2023-11-20 Thread Tixy
On Mon, 2023-11-20 at 11:21 +0100, to...@tuxteam.de wrote:
> (and oh, it hasn't been mentioned: make super-sure some smart and
> overly helpful automounter has got hold of the USB).

That's a good point. I tend to use an Ubuntu live image to do things
like cloning my main disk, and I've wasted quite a few hours after not
noticing it's auto-mounting the disk I'm copying too and so trashing my
clone. (I find out the copy is bad when doing a binary compare after
the multi-hour copying is done.)

-- 
Tixy




Re: IMAP vs POP was Thunderbird vs Claws Mail

2023-11-19 Thread Tixy
On Sun, 2023-11-19 at 07:58 -0800, Peter Ehlert wrote:
> > Question: with IMAP is it feasible for a mail client to Leave
> > messages 
> > on the server?
> My question was incomplete.  I should have added that I must have
> local 
> copies of almost everything, for Me to filter an purge.
> --- > So you folks discussing IMAP made it super clear that POP is my
> only choice. < ---

I don't see why you need POP to filter email. Your email client will
almost certainly let you create filters to process and delete emails.
E.g. I use IMAP with Evolution mail client and have various filters for
spam and kill files. Amongst the many filter options is the ability to
pipe new messages to an external program and the perform actions on the
result. That's how I implement killfiles for this email list, I have a
bash script to match email headers against a kill list and then if my
script returns 'true' I have evolution set to delete them.

-- 
Tixy




Re: Why is bullseye-backports recommended on bookworm?

2023-11-17 Thread Tixy
On Thu, 2023-11-16 at 14:04 -0600, David Wright wrote:
> On Thu 16 Nov 2023 at 13:02:28 (+0100), Vincent Lefevre wrote:
> > On 2023-11-15 13:54:51 -0600, David Wright wrote:
> > > On Wed 15 Nov 2023 at 20:01:20 (+0100), Vincent Lefevre wrote:
> > > > On 2023-11-15 18:06:45 +, Tixy wrote:
> > > > > On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote:
> > > > > > On 2023-11-15 16:39:15 -, Curt wrote:
> > > > > > > On 2023-11-14, Vincent Lefevre  wrote:
> > > > > > > > 
> > > > > > > > The base number is the same, but I would have thought that this 
> > > > > > > > other
> > > > > > > > kernel might have additional patches.
> > > > > > > > 
> > > > > > > > > That's why I suggested ignoring the message.
> > > > > > > > 
> > > > > > > > Then why does reportbug mention the bullseye-backports kernel?
> > > > > > > 
> > > > > > > Because it kind of looks newer if you're a not very bright 
> > > > > > > software
> > > > > > > construct, he opined.
> > > > > > 
> > > > > > But the bookworm-backports kernel is even newer.
> > > > > > So why not this one?
> > > > > 
> > > > > Because it's a different package?
> > > > 
> > > > There is no guarantee that a package with the same name in a
> > > > different distribution has the same meaning (because packages
> > > > get renamed...). So I would say that this is not a good reason.
> > > 
> > > Well, it would seem strange to provide a backport for a package
> > > and call it by a different name. But with kernels, there's always
> > > the problem of a myriad of slightly different versions, so a
> > > fuzzy name match might be appropriate.
> > 
> > In any case, if a package is renamed (which particularly applies to
> > unstable, I don't know about backports), I would expect reportbug
> > to also consider the new name for a newer version of the package.
> > In short, its search for newer versions should be based on the
> > source package rather than the binary package.
> 
> As I said above, I don't know whether they apply any fuzziness to the
> version numbers in view of the multiplicity of linux-image versions
> (and sources). As far as a 'rename' is concerned, I don't think that
> linux-image has changed name since it was kernel-image in sarge.

There is no binary package called 'linux-image'. My PC has 'linux-
image-amd64' installed which is a meta package who's description says
'This package depends on the latest Linux kernel and modules for use on
PCs with AMD64'.

At time of writing, that depended on package in stable is called
'linux-image-6.1.0-13-amd64' and the version of that package is
'6.1.55-1'. This is the kernel installed on my machine.

In the original post that sparked this thread, Vincent showed reportbug
saying that same binary package (linux-image-6.1.0-13-amd64) had a
newer version available in backports, with the version number
6.1.55+1~bpo11+1.

Report bug is correct, that is a newer version by Debian versioning
rules, there is no 'fuzzy' matching involved...

$ dpkg --compare-versions 6.1.55+1~bpo11+1 gt 6.1.55-1; then echo True; else 
echo False; fi
True

Now, I admit, looking in a prior releases backports for a newer version
seems wrong, assuming the machine in question didn't have that release
in it's source.list.

-- 
Tixy



Re: Hardware Advice Wanted: Router

2023-11-16 Thread Tixy
On Thu, 2023-11-16 at 15:56 +0800, jeremy ardley wrote:
> The FriendlyPC version run a vendor version of Debian with some packages 
> especially compiled for the device such as ffmpeg and graphics drivers
> 
> Armbian is usually a bit slower in releases and produces a more 
> canonical Debian version with differences in the SBC specific device 
> drivers using dynamic overlays. Most packages are pure debian


Thanks for replying. I'm just want something to act as a router, NAS
using NFS, and SMTP/IMAP sever for my email. I.e. Ethernet, USB and
SATA. What I have at the moment works finem its just that when Debian
drops support for the armel architecture I'm going to have to fork out
for new hardware, so am keeping my eye out for cheap options.

Another alternative is to just build armel myself. That might work for
the first release after the architecture is dropped, assuming it isn't
dropped for some major region, like broken compilers etc.

-- 
Tixy



Re: Hardware Advice Wanted: Router

2023-11-16 Thread Tixy
On Thu, 2023-11-16 at 10:49 -0500, Stefan Monnier wrote:
> > 
> 
> > I'm currently running a Globalscale SheevaPlug and a DreamPlugs but
> > Debian support for the old ARM architecture is likely to end soon.
> > (Dropping it seems to come up each release, but so far they're
> > still
> > releasing for it.)
> 
> If these can run the `armhf` port you should be fine for a few
> more years.  For `armel` the writing is on the wall, tho.

They're armel. ARMv5 Thumb mode only.

-- 
Tixy



Re: Hardware Advice Wanted: Router

2023-11-15 Thread Tixy
On Thu, 2023-11-16 at 09:04 +0800, jeremy ardley wrote:
> My current favourites are RK3588 based CPU SBC devices which have an 
> exceptionally fast set of CPUs, high speed networking, and options for 
> Debian or Ubuntu or OpenWRT or Armbian. 

Are these the usual SBC setup where you have to run the vendor kernel,
plus possibly other custom bits, or would pure Debian including kernel
run on them?

I'm currently running a Globalscale SheevaPlug and a DreamPlugs but
Debian support for the old ARM architecture is likely to end soon.
(Dropping it seems to come up each release, but so far they're still
releasing for it.)

-- 
Tixy



Re: Why is bullseye-backports recommended on bookworm?

2023-11-15 Thread Tixy
On Wed, 2023-11-15 at 18:15 +0100, Vincent Lefevre wrote:
> On 2023-11-15 16:39:15 -, Curt wrote:
> > On 2023-11-14, Vincent Lefevre  wrote:
> > > 
> > > The base number is the same, but I would have thought that this other
> > > kernel might have additional patches.
> > > 
> > > > That's why I suggested ignoring the message.
> > > 
> > > Then why does reportbug mention the bullseye-backports kernel?
> > 
> > Because it kind of looks newer if you're a not very bright software
> > construct, he opined.
> 
> But the bookworm-backports kernel is even newer.
> So why not this one?

Because it's a different package? bookworm-backports has a linux-6.5
package which is not a newer version of the linux-6.1 package it's
totally separate as far as the packaging system is concerned.

-- 
Tixy



Re: No 6.5.10-4 realtime kernel?

2023-11-14 Thread Tixy
On Mon, 2023-11-13 at 20:45 +0100, Gilles Mocellin wrote:
> > On Sun, Nov 12, 2023 at 10:04 AM Scott Denlinger
> > 
> > wrote:
> > > Does anyone know why there are no stock realtime kernels in trixie/sid? I
> > > currently have 'linux-image-6.5.0-1-rt-amd64-unsigned' installed, but I
> > > don't see any newer RT kernels available.
> > > 
> > > Scott Denlinger
> 
> Hello, I also was looking for it, but I've seen that the standard kernel 
> seems 
> to have some preemptive patch (dynamic ?) :
> 
> So I think the kernel packagers think it's sufficient ?

Quoting a recent article from LWN [1]

   PREEMPT_DYNAMIC, was added to the 5.12 kernel by Michal Hocko in
   2021. It allows the preemption choice to be deferred until boot
   time, where any of the modes except PREEMPT_RT can be selected by
   the preempt= command-line parameter. PREEMPT_DYNAMIC allows
   distributors to ship a single kernel while letting users pick the
   preemption mode that works best for their workload. 

So if you specificity need a real-time kernel this won't give it to
you.

[1] https://lwn.net/Articles/944686/

-- 
Tixy



Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Tixy
On Sat, 2023-11-04 at 20:08 +0100, Martin wrote:
[...]
> BTW putting above script into /etc/nftables.conf (at the bottom of file)
> did not ever worked - I had always to run that file manualy as root.
> Command 'nft list ruleset' only then showed this table.
> I have no idea why. To me it seemed as if /etc/nftables.conf file
> was not executed (I have rebooted many times so this file should run).
[...]

Did you enable the nftables service? To do that, use:

# systemctl enable nftables.service

and to see status of the service

# systemctl status nftables.service

-- 
Tixy



Re: selinux causing problems

2023-10-31 Thread Tixy
On Tue, 2023-10-31 at 18:36 +1300, Alex King wrote:
> Now it seems that selinux is active again, and even when I try to set 
> selinux=0 to disable it, it is still running and spamming the logs with 
> messages like
> 
> logrotate.service: Failed to read SELinux context of 
> '/lib/systemd/system/logrotate.service', ignoring: Operation not permitted
> 
> 
> How should I disable selinux?

I'm guessing here, but perhaps selinux _is_ disabled but things are
still trying to use it and producing error messages. Have you tried
uninstalled the 'apparmour' package? I remember doing this in years
past when it first started getting installed and putting noise on boot
screen and in logs.

-- 
Tixy



Re: Lenovo E16 Gen1 with Intel Iris adjust brightness, get Fn-Keys working

2023-10-24 Thread Tixy
On Tue, 2023-10-24 at 09:32 +0200, basti wrote:
> 
> OK, I can write the values ​​to 
> /sys/class/backlight/intel_backlight/brightness
> 
> The default is 15040, which seems to be the maximum.
> Nothing visible changes between 15040 and 13000.
> 60 is very dark.
> It therefore looks like an exponential function.
> 
> I have to see how I can represent this in a function to use it with the 
> fn-keys.
> 

You can edit ~/.config/openbox/lxde-rc.xml

Here's my full notes from when I did what your trying to do on a laptop
many years ago. This obviously needs modifying for your machine...

0. Edit /etc/rc.local to add

# make brightness writeable
chmod a+w 
/sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight/brightness
# set brightness to a nice default
echo 1200 
>/sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight/brightness

   The make file executable

chmod a+x /etc/rc.local

   UPDATE: rc.local now needs a shebang at the top, i.e. #!/bin/sh

1. Create /home/tixy/bin/bl- to reduce brightness in steps

#!/bin/bash


device="/sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight"
step=200
curval=`cat $device/brightness`
newval=`echo $(expr $curval - $step)`
if [ $newval -le $step ]; then
  newval=$step
fi
echo $newval
echo $newval >$device/brightness

2. Create /home/tixy/bin/bl+ to increase brightness in steps

#!/bin/bash


device="/sys/devices/pci:00/:00:02.0/drm/card0/card0-LVDS-1/intel_backlight"
step=200
curval=`cat $device/brightness`
maxval=`cat $device/max_brightness`
newval=`echo $(expr $curval + $step)`
if [ $newval -ge $maxval ]; then
  newval=maxval
fi
echo $newval
echo $newval >$device/brightness

3. Edit '' section of ~/.config/openbox/lxde-rc.xml


  
/home/tixy/bin/bl+
  


  
/home/tixy/bin/bl-
  




Re: Bookworm: NetworkManager

2023-10-22 Thread Tixy
On Sat, 2023-10-21 at 17:13 -0400, Pocket wrote:
> I am just using what was installed by my scripted debian installation

A day ago when people pointed out that Network Manager only gets
installed if you select desktop install configuration, you denied that
was true by saying "Well the default install for bookworm does install
it and use it."

Now you admit you're using some kind of script to install Debian, I
think it's very misleading to call that 'a default install'. If, you
have a script you wrote or got from somewhere that installs software
that you don't want why don't you change the script, or just uninstall
Network Manager?

-- 
tixy



Re: Mailutils+nullmailer: sender full name

2023-10-19 Thread Tixy
On Wed, 2023-10-18 at 13:56 -0400, Greg Wooledge wrote:
[...]
> Before stretch, if you had heirloom-mailx installed, both "mail -a file"
> and "mailx -a file" worked.  After upgrading to stretch, you'd have an
> s-nail program, but *not* a mail or mailx program, so all your scripts
> would break.  And if you did the obvious thing and installed bsd-mailx
> as a replacement, "mailx -a file" would try to add a header named "file"
> instead of attaching a file named "file".
> 
> So, after the stretch upgrade, you would either have to change all of
> your scripts to use s-nail instead of mailx, or
[...]

That brings back memories. I did that and switched to using s-nail by
name for scripts that send me status and backup report emails with
filtered logs as attachments.

-- 
Tixy



Re: Mailutils+nullmailer: sender full name

2023-10-18 Thread Tixy
On Wed, 2023-10-18 at 11:28 -0500, David Wright wrote:
> (Aside: does anyone know what "heirloom-mailx" is?)

I remember it being the mailx compatible program that got installed by
default many releases ago, and it was replaced by s-nail in
2016. (Possibly as a fork of that orphaned project?)

I still use s-nail on all my machines.

-- 
Tixy



Re: apt error, fresh install Debian 12/Dell desktop

2023-10-10 Thread Tixy
On Tue, 2023-10-10 at 17:11 +0200, Anders Andersson wrote:
> This is a bit crazy. It can't be a "fresh install" if you have the
> amd64 kernel trying to configure the closed firmware for a raspberry
> pi.

As Махно pointed out in another reply [1], this does really seem to be
the case. If you follow the thread they linked to it occurs when
installing from the 12.0 live image and there are claims it's fixed in
12.1.

[1] https://lists.debian.org/debian-user/2023/10/msg00269.html



Re: git setup

2023-08-26 Thread Tixy
On Fri, 2023-08-25 at 22:36 +, Russell L. Harris wrote:
> If pushing from PRODUCTION is more reliable or less trouble-prone than
> pulling from BACKUP, kindly explain to me, and I shall change.

Another consideration is that to pull from PRODUCTION requires it to be
running a service (e.g. ssh) to give BACKUP access. If PRODUCTION is
something like a laptop that you use when not at home, then you may not
want to have said service exposing itself on strange wifi networks.

-- 
Tixy



Re: AW: Debugging initramfs, server hangs during boot process

2023-08-26 Thread Tixy
On Sat, 2023-08-26 at 11:07 +0200, thah...@t-online.de wrote:
> I had debug on the command line before, just didn't know of debug=vc
> However the output on the screen is the same with either one.
> 
> Last line is clocksource: Switched to clocksource tsc

I notice two 1 second delays during boot on my new PC which occurred
when TSC related stuff was the last line on the screen. I did fiddle
around with some settings (can't remember what) in order to try and
remove this delay, but decided to leave things at default in the end.

Now googling for "clocksource TSC" gets me a Redhat page about hardware
clocks. [1] Maybe you could try changing the clock with
"clocksource=hpet" or something else, in case the kernel is having
problems with TSC? It's ominous that some search results reveal the
commandline option "tsc=reliable" implying the opposite may true
sometimes.

[1] 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_real_time/7/html/reference_guide/chap-timestamping

-- 
Tixy



Re: Debugging initramfs, server hangs during boot process

2023-08-26 Thread Tixy
On Sat, 2023-08-26 at 07:59 +0200, to...@tuxteam.de wrote:
> On Sat, Aug 26, 2023 at 07:40:21AM +0200, Michel Verdier wrote:
[...]
> > 
> > Did you try with "debug" on the linux command line to get more logs
> > ?
> 
> I thought of that, too, but debug writes to a tmpfs (it has to, at this
> point). If the machine locks up, the log is lost...

Logs will appear on the screen so long as you don't have the 'quiet'
parameter on the Linux commandline.

-- 
Tixy



Re: Please verify Gnome and KDE wiki articles for correctness

2023-08-26 Thread Tixy
On Sat, 2023-08-26 at 00:55 -0400, Jeffrey Walton wrote:
> I'm getting the
> message, "No Popularity contest entry for kde-full" (and friends). I
> use kde-full and I have popularity contest enabled, so there should be
> at least one entry.

Perhaps because they're metapackages?

-- 
Tixy



Re: git setup

2023-08-25 Thread Tixy
On Fri, 2023-08-25 at 19:47 +0200, john doe wrote:
> On 8/25/23 13:44, Tixy wrote:
> > On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> > > Yes, I think a bare remote is the way to go in this context
> > 
> > You can make a repo bare by editing it's config file (.git/config) to
> > have 'bare = true' instead of 'bare = false' under the '[core]'
>  >
> 
> Generaly, the '.git' extension symbolises a bare repository!

The opposite is true, the .git directory is the default location for
git's stuff in non-bare repos.

   $ git init test
   # some output omitted
   Initialized empty Git repository in /home/tixy/test/.git/
   
   $ ls -lA test
   total 4
   drwxr-xr-x 7 tixy tixy 4096 Aug 25 21:28 .git
   
   $ cat test/.git/config
   [core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true


For bare repos it doesn't create the .git directory...


   $rm -rf test
   $git init --bare test
   # some output omitted
   Initialized empty Git repository in /home/tixy/test/
   
   $cat test/config
   [core]
repositoryformatversion = 0
    filemode = true
bare = true


-- 
Tixy



Re: git setup

2023-08-25 Thread Tixy
On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> Yes, I think a bare remote is the way to go in this context

You can make a repo bare by editing it's config file (.git/config) to
have 'bare = true' instead of 'bare = false' under the '[core]'
section. I do this after copying the .git directory to my remote server
when setting up a new repo.

Google returns a Stack Overflow answer [1] that says you can do the
same with:

  git config --bool core.bare true

[1] 
https://stackoverflow.com/questions/2199897/how-to-convert-a-normal-git-repository-to-a-bare-one

-- 
Tixy



Re: git setup

2023-08-25 Thread Tixy
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
> #!/bin/bash
> # post-commit
> # 2023.08.24 2200gmt
> 
> ssh backup "git pull"
> exit 0
> 

You could omit the 'exit 0' so it returns the error code from the ssh
command, that way you'll get some feedback from failures to backup
which you would probably want to know about.

I'm also a bit confused about doing it this way. The usual workflow
with git is to 'push' to the remote repository, which is in fact what
you originally asked how to do.
 
As sothers pointed out, you push with the command 'git push' which you
could do in the hook script instead of 'ssh backup "git pull"'. But
whatever works for you I guess.

Note, if you ever edit commits then having an automated 'pull' or
'push' command will fail, as by default they will only do a fast-
forward operation. There are commandline options and config setups to
change this.

-- 
Tixy



Re: kernel 6.4.0-3 (testing) cannot be installed with virtualbox-dkms

2023-08-24 Thread Tixy
On Thu, 2023-08-24 at 10:06 +0200, Erwan David wrote:
> I had an upgrade failure today, when upgrading kernel to 6.4.0-3 : 
> virtualbox-dkms needs a function which disappeared from kernel headers.
> 
> I opened the bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050406
> 

Which has been marked as a duplicate of another bug [1] which includes
a link to the Virtualbox bug tracker [2] where it looks like they have
committed a fix a couple of days ago. So perhaps you want to get the
latest Virtualbox code?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050096
[2] https://www.virtualbox.org/ticket/21796

-- 
Tixy



Re: Package policy?

2023-08-08 Thread Tixy
On Tue, 2023-08-08 at 16:24 +0200, Hans wrote:
> Hi folks, 
> 
> sometimes I do not understand, how debian is handling packages. Here is 
> another weired case.
> 
> Package roger-router: available in bullseye, NOT available in bookworm, but 
> again available in sid???

Probably because it had a critical bug that did get fixed in time for
the Bookworm release so it was removed from Bookworm. It probably was
ever removed from sid, just Bookworm when it was 'testing'.

> 
> I can only guess,

You don't have to guess, you can look at the package tracker...
https://tracker.debian.org/pkg/roger-router

>  the package maintainers removed it, because it did not work 
> somewhow, but why then put it back again?

It's not been put back again, it's still not in 'testing' because it's
been broken for nearly a year. The package tracker shows it's history,
looks like one of the libraries it depends on isn't present in the
correct version.

-- 
Tixy



Re: Pulseaudio - Daemon.conf

2023-07-19 Thread Tixy
On Wed, 2023-07-19 at 01:24 +0200, Stefan Schumacher wrote:
> I noticed that pulseaudio is not part of Debian Bookworm anymore.

Yes it is [1] and it's still running on my machine after upgrading to
Bookworm. (I run the LXDE desktop.)

[1] https://packages.debian.org/bookworm/pulseaudio

-- 
Tixy



Bookwork upgrade fail with encrypted root

2023-06-12 Thread Tixy
Anyone with an encrypted root partition should probably follow the
advice in the NEWS for cryptsetup from the last release (buster) which
at the time said.

On systems which do rely on the initramfs integration, one can mark
'cryptsetup-initramfs' as being manually installed (so APT never
selects it for auto-removal) with the following command:

apt-mark manual cryptsetup-initramfs

My failure to do this caused cryptsetup-initramfs to become an
'obsolete' package in Aptitude which I didn't spot when cleaning the
these up after what I thought was a successful upgrade. This resulted
in an unbootable system.

I guess this shouldn't affect most people, it was the result of:

A) The cryptsetup package in Bookworm changing from depending on
cryptsetup-initramfs to just recommending it.

B) Me having APT configured to not install recommends.

Though thinking about this again as I write this, it seems that once a
recommended package is installed it shouldn't show up as 'obsolete'.
Note, I do have the config:

  APT::AutoRemove::SuggestsImportant "false";

But RecommendsImportant is left as the default (true).

Hmmm, perhaps I did something else to cause cryptsetup-initramfs to be
removed?

Either way, it seems safe advice to other people with an encrypted root
partition to mark the package as manually installed to help prevent
issues.

-- 
Tixy



Re: Debian home page -> Download link broken:

2023-06-12 Thread Tixy
On Sun, 2023-06-11 at 15:24 -0400, Jeffrey Walton wrote:
> On Sun, Jun 11, 2023 at 2:12 AM Tixy  wrote:
> > 
> > On Sat, 2023-06-10 at 23:55 -0400, Jeffrey Walton wrote:
> > > Debian's wiki says to use apt-get:
> > > https://wiki.debian.org/DebianUpgrade. Also see
> > > https://www.debian.org/doc/manuals/debian-faq/uptodate.html .
> > > 
> > > Maybe it's time for a complete refresh of those documents.
> > 
> > Or maybe the wiki page should be deleted, or just say go RTFM, i.e.
> > read the release notes for the release you want to upgrade to.
> 
> Tixy, I checked the manual at
> https://www.debian.org/doc/manuals/debian-handbook/sect.apt-get.en.html
> . I cannot find the requirement to run 'apt upgrade'.
> 
> Can you provide a reference, please?

Sorry, I was referring to the release notes [1] not the Debian
Handbook.

I must admit that I didn't read the Wiki before now and to be fair it
does say at the beginning to go read the release notes before going on
to summarise the commands that you may need just using 'apt-get'.
Note that release notes for the past two releases say to use the 'apt'
command for everything, e.g.:

apt update
apt upgrade --without-new-pkgs
apt full-upgrade

And for making space and cleaning up:

apt autoremove
apt clean

I also see that the Debian Handbook says that before starting APT
related work to use 'apt update' and the release notes points out the
issue [2] that users of apt-get may need --allow-releaseinfo-change.

[1] 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
[2] 
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#updating-lists

-- 
Tixy



Re: fstrim: /: the discard operation is not supported

2023-06-11 Thread Tixy
On Sun, 2023-06-11 at 19:54 +0200, hede wrote:
> Hi, 
> 
> on bullseye fstrim was working fine, but after the upgrade to bookworm fstrim 
> stops working. 
> Setup is: ext4 on LUKS on LVM on SSD

I have same setup on the machine I upgraded to Bookworm today and I
just checked and discards still work.

[...]
> 
> But the crypttab includes:
> sda2_crypt UUID=[UUIDishere] none luks,discard
> 
> I've added "issue_discards = 1" to /etc/lvm/lvm.conf without success - and 
> btw. that wasn't needed before the upgrade. 

I have both those settings, have done since I googled how to do this a
few releases ago.

> Any hints what to test or where to search for a solution?

After changing lvm.conf did you rebuild initramfs and reboot?

-- 
Tixy



Re: Debian home page -> Download link broken:

2023-06-11 Thread Tixy
On Sat, 2023-06-10 at 23:55 -0400, Jeffrey Walton wrote:
> Debian's wiki says to use apt-get:
> https://wiki.debian.org/DebianUpgrade. Also see
> https://www.debian.org/doc/manuals/debian-faq/uptodate.html .
> 
> Maybe it's time for a complete refresh of those documents.

Or maybe the wiki page should be deleted, or just say go RTFM, i.e.
read the release notes for the release you want to upgrade to.

-- 
Tixy



Re: Email bodies not show anymore in Evolution Email

2023-05-04 Thread Tixy
On Thu, 2023-05-04 at 20:09 +0200, zithro wrote:
> 
> A recent email from the Debian security team confirms this (Advisory 
> DSA-5396-2) :
> 
> "The webkit2gtk update released as 5396-1 introduced a compatibility
> problem that caused Evolution to display e-mail incorrectly. Evolution
> has been updated to solve this issue.
> 
> For the stable distribution (bullseye), this problem has been fixed in
> version 3.38.3-1+deb11u2."
> 

Yep, just updated and the problem is fixed by

evolution (3.38.3-1+deb11u2) bullseye-security; urgency=medium

  * Cherry pick a couple of upstream patches to solve regressions caused
by the upgrade to WebKitGTK 2.40.x:
- debian/patches/frame-flattening.patch: display email bodies properly
  (Closes: #1035469).
- debian/patches/scroll-preview-messages.patch: allow scrolling
  message previews with the space bar.

 -- Alberto Garcia   Thu, 04 May 2023 17:54:18 +0200




Re: Email bodies not show anymore in Evolution Email

2023-05-04 Thread Tixy
On Thu, 2023-05-04 at 12:07 +0200, Christoph Pleger wrote:
> > 
> Hello,
> 
> > I have had just the same problem. I think it is caused by the last 
> > security upgrade by unattended-upgrades of these packages:
> > gir1.2-javascriptcoregtk-4.0
> > gir1.2-webkit2-4.0
> > libjavascriptcoregtk-4.0-18
> > libwebkit2gtk-4.0-37
> 
> Ah, thank you very much for that information. In the meanwhile, I
> found
> that there is already a bug report available at Debian about that.

That's good, because I too can only read email by hitting Ctrl-U to
view the source.

-- 
Tixy



Re: disk usage for /usr/lib on bullseye

2023-05-02 Thread Tixy
On Tue, 2023-05-02 at 22:28 +0800, Bret Busby wrote:
> I think that, to remove all installed packages, a system administrator, 
> from the superuser level, needs to run something like
> rm -r /

Or

  apt remove '*'

Man page for apt says it accepts regex and globs for package
specifiers. Other tools like apt-get and aptitude also allow some form
of wildcard specification.

I don't know which of the various packaging tools allow you to force
uninstalling priority essential packages though, but the low level dpkg
itself does, so you can come up with a shell one-liner to get a list of
installed packages and remove them all. Of course, this would break at
some point after removing a package with executable programs used by
package scripts. ;-)

-- 
Tixy





Re: disk usage for /usr/lib on bullseye

2023-05-02 Thread Tixy
On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
> On 2/5/23 16:58, Bret Busby wrote:
> > On 2/5/23 11:42, David Wright wrote:
> 
> 
> 
> > > 
> > > > > > Have you tried running also
> > > > > > apt autoclean
> > > 
> > > I thought that just cleared /var/cache/apt/archives/.
> > > 
> > > > > > and
> > > > > > apt purge
> > > 
> > > I've never tried that without a package name. What does it do?
> > > 
> > 
> > RTFM ?
> > 
> 
> man apt

Which doesn't say what 'apt purge' does without a package name. It says
'Performs the requested action on one or more packages specified via
regex(7), glob(7) or exact match'. It doesn't go on to say what happens
if you leave that blank. 3 possibilities that spring to mind is that
this is and error, a noop, or means 'every package'. The latter you be
real bad, the other two now a useful suggestion to people. Of course,
it could be special cased to mean 'purge everything not installed',
which count be useful, but the man page doesn't say that.

-- 
Tixy



Re: disk usage for /usr/lib on bullseye

2023-05-01 Thread Tixy
On Mon, 2023-05-01 at 13:51 +, Bonno Bloksma wrote:
[...]
> On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have 
> been operating for a while and 1+G on a machine that has been operating for a 
> shorter while.
> 
> The cause seems to be the folder /usr/lib/modules# 
> linams:/usr/lib/modules# du * -sh
> 4.7M    5.10.0-10-amd64
> 4.7M    5.10.0-11-amd64
> 4.7M    5.10.0-12-amd64
> 4.7M    5.10.0-13-amd64
> 4.7M    5.10.0-15-amd64
> 4.7M    5.10.0-16-amd64
> 309M    5.10.0-18-amd64
> 309M    5.10.0-19-amd64
> 309M    5.10.0-20-amd64
> 309M    5.10.0-21-amd64
> 309M    5.10.0-22-amd64
> 4.7M    5.10.0-7-amd64
> 4.7M    5.10.0-8-amd64
> 4.7M    5.10.0-9-amd64

I think I see the same issue. I just looked at /usr/lib/modules and see
one extra directory for kernel that isn't installed (5.10.0-18-amd64).
Because this issue seemed familiar I looked at my bash command history
and that has me cd'ing into that directory and doing a du command there
and then deleting stuff. So I guess I've also resorted to manually
cleaning it up in the past.

-- 
Tixy




Re: Evolution email (problem?) (IMAP, Gmail, email compacting)

2023-05-01 Thread Tixy
On Sun, 2023-04-30 at 18:24 -0400, Default User wrote:
> It does occur to me that Evolution may use the maildir format rather
> than the mbox format.  I just ASSumed that it used mbox, since in Menu
> > File, there is an option to save messages in mbox format.  If
> Evolution uses the maildir format, compacting apparently does not
> apply, which would seem to explain it.  I have not yet determined
> whether Evolution uses mbox or maildir.  

I thought we were talking about IMAP protocol access to Google? In
which case Evolution isn't storing email in any format [1], it's
accessing it on a remote server. Evolution does have an 'On This
Computer' email account, don't know what format it uses for that. In
Evolution you can also create email accounts where email is stored
locally in maildir or mbox format. I used maildir some years ago to
have an email archive of some mailing lists. 

[1] Well, Evolution does cache email in ~/.cache/evolution/mail
which seems to involve SQLite database and a file for each email. If
you want to free that space you can just 'rm -rf ~/.cache/evolution'
but I guess if you have 'download for offline use' configured or
actually look at the remote email folders again it will re-download
them.

-- 
Tixy



Re: Evolution email (problem?) (IMAP, Gmail, email compacting)

2023-04-30 Thread Tixy
On Sun, 2023-04-30 at 11:19 -0400, Default User wrote:
> (BTW, if anyone does have information about compacting folders in
> Evolution, I would love to hear about it!)

What is 'compacting', what is it meant to do? Sounds like 'compressing'
to me, don't know if protocols like IMAP has a way to ask the server to
compress it's folders. (I would have though how emails are actually
stored would be an internal implementation detail of the server).

If it just means really deleting email, then you can select the menu
option File > Empty Wastebasket which does that for all accounts. Or
for just a single account, right click on it's Wastebasket. There is
also Folder > Expunge which I believe does it for a single folder.

You can also configure Evolution to empty the wastebasket after a
period of time, or as I have it configured, whenever you close
Evolution. (I've always hated the idea of Wastebaskets, if I delete
something I want it deleted, not just hidden and taking up space).

-- 
Tixy





Re: Evolution email (problem?)

2023-04-27 Thread Tixy
On Thu, 2023-04-27 at 12:15 -0400, Default User wrote:
> If a message is in both of the folders "Inbox" and "All Mail", it CAN
> NOT be directly deleted from "All Mail". It stays in both folders, with
> only the one in "All Mail" having a line through it, showing that is
> marked for deletion, but is not deleted, and is not even moved to
> "Trash", which remains empty. 

Well, one email can't be _in_ two folders. You can have two emails, one
in each folder, and deleting one shouldn't affect the other. Except
you're using Google's Gmail where 'folders' aren't really folders, just
tags applied in a database. Who knows how it's going to behave when
they Google maps that onto the IMAP protocol.

-- 
Tixy



Re: Evolution email (problem?)

2023-04-27 Thread Tixy
On Wed, 2023-04-26 at 11:05 -0400, Default User wrote:
> Even if it did not work from a Live Debian session, it makes no sense
> to me that Evolution could be designed this way.  I see no good reason
> that messages can be directly deleted from any other folder, but not
> [Gmail]/All Mail.  
> 
> Does anyone have a solution, so that messages must be moved to another
> folder (if they are not also there already), just to be deleted?  Or at
> least a "good" explanation as to why Evolution appears to be designed
> this way?  

I'd be inclined to blame Gmail's quirks.

Personally, I've used Evolution since Debain 5 without issue, though
not with Gmail though. Well, except on a work laptop for a few months
until I realised it didn't behave properly (like hiding your own mails
sent to lists) so I just set up a rule for gmail to forward all mail to
proper IMAP sever (Dovecot) run by me and used that for work email.

-- 
Tixy 



Re: Apt sources.list

2023-04-15 Thread Tixy
On Sat, 2023-04-15 at 08:11 -0400, pa...@quillandmouse.com wrote:
> Folks:
> 
> Here is my sources.list file:
> 
> ---
> 
> deb http://debian.uchicago.edu/debian/ bookworm main contrib non-free
> deb-src http://debian.uchicago.edu/debian/ bookworm main contrib non-free
> 
> deb http://security.debian.org/debian-security bookworm-security main
> contrib non-free deb-src http://security.debian.org/debian-security 
> bookworm-security main contrib non-free
> 
> ---
> 
> According to https://www.debian.org/releases/, bookworm at this time is
> "testing". But when the next release comes, bookworm will still be
> bookworm, but "testing" will be bookworm "plus". I'd like to follow
> testing, regardless of the status of Debian official releases.
> 
> So... in my sources.list, if I change "bookworm" to "testing", will it
> do that, and (other than the instabilities of testing) is there any
> liability to it?

Testing doesn't get explicit security support so there's no point in
having 'testing-security' lines in sources.list (I guess it'll give an
error anyway).

-- 
Tixy



Re: how to limit a CPU temperature?

2023-04-08 Thread Tixy
On Sat, 2023-04-08 at 10:17 -0400, songbird wrote:
> 
>   i have an intel processor and it has the MAX which does
> prevent it from going higher (100C), but i'd like to keep it
> at 70C or lower.
> 
>   i've been trying to find anything that will let me set this
> but no luck yet in my searches.

I installed 'thermald' to stop my CPUs hitting the max junction
temperature and hard resetting after a few minutes. I was quite
surprised that the standard kernel doesn't actually have thermal
protection which throttles CPU clocks and requires an external
userspace program to do this.

-- 
Tixy



Re: Re: home server for email box

2023-03-10 Thread Tixy
On Fri, 2023-03-10 at 21:29 +0900, p...@ymail.ne.jp wrote:
> As you suggested I may use other relays as outgoing gateway. But the
> home box will receive and store messages. I can operate the email
> accounts for me and my family on this server.

This is what I do. But another thing to bear in mind is what happens if
you have a problem with your home internet connection or with the
computer receiving your email? Yes, email senders will retry for a
while, but personally I've had my ADSL line go down for a week or more.
Also, if you are away on holiday you won't be there to fix a broken
email server. For most people, email service is pretty critical so you
will likely want a second fallback email server somewhere else. This is
what I do, I used to have a VPS for this but to save money I recently
moved to an email hosting service that supports receiving emails for
other domains.

-- 
Tixy





Re: Strange application menus (File, Edit…) behaviour since last update

2023-03-09 Thread Tixy
On Thu, 2023-03-09 at 04:32 -0500, Timothy M Butterworth wrote:
> On Thu, Mar 9, 2023 at 4:06 AM Timothy Butterworth <
> timothy.m.butterwo...@gmail.com> wrote:
> 
> > Try running apt fully upgrade
> > 
> `sudo apt full-upgrade` sorry about that my tablet auto-corrected.

And it broke threading.

-- 
Tixy



Re: service vs systemctl

2023-03-07 Thread Tixy
I accidentally deleted a sentence in my last reply, here's the
corrected version...

On Tue, 2023-03-07 at 15:38 +0800, Ken Young wrote:
> Hello
> 
> For debian 11, service is just a wrapper to systemctl, is it right?

It's a 217 line shell script and looking at it it checks for which init
system is in use. So if you have systemd (Debian's default now) then
yes, it will call systemctl.

> So for server management, both commands below have the same results.
> 
> sudo service nginx start
> sudo systemclt start nginx
> 

They may not be the same, e.g. under the section of the script dealing
with both stop and start is this comment

# Follow the principle of least surprise for SysV people:
# When running "service foo stop" and foo happens to be a service that
# has one or more .socket files, we also stop the .socket units.
# Users who need more control will use systemctl directly.

Personally, I still use 'service' through habit and won't change until
it doesn't do what I expect.




Re: service vs systemctl

2023-03-07 Thread Tixy
On Tue, 2023-03-07 at 15:38 +0800, Ken Young wrote:
> Hello
> 
> For debian 11, service is just a wrapper to systemctl, is it right?

It's a 217 line shell script and looking at it it checks for which init
system is in use. So if you have systemd (Debian's default now) then
yes, it will call systemctl.

> So for server management, both commands below have the same results.
> 
> sudo service nginx start
> sudo systemclt start nginx
> 

# Follow the principle of least surprise for SysV people:
# When running "service foo stop" and foo happens to be a service that
# has one or more .socket files, we also stop the .socket units.
# Users who need more control will use systemctl directly.

Personally, I still use 'service' through habit and won't change until
it doesn't do what I expect.

-- 
Tixy



Re: Debian 11 upgrade to Debian 12

2023-02-28 Thread Tixy
On Tue, 2023-02-28 at 14:52 -0500, Greg Wooledge wrote:
> On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > [...]
> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > I ran apt update and apt upgrade. I guess I could have run apt 
> > > full-upgrade
> > > and that probably would have worked better.
> > 
> > It would have. If you looked at the release notes [1] it suggests
> > 
> > # apt upgrade --without-new-pkgs
> > # apt full-upgrade
> > 
> > Then lists some possible issues and there remedy.
> > 
> > [1] 
> > https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
> 
> It's also worth mentioning that in bookworm, non-free firmware has been
> moved to a new section called "non-free-firmware".  If you use any of
> that -- most people do! -- then you either need to change "non-free" to
> "non-free-firmware" or to "non-free non-free-firmware", depending on
> your specific needs.
> 

That's is the release notes too :-) (I know, there's probably only a
small minority of us who actually read the docs before upgrading.)

-- 
Tixy



Re: Debian 11 upgrade to Debian 12

2023-02-28 Thread Tixy
On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
[...]
> All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> and that probably would have worked better.

It would have. If you looked at the release notes [1] it suggests

# apt upgrade --without-new-pkgs
# apt full-upgrade

Then lists some possible issues and there remedy.

[1] 
https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade

-- 
Tixy



Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

2023-02-28 Thread Tixy
On Tue, 2023-02-28 at 16:05 +0100, daven...@tuxfamily.org wrote:
> 
> It's the systemd-style so-called "predictable" interfaces names.
> Replacing the older the eth0, wlan0, and so on…
> 
> ens-something (annoying name made of multiple letters and digits) is the 
> new name for eth0

Or eno for ethernet too. My ethernet started out as eno2 when I
did the initial install and this changed to eno1 when I disabled the
onboard wireless in the bios.

-- 
Tixy 



Re: MPV Player...

2023-02-27 Thread Tixy
On Mon, 2023-02-27 at 08:04 +0100, Luna Jernberg wrote:
> There is newer mpv in the http://deb-multimedia.org/ testing repos (if
> you feel like running testing)

Two reason's not to recommend that: deb-multimedia isn't run by the
Debian project and mixing in stuff from another release it fraught with
problems. As is oft pointed out here, see...
https://wiki.debian.org/DontBreakDebian

-- 
Tixy



Re: cpu supported?

2023-02-18 Thread Tixy
On Sat, 2023-02-18 at 07:09 +, piorunz wrote:
> On 18/02/2023 06:17, Tom wrote:
> 
> 
> > It also has 2 drives one is chip and the other spins.
> 
> What?
> 

I'm guessing that's one SSD and one spinning magnetic media hard drive.

-- 
Tixy



Re: bookworm

2023-02-09 Thread Tixy
On Thu, 2023-02-09 at 11:38 +0100, Dariusz wrote:
> Hi, is there any chance for WiFi firmware-atheros for Bookworm in the 
> estimated time?

If you mean firmware-atheros appears to be missing, it could be that
it's moved from the 'non-free' section of the archive, to the new
section 'non-free-firmware'. See...
https://lists.debian.org/debian-user/2023/01/msg00706.html

-- 
Tixy



Re: Initramfs/ Initrd Resolution

2023-01-30 Thread Tixy
On Mon, 2023-01-30 at 12:48 +0100, basti wrote:
> Is there an option to setup the resolution in the Initramfs (initrd)?

I set the linux console mode with via a grub config option in
/etc/default/grub. i.e.

GRUB_GFXPAYLOAD_LINUX=keep

Which I believe stops grub changing the display mode before starting
linux, and linux itself just uses whatever mode the hardware is set to.

-- 
Tixy



Re: switch from IDE to AHCI causes not finding root FS

2023-01-28 Thread Tixy
On Sat, 2023-01-28 at 10:47 +0100, didier gaumet wrote:
> I would think you only need to regenerate initramfs (after having
> switched the UEFI/BIOS to AHCI instead of IDE) because last time it was
> generated with the dep parameter, the PC was in IDE mode so AHCI was
> not included.
> 
> if you want to explicitely specify modules for AHCI usage, I think the
> name of the module is simply AHCI:
> https://wiki.archlinux.org/title/Mkinitcpio/Minimal_initramfs
> 

Or, if there's no particular reason to try for a minimal initramfs,
edit /etc/initramfs-tools/initramfs.conf to put it back to what seems
to be the default 'MODULES=most' rather than 'MODULES=dep'.

-- 
Tixy



Re: Vulnerable git in bullseye - what's the process?

2023-01-27 Thread Tixy
On Fri, 2023-01-27 at 11:28 +, Brad Rogers wrote:
> On Fri, 27 Jan 2023 11:36:12 +0100
> "Sijmen J. Mulder"  wrote:
> 
> Hello Sijmen,
> 
> The security-tracker CVE page you cited has links to all the
> information you requested.
> 

Does it? It links to a bug which says it's been fixed in sid. And the
PTS shows it was fixed yesterday in old-stable and sid. But no sign I
can see that anything is being done for stable (Bullseye) which is what
Sijmen asked about. (I wouldn't know where to look for stable security
update activity).

-- 
Tixy



Re: USB enumeration issue

2023-01-25 Thread Tixy
On Wed, 2023-01-25 at 08:06 +, Tixy wrote:
> My final idea: have you used a wireless keyboard or mouse? 

or wireless headphones.



Re: USB enumeration issue

2023-01-25 Thread Tixy
On Tue, 2023-01-24 at 19:36 -0800, Matthew McAllister wrote:
[...]
> BTW, this is what the logs contained when the device was last
> successfully started. (It is indeed the bluetooth chip; no idea why
> it's not a PCI device.)

My final idea: have you used a wireless keyboard or mouse? (I'm
clutching at straws here, as I don't think they use the bluetooth
standard). I have wireless devices on one of my machines and the
receiver for the PC is a tiny USB device that only sticks out about 5mm
from the case, just wondered if you have such a thing plugged in and
overlooked.

-- 
Tixy



Re: USB enumeration issue

2023-01-24 Thread Tixy
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port numbers may change over time and depend on
> > what's plugged in).
> 
> That was the perfect piece of advice. I found the exact log where the
> issue began:
> 
> 2023-01-06T20:20:28.225698-08:00 cockpit kernel: [   25.515977] usb 1-5: 
> Failed to suspend device, error -110

That timestamp is half a day before linux 6.1 accepted into unstable
[1] so in theory the problem started before the new kernel, but the
timing looks suspicious, so I think comparing the first log you have
for booting with 6.1 with the last log with 6.0 would be invaluable.

(The device numbers could change between kernel versions if enumeration
order changed, so that TIMEOUT error (-110) could be related to a
different device).

Also, just try booting using linux 6.0 to see if that fixes anything.
That still seems to available, so if you uninstalled it, it can be
reinstalled.

[1] 
https://tracker.debian.org/news/1406376/accepted-linux-614-1-source-into-unstable/

-- 
Tixy



Re: USB enumeration issue

2023-01-24 Thread Tixy
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> > Also, looking at old kernel logs from back when it was working
> > would be useful (/var/log/kernel.N.gz where N if the biggest number
> > there is). Hopefully that will show what device is on usb 1-5
> > (though I believe port numbers may change over time and depend on
> > what's plugged in).
> 
> That was the perfect piece of advice. I found the exact log where the
> issue began:
> 
> 2023-01-06T20:20:28.225698-08:00 cockpit kernel: [   25.515977] usb 1-5: 
> Failed to suspend device, error -110
> 

What would be useful is the log of the boot before that, where usb 1-5
worked, to see log messages for 'usb 1-5' to find out what it is.

-- 
Tixy



Re: USB enumeration issue

2023-01-24 Thread Tixy
On Mon, 2023-01-23 at 19:54 -0800, Matthew McAllister wrote:
> Coincidentally, this is also exactly when the bluetooth on my motherboard 
> stopped working. (The WiFi is on the same MT7921K chipset and still works 
> weirdly).
> 
> Can you suggest any steps other than straight-up RMA'ing the mobo? (That 
> might fix the USB-C as well, heh.)

I would still place my bet on a software problem.

Was the boot with the first time of failure the same kernel version and
wifi firmware as the previous successful boot?  If the problem stated
with a new kernel or firmware version then that would be a smoking gun,
and you could prove it by booting the earlier kernel or reverting
firmware. 

-- 
Tixy






Re: USB enumeration issue

2023-01-23 Thread Tixy
On Mon, 2023-01-23 at 13:54 +0500, Alexander V. Makartsev wrote:

[...]
> > [   66.959391] usb 1-5: device not accepting address 5, error -71
> > [   66.960945] usb usb1-port5: unable to enumerate USB device
> > 
> > This occurs when *no USB cables are plugged in*. The kernel is 
> > stalling the entire boot process to enumerate some internal USB hub, I 
> > assume.
> > 
> > My front USB-C is broken as far as I can tell, so I tried unplugging 
> > the header. The issue persisted.
> > 
> > The front USB 3.0 work correctly and I couldn't get the header 
> > unplugged anyways, so I didn't test if that was the issue.
[...]

On 23.01.2023 11:40, Matthew McAllister wrote:
> Start troubleshooting process by unplugging all USB devices,
> 

He said he did that ;-)

> [...]
> There is one additional thing, if your "PC" is a laptop, then it is 
> possible there is an internal device inside that uses USB bus to 
> function, e.g. WiFi adapter, WWAN adapter, etc.

He also said he unplugged the header for the front USB so guess that's
a desktop.

Another things to try is booting using an older kernel, presumably
there is one still installed as Debian doesn't automatically uninstall
kernels.

Also, looking at old kernel logs from back when it was working would be
useful (/var/log/kernel.N.gz where N if the biggest number there is).
Hopefully that will show what device is on usb 1-5 (though I believe
port numbers may change over time and depend on what's plugged in).

-- 
Tixy



Re: Cloning a disk: partclone?

2023-01-20 Thread Tixy
On Fri, 2023-01-20 at 14:56 +0200, Anssi Saari wrote:
> Tixy  writes:
> 
> > Surely it's also straightforward to just copy the data in the partition
> > then resize the filesystem...
> > 
> >  cp /dev/sdX1 /dev/sdY1
> >  resize2fs /dev/sdY1
> 
> Sure. Partclone, since the OP asked about that, can speed this up for a
> partition since it's smart enough to not copy parts of the partition
> that aren't in use.

Which apart from speed would probably be good if the target is an SSD,
as the disk does have to allocate flash memory for that unused data.
(I'm thinking of the discussion about SSDs we had here a few weeks
ago).

-- 
Tixy



Re: Cloning a disk: partclone?

2023-01-19 Thread Tixy
On Thu, 2023-01-19 at 19:56 +, Tixy wrote:
> 
> Surely it's also straightforward to just copy the data in the partition
> then resize the filesystem...
> 
>  cp /dev/sdX1 /dev/sdY1
>  resize2fs /dev/sdY1
> 
> Assuming you've already partitioned the target disk /dev/sdY to how you
> want it. (And assuming the filesystem is ext2..ext4)

Addendum: If you want to check the copy is successful (good idea) you
can

  cmp /dev/sdX1 /dev/sdY1

before resizing it.



Re: Cloning a disk: partclone?

2023-01-19 Thread Tixy
On Thu, 2023-01-19 at 20:34 +0100, DdB wrote:
> Am 19.01.2023 um 19:49 schrieb Tom Browder:
> > On my main PC, I would like to clone my boot drive onto another disk for
> > 2 reasons:
> > 
> > 1. Use a larger disk for the main drive
> > 2. Create an emergency recovery disk
> > 
> > A new Debian package to me is "partclone". Questions:
> > 
> > + Can that be used for both purposes?
> > 
> > + Can it do a complete clone on an active disk? Or do I need a live CD
> > or USB stick?
> > 
> > Thanks.
> > 
> > -Tom
> When i set up a similar job on my neighbor's home comp, i chose
> http://www.fsarchiver.org/
> Straightforward, yet flexible, can deal with resizing partition(s) and
> such. I use it from a live DVD, that is available thru grub menu, no
> media involved.

Surely it's also straightforward to just copy the data in the partition
then resize the filesystem...

 cp /dev/sdX1 /dev/sdY1
 resize2fs /dev/sdY1

Assuming you've already partitioned the target disk /dev/sdY to how you
want it. (And assuming the filesystem is ext2..ext4)

-- 
Tixy



Re: Passwords

2023-01-17 Thread Tixy
On Tue, 2023-01-17 at 09:51 +0100, DdB wrote:
> 
> But somehow, i feel there could be more caring about avoiding to teach
> future hackers by accident. Is this kind of lesson appropriate for a
> users list?

Yes. It's a common occurrence, and trivial to deal with - if you have
physical access to the computer or disk. And if you have such access 
then that password isn't actually protecting anything you couldn't do
without the password.

If you google "linux forgotten root password" then you will find these
techniques are explained all over the web, e.g. Redhat's site, Arch
wiki etc.

-- 
Tixy

 



Re: Python curses

2023-01-10 Thread Tixy
On Tue, 2023-01-10 at 09:18 -0500, pa...@quillandmouse.com wrote:
> Follow-up question, in case you know this too: apparently, when you
> purchase a Kindle book and read it via the Kindle app on your Android
> phone, the document doesn't exist on the phone itself. I've
> plugged my phone into my PC and examined every directory under Android
> and the SIM card, and I can't find a trace of the Kindle book I
> purchased.

Because you didn't purchase it. You paid for the right to read it
whenever you want, until such time as Amazon decided to shut down the
Kindle service that is. Or it decides you shouldn't have been sold it
and deletes it. [1] That's how digital 'purchases' work.

> 
> I've installed Calibre, but without having the Kindle file in hand, I
> can't convert it. So... any idea how to actually pry the Kindle file
> out of Amazon's greedy hands, so I can point Calibre at it?

I doubt that's possible because I assume these things are protected
with DRM to stop people from copying them, or escaping the clutches of
Big Corp who want to monitor what you do in order to sell you more
stuff.

[1] https://www.theregister.com/2009/07/18/amazon_removes_1984_from_kindle/

-- 
Tixy



Re: How can I check (and run) if an *.exe is a DOS or a Windows program?

2023-01-07 Thread Tixy
On Sat, 2023-01-07 at 08:47 -0500, Jude DaShiell wrote:
> If I remember correctly, dos and windows .com and .exe programs all have
> control-z as their first character.  The file command may also help.

If I remember correctly, COM files have no header, the first byte is
the first machine code instruction of the program, and it expects to be
loaded at address 100h in memory. (As CP/M did).

EXE files start with the ASICI chars 'M' and 'Z' (not sure on order).
And they'll be some header information too, I beleive. It'll all be in
a wikidepdia article I'm sure.

Yep, I remembered correctly...

https://en.wikipedia.org/wiki/COM_file
https://en.wikipedia.org/wiki/DOS_MZ_executable

And there seems to be a newer format used when Windows was
introduced...

https://en.wikipedia.org/wiki/New_Executable

-- 
Tixy



Re: Wear levelling on micro-sd cards

2022-12-27 Thread Tixy
On Tue, 2022-12-27 at 13:47 +, Tim Woodall wrote:
> On Tue, 27 Dec 2022, Tixy wrote:
> 
> > On Mon, 2022-12-26 at 21:37 +, Tim Woodall wrote:
> > > > 
> > > But now I'm concerned about disks in a raid-1. Everything gets written
> > > when the raid rebuilds.
> > > 
> > > I've found fstrim - but that only seems to be for filesystems.
> > > 
> > > How do I tell the card that the free space in the VG really is free?
> > 
> > You probably can't. I've not heard of removable cards supporting the
> > 'trim' command.
> > 
> > 
> I found a issue_discards setting in lvm.conf. Set that, then created a
> LV using the remaining space and deleted it again.
> (this wasn't an sd card, was my main machine that I run in a raid-1
> configuration)
> 
> There's definitely something implemented on sd cards: fstrim works on an
> identical, working, card while it fails on my broken one.

Interesting, doing a Google search finds that SD cards do support
this... https://superuser.com/a/1554860

Though that was with an actual MMC device though, don't know about the
interfaces which now all seem to be implemented at the end of USB. In
fact the forum reply above says:

   USB to SD card adapters ("SD card readers") could support this
   command by advertising the TRIM or UNMAP commands via the USB
   storage interface, and translating these to the MMC_ERASE command,
   but I've yet to find a USB adapter which does this.
   
-- 
Tixy



Re: Wear levelling on micro-sd cards

2022-12-27 Thread Tixy
On Tue, 2022-12-27 at 11:31 +0100, Nicolas George wrote:
> Tixy (12022-12-27):
> > The card could know what blocks of flash have been written to, it's the
> > thing that has done the writing.
> 
> Indeed. And as I said already, unless the card is pathologically
> underused

You said 'unless the card is brand new'

> , “what blocks of flash have been written to” eventually
> becomes “all of them”.

Only in the case where the SD card has at some point been completely
full, and you maintain cases where that isn't true is 'pathological'.

Guess my storage uses are pathological then, because apart from the
extreme example of that restricted 4GB partition I use for a root
filesystem, my other 'normal' usage doesn't fill removable flash
storage either. E.g I copy images and videos from my digital cameras to
my PC then delete them from the cameras, and the backup storage on my
keyring I carry around isn't full. (Backup storage performance falls
badly as it fills, presumably due to lack off readily available erased
blocks, so that tells you to go buy a bigger flash stick :-)

-- 
Tixy





Re: Wear levelling on micro-sd cards

2022-12-27 Thread Tixy
On Mon, 2022-12-26 at 21:26 +0100, Nicolas George wrote:
> Tixy (12022-12-26):
> > He didn't mention filesystems.
> > 
> > The controller in the card would surely know what flash blocks contain
> > data, so writing the whole card first would reserve those blocks as
> > 'in-use' leaving just a relatively small amount of spare blocks which
> > would be available for erasure and reuse the that repeated write.
> 
> Unless the card is brand new, “what flash blocks contain data” is “all
> of them”. The information whether a block is used or not used resides in
> the filesystem data structures.
> 

The card could know what blocks of flash have been written to, it's the
thing that has done the writing. Very simplistically, if the OS writes
to sector N, card has to allocate a block of flash to contain the data
for that sector. If OS writes to sector N again, card has to get an
erased block of flash to write new sector data to, then it can erase
the old block of flash which it now knows is unused. (Note blocks are
much bigger than sectors, and the data structures and algorithms for
keeping track of what's where will be proprietary 'magic'.)

So, if like me, you have a 64GB card, with just a 4GB partition
containing a filesystem, then the OS will never have written to sectors
outside that partition and the controller on the card would never have
had to allocated flash for them. Therefore it can know about 60GB of
unused flash, plus whatever extra reserve the card was manufactured
with.

What SD cards actually do in reality though, I don't know.

-- 
Tixy



Re: Wear levelling on micro-sd cards

2022-12-27 Thread Tixy
On Mon, 2022-12-26 at 21:37 +, Tim Woodall wrote:
> > 
> But now I'm concerned about disks in a raid-1. Everything gets written
> when the raid rebuilds.
> 
> I've found fstrim - but that only seems to be for filesystems.
> 
> How do I tell the card that the free space in the VG really is free?

You probably can't. I've not heard of removable cards supporting the
'trim' command.



Re: Wear levelling on micro-sd cards

2022-12-26 Thread Tixy
On Mon, 2022-12-26 at 20:46 +0100, Nicolas George wrote:
> John Conover (12022-12-26):
> > So, the more unused SD space is better, since wear leveling writes to
> > a "bit" that has been written to fewer times.
> > 
> > To test, say with a 16 GB SD, fill the SD to all except the last 1 KB,
> > and with a looping script, write 1KB of 1's to the remainder of the
> > SD, erase the "bits," then 1KB of 0's, erase the "bits", and so on;
> > the SD card will fail within hours to a few days, (with luck-note that
> > MTBF is mean time between failures, meaning that by MTBF, half will
> > have failed, half still running; its a stochastic/probability issue;
> > it does NOT mean that all are expected to last at least 6K writes.)
> > 
> > Doing the same test without filling to the last 1 KB, and the SD card
> > will last a very long time, (about 16 million total writes.)
> 
> Are you suggesting that the microcontroller of the SD card is capable of
> decoding filesystem data structures to find out which sectors are
> unused?

He didn't mention filesystems.

The controller in the card would surely know what flash blocks contain
data, so writing the whole card first would reserve those blocks as
'in-use' leaving just a relatively small amount of spare blocks which
would be available for erasure and reuse the that repeated write.

However, ff you only ever used the first few GB (say by putting a
filesystem on a partition a fraction the size of the card). Then
there's lots of unused flash blocks that can be cycled through by any
ware levelling algorithm the card implements.

-- 
Tixy



Re: sleep on a low-usage NAS ?

2022-12-12 Thread Tixy
On Tue, 2022-12-13 at 08:39 +0800, jeremy ardley wrote:
[...]
> Ideally, I'd like it to go to sleep after 30 minutes of inactivity, but 
> wake more or less instantly when a new smb connection is initiated.

Look at the -S option to the 'hdparm' command.

I find disks seem to occasionally forget their power settings, so I
reissue the command in my script that does some daily backup tasks.

[...]
> I need advice on what else I can do to keep the device with disks unspun 
> for most of the day, yet still be available almost immediately when 
> other clients on the LAN need some NAS services.
> 

It won't be 'immediate' as it takes time for the motor to get a disk
spinning at the correct speed, about 3 seconds for my 3 inch drives.

-- 
Tixy



Re: Debian failed

2022-12-05 Thread Tixy
On Mon, 2022-12-05 at 16:20 +0800, Bret Busby wrote:
> Perhaps, the original poster should install and use, Debian Experimental?
> 
> It seems fitting...
> 
> :)

I know that wasn't a serious suggestion, but thought I would point out
that 'unstable' (AKA 'sid') is the bleeding edge in-development
distribution and 'experimental' doesn't contain a full distribution,
it's just a place for developers to distribute experimental packages.

-- 
Tixy



Re: hangs at boot

2022-11-30 Thread Tixy
On Thu, 2022-12-01 at 01:36 +0100, jd wrote:
> On 2022-11-30 18:52, Hans wrote:
> > Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd:
> > 
> > Try to deinstall cups and remove any usb cameras. I had had the problem, 
> > that
> > cups detected an usb camera as a printer and then stopped booting.
> 
> 
> I tried removing all cups packages, then it just stalled at Unattended 
> upgrades shutdown instead.
> 
> So I tried disabling that, and now it stalls at Hostname Service.
> 
> I'm guessing there's some underlying issue that hasn't got anything to 
> do with these services but I have no idea what it might be.

The above, and presumably 'remote CUPS printers' in the earlier post,
involve the network and related services like DNS or DHCP.

-- 
Tixy 



Re: blacklist mei_me?

2022-11-15 Thread Tixy
On Tue, 2022-11-15 at 11:10 +0100, hw wrote:
> Hi,
> 
> this module causes delays when booting and I'm finding this in dmesg:
> 
> 
> [   14.889003] mei_me :00:16.0: hw_reset failed ret = -62
> [   20.009003] mei_me :00:16.0: hw_reset failed ret = -62
> [   25.129003] mei_me :00:16.0: hw_reset failed ret = -62
> [   25.129315] mei_me :00:16.0: reset: reached maximal consecutive resets:
> disabling the device
> [   25.129797] mei_me :00:16.0: reset failed ret = -19
> [   25.130086] mei_me :00:16.0: link layer initialization failed.
> [   25.130431] mei_me :00:16.0: init hw failure.
> [   25.130745] mei_me :00:16.0: initialization failed.
> 
> 
> Should I just blacklist it or is that a bad idea?  Apparently whatever it is 
> for
> gets disabled anyway and it doesn't seem to be a disadvantage other than 
> causing
> delays.
> 

If you use Google to search for mei_me you'll lots o similar reports
going back a decade, e.g. https://bbs.archlinux.org/viewtopic.php?id=168403

These seem to suggest blacklisting the module or disabling Management
Engine Interface in the BIOS.

-- 
Tixy



Re: sid - no sound on speakers

2022-11-13 Thread Tixy
On Sat, 2022-11-12 at 19:01 +1000, David wrote:
> What are you running?
> Stable, Testing, Unstable?

The subject line if prefixed with 'sid'. So Unstable I presume.

-- 
Tixy



Re: "usermod: user user is currently used by process" while using (trying to) thunderbird to back up my gmail account's data ...

2022-11-06 Thread Tixy
On Sun, 2022-11-06 at 15:38 +, Albretch Mueller wrote:
[...]
> $ usermod --move-home --home "${_NEW_HOME}" "${_WHMI}"
> usermod: user user is currently used by process 1141
> 
> $ sudo ps -aux | grep 1141
> user1141  0.0  0.1  15600  9144 ?Ss   Nov05   0:00
> /lib/systemd/systemd --user
> user   50636  0.0  0.0   6244   712 pts/0S+   06:42   0:00 grep 1141
> 
>  Unless they are both trying to exclusively access /etc/passwd, I
> can't understand how /lib/systemd/systemd could possibly relate to
> usermod.
> 
>  Any suggestions?

Probably a red herring, but I remember reading a while ago that
managing users home directories was another thing systemd was trying to
take over. A quick google search leads to things like:

https://opensource.com/article/22/3/manage-users-home-directory-systemd-homed
https://systemd.io/HOME_DIRECTORY/

So might be worth running the 'homectl' command to see if it exists, it
doesn't on my the Debian 11 install. So like I said, probably a red
herring.

-- 
Tixy



Re: Cheap NAS

2022-10-20 Thread Tixy
On Thu, 2022-10-20 at 17:41 +0700, Max Nikulin wrote:
> On 17/10/2022 22:50, Tixy wrote:
> > # Set spindown time for disk
> > if NAS1=`findmnt -n -o SOURCE /nas1/main`; then /sbin/hdparm -S120 
> > $NAS1; fi
> > 
> > 
> > 
> > 
> > Rather than hard code the disk as /dev/sdc I use 'findmnt' to get the
> > disk name from the point it's mounted at (/nas1/main in this case).
> 
> Are there known problems with using e.g. WWN (/dev/disk/by-id/... in 
> /etc/hdparm.conf) for per-disk configuration?

I didn't know of /dev/disk/by-id/wwn-* file or of /etc/hdparm.conf
until I just googled that, that looks like they would be designed for
the task. Assuming however that you can rely on udev (?) having already
created those paths before hdparm is run. (I seem to remember having
had race conditions related to those paths in the past.)

In my case, I spread out wear by rotating disks through different uses:
main NAS drive, nearline backup mirror of that, and offline backup. So
I decided rather than mount by UUID or similar, I'd mount by filesystem
label instead, then I could just relabel the disks when I rotated them.

Of course, having just written that, I realise I don't need findmnt and
can just use the label in /dev/disk/by-label/ (again, assuming they
exist in time).

-- 
Tixy





  1   2   3   4   5   6   >