Posts by webman

webman · Installation

Hello All!

Thanks, @fsmithred!
I followed this advice, event though it shows another theme!
My problem was not old/new naming convention, but changing interface names between boot - not daily though
and a quick reboot is not an answer. But I looked at this kernel commandline option and it seems not to have any effect!
But I found 70-persistent-net.rules, something, I've not regarded before.
Astroundingly, the mapping, applied in this file, does NOT fit the reality completely, there is an exception for one interface.
Then I changed the rules/names, but the problem persists. Then I enabled udev debug logging and saw, that the interface,
which hasnt followed the rule, was renamed two times: From eth0 to eth2, the from eth2 to eth3.
"Predictbale interface names" .....
Anyway, which kernel commandline applied.
Additionally, I found, that there COULD be "net.naming-scheme=v250", according to this thread:
udevd produce same ID_NET_NAME_SLOT for different NIC, so break rename #28929 :
https://github.com/systemd/systemd/issues/28929
But from this thread, I found a hint: "udevadm test-builtin" and I used it like this:

$ udevadm test-builtin net_id /sys/class/net/gif0 (where gif0 is now my 10GbE-IF)
calling: test-builtin
=== trie on-disk ===
tool version:          3
file size:         9709412 bytes
header size             80 bytes
strings            2419020 bytes
nodes              7290312 bytes
Load module index
ID_NET_NAME_MAC=enx001999c13f23
ID_OUI_FROM_DATABASE=Fujitsu Technology Solutions GmbH
ID_NET_NAME_PATH=enp4s0f0
Unload module index

This <enp4s0f0> (under: ID_NET_NAME_PATH) is probably the original IF-name and could explain, why
the "70-persistent-net.rules" cannot work:
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" - because they trigger (not!) on interface
names, which do not exist?
After I enabled udev debug logging, I have to look deeper at systemstart in the next days.
So wether "net.naming-scheme=v250" nor "net.ifnames=1" made something!
To udev logging: The shown output ("=== trie on-disk ===") appears in LSPCI too:

08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
=== trie on-disk ===
tool version:          3
file size:         9709412 bytes
header size             80 bytes
strings            2419020 bytes
nodes              7290312 bytes

at the end of the list of network cards.

