Re: Edit NIC Address

[Felix Miata]

David composed on 2024-01-04 04:30 (UTC):

> With the latest Debian I'm trying to find the file to edit to change
> the IP address of a remote box, can anybody point me in the correct
> direction please?

> I can SSH into this box, but cannot find the file to edit.

Traditionally it would be in /etc/network/interfaces used by ifupdown. Mine is 
in
/etc/systemd/network/eth0.network because I'm using systemd-networkd. Where
NetworkMangler users keep theirs I have no information. If you can search files 
in
the /etc/ tree for string 192.168. or 10.0. or 172.16. likely you'll find it.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Edit NIC Address

[David]

Morning Group,

With the latest Debian I'm trying to find the file to edit to change
the IP address of a remote box, can anybody point me in the correct
direction please?

I can SSH into this box, but cannot find the file to edit.

Thank you,

David.

Re: kbrequest as in older /etc/inittab

[Mike McClain]

On Mon, Jan 01, 2024 at 10:36:41AM -0600, David Wright wrote:
> Is the history of this issue relevant?
>   https://forums.raspberrypi.com/viewtopic.php?t=282768

David the most relevant part of that old post is the last line.

> On Mon, 1 Jan 2024 13:53:44 -0500 Greg Wooledge wrote:
> Oh, it's the same *name*.  Huh.  So, Mike, whatever you figured out in
> 2020, you entirely forgot, and now you're starting over in a new forum?

Yes, Greg, my name is still Mike. Have you always been Greg?

If you think I figured it out in 2020 you clearly didn't read that
post. I suggest you go back and read the last line at least.

> What are you actually trying to do?  If all you want are a bunch of
> additional text consoles, you can simply increase the number of gettys
> by editing the /etc/systemd/logind.conf file:

I don't think I can state any more clearly what I'm trying to do than
'to tie a call to openvt to Alt Up'. I'm assuming you don't know how
to do that either.

You're quite right you can increase the number of gettys
and you can log into every one of them before you can use them.

I'd like to thank you for the reference to logind.conf. I've been
looking for a while where the login on tty6 was coming from having set
ACTIVE_CONSOLES="/dev/tty[1,3]" in /etc/default/console-setup.
You are often helpful.

One of these days I'll find a solution, I thought triggerhappy might
do but so far haven't made that work either.

Be well fellas,
Still Mike
--
1984 was not meant as a blueprint for democratic governments.

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Jeffrey Walton]

On Thu, Jan 4, 2024 at 6:18 PM Joel Roth  wrote:
>
> On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> > In theory, it should
> > be as simple as refind-install. So the only reason I could guess to be the
> > reason would be that rEFInd might not be capable of handling LUKS, which
> > would be quite disappointing.
>
> My experiences are with vanilla filesystems only. LUKS
> obviously has specific requirements. Perhaps you could try
> having a root partition that is unencrypted?

Be careful of that. Someone who is encrypting the filesystem likely
has password protected the firmware, disabled booting from USB sticks,
and disabled the root account so a rescue console cannot be used to
sidestep access restrictions. That is, you don't want to hand out a
passwordless root shell in rescue mode. Also see
.

Jeff

NFS: IPV6

[Pocket]

Where can I find information on how to configure NFS to use ipv6 
addresses both server and client.


I haven't found any good information on how to do that and what I did 
find was extremely sparce.


I have NFS mounts working using ipv4 and want to change that to ipv6


--
Hindi madali ang maging ako

Re: Content of /etc/ethers

[Rick Thomas]

Thank you for mentioning "dnsmasq".  I do the same thing on my home network and 
it works very well.
Rick

