| systemdlete | when anacron starts on my beowulf laptop, it says "Starting anac(h)ronistic cron: anacron deferred while on battery power" -- that would be fine except that the laptop is plugged in when I run "service anacron start" and get that message | 03:00 |
|---|---|---|
| systemdlete | I've web searched for this, and it seems this was a known issue back in 2003(?) Had something to do with the switch from apm to acpi or something. | 03:02 |
| systemdlete | Anyway, has this ever been addressed since then? | 03:02 |
| systemdlete | Incidentally, my anacron jobs are *not* running. | 03:02 |
| bb|hcb | systemdlete: anacron is not forked, maybe checking if the same problem is there in Debian and filing a bug report there? | 03:03 |
| bb|hcb | for reference: https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=anacron&x=submit | 03:03 |
| systemdlete | bug has already been filed for this, long ago. | 03:04 |
| systemdlete | I'm looking at mailing list comments from 18 years ago | 03:04 |
| bb|hcb | :( | 03:04 |
| bb|hcb | Do you have a proposed fix? | 03:04 |
| systemdlete | I'm wondering if I'd be better off disabling anacron and just running jobs the old-fashioned cron way. I mean, my laptop is on wall power most of the time anyway. | 03:05 |
| systemdlete | (the battery is flakey, at least with devuan running on it. I am sure it works quite nicely with Windoze) | 03:05 |
| systemdlete | no, I have no idea how to best fix this. I only just started looking at this about 2 days ago when I first noticed it. | 03:06 |
| systemdlete | bb|hcb, do you run beowulf on a laptop by any chance? | 03:06 |
| bb|hcb | nope, I run chimaera long before it was released | 03:07 |
| systemdlete | on a laptop? | 03:07 |
| bb|hcb | couple of them | 03:07 |
| systemdlete | did you run an earlier devuan on either of them before now? | 03:08 |
| bb|hcb | an old one (10yrs asus) is with me right now | 03:08 |
| systemdlete | mine is an asus also, but it is a tablet, not a real laptop but it comes with a keyboard | 03:09 |
| bb|hcb | it was very brief - i installed beowulf and immediately upgraded | 03:09 |
| systemdlete | ok, thanks. | 03:09 |
| systemdlete | so maybe... | 03:09 |
| bb|hcb | if you want me to test something, its ok... | 03:09 |
| systemdlete | nah. You don't have to unless you are curious | 03:10 |
| systemdlete | might be interesting | 03:10 |
| systemdlete | I appreciate the offer | 03:10 |
| systemdlete | bb|hcb, do you get the same message from anacron? "service anacron restart" | 03:11 |
| systemdlete | or maybe stop it and start it | 03:11 |
| systemdlete | (I mean, do you get the same message under chimaera?) | 03:12 |
| systemdlete | but I have a different issue, to do with installing devuan (chimaera in this case, but the same has happened with beowulf and ascii too). | 03:13 |
| systemdlete | There seems to be no obvious way in the partitioning portion of the install to request that a volume group be encrypted rather than individual volumes | 03:14 |
| bb|hcb | hm, anacron works as expected | 03:14 |
| bb|hcb | there is message only when i pull the power | 03:15 |
| systemdlete | I mean, I can probably do the disk partitioning outside the installer manually, but I am not sure if the installation will work correctly after that | 03:15 |
| bb|hcb | that is with anacron 2.3-30 | 03:16 |
| systemdlete | And another issue is that I accidentally created one partition, but then went back and split that into 2 partitions. But the LVM part of the partitioning still thinks the 1st partition is the full length of the disk. | 03:17 |
| bb|hcb | maybe its my wrong personal preference, but I'd rather leave free space during install and do the changes afterwards... | 03:17 |
| systemdlete | not wrong, really. bb|hcb, I used to do linux installs that way also | 03:18 |
| systemdlete | I used to feel intimidated by stuff like raid and lvm. These days, I enjoy using them very much, now that I took the time to try them | 03:19 |
| systemdlete | As to the first issue, with anacron, it sounds like maybe chimaera has resolved this. But it could also be the particular "laptop" I am using. | 03:20 |
| systemdlete | this is a "Transformer" based on the Intel cherry trail platform. | 03:20 |
| bb|hcb | when you touch partitions, it is very likely the kernel view not to get updated; use lsblk to see if the change is there or not; if not, most easy is to reboot | 03:20 |
| systemdlete | (SoC?) | 03:20 |
| systemdlete | right bb|hcb | 03:21 |
| systemdlete | I probably need to sync the new config at a command prompt (shelling out to F1 console) | 03:21 |
| systemdlete | partprobe | 03:23 |
| systemdlete | which is not available in the shell at this point. :( | 03:24 |
| systemdlete | but there is another tool that can do this also... | 03:24 |
| bb|hcb | blockdev --rereadpt /dev/XXX | 03:24 |
| systemdlete | kpartx | 03:25 |
| systemdlete | hmm blockdev, ok | 03:25 |
| systemdlete | blockdev: Device or resource busy | 03:26 |
| bb|hcb | I may be old-fashioned, but I use fdisk (especially after GPT support is there) ;) blockdev is a low-level tool that allows telling the kernel to refresh the partition table | 03:26 |
| systemdlete | neither df nor mount show any /dev/sda partitions | 03:26 |
| bb|hcb | that means the partition is in use, most easy is reboot; it may be mapped as lvm or part of raid, who knows | 03:27 |
| bb|hcb | mount may not see it, check in /proc/mounts | 03:29 |
| systemdlete | sorry, while I was waiting I continued with the install. It is encrypting now. | 03:32 |
| systemdlete | But what I really wanted is one key for the entire vg. I worry I will get a system with a decryption prompt at boot for 5 different volumes! | 03:33 |
| systemdlete | I think I know how to fix that, but what a pain | 03:33 |
| systemdlete | The whole idea was for the one vg to be encrypted. Then if I want additional volumes to be encrypted, I can just add new space to the one, encrypted vg | 03:34 |
| systemdlete | I can modify the crypttab after install and set the volumes up to use the same key. | 03:37 |
| systemdlete | I've done this already when I had to add new physical disks to some VMs. But lvm does support encrypted VGs -- I've tried it and it looked like it works. | 03:38 |
| systemdlete | Its just the installer that does not know how to do this. | 03:38 |
| gast0n | hi, live-build is still maintained? | 03:39 |
| bb|hcb | systemdlete: I have no idea, never did that. Laptops are like a temp resource for me and I always do the simple encrypted all-in-one part... | 03:42 |
| systemdlete | Recently (about the last week) I've had file systems go readonly on me. These are in VMs, so it cannot be a hardware issue (I've checked the host system and there are no hard errors in the kern.log) | 10:34 |
| systemdlete | I'm supposing that this is related to a recent kernel maybe? | 10:35 |
| systemdlete | I have updated the systems here (mostly VMs, a couple of physical boxes) and maybe there was a kernel update, idr now. | 10:35 |
| systemdlete | After a reboot -- and fsck -- they seem to go back to normal, though today I had another one go readonly on me, and it had been rebooted just a few days ago. | 10:36 |
| systemdlete | This is troubling since I have not seen this behavior on any linux system in years. | 10:37 |
| systemdlete | These are devuan systems. All are beowulf, though one is ascii (to be upgraded soon...) but I don't remember if that one had this problem recently. | 10:38 |
| systemdlete | All of the systems experiencing this are VMs. Hosts have not seen this. | 10:39 |
| adam_free2air | through validating arm builds, i have discovered that there is an additional dependency of xorg for chimaera minimal builds to install xfce4 with slim as per https://www.devuan.org/os/documentation/dev1fanboy/en/minimal-xfce-install.html | 14:38 |
| adam_free2air | (don't think slim by default plays well with wayland) | 14:39 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!