- luv-main - example.com

GUI problem
by stripes theotoky 31 Jan '19

31 Jan '19

I had a perfectly good working Devuan system running testing .(beowulf /ceres) Ran some updates a few days ago and everything was working fine. Rebooted starts normally brings up slim, user name and password as normal then a black screen. Switching to a terminal Alt Ctrl F1 allows me to log in. startx and xinit fail Obviously the video card is good or I couldn't get to the log in screen or use the terminal. The system is using the nouveau video driver. It was I believe running the Nvidia driver before the updates Only error I notice on shutdown is that slim is not running which I presume is due to a failure to startx. Where do I start debugging this one? Beats me right now. Stripes. -- Stripes Theotoky -37 .713869 145.050562

2 3

Contemplating a complex UEFI-based Linux installation
by Jason White 30 Jan '19

30 Jan '19

I have a Lenovo P51 laptop here (currently running Microsoft Windows 10) on which I'm contemplating installing Linux - probably Arch Linux, or perhaps Debian Testing - or another distribution that is kept fairly up to date. Arch is of interest in that the packages are kept fairly close to upstream, which could be useful for some of my purposes (e.g., reporting bugs on accessibility-related tools such as braille display software and screen readers, and compiling development versions thereof). I need to keep Microsoft Windows around for work purposes, due to compatibility issues. I'm contemplating a dual-boot configuration. I would rather not turn off Microsoft's virtualization-based security, which requires Secure Boot to be enabled; unfortunately, there are too many vulnerabilities and plenty of Windows malware is circulating. On the Windows side, I have enabled Device Guard and Credential Guard in local group policy, set to require "secure boot with UEFI lock". I don't know whether this will complicate Linux installation, or whether it will need to be disabled, even temporarily. At this point, neither an Arch ISO image (written to a USB drive with dd) nor a GRML64 image will boot. I suspect Secure Boot is responsible, unless of course this system cannot boot from these prepared ISO images. I've read documentation on the Arch wiki and elsewhere about UEFI and Secure Boot, most of which is not very clear or somewhat incomplete. There are several boot loaders from which to choose, for example, as well as complications with Secure Boot. I've installed Arch before (and Debian more than once), but only on BIOS-based systems and never with another operating system also present. Further, there are various reports of mixed success with Linux on this particular laptop model. It isn't clear what information is up to date. Also, I want to avoid corrupting the UEFI firmware or data in ways that would necessitate board replacement; I've had to deal with unrelated hardware issues recently and definitely don't want to have to go through the pain of that experience again, if I can avoid it. So, what would be my best source of advice at this point on how to proceed? Suggestions and links would be welcome. I'm also willing to discuss it with someone who knows UEFI well, if necessary.

5 7

Re: postfix boot dependencies with systemd
by Craig Sanders 28 Jan '19

28 Jan '19

On Sat, Jan 26, 2019 at 10:13:10PM +1100, Russell Coker wrote: > It appears that the boot of my laptop is delayed by postfix depending on > network-online.target. How can I change this? Postfix is only listening on > 127.0.0.1 so there's no reason for it to wait until my laptop connects to > the Wifi network before continuing the boot. > > I ran "systemctl edit postfix@-" and "systemctl edit postfix@" and put the > below in which should make it not depend on network-online.target. But it > doesn't change anything. Any ideas? is there a loopback only target you can make it depend on rather than network-manager? other than that, my only idea is to dump network manager and manually configure your network with /etc/interfaces. I've always found that's best, anyway - NM is OK-ish for the simplest of network configs but a complete PITA for anything even slightly complex. craig -- craig sanders <cas(a)taz.net.au> BOFH excuse #44: bank holiday - system operating credits not recharged

3 3

Waking up a USB scanner, other than reboot
by Mark Trickett 26 Jan '19

26 Jan '19

Hello All, I have an Agfa SnapScan 1236. If it is not used for a while, it goes to sleep and even turns itself off. I would like to be able to wake it up, without a reboot,without disconnecting power, without disconnecting the USB cable. Does anyone have ideas? Even when it is "misbehaving" running snapscan -L will find it, but using snapscan to actually scan a document fails to open the scanner. Even when used after a boot, I need to scan the first page I put in twice, it is a medical capable scanner with a lamp in the lid as well as underneath. I would like the first scan to not be in transparency mode. I was given it by a medical practice who have migrated from film X-Rays to digital ones. This will also help for when I do want to scan transparencies. Regards, Mark Trickett

2 2

rsync and filesystem capabilities
by Russell Coker 21 Jan '19

21 Jan '19