On Wed, Jan 3, 2024, at 9:29 PM, Stefan Monnier wrote:
>> Which tools read /etc/ethers, what do they expect in there, what do
>> they do with the contents?
>
> AFAIK it's mostly unused nowadays.  I have such a file on my DHCP
> server, where `dnsmasq` reads it (lets me give static IP addresses to
> some of my machines, even though they're configured via DHCP,
> i.e. they're "dynamically static").
>
>
> Stefan

Re: Possibly broken Grub or initrd after updates on Testing

[Richard Rosner]

On 04.01.24 19:02, David Wright wrote:

Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?

Cheers,
David.


Let's hope the mailing list let's this go through.


Keep in mind, this is based on the assumption that your whole / 
partition is LUKS encrypted (in my case now LUKS2). 
"root-partition-UUID" is the UUID that's shown in Disks or on the Grub 
screen for the decryption password prompt. Now, I can't say for sure 
what "root-partition-UUID2" is, but that's what seems to be symlinked to 
/dev/dm-0 and with blkid, one of the entries will look like this:



/dev/mapper/luks-: UUID="" 
BLOCK_SIZE="4096" TYPE="ext4"



So maybe it's just some kind of virtual UUID for the decrypted root 
partition.



#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if loadfont unicode ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod cryptodisk
insmod luks2
insmod gcry_rijndael
insmod gcry_rijndael
insmod gcry_sha256
insmod ext2
set root='cryptouuid/'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='cryptouuid/' 

else
  search --no-floppy --fs-uuid --set=root 
fi
insmod png
if background_image /boot/grub/.background_cache.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
    set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class 
gnu --class os $menuentry_id_option 
'gnulinux-simple-' {

    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_gpt
    insmod cryptodisk
    insmod luks2
    insmod gcry_rijndael
    insmod gcry_rijndael
    insmod gcry_sha256
    insmod ext2
    set root='cryptouuid/'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root 
--hint='cryptouuid/' 

    else
      search --no-floppy --fs-uuid --set=root 
    fi
    echo    'Loading Linux 6.5.0-5-amd64 ...'
    linux    /boot/vmlinuz-6.5.0-5-amd64 
root=UUID= ro  quiet

    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-6.5.0-5-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-' {
    menuentry 'Debian GNU/Linux, with Linux 6.5.0-5-amd64' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-6.5.0-5-amd64-advanced-' {

    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_gpt
    insmod cryptodisk
    insmod luks2
    insmod gcry_rijndael
    insmod gcry_rijndael
    insmod gcry_sha256
    insmod ext2
    set root='cryptouuid/'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root 
--hint='cryptouuid/' 

    else
      search --no-floppy --fs-uuid --set=root 
    fi
    echo    'Loading Linux 6.5.0-5-amd64 ...'
    linux    /boot/vmlinuz-6.5.0-5-amd64 
root=UUID= ro  quiet

    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-6.5.0-5-amd64
    }
    menuentry 'Debian GNU/Linux, with Linux 6.5.0-5-amd64 (recovery 
mode)' --class debian --class gnu-linux 

Re: Possibly broken Grub or initrd after updates on Testing

[David Wright]

On Wed 03 Jan 2024 at 22:00:20 (+0100), Richard Rosner wrote:
> On 03.01.24 21:04, Eddie wrote:
> > On 1/3/24 14:23, Richard Rosner wrote:
> > > So, since for whatever reason Grub seems to be broken beyond
> > > repair, I today tried to just replace it with rEFInd.
> > > Installation succeeded without any trouble. But when I start
> > > my system, rEFInd just asks me if I want to boot with fwupd or
> > > with the still very broken Grub. Am I missing something? Is
> > > rEFInd really just something to select between different OSs
> > > (and not just different distributions like Grub can very well
> > > do) and then gives the rest over to their bootloaders or am I
> > > missing something so rEFInd will take over all of Grubs jobs?
> > 
> > I have had very good results using "Boot-Repair" software to
> > recover Grub difficulties.
> > 
> Thanks, this actually did the job. I don't know what it was, but my
> guess is it was the step "purge Grub before reinstalling it".
> 
> 
> PS: rewrote to the old subject, as this is clearly an answer to the
> original problem, as it doesn't have anything to do with replacing
> Grub all together.

Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?

Cheers,
David.

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Joel Roth]

On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> In theory, it should
> be as simple as refind-install. So the only reason I could guess to be the
> reason would be that rEFInd might not be capable of handling LUKS, which
> would be quite disappointing. 

My experiences are with vanilla filesystems only. LUKS
obviously has specific requirements. Perhaps you could try
having a root partition that is unencrypted?

-- 
Joel Roth

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Richard Rosner]