For the moment, I choosed a completely different set of names (eno0 for MoBo-IF, eif<N>
for the ethernet (better: 1Gbe) and gif<N> for the 10GbE interfaces. And these coming - at least
for the moment - up with exactly this names without any problem.

The drama will probably start, if I now start setting the "sriov_numvfs"
variable to get man VFs (asked a question in another part of this forum).

webman · Hardware & System Configuration

Hello All!
Just a very simple script and where and how to install it would help
me getting started!

Thanks,
Manfred

webman · Hardware & System Configuration

Hello!
How can I send sound from scripts or services, running at root?
Know not much about this, but pulseaudio seems to be a problem.
Although I found this:

pulseaudio --start --log-target=syslog --system

BUT, this is systemd, or not?
The man file says:

--system[=BOOL]
              Run as system-wide instance instead of per-user. Please note that this disables
             certain features of ..... (without mentioning them!)

So it is unclear about this!
Just an "aplay <file>" would enough for me!

Probably remove pulse and install pipewire?
Woudl they run without something like the
xdg-desktop(-portal) and can I remove these?

Thanks,
Manfred

webman · Hardware & System Configuration

Hi!
As long as I was on debian (bullseye so far), virtual functions
(VF) from SR-IOV interfaces have had a relation to its physical
part (PF), like here from an Intel X710:

enp66s0f0	PF
enp66s10f80v0   VF
enp66s10f81v1	VF
....

This seems no longer the case, at least for my daedalus setup
and even the "80/81" (in the names above) are really ugly.
If I have 5 physical inferfaces, they are named from eth0 to eth4.
If I issue "echo 8 cat /sys/class/net/<IFACE>/device/sriov_numvfs"
this generates a sequence of new interfaces (VFS), just as numbered
as eth<N> and after my existing ifaces, so starting with eth5 ....
Then I repeat this for the second NIC and the chaos
is complete and they should be applied to QEMU and LCC without
pooling, I must be able to map a VF to a PF (for example, to end up
on a 10GbE port/VF).

I made a script for this (the same, the sets the sriov_numvfs
value). So, if eth5 is my 10GbE port0 (in 0-1), then I create
the names for the new IFs like:
eth5-00 - eth5-07 and the same for the second NIC.

I have not tried it in "rc.local" just now, but this is,
what I di on my debian (rename not done).
But is there a better place, I am not just en par with
sysv-int? And other hint about the interface naming
are reallay welcome!

Thanks,
Manfred

webman · Installation

Hello!
I have no clue, what causes this, but the network interface names are changing often.
So, for this cases, there were no software or hardware changes applied.
I am using daedalus, devuan5, with ZFS on root, using kernel:

6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux

on a ASRock X570M Pro4.
The situation is to see, if one looks into '/sys/class/net', here two examples.

##Previous boot:

##eth0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/net/eth0    <==
##eth1 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.0/net/eth1
##eth2 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.1/net/eth2
##eth3 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:06.0/0000:08:00.0/net/eth3
##eth4 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.1/net/eth4

##Current boot:

eth0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.0/net/eth0/
eth1 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.1/net/eth1/
eth2 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:06.0/0000:08:00.0/net/eth2/
eth3 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/net/eth3/   <==
eth4 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.1/net/eth4/

How can this be fixed?
BTW, the 0000:08:00.0 is the mainboard interface, which I use as basic interface for LAN access.
I could list the pci-device order (and have saved it), but there are never changes.
This is not a desktop, and this behavior makes ssh access impossible!

Regards,
Manfred

webman · Installation

Installed qemu-guest-agent, but found it disfunctional, at
least, cut&paste from host to guest does not work.
Then I saw, it has not been started - whyever.

/etc/init.d/qemu-guest-agent start
qemu-ga: transport endpoint not found, not starting ... (warning).

Then I saw a newer version in backports and installed this.

qemu-guest-agent:
  Installed: 1:7.2+dfsg-7+deb12u5
  Candidate: 1:7.2+dfsg-7+deb12u5
  Version table:
     1:8.2.1+ds-1~bpo12+1 100
        100 http://deb.devuan.org/merged daedalus-backports/main amd64 Packages
 *** 1:7.2+dfsg-7+deb12u5 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
        100 /var/lib/dpkg/status

But at the end of this setup, the same error appeard:

Setting up qemu-guest-agent (1:8.2.1+ds-1~bpo12+1) ...
qemu-ga: transport endpoint not found, not starting ... (warning).
Processing triggers for man-db (2.11.2-2) ...

And the service says it:

# /etc/init.d/qemu-guest-agent status
qemu-ga is not running ... failed!

Regards,
Manfred

webman · Installation

Hello!
I just - for testing - setup ZFS in a kvm guest.
If fails miserably, because the package has left off dependencies.
I am listing the problem messages here (and a bad solution further down).

apt install zfsutils-linux -t daedalus-backports

Setting up zfs-dkms (2.2.4-1~bpo12+1) ...
Loading new zfs-2.2.4 DKMS files...
Building for 6.1.0-15-amd64
Module build for kernel 6.1.0-15-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.
....
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
invoke-rc.d: initscript zfs-import, action "start" failed.
dpkg: error processing package zfsutils-linux (--configure):
 installed zfsutils-linux package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-15-amd64
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Next, I installed the headers mentioned above.

apt install linux-headers-6.1.0-15-amd64

went through a while ....

Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.1.0-15-amd64..........................................................................
...............................................................................................................
................................................................
Signing module /var/lib/dkms/zfs/2.2.4/build/module/zfs.ko
Signing module /var/lib/dkms/zfs/2.2.4/build/module/spl.ko

Running the post_build script:
Cleaning build area...

zfs.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.1.0-15-amd64/updates/dkms/

 ....

dkms: autoinstall for kernel: 6.1.0-15-amd64.
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

The same story as for my first installation attempt.
From this, I know, how to continue:

apt install zfsutils-linux -t daedalus-backports

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
zfsutils-linux is already the newest version (2.2.4-1~bpo12+1).
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/spl.ko 
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/zfs.ko 
Mounting ZFS filesystem(s) .
Load ZFS filesystem(s) keys.
Sharing ZFS filesystems .
Setting up zfs-zed (2.2.4-1~bpo12+1) ...
Starting ZFS Event Daemon .

The zfs packages are in an invalid state, which has to be fixed!

Regards,
Manfred

webman · Installation

Hello!
At shutdown, I get the message:

Unmounting ZFS filesystems cannot unmount 'var/log/': pool or dataset is busy ...failed!

What to do about this error and situation?

Thanks,
Manfred

webman · Installation

Created a base chimeara setup on one disk and setup zfs.
Works, can create/destroy pools and filesystems.
Then create a bootstrap setup, following the instruction for debian bookworm(!!!), ignoring
just the systemd part. In a first glance, everything was ok, installed simple software and
rebooted several times - until I snapshotted the rpool and bpool (syspool/bootpool for me).
Found grub bug description and mounted the pools, upgraded to grub from backport.
After bottable again, a lot of error coming up, which may have to do with mount-orde.

Configuring network interfaces...if-up.d/mountnfs[eth3]: waiting for interface eth1 before doing NFS
 mounts ... (warning).

 Starting enhanced syslogd: rsyslogdrsyslogd: $WorkDirectory: /var/spool/rsyslog can not be accessed,
 probably does not exist - directive ignored [v8.2302.0 try https://www.rsyslog.com/e/2181 ]

>dir exist (perms: root/root)

Sharing ZFS filesystems failed to lock /etc/exports.d/zfs.exports.lock: No such file or directory

uups! dont understand!
>Can import/export pools and are mounts are like set in the installtion.

configfs not found in /proc/mount: exiting!

rsyslog does not accept messages from logger (but after restarting it),
same for ulogd2.

I just shortly made a "recommendation" in the ZFS group to provide detailed instructions for
sysv init systems - but his if future ....
Other instructions I found on Galaxy, skip the setup of the filesystems with its individual mount,
which are probably the root of the problem.

Have had a look for the configfs - I dont understand it. Looked at two other devuan installations
(live and standard [in KVM]) and there, it is at least not mounted.

Here are my zfs mounts

$ zfs list -r -o name,canmount,mounted,overlay,mountpoint
NAME                 CANMOUNT  MOUNTED  OVERLAY   USED  MOUNTPOINT
bootpool             off       no       on        112M  /boot
bootpool/BOOT        off       no       on        111M  none
bootpool/BOOT/devu5  on        yes      on        111M  /boot
syspool              off       no       on       6.86G  /
syspool/ROOT         off       no       on       1.35G  none
syspool/ROOT/devu5   noauto    yes      on       1.35G  /
syspool/home         on        yes      on       5.35G  /home
syspool/home/root    on        yes      on       5.35G  /root
syspool/ops          on        yes      on       2.55M  /ops
syspool/ops/tools    on        yes      on       2.32M  /ops/tools
syspool/opt          on        yes      on         96K  /opt
syspool/srv          on        yes      on         96K  /srv
syspool/tmp          on        yes      on        188K  /tmp
syspool/var          off       no       on        149M  /var
syspool/var/cache    on        yes      on        147M  /var/cache
syspool/var/lib      off       no       on         96K  /var/lib
syspool/var/log      on        yes      on        884K  /var/log
syspool/var/mail     on        yes      on         96K  /var/mail
syspool/var/spool    on        yes      on        192K  /var/spool

Any help would be really great!

++Manfred

webman · Installation

But why does it work in Debian itself?
As I wrote: Made comparable installs (all via netsetup).
Regards,
Manfred

webman · Hardware & System Configuration

Hello!

Wondering, why my DNS log (dnsmasq) is that large and took an tcpdump.
Easy to see, that my new devuan daedalus (running in KVM) causes this,
but the root cause is not easy to find.

Now, that I have Systemtap made running, this is a snip.

stap /ops/monits/watchport53.stp 
exim4[15354] sent packet to 192.168.26.254:53
exim4[15354] sent packet to 192.168.26.254:53
exim4[15364] sent packet to 192.168.26.254:53

So, exim4 ist the beast - dnsmasq shows:

04:55:07 dnsmasq[236175]: 3981 192.168.99.58/35315 query[AAAA] devu5test.home.local from 192.168.26.58
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/35315 config devu5test.home.local is NODATA-IPv6
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/36463 query[AAAA] devu5test1kvm from 192.168.26.58
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/36463 config devu5test1kvm is NODATA-IPv6

The hit to this is the fact, that it queries for its own host, which
does not have any ipv6 address (disabled by kernel commandline)
and no ipv6 addresses in hosts.
The other importent problem with this is, that it makes dns-log checks a pain.

Note (later added): I've removed the ipv6 address from exim's config.

How can I stop this dirty packet flood?

Thanks,
Manfred

webman · Hardware & System Configuration

Someone should contact packagemanagement or whoever is responsible for this.
I dont know!

Regards,
Manfred

webman · Hardware & System Configuration

Hello!

According to the given error message:

$ stap-prep
Configuring for kernel release 6.1.0-16-amd64
Debuginfo automatic downloading is not configured via $DEBUGINFOD_URLS
/usr/bin/stap-prep: line 80: rpm: command not found

Now, I found time to look into the script.
The error is obviously easy to see, the root cause is in line 182:

(180) DISTRO="$(lsb_release --id --short 2> /dev/null)"
(181) case "$DISTRO" in
(182) Debian|Ubuntu) <===
(183)        prep_deb_based "$@"
(184)        ;;
(185) *)
(186)        prep_rpm_based "$@"
(187)        ;;
(188) esac