I use rsync for most of my backups. For a restore I can rsync the files back and touch /.autorelabel to restore the SE Linux labels. That combination gets all setuid files etc, but doesn't get file capabilities. Below is an example. Is there a good way of preserving capabilities apart from running "getcap /bin/* /sbin/* /usr/bin/* /usr/sbin/*" and storing the output? Currently /bin/ping seems to be the only commonly used program using filesystem capability flags. Also is there a way of telling Debian to restore capabilities apart from "apt-get --reinstall install iputils-ping"? root@sevm:~# cp -a /bin/ping . root@sevm:~# rsync -va /bin/ping ping2 sending incremental file list ping sent 61,328 bytes received 35 bytes 122,726.00 bytes/sec total size is 61,240 speedup is 1.00 root@sevm:~# getcap ping ping2 ping = cap_net_raw+ep root@sevm:~# -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

4 8

Grub in text mode
by Russell Coker 12 Jan '19

12 Jan '19

Recently Grub has been changing to a high resolution mode. On some systems this is really slow, presumably due to having a crap BIOS. On kvm/qemu systems it doesn't work with -display curses. How do I get grub to stick to 80x25 text? -- Sent from my Huawei Mate 9 with K-9 Mail.

3 7

scsi
by Andrew Greig 12 Jan '19

12 Jan '19

5 8

Many to many VPN
by Russell Coker 11 Jan '19

11 Jan '19

If you have servers in multiple countries and people using those servers in multiple locations what's a good way of setting up a VPN? If you have a VPN server at each DC then performance will be great but users have to setup multiple instances of the VPN software which they will mess up and time will be wasted. If you have a VPN server at one DC then a user who connects to a server in a different DC gets longer ping times. Also an outage in one DC breaks everything. Any ideas? Support is required for Linux servers and Linux, Windows, and OS/X clients. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

4 4

Setting MTU on ethernet bridge with netplan
by Toby Corkindale 04 Dec '18

04 Dec '18

Background: I decided my home Linux server had been through too many LTS upgrades, and did a fresh install of Ubuntu Server 18.04. The old /etc/network/interfaces.d system has been replaced by netplan and networkd. I was able to configure a bridge device and attach ethernet devices, but setting the MTU doesn't work. (I have the MTU configured in netplan for both the ethernet device and the bridge device) I managed to hack in a workaround by making a networkd-dispatcher script (routable.d) that calls `ip link set mtu ...`, but wondered if there's a proper way to make this work on netplan? Cheers Toby

1 0

ethernet failure on local network using debian
by bnis＠fastmail.fm 02 Dec '18

02 Dec '18

Hello everyone, My problem is that I cannot get the ethernet card on the local network to get up. I'm new to debian after many years of red-hat/fedora. The machine: HP Compaq Elite 8300 SFF (Core i5). The system: debian buster (testing) Some information: [ben@til ~]$ systemctl status networking.service networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2018-11-24 21:43:38 AEDT; 6min ago Docs: man:interfaces(5) Process: 460 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Process: 452 ExecStartPre=/bin/sh -c if [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environ Main PID: 460 (code=exited, status=0/SUCCESS) [ben@til etc]$ ip addr <snip> 2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 30:b5:c2:05:28:70 brd ff:ff:ff:ff:ff:ff 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 <snip> [ben@til etc]$ lspci -nnk <snip> 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC [10ec:8169] Kernel driver in use: r8169 Kernel modules: r8169 The eno1 is onboard, connected to adsl and works fine. If I restart the network with 'systemctl restart networking', or, './etc/init.d/networking restart', the network goes down and fails. The enp3s0 is connected to a switch on a local network which has two other fedora computers on it. With a previous debian box all I did to have it work on this network was write the following config, reboot, and it worked. I was guided by https://www.debian.org/doc/manuals/debian-reference/ch05. That old box went bung, so I acquired the current one and tried the same config, with the appropriate name changes. That config is in /etc/interfaces (which I created on this machine): -------start config----- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eno1 iface eno1 inet dhcp # This is an autoconfigured IPv6 interface iface eno1 inet6 auto # local net allow-hotplug enp3s0 iface enp3s0 inet static address 192.168.0.3 netmask 255.255.255.0 -----------end config----------- There is no /etc/network/interfaces.d/ on this machine. And this particular ethernet card is the same one that worked in previous debian box. Here are the commands I've used, but none has succeeded in getting the card up, though the ip address was assigned and shown in the 'ip addr' output. There were no error messages other than "FAILED" in the systemctl status output. ip addr add 192.168.0.3 dev enp3s0 ip addr add 192.168.0.3/24 dev enp3s0 ip link set enp3s0 up /etc/init.d/networking restart I was hoping for some help to let me know what I need to do to get this ethernet working? ben

3 4