Well, that was a bust. I accidentally didn't just format the EFI 
partition, but deleted it. So I re-created it with the help of disks and 
gparted (to leave the first 3 MB empty, I remeber that being a fix added 
kinda recently to combat bad BIOS/EFI implementations, since Windows is 
doing the same and nobody could come up with anything better.


Anyways, after installing rEFInd with no grub present, it would boot 
into rEFInd, but that's it. No boot options, nothing under F2. Also, I 
couldn't find anything helpful on the Arch Wiki page for this. In 
theory, it should be as simple as refind-install. So the only reason I 
could guess to be the reason would be that rEFInd might not be capable 
of handling LUKS, which would be quite disappointing. Maybe I'll take a 
look at systemd-boot in the next days, as I don't need any customization 
anyways, and maybe it can handle encryption (or better decryption) 
better than Grub — especially with LUKS2 grub seems a bit unreasonably slow.


On 04.01.24 11:56, Richard Rosner wrote:
Good to know that it should be possible. But as mentioned, these 
symbols only offer me to boot from grub or fwupd. F2 also doesn't show 
that much more, it merely gives me the option to boot into the BIOS 
settings. Maybe I'll have to completely purge all Grub packages, wipe 
the existing EFI partition and then try to install rEFInd. I'll have 
to check.


On Thu, Jan 4, 2024, 09:29 Joel Roth  wrote:

On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond
repair, I today
> tried to just replace it with rEFInd. Installation succeeded
without any
> trouble. But when I start my system, rEFInd just asks me if I
want to boot
> with fwupd or with the still very broken Grub. Am I missing
something? Is
> rEFInd really just something to select between different OSs
(and not just
> different distributions like Grub can very well do) and then
gives the rest
> over to their bootloaders or am I missing something so rEFInd
will take over
> all of Grubs jobs?

I boot my debian-based system with rEFInd.  Grub is not
present. A couple big icons show on the boot screen. The
small print at the bottom mentions hit F2 for more options.
On my system, F2 offers a selection among all kernels
present.

rEFInd installs into  EFI/refind/ in the EFI partition.
I originally encountered it looking for something to
boot debian on a Intel Mac. It's been trouble-free.




> On 01.01.24 21:45, Richard Rosner wrote:
> >
> >
> > On 01.01.24 21:20, Richard Rosner wrote:
> > >
> > > On 01.01.24 20:30, David Wright wrote:
> > > > On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
> > > > > On 01.01.24 18:13, David Wright wrote:
> > > > > I can boot by hand, but since this is all archived
anyways and it's
> > > > > uneccessarily difficult to find some sort of guide how
to even do
> > > > > this, it might as well be a documentation for users
having such
> > > > > troubles in the future.
> > > > >
> > > > > Also, besides the way that I have no clue how it would
have to look
> > > > > like to set up a paragraph in the grub.cfg, I simply
don't see
> > > > > anything wrong with it anyways. So I can't even look at
the grub
> > > > > settings files grub.cfg is being generated from to check
where the
> > > > > error lies.
> > > > You append the commands that you used to boot manually
with into
> > > > /etc/grub.d/40_custom, observing the comments there, and
also into
> > > > grub.cfg itself at the appropriate place (near the
bottom). The
> > > > former is so that Grub includes it in any new grub.cfg
that you
> > > > create.
> > > Good to know.
> > Edit:, never mind. Tried that, it still booted straight to the
UEFI BIOS
> > menu after entering my password. At this point, I'm seriously
> > considering slapping rEFInd on it and pray that it picks up on
> > everything automatically and fix the situation. But so should
Grub have,
> > besides the fact that I can't even be entirely sure Grub is to
blame and
> > not something else.

-- 
Joel Roth

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

[Michael Kjörling]

On 3 Jan 2024 13:25 -0700, from charlescur...@charlescurley.com (Charles 
Curley):
>> As a background process, try running something like
>> 
>> # ionice find / -xdev -type f -exec cat {} + >/dev/null
> 
> That would only reach files on the partition where it is run.

I covered that on the next few lines, which you choose not to quote.

> Since there is another operating system on this drive,

That kind of information might be helpful to include up front.

> and there are parts of
> the drive normally inaccessible to any operating system,

That's true, but it would have told you about any error in any
accessible data _and_ also told you which file or directory was
affected if that was the case. If the error is in an inaccessible
portion of the drive and the system is working normally aside from a
note in SMART data, then it would stand to reason that the error would
be in an unused location; thereby not likely to affect usage (because
a known bad spot would be reallocated elsewhere by the firmware on the
next write).

Also, badblocks too will only deal with user-accessible blocks; if the
drive already had remapped a bad location, for example as a part of a
write to an identified bad block, the original error would be
invisible to badblocks even if it still was an error.


On 3 Jan 2024 16:27 -0700, from charlescur...@charlescurley.com (Charles 
Curley):
> OOPS! -w is the destructive test. I now have a hard drive full of 0x00s.

After restoring your most recent backup, consider doing a fstrim to
TRIM unused blocks.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: [HS] LINUX ENTREPRISE

[steve]

Le 04-01-2024, à 11:20:37 +, Yves Rutschle a écrit :


On Wed, Jan 03, 2024 at 01:49:21PM +0100, ilario.quinson@e.email wrote:


svp  c'est quoi CISO?


Chief Information System Officer, la version shakespearienne de RSSI.


May I correct? It's

Chief Information __Security__ Officer

s.

Re: Change suspend type from kde menu

[Max Nikulin]

On 04/01/2024 22:21, Valerio Vanni wrote:

Il 04/01/2024 15:48, Max Nikulin ha scritto:


Is it really necessary to kill kaffeine or it is enough to pause or to 
stop playing? It might be possible using a D-Bus query.

[...]

If it's started normally, it's enough to stop playing
But how would you try to request it to stop?


I would play with "busctl --user", "busctl --user tree SERVICE", "busctl 
--user introspect SERVICE OBJECT" to figure out if suitable methods are 
available.



If it's started with "-lastchannel" no, you have to close it.
But then you have also to request it to play again.


Is there an action that releases the device? "ls -l /proc/PID/fd" to check.

Ideally kaffeine should implement the Inhibit interface and should close 
devices on suspend or on user session switch.

Re: Change suspend type from kde menu

[Greg Wooledge]

On Thu, Jan 04, 2024 at 03:07:59PM +0100, Valerio Vanni wrote:
> Il 03/01/2024 17:41, Greg Wooledge ha scritto:
> > The su command is not an ideal choice for this, in fact.  The setpriv(1)
> > command is better suited for running programs as other user accounts,
> > without doing crazy PAM stuff like su does.
> 
> Can you explain better?

http://jdebp.info/FGA/dont-abuse-su-for-dropping-privileges.html

Re: Change suspend type from kde menu

[Valerio Vanni]

Il 04/01/2024 15:48, Max Nikulin ha scritto:

On 04/01/2024 21:03, Valerio Vanni wrote:

 kaffeine_killed=$(/usr/bin/killall kaffeine 2>&1)
 echo $kaffeine_killed > /temp/kafstate.txt
 /usr/bin/sleep 2
 /usr/sbin/rmmod cx23885


Is it really necessary to kill kaffeine or it is enough to pause or to 
stop playing? It might be possible using a D-Bus query. My expectation 
is that the device should be closed.


I choosed to kill it because it seemed easier.
If it's started normally, it's enough to stop playing
But how would you try to request it to stop?

If it's started with "-lastchannel" no, you have to close it.
But then you have also to request it to play again.

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

[Max Nikulin]

On 04/01/2024 03:25, Charles Curley wrote:

I decided
instead to boot to a USB stick and run badblocks. The read-only test
took 12 minutes and reported no errors.

I now have a writing test (-w) running. It has reported no failures on
its first pass.


Is badblock writing test useful for SSD taking into account wear 
leveling? Each write should be mapped to another physical address. All 
errors should be handled by firmware.


To test low-end USB pen drives and SD cards there is the f3 (Fight Flash 
Fraud or Fight Fake Flash) tool, however such test should not be 
necessary for a SATA SSD.


Have you checked that no firmware update is available for this drive?

I have experienced just a few failures of HDD. It may be irrelevant for 
SSD, but in the case of HDD I would replace the disk reporting 
Current_Pending_Sector as soon as possible. It seems, repeating reports 
from smartd are intentional.


On the other hand the "VALUE" has not decreased and is still 100, and 
the attribute is not marked as "pre-fail". Perhaps there is not reason 
to worry to much.


I am unsure concerning accounting if an error happens during reading a 
file then the file is deleted without overwriting and the address range 
is marked unused (trimmed).

Re: Nvidia driver on Debian 10

[Franco Martelli]

On 03/01/24 at 19:28, Thomas Anderson wrote:

Thanks a lot, Macro!

it worked. Sorry for delay, I got side tracked with "my day" =)