Just insert "|Devuan" after "Ubuntu" in the case expression and it works.
Sad, but usual for the SystemTap installations all the time, the script
contains - ALWAYS(??) - such errors.
Additionally, at the end of the result (of running 'stap-prep'), you get this:

......
Processing triggers for runit (2.1.2-54) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
You need package linux-image-6.1.0-16-amd64-dbgsym but it does not seem to be available

No such package exist, but systemtap is running now (say, at least my old script).
Another pointless waste of time.

Regards,
Manfred

webman · Installation

Hi All!

Just wondering, that, for example, xfce4 or xrdp does not enforce the installation of xorg.
Was using a LXC container (using daedalus, kernel 5.10) which should run OpenHAB.
How is this to explain?
I fumbled around for some hours without to understand it.
I just installed another LXC container, configured network, installed minimal tools,
again using devuan daedalus via 'lxc-create'.
Then 'apt install xfce4', following by 'apt install xrdp'.
xrdp comes up with an empty window and I found no xorg installed!
Just to refresh myself, because "Ithink I do it this ways ever" (for tests),
I repeated the same steps to install debian bookworm - works immidiately.
Has included xorg!

If I manually install xorg after that, I am seeing a <defunkt> xorg process,
which fast exits. This is a container, so I cannot connect to the console,
but made this countlesse number of times without any problem.

