You are not logged in.
Chimera it seems to have sound. alsa only. Using a realtek alc892.
outputs of,
aplay -l
speaker-test
cat /proc/asound/pcm
This is apparently a replacement option
https://www.youtube.com/watch?v=28tZ-S1LFok
When I'm Small - Phantogram
Some one shared this with me so I thought this is cool one to forward.
I just decided to make a quick sysV init script to configure iptables at boot rather then install iptables-persistance
Mainly because I've made mistake of not enabling ufw and then starting plugging away about my computing lol.
I'd say it's a good early step. Just add your iptable script to /etc/init.d
then run
update-rc.d "$iptables_default_script" defaults
update-rc.d $iptables_default_script enable
I don't know much about dnsmasq. I just set it in /etc/resolv.conf I know it's probably wrong way but it's simple
an example script could look like this
#!/bin/sh
### BEGIN INIT INFO
# Provides: iptable_defaults
# Required-Start: $network
# Required-Stop:
# Should-Start:
# Should-Stop:
# X-Start-Before:
# Default-Start: 2 3 4 5
# Default-Stop:
# Short-Description: simple-iptables
# Description: configure iptables before connecting to internet
### END INIT INFO
ip=iptables
ip6=ip6tables
$ip6 -A INPUT -j DROP
$ip -A INPUT -j DROP
$ip -A FORWARD -j DROP
$ip6 -A FORWARD -j DROP
.
Here's an example for Devuan:menuentry 'Devuan' { search.fs_uuid f203d9ec-a53c-4f33-ad2a-222cf8f8dbcd configfile /boot/grub/grub.cfg }
Alternatively just build a complete menuentry, like this:
menuentry 'Devuan' { search.fs_uuid f203d9ec-a53c-4f33-ad2a-222cf8f8dbcd linux /vmlinuz ro quiet root=UUID=f203d9ec-a53c-4f33-ad2a-222cf8f8dbcd initrd /initrd.img }
^ That uses the /vmlinuz & /initrd.img symlinks that always point to the current kernel version so it doesn't need to be updated after kernel upgrades.
Slackware has similar symlinks in /boot/vmlinuz, /boot/vmlinuz-generic & /boot/vmlinuz-huge with /boot/initrd.gz remaining unchanged regardless of kernel version.
The kernel & initramfs images for Artix are unversioned so they can also be called directly with no need to edit after updates.
And to be clear: this is not a problem with Devuan and there is nothing the Devuan developers can do about it.
Hi, how would I generate a menu entry or a grub config for an encrypted boot partition? Also when I make a custom ISO how can i change the boot menu for that said USB? I'd like to optimize grub.
Possible to use variables in the grub menu? Like for UUID and the like?
set root = (hd0,$root)
linux /boot/vmlinuz
initrd /boot/initrd
boot
(can initrd be an initramfs?) Can i customize this?
menuentry 'Devuan' {
search.fs_uuid $bootuuid
configfile /boot/grub/grub.cfg
}
What if I am using an MBR with encrypted boot. What can I do to make it direct menu entry?
I'd be careful with some git repos or even possible for spoofing to MitM attack package distribution.
Ideally if you had a rsync of a mirror locally you could update systems through a lan connection much more securely without having to go through internet hoops.
I'd make sure you have packages like wpa_supplicant, iw, net-tools, and dhclient.
possible for gzip to provide a different hash depending on gzip version?
I am not running into many issues if elogind is still installed. dependency wise you don't really need to run it but more uncomplicated if it's present.
First fuse is kind of like a pipe. I'd maybe start to see what happens right after fuse.
a perf event could be indication of a signal interrupt or something slowed down the kernel.
Also then you see a bridge and virbo.
If you are on a tower or your laptop turn off your Virtualization features in bios. hope it gets enforced.
As for checking your logs after you could probably just suppress output.
Did you try system on different hardware? could fix error.
Hello,
I only noticed tomoyo because by default this LSM is configured in kernel on. But in default it's not installed so it's throwing errors.
the MAC module seems.. useful if one was to deploy it.
I see we have other ways to initiate MAC without Tomoyo. But Tomoyo works as a good audit / logging system without MAC it would log with very little interrupts on normal operation. I like tomoyo's tree system. Right now most if not all my logging is only from kprint.
Just curious was there a choice to enable tomoyo but not include the tomoyo-tools by default?
As for MAC has anyone deployed any software with it? By default it is enabled so I would like to get some use out of it.
I made a switch to try wayland and sway. It ran fine from user space on tty6. While Xorg was running on 7.
Have not done much testing. Been more busy looking at other stuff lower.
There must be something wrong with whatever generates that list. There's no systemd package in devuan.
root@ceres:/# apt policy systemd systemd: Installed: (none) Candidate: (none) Version table:
Same as the rest of the banned packages.
https://pkgmaster.devuan.org/bannedpackages.txt
Depending what iso you start from some of the live iso's boot with an orphan systemd/ cgroup/agent.
output of
netstat -an
you can set a kernel variable to ignore / orphaned process.
could be a block size issue. If you are expecting 1024 bs but you are sending 512 and only get half a block. It might not write everything.
avahi has a few dependencies. You can remove it though. You don't really need that frame work.
Apt is default package manager in devuan.
with a vega gpu. on AMD system, you might need some firmware to get it to boot outside of console / lowresolution getty.
I had a similar issue on a old live USB. xinit would run in tty1.
Then Xorg would run in tty7. When I open tty1, it would crash xorg in tty7. Then xinit would get slim running on tty1 where tty7 becomes nothing.
I somehow fixed after updating the live-iso.
There is also sudo -i to just pretty much login as root.
to make it request password everytime you might need to set alias in .bashrc when sudo is invoked.
Although I am unsure how to block sudo -i using an alias.
You keep saying "encrypted snapshot" but I don't know if you can have the contents of the iso encrypted. You can have the iso ready to install an encrypted system, and you can have it ready to make a live-usb with encrypted persistence.
To install an encrypted system, you need cryptsetup, cryptsetup-bin, cryptsetup-run, cryptsetup-initramfs (that's the one that's usually missing) and whatever else comes in with those.
I must of been talking about encrypted persistence on the live usb is all. Only use I see in it is maybe using GPG keys instead of passphrases. Then you can use a USB to decrypt your drive.
If you snapshot an encrypted system I see it saves fstab entries of Uuid of encrypted disk. So on boot it looks and trys to decrypt it. If it's there it will prompt for password in normal grub behavior. If you set gpg keys instead it would just unlock it. Maybe if it's setup right it'd work faster then decrypting it other ways.
So i'm the only one here who has broken slim?-)
have you tried installing seatd?
I recently removed it and slim works fine. There must of been a fix upstream?
However, I removed sudo and make live system. It still autologin into user 1000.
But interesting when I run w. slim session is invisible. When login it shows a user. But I don't see tty7 in daedalus where I would see the openbox session in chimaera.
But yeah you don't need sudo.
update-rc.d bluetooth disable
Lenart now works at microsoft.
Make up your mind on that.
this guide maybe of use.
https://thonkpeasant.xyz/guides/other/luks-suspend.html
Try to disable kvm or intel virtualization on your bios.
This usually fixes any boot issues regarding kvm.
I believe this is something that should get looked into.
Will this issue be fixed?
Maybe, but as mentioned devuan installer iso's only boot in mbr.
a uefi only system is not ideal. Probe through your bios and try different settings.
when you partition your disk make sure to make a gpt partition table.
partition your first partition as ef02 (Fat32) efi format. Doesn't have to be too large.
Then format rest of the system as you like.
If you do a mdos partition table you must leave a small >1mb partition that is not formatted or tagged as grub_bios to get the efi boot partition to work. om MSDOS partition table.
Refer to the refractainstaller instructions for more details.
check fstab and make sure it mounts your boot partition properly if not done automatically. Sounds like you didn't have a efi partition formatted and the installer proceeded without it.