On 03/01/2024 12:03, Marco Moock wrote:

Am 03.01.2024 um 11:52:59 Uhr schrieb Thomas Anderson:


Here is the output. Wow, a lot.

All those lines with ii at the beginning mean the package is installed.

apt remove *nvidia* -s

Check if the result is ok and then run it without -s (-s only
simulates).





Give it a try to nouveau driver, here it works very well with kernel 
6.1.55 the only drawback I have is to restart the windows compositor 
when I suspend to RAM, good luck


Cheers
--
Franco Martelli

Re: Change suspend type from kde menu

[Max Nikulin]

On 04/01/2024 21:03, Valerio Vanni wrote:

     kaffeine_killed=$(/usr/bin/killall kaffeine 2>&1)
     echo $kaffeine_killed > /temp/kafstate.txt
     /usr/bin/sleep 2
     /usr/sbin/rmmod cx23885


Is it really necessary to kill kaffeine or it is enough to pause or to 
stop playing? It might be possible using a D-Bus query. My expectation 
is that the device should be closed.

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

[Charles Curley]

On Thu, 4 Jan 2024 11:58:54 +0100
 wrote:

> > 
> > OOPS! -w is the destructive test. I now have a hard drive full of
> > 0x00s. I should have used the -n option. However, it reported no
> > failures.  
> 
> Ouch, I hope you had a backup.

All the essential stuff, yes.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Change suspend type from kde menu