Can someone shed some light onto this or give me a tip?
(Used 'devuan daedalus, kernel 5.10)

Thanks anyway,
Manfred

webman · Hardware & System Configuration

Hello!

Just installed Devuan (daedalus, 6.1.0-16-amd64) in a KVM vm.
Installation of Systemtap (4.8-2) went ok, but the importent step,
executing 'stap-prep' failed:

$ stap-prep
Configuring for kernel release 6.1.0-16-amd64
Debuginfo automatic downloading is not configured via $DEBUGINFOD_URLS
/usr/bin/stap-prep: line 80: rpm: command not found

Quite easy to see, there is usually no rpm, has to be apt ....
How can this be fixed?

Thanks,
Manfred

webman · Installation

Hello!

Just installed a new KVM guest with chimaera, but my network-install
(via PXE) failed - worked shortly before!
After selecting language/country and specifying the proxy,
On screen "Download installer components" I am getting the message:

No kernel modules found
No kernel modules were found. This is probably due to a mismatch between the kernel used
by this version of the installer and the kernel version in the archive.

Have had downloaded a netboot.tar.gz some weeks ago but can currently
not find one any more - does this imply a newer version?

Edit:
Where in this installers are the sources defined?
I was able to find a new realease of the debian-installer - which ist
probably exact the same - what then about the sources?

Thanks,
Manfred

webman · Installation

Hello!

I am using KVM to try to install zfs on boot with chimaera,
I've done this since years with debian, using bios-boot
and separate partitions for the bpool and rpool (bootpol
and syspool - my names).
I followed the instructions for debian(!) bullseye, knowing,
that the missing systemd-part may leave "a hole", that I
cannot understand with sysvinit (wether OpenRC nor runit installed).
On a first glance, everything looks ok, but a red message
at shutdown/reboot indicates a (un)mount problem.
But network shares (cifs) do NOT mount at boot, as usual
(have hardware with chimaera to compare), which is a strong
requiremnent for me.
Additionally, if your last command was 'shutdown -r now'
and you login afterwards and use the up-arrow key, exact
this command must be back - but isnt. Something with the
root account not flushed storage/handled properly bevor shutdown.
The message at shutdown is nowhere to find (syslog/daemon).
bootlog (re-)installed (dont remember, if this was installed
by default) in the hope to get less logs to lookup (systemd
is unbeatable in this regard).
bootlogd shows mount errors at boot time:

mount: /home/shared: mount point does not exist.
mount: /ops/tools: mount point does not exist.
mount: /ops/install/global: mount point does not exist.
mount: /home/shared: mount point does not exist.
mount: /ops/tools: mount point does not exist.
mount: /ops/install/global: mount point does not exist.

This means, something looked for the mountpoints before
the syspool has been imported?
The logline above says:

Configuring network interfaces...if-up.d/mountnfs[eth1]: waiting for interface eth0 before doing NFS mounts ... (warning).

Additionally, the file /etc/network/if-up.d/mountnfs is not executed
(I added logger-statements).

My syspool is as follows:

zfs list -o name,canmount,mounted,overlay,mountpoint
NAME                               CANMOUNT  MOUNTED  OVERLAY  MOUNTPOINT
bootpool                           off       no       on       /boot
bootpool/BOOT                      off       no       on       none
bootpool/BOOT/devuan               on        yes      on       /boot
syspool                            off       no       on       /
syspool/ROOT                       off       no       on       none
syspool/ROOT/devuan                noauto    yes      on       /
syspool/home                       on        yes      on       /home
syspool/home/root                  on        yes      on       /root
syspool/home/shared                on        yes      on       /home/shared
syspool/ops                        on        yes      on       /ops
syspool/ops/install                on        yes      on       /ops/install
syspool/ops/install/global         on        yes      on       /ops/install/global
syspool/ops/install/local          on        yes      on       /ops/install/local
syspool/ops/install/local/zfsdone  on        yes      on       /ops/install/local/zfsdone
syspool/ops/tools                  on        yes      on       /ops/tools
syspool/usr                        off       no       on       /usr
syspool/usr/local                  on        yes      on       /usr/local
syspool/var                        off       no       on       /var
syspool/var/lib                    off       no       on       /var/lib
syspool/var/log                    on        yes      on       /var/log
syspool/var/mail                   on        yes      on       /var/mail
syspool/var/spool                  on        yes      on       /var/spool

Like in the ZOL docs for bullseye-on-root, some filesystems
(syspool/var, syspool/var/lib, syspool/usr) have been created like this:

zfs create -o canmount=off	syspool/var/lib

(can be seen in column CANMOUNT).

At initramfs-prompt, the pool can be listed, but nothing has been mounted so far.
This could mean, some sysvinit services come into the game and that is, where
I fail. I remember the times of debian-squeeze, where the zfs-mountpoints
were set to "legacy" and the fstab contains mounts of it (I am, at the moment,
not able to find my old notes), currently, no zfs mounts in fstab.
What I see is a wrong mount-oder - zfs, to be considered local, must be mounted
first!
Astoundig: Using 'service networking --full-restart' invokes netmounts
(and due to my inserted logging statements, I can see it) and it succeeds.
BTW, looking for a way to enhance logging-level!

NB: There is another problem with the network (not part of my question) wich
looks like a KVM problem: The interfaces come up in another order and so, the
static network configuration is not working. Most of the time, another boot fixed it.
Found many discussion about this (the VM gets a SR-IOV VF as NIC), without
final conclusion (bug or feature).

All things said above were noted, when the network was up properly.

Some help would be great and I can send full logs.

Thanks,
Manfred

webman · Installation

Thanks!

rolfie wrote:

Testing in Devuan is called Daedalus: https://www.devuan.org/os/releases

Have not known this!

Regards,
Manfred

webman · Installation

This looks for me like an individual package install, which I wished to escape.
In debian, the newer version is in the testing repository, so no single package install.
In devuan, so far I looked on the lists, there is no testing, but experimental - dont know the difference.
This might have led to your package links. A devuan repo named testing is not listed on the page:
https://www.devuan.org/os/packages

In debian it is listed:

xtables-addons-dkms:
Installed: (none)
Candidate: 3.13-1+deb11u1
Version table:
3.23-1 -10
-10 http://deb.debian.org/debian testing/main amd64 Packages
3.13-1+deb11u1 990
990 http://deb.debian.org/debian bullseye/main amd64 Packages

Due to my preferences-file it is listed with "-10".
But in devuan (experimental in sources):

xtables-addons-dkms:
Installed: (none)
Candidate: 3.13-1+deb11u1
Version table:
3.13-1+deb11u1 500
500 http://deb.devuan.org/merged chimaera/main amd64 Packages

After your reply, I tried a deeper search and found 'testing' mentioned, without explicit link.
Entered it in the source list and updated - seems to be present!
But does NOT list xtables-addons-dkms, the list above stays the same which lead me
to "individual package install".
BTW, while trying this, the 'experimental' disappeard!

BTW, the mentioned bug, according to the mailinglist debate,
has been fixed in 2020(!!), but never came into the repositories.
Continues the pain with the old patch-o-matic (10 years ago).
Has nothing to do with "willing", I have not the competition
to build a security relevant package.

Though I am trying, I'll make an exception and download the
package - can you give a hint? The daedalus or the ceres version?
I looked to the packages and it needs "xtables-addons-common (>= 3.23)",
which is also not in the repository (has 3.13) .....

Regards,
Manfred

webman · Installation

ralph.ronnquist wrote:

https://pkginfo.devuan.org/xtables-addons-dkms

Like I mentioned, there is nothing for chimaera.
Which dependency hell will another repository open for me?
-Manfred

webman · Installation

Hello!

Just installed my first devuan (chimaera) on a piece of hardware.
But this may become my next firewall, so I looked for the mentioned
package and it is not there - I added the experimental repo too.
For debian, this is in testing with 3.23-1, while usually there
is 3.13-1+deb11u1 and so in devuan.
But this package is buggy and is not to install.

Some tips, other then building, would be great.
I know from experience that the 3.23-1 works well.

Thanks,
Manfred

webman · Desktop and Multimedia

Thank you!
This may be it.
I'll try it out!

webman · Hardware & System Configuration

Yes, I stumpled over this on my naive first try and desktop users can even not save all of their,
settings, eben though it "principially" worked.
For samba, there is probably hope via ksmb in the future, I asked them on github. No time now to
ask on cifs mailing-list currently.
For kvm, where the most of my work happens, there is the same for virtiofs(d) and a request is open
to pass a full featured host filesystem - would apply for me too (using zfs).
I need to integrate additional software and will do this using chroot and/or containers.
The best bet for the moment, it looks, is to pass a blockdev to the guest and install zfs in the guest system.
I am on the road to test this and it basicall works. This would allow me to make snapshots and even replicate
them over the network. So I would be, at least, able to have history on a users homedir.
I'll look really to check your example, because it would allow me, to get rid of systemd.
With systemd, if you have configured, say, 10 users, you'll see their mounts, even they are not logged in .....
This is improper state management for users, in my eyes.

webman · Desktop and Multimedia

Hello!

I am looking to understand, where to configure XFCE4 to behave the same as on my debian (bullseye).
At least two things matter:
- dialogs are not resizable
- cannot switch user (logging in parallel with a second user).
Can someone probably shed some light onto this?

Thanks,
Manfred

webman · Hardware & System Configuration

Hi!

Thank you for your investigation and a big sorry for my late reply.
I am having too much trouble at the moment with something like
this.
I've heart about pam-mount, but, due to the fact, that this moment
I stay on debian, I looked there(!), but missed it.
I just (this moment) checked for that package in the VM and it is really there.
But I must delay further, because at the moment, it's not clear if/how
I can use the whole users homedir on a share - there are hints to this,
but they do not work. I asked in the samba groub, but they directed
mit to "cifs" mailinglist and I have first to make that clear and understandable
completely. If this does not become possible, I'll install ZFS in the VM.
The whole thing is about snapshots (the samba share can be snapshotted
on the server).

Regards,
Manfred

The officially official Devuan Forum!

#26 Re: Installation » daedalus: network interface names changing with (nearly) each boot » 2024-06-15 00:18:36

#27 Hardware & System Configuration » sysv-init: Looking for example/run a script permanently, like service? » 2024-06-13 19:26:01

#28 Hardware & System Configuration » Need acoustic signalling (sound) where only root account is present » 2024-06-13 19:22:26

#29 Hardware & System Configuration » How handle network interface naming for SOME interfaces (VF/SR-IOV) » 2024-06-13 19:03:58

#30 Installation » daedalus: network interface names changing with (nearly) each boot » 2024-06-13 18:44:40

#31 Installation » qemu-guest-agent - dysfunctional package » 2024-06-13 18:15:17

#32 Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-13 17:57:52

#33 Installation » zfs on root successfully installed - but unmount problem at shutdown » 2024-06-13 17:34:39

#34 Installation » chimaera: Stucking with zfs on root - mount and other errors » 2024-05-06 03:22:48

#35 Re: Installation » packagemanagement and dependencies - xfce4 setup does not install xorg » 2024-01-11 22:41:50

#36 Hardware & System Configuration » exim4 floods dns (and its log) with AAAA queries, though NO ipv6 avail » 2024-01-09 04:02:33

#37 Re: Hardware & System Configuration » Systemtap packaging error - cannot be used » 2024-01-09 03:46:07

#38 Re: Hardware & System Configuration » Systemtap packaging error - cannot be used » 2024-01-09 03:44:32

#39 Installation » packagemanagement and dependencies - xfce4 setup does not install xorg » 2024-01-09 02:46:54

#40 Hardware & System Configuration » Systemtap packaging error - cannot be used » 2024-01-07 08:44:43

#41 Installation » Find the latest 'netboot.tar.gz' » 2023-05-05 20:32:27

#42 Installation » zfs on boot causes problems » 2023-05-01 14:29:34

#43 Re: Installation » Searching package xtables-addons-dkms » 2023-05-01 14:03:28

#44 Re: Installation » Searching package xtables-addons-dkms » 2023-04-28 20:04:31

#45 Re: Installation » Searching package xtables-addons-dkms » 2023-04-28 09:46:58

#46 Installation » Searching package xtables-addons-dkms » 2023-04-27 23:15:24

#47 Re: Desktop and Multimedia » XFCE4 config on devuan - differences to debian » 2023-04-09 11:13:12

#48 Re: Hardware & System Configuration » How mount samba/cifs share as users home directory at users login? » 2023-04-09 11:11:52

#49 Desktop and Multimedia » XFCE4 config on devuan - differences to debian » 2023-04-04 13:40:34

#50 Re: Hardware & System Configuration » How mount samba/cifs share as users home directory at users login? » 2023-04-03 05:38:40

Board footer