[Valerio Vanni]

Il 03/01/2024 17:41, Greg Wooledge ha scritto:


The UID of 1000 will have to be verified, as well as the YOURUSER.
UID 1000 is what Debian uses for the initial user account that's
created during installation, but if for some reason that's not the
account who's currently logged in, then obviously this won't work.


In my case it's ok


The su command is not an ideal choice for this, in fact.  The setpriv(1)
command is better suited for running programs as other user accounts,
without doing crazy PAM stuff like su does.


Can you explain better?


It also has the advantage
of not needing a username -- it can work with just the UID.

 uid=1000 gid=1000
 setpriv --reuid "$uid" --regid "$gid" --init-groups \
   env XDG_RUNTIME_DIR=/run/user/"$uid" DISPLAY=:0 XDG_CURRENT_DESKTOP=KDE \
   keffeine >/dev/null 2>&1 &


In a (used like a) single user system like this, I know both username 
and uid.

In a multi-user one, you have to find them. And it doesn't seem simple.

Re: Change suspend type from kde menu

[Valerio Vanni]

Il 03/01/2024 23:52, Valerio Vanni ha scritto:

Il 03/01/2024 17:18, Franco Martelli ha scritto:

On 02/01/24 at 19:15, Valerio Vanni wrote:

This way, I don't have to remember to close kaffeine before suspend.


If you have Kaffeine always running on your system you can try this 
script:


I had an idea to do a relaunch, but it's not always running.


Now I've done this, to relaunch only if it was running:

--
#!/bin/bash
case "$1" in
pre)
#code execution BEFORE sleeping/hibernating/suspending
kaffeine_killed=$(/usr/bin/killall kaffeine 2>&1)
echo $kaffeine_killed > /temp/kafstate.txt
/usr/bin/sleep 2
/usr/sbin/rmmod cx23885
;;
post)
#code execution AFTER resuming
/usr/sbin/modprobe cx23885
/usr/bin/sleep 3
kaffeine_killed=$(cat /temp/kafstate.txt)
if [[ $kaffeine_killed == "" ]]; then
/usr/bin/su valerio -c 'XDG_RUNTIME_DIR=/run/user/1000 
DISPLAY=:0 XDG_CURRENT_DESKTOP=KDE /usr/bin/kaffeine --lastchannel 
>/dev/null 2>&1 &'

fi
rm -f /temp/kafstate.txt
;;
esac

--

Re: Content of /etc/ethers

[Fred]

On 1/3/24 18:07, Steve Keller wrote:

Which tools read /etc/ethers, what do they expect in there, what do
they do with the contents?  Is it only used to show names to a user or
take names from a user instead of MAC addresses, like in tcpdump?

The Linux man page says the entries in /etc/ethers should be numeric
IP addresses or names which can be resolved by DNS, while the FreeBSD
man page says there should be fully qualified names in /etc/ethers
which should also be in /etc/hosts.

But does really some tool get a MAC address from somewhere, converts
it to a name using /etc/ethers, and then expects to resolve that name
into an IP address?

I would like to put names of hosts or interfaces in there, which don't
necessarily have an IP address or no entry in /etc/hosts or DNS, like
switches, access points or routers with multiple interfaces,
interfaces of a Linux bridge, etc.

And may the entry in /etc/ethers contain a '.' to separate a name and
an interface number or VLAN ID, like host.0 and host.1 for the LAN and
WLAN interface?

Steve


Hello,

My local network uses static manually assigned IP addresses rather than 
DHCP.  Some equipment I designed needs to get an IP address so I 
implemented RARP which is fairly simple.  The /etc/ethers file is read 
by one computer on the network when it receives an RARP request and 
reports back the requester's IP address.  There is an RARP server in the 
Debian packages.


Best regards,
Fred

Re: The current package wpasupplicant doesn't support WPA3-Personal authentication. What alternatives to it exist?

[debian-user]

Greg Wooledge  wrote:
> On Thu, Jan 04, 2024 at 12:04:52AM +0100, Stella Ashburne wrote:
> > >   https://packages.debian.org/bookworm/wpasupplicant
> > >  
> > The main heading of that web page is Package: wpasupplicant
> > (2:2.10-12)
> > 
> > Immediately below it is the sub-heading that states
> > 
> > client support for WPA and WPA2 (IEEE 802.11i)
> > 
> > I fail to see WPA3 mentioned therein.  
> 
> Read more.
> 
>   client support for WPA and WPA2 (IEEE 802.11i)
> 
>  wpa-supplicant is a userspace daemon handling connection and
>  authentication in wireless and wired networks, primarily secured
> with the WPA/WPA2/WPA3 protocols. This software provides key
> negotiation with the access point (WPA Authenticator), and controls
> association with IEEE 802.11i networks.

I do think Stella has a point in that the description page has a bug -
the sub-heading and the following text are not consistent. She should
raise an issue/bug report/whatever IMHO.

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Richard Rosner]

You should really re-read the FAQ that was sent in just two days ago...

On January 4, 2024 11:58:28 AM GMT+01:00, Jeffrey Walton  
wrote:
>On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner  wrote:
>>
>> Wow, what a bunch of unhelpful comments.
>>
>> First, if it wasn't for Eddie recommending boot-repair, "broken beyond 
>> repair" in fact was the very fitting term.
>
>Here was Eddie's comment" I have had very good results using
>"Boot-Repair" software to recover Grub difficulties."
>
>"Broken beyond repair" seems to be context dependent. And it seems to
>depend on the user.
>
>> Second, have you maybe considered that I've already read the home page of 
>> rEFInd and came to the same conclusion? Besides the fact that the page is 
>> virtually unreadable - both from a visual and a content point of view - I 
>> have yet to find anything indicating what it is actually capable of and what 
>> not. Because as far as I can tell, it should be able to do what I want it to 
>> do.
>
>No. You did not state it. And you did not cite something you did not
>understand. I think you are full of shit.
>
>> So please, if you don't have anything to add other than snarky remarks, just 
>> don't answer.
>
>You mean like: "So, since for whatever reason Grub seems to be broken
>beyond repair"?
>
>Jeff
>

Re: [HS] LINUX ENTREPRISE

[Yves Rutschle]

On Wed, Jan 03, 2024 at 01:49:21PM +0100, ilario.quinson@e.email wrote:
> 
> svp  c'est quoi CISO?

Chief Information System Officer, la version shakespearienne de RSSI.

Y.

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

[tomas]

On Wed, Jan 03, 2024 at 04:27:54PM -0700, Charles Curley wrote:
> On Wed, 3 Jan 2024 13:25:26 -0700
> Charles Curley  wrote:
> 
> > I now have a writing test (-w) running. It has reported no failures on
> > its first pass.
> 
> OOPS! -w is the destructive test. I now have a hard drive full of 0x00s.
> I should have used the -n option. However, it reported no failures.

Ouch, I hope you had a backup.

> -- 
> Does anybody read signatures any more?

I *never* do.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Jeffrey Walton]

On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner  wrote:
>
> Wow, what a bunch of unhelpful comments.
>
> First, if it wasn't for Eddie recommending boot-repair, "broken beyond 
> repair" in fact was the very fitting term.

Here was Eddie's comment" I have had very good results using
"Boot-Repair" software to recover Grub difficulties."

"Broken beyond repair" seems to be context dependent. And it seems to
depend on the user.

> Second, have you maybe considered that I've already read the home page of 
> rEFInd and came to the same conclusion? Besides the fact that the page is 
> virtually unreadable - both from a visual and a content point of view - I 
> have yet to find anything indicating what it is actually capable of and what 
> not. Because as far as I can tell, it should be able to do what I want it to 
> do.

No. You did not state it. And you did not cite something you did not
understand. I think you are full of shit.

> So please, if you don't have anything to add other than snarky remarks, just 
> don't answer.

You mean like: "So, since for whatever reason Grub seems to be broken
beyond repair"?

Jeff

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Richard Rosner]

Good to know that it should be possible. But as mentioned, these symbols
only offer me to boot from grub or fwupd. F2 also doesn't show that much
more, it merely gives me the option to boot into the BIOS settings. Maybe
I'll have to completely purge all Grub packages, wipe the existing EFI
partition and then try to install rEFInd. I'll have to check.

On Thu, Jan 4, 2024, 09:29 Joel Roth  wrote:

> On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> > So, since for whatever reason Grub seems to be broken beyond repair, I
> today
> > tried to just replace it with rEFInd. Installation succeeded without any
> > trouble. But when I start my system, rEFInd just asks me if I want to
> boot
> > with fwupd or with the still very broken Grub. Am I missing something? Is
> > rEFInd really just something to select between different OSs (and not
> just
> > different distributions like Grub can very well do) and then gives the
> rest
> > over to their bootloaders or am I missing something so rEFInd will take
> over
> > all of Grubs jobs?
>
> I boot my debian-based system with rEFInd.  Grub is not
> present. A couple big icons show on the boot screen. The
> small print at the bottom mentions hit F2 for more options.
> On my system, F2 offers a selection among all kernels
> present.
>
> rEFInd installs into  EFI/refind/ in the EFI partition.
> I originally encountered it looking for something to
> boot debian on a Intel Mac. It's been trouble-free.
>
>
>
>
> > On 01.01.24 21:45, Richard Rosner wrote:
> > >
> > >
> > > On 01.01.24 21:20, Richard Rosner wrote:
> > > >
> > > > On 01.01.24 20:30, David Wright wrote:
> > > > > On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
> > > > > > On 01.01.24 18:13, David Wright wrote:
> > > > > > I can boot by hand, but since this is all archived anyways and
> it's
> > > > > > uneccessarily difficult to find some sort of guide how to even do
> > > > > > this, it might as well be a documentation for users having such
> > > > > > troubles in the future.
> > > > > >
> > > > > > Also, besides the way that I have no clue how it would have to
> look
> > > > > > like to set up a paragraph in the grub.cfg, I simply don't see
> > > > > > anything wrong with it anyways. So I can't even look at the grub
> > > > > > settings files grub.cfg is being generated from to check where
> the
> > > > > > error lies.
> > > > > You append the commands that you used to boot manually with into
> > > > > /etc/grub.d/40_custom, observing the comments there, and also into
> > > > > grub.cfg itself at the appropriate place (near the bottom). The
> > > > > former is so that Grub includes it in any new grub.cfg that you
> > > > > create.
> > > > Good to know.
> > > Edit:, never mind. Tried that, it still booted straight to the UEFI
> BIOS
> > > menu after entering my password. At this point, I'm seriously
> > > considering slapping rEFInd on it and pray that it picks up on
> > > everything automatically and fix the situation. But so should Grub
> have,
> > > besides the fact that I can't even be entirely sure Grub is to blame
> and
> > > not something else.
>
> --
> Joel Roth
>
>

Re: The current package wpasupplicant doesn't support WPA3-Personal authentication. What alternatives to it exist?

[tomas]

On Thu, Jan 04, 2024 at 07:13:01AM +0800, Bret Busby wrote:

[...]

> Then "fail" seems to be the appropriate word.

[...]

> If all else fails, read the words in front of you.

Folks, please, no need to be snarky.

Everyone of us overlooks something at times; something obvious to
someone may escape someone else and vice versa [0].

In this case it's honestly difficult to thoroughly understand those
marketing monikers which encompas a thicket of encryption primitives,
key lengths, key exchange protocols, key management strategies, authen
protocols and the whole sh*t pie up to the top.

I don't, and I admit it.

Here's one link to the source (which I found in Debian's package page
which seems to suggest that they actually "do" WPA3 [1]. The next step
would be to find out what "to do WPA3" actually means, since there
will be probably lots of things which are optional and both parties
have to negotiate, and there's possibly a policy part where one party
can say "ah, no, if you can't do thingmajig-2 with at least 193 bits
I'm out" or something.

The next step would be to contact their mailing list and ask.

Cheers

[0] And yes, please, remind me if I fail this standard,
   which I'm sure I do at times.

[1] https://w1.fi/wpa_supplicant/

-- 
t


signature.asc
Description: PGP signature

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Pocket]

On 1/4/24 02:45, Richard Rosner wrote:

Wow, what a bunch of unhelpful comments.

First, if it wasn't for Eddie recommending boot-repair, "broken beyond 
repair" in fact was the very fitting term.


Second, have you maybe considered that I've already read the home page 
of rEFInd and came to the same conclusion? Besides the fact that the 
page is virtually unreadable - both from a visual and a content point of 
view - I have yet to find anything indicating what it is actually 
capable of and what not. Because as far as I can tell, it should be able 
to do what I want it to do.





Have you looked at this?

https://wiki.archlinux.org/title/REFInd

I don't know if it will help as I do not use REFInd nor have I any 
experience with it.


--
Hindi madali ang maging ako

Re: Re: Rescue mode when root account locked

[Jeffrey Walton]

On Thu, Jan 4, 2024 at 2:48 AM Larry Tyree  wrote:
>
> What do I do with no access to another computer?

I'm having trouble following your thread. The "Re: Re:" is throwing me off.

Is this the original message you are replying to:
?

Jeff

Re: Cuelgues aleatorios

[fernando sainz]

Hola.
Llego ya tarde a este hilo.
No se si habrás hecho un test a la RAM (con memtest) Hace unos días un
equipo de un familiar tenía un comportamiento errático y resulto ser uno de
los módulos de memoria.

Un saludo.


El jue, 4 ene 2024 a las 10:02, Luis Muñoz Fuente (<
luis.munoz@juntadeandalucia.es>) escribió:

>
> El 29/12/23 a las 16:09, Camaleón escribió:
> > Si piensas que Firefox es el culpable, crea un perfil nuevo y trabaja
> > con él a diario, para ver si el fallo persiste.
>
> Hola:
> También me pasa con Chromium, así que no creo que sea específico de
> Firefox. Me pasa aleatoriamente y puede ocurrir cada 4 días. Ayer mismo
> me pasó y tenía abiertas tres pestañas. Reinicié y al volver a abrir las
> mismas pestañas no se colgó, y eso pasa siempre, así que no puedo
> reproducir el error. El sistema se queda totalmente colgado, como
> comenté, no puedo acceder por ssh y las teclas sysrq no hacen
> absolutamente nada, y comprobé que funcionan correctamente con el equipo
> sin colgarse. He visto por internet que a más gente le pasa lo mismo con
> mi procesador AMD Ryzen 5 1600X, independientemente del sistema
> operativo, pero no sé si será esa la causa. También hice un guión de
> bash para volcar a un archivo cada tres segundos los procesos que más
> cpu consumen y cuando se cuelga no hay ninguno que consuma demasiado,
> aunque siempre ocurre con el navegador funcionando.
> Seguiré intentando encontrar el fallo.
> Saludos
>
>
>

Re: Cuelgues aleatorios

[Luis Muñoz Fuente]

El 29/12/23 a las 16:09, Camaleón escribió:
> Si piensas que Firefox es el culpable, crea un perfil nuevo y trabaja 
> con él a diario, para ver si el fallo persiste.

Hola:
También me pasa con Chromium, así que no creo que sea específico de
Firefox. Me pasa aleatoriamente y puede ocurrir cada 4 días. Ayer mismo
me pasó y tenía abiertas tres pestañas. Reinicié y al volver a abrir las
mismas pestañas no se colgó, y eso pasa siempre, así que no puedo
reproducir el error. El sistema se queda totalmente colgado, como
comenté, no puedo acceder por ssh y las teclas sysrq no hacen
absolutamente nada, y comprobé que funcionan correctamente con el equipo
sin colgarse. He visto por internet que a más gente le pasa lo mismo con
mi procesador AMD Ryzen 5 1600X, independientemente del sistema
operativo, pero no sé si será esa la causa. También hice un guión de
bash para volcar a un archivo cada tres segundos los procesos que más
cpu consumen y cuando se cuelga no hay ninguno que consuma demasiado,
aunque siempre ocurre con el navegador funcionando.
Seguiré intentando encontrar el fallo.
Saludos

Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing]

[Joel Roth]

On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, I today
> tried to just replace it with rEFInd. Installation succeeded without any
> trouble. But when I start my system, rEFInd just asks me if I want to boot
> with fwupd or with the still very broken Grub. Am I missing something? Is
> rEFInd really just something to select between different OSs (and not just
> different distributions like Grub can very well do) and then gives the rest
> over to their bootloaders or am I missing something so rEFInd will take over
> all of Grubs jobs?

I boot my debian-based system with rEFInd.  Grub is not
present. A couple big icons show on the boot screen. The
small print at the bottom mentions hit F2 for more options.
On my system, F2 offers a selection among all kernels
present. 

rEFInd installs into  EFI/refind/ in the EFI partition.
I originally encountered it looking for something to
boot debian on a Intel Mac. It's been trouble-free.




> On 01.01.24 21:45, Richard Rosner wrote:
> > 
> > 
> > On 01.01.24 21:20, Richard Rosner wrote:
> > > 
> > > On 01.01.24 20:30, David Wright wrote:
> > > > On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
> > > > > On 01.01.24 18:13, David Wright wrote:
> > > > > I can boot by hand, but since this is all archived anyways and it's
> > > > > uneccessarily difficult to find some sort of guide how to even do
> > > > > this, it might as well be a documentation for users having such
> > > > > troubles in the future.
> > > > > 
> > > > > Also, besides the way that I have no clue how it would have to look
> > > > > like to set up a paragraph in the grub.cfg, I simply don't see
> > > > > anything wrong with it anyways. So I can't even look at the grub
> > > > > settings files grub.cfg is being generated from to check where the
> > > > > error lies.
> > > > You append the commands that you used to boot manually with into
> > > > /etc/grub.d/40_custom, observing the comments there, and also into
> > > > grub.cfg itself at the appropriate place (near the bottom). The
> > > > former is so that Grub includes it in any new grub.cfg that you
> > > > create.
> > > Good to know.
> > Edit:, never mind. Tried that, it still booted straight to the UEFI BIOS
> > menu after entering my password. At this point, I'm seriously
> > considering slapping rEFInd on it and pray that it picks up on
> > everything automatically and fix the situation. But so should Grub have,
> > besides the fact that I can't even be entirely sure Grub is to blame and
> > not something else.

-- 
Joel Roth