phillipsjk256 | rwp: have you asked in #nouveau about it? though they would probably want you to test with the latest version. | 02:04 |
---|---|---|
rwp | phillipsjk256, I haven't asked there. I am on ceres so should be fairly current. | 02:43 |
systemdlete | fsmithred: How much disk space will I need to install /iso/refracta10.1_xfce_amd64-20201004_1854.iso ? Thanks | 03:04 |
fsmithred | systemdlete, what are you going to do with it? I would not give it less than 6GB, but I think it takes around 4 | 03:10 |
systemdlete | Ok, that's fine. I just want to give it a shot. | 03:10 |
systemdlete | a "standard" 8gb hard drive should do... | 03:11 |
systemdlete | (standard in vbox, that is) | 03:11 |
fsmithred | I use 12 if I'm going to make a snap[shot | 03:11 |
systemdlete | I can always add more disk later. | 03:11 |
systemdlete | So more or less, it follows the same pattern as devuan then, in terms of how much disk space is needed? | 03:12 |
fsmithred | I found a couple of bugs in that iso and I'm pretty pissed off about it | 03:12 |
systemdlete | uh oh | 03:12 |
systemdlete | maybe I should wait then? | 03:12 |
fsmithred | somewhow, ff-esr changed the default search engine from ddg to goober | 03:12 |
fsmithred | and removed the search box from the toolbar | 03:13 |
systemdlete | yipes | 03:13 |
systemdlete | have you seen the new tbird? | 03:13 |
systemdlete | egads | 03:13 |
fsmithred | not yet | 03:13 |
systemdlete | I mean, it is ok, but frankly... I wish they'd work on bugs first. | 03:13 |
systemdlete | same thing for vbox | 03:13 |
systemdlete | what is "a snapshot"? | 03:14 |
systemdlete | I know this for vbox | 03:15 |
fsmithred | make your own live-iso with refractasnapshot | 03:15 |
systemdlete | oh. No. | 03:15 |
systemdlete | I don't think I'll be doing that. | 03:15 |
fsmithred | copies the installed system and rolls it up into isohybrid | 03:15 |
systemdlete | I see. | 03:15 |
systemdlete | It sounds like 8 or so should be plenty for me. | 03:15 |
systemdlete | But as far as the bugs, other than ff, anything else to note? | 03:16 |
fsmithred | I don't think so | 03:16 |
systemdlete | good! | 03:16 |
fsmithred | I think there was a kernel upgrade right after I made those | 03:16 |
systemdlete | I'll just switch the search engine back to duckduckgo | 03:16 |
systemdlete | I'll upgrade after the install, as I normally do | 03:17 |
systemdlete | thanks again... | 03:20 |
systemdlete | what does "high contrast" do exactly? Is that to do with the display characteristics? (low light, eg?) | 03:21 |
systemdlete | or is that for low-vision users | 03:21 |
fsmithred | yeah for vision-impaired | 03:22 |
fsmithred | it's the gnome high-contrast theme | 03:22 |
systemdlete | Do you have an option for us low-comprehension folks? | 03:22 |
fsmithred | boot it and stand back | 03:22 |
systemdlete | gotcha | 03:22 |
fsmithred | if you need passwords, user:user root:root | 03:23 |
systemdlete | thanks | 03:23 |
systemdlete | So I think I am (finally) getting this... | 03:27 |
systemdlete | One *must* have the additional 6gb or so of space if one wants to install to hard disk | 03:27 |
systemdlete | I think that is the whole point to refracta, isn't it? | 03:27 |
fsmithred | what? | 03:28 |
systemdlete | I don't see any installer | 03:28 |
fsmithred | refractainstaller in a root terminal or Refracta Installer from the menu | 03:28 |
fsmithred | System | 03:28 |
systemdlete | So I was guessing I have to make an iso image, like you were saying... | 03:28 |
systemdlete | oh | 03:28 |
fsmithred | no | 03:28 |
fsmithred | you downloaded an iso | 03:28 |
fsmithred | you can install it | 03:28 |
systemdlete | aha | 03:28 |
systemdlete | I see. | 03:28 |
fsmithred | you only need to make your own iso if you want to change things and make your own live-iso | 03:29 |
systemdlete | I was expecting something more... well, kind of "obvious" for those of us who wouldn't usually go poking through menus | 03:29 |
fsmithred | yeah, I know. Everyone else puts an icon on the desktop. | 03:29 |
Dzhigit | Hello. After migrating from Debian Buster to Devuan Beowulf, and now to unstable, GNOME Software is not working and says No Application Data Found. apt and packagekit are still working and I can use pkcon. Running gnome-software through env LANG=C gnome-software shows the following errors: 02:16:04:0645 PK failed to set proxy: | 03:30 |
Dzhigit | GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the session02:16:04:0647 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the session | 03:30 |
systemdlete | nw. I just didn't realize | 03:30 |
fsmithred | https://www.devuan.org/os/documentation/install-guides/beowulf/live-gui | 03:30 |
systemdlete | oh. There's documentation. | 03:31 |
fsmithred | picture book | 03:31 |
systemdlete | :) | 03:31 |
systemdlete | cartoon characters showing me how to do it? | 03:31 |
systemdlete | talking dogs and cats, e.g. | 03:32 |
systemdlete | j/k, j/k | 03:32 |
fsmithred | monkeys | 03:32 |
systemdlete | of course | 03:33 |
systemdlete | Dzhigit: You upgraded to unstable and it has bugs -- really? lol | 03:34 |
Dzhigit | systemdlete, no, the bug was there in Beowulf as well | 03:35 |
systemdlete | at least it is consistent... | 03:36 |
Dzhigit | I upgraded to unstable after upgrading from buster to beowulf | 03:36 |
Dzhigit | actually the only bug I have from unstable is brightness control not working on this laptop | 03:38 |
systemdlete | you live dangerously. I would not ever try that, at least not expecting that it would be stable. | 03:38 |
fsmithred | did you follow the buster to beowulf migration guide? | 03:38 |
Dzhigit | yes | 03:38 |
fsmithred | ok, good. I don't remember what's in it, but I know there are some tricky spots. | 03:39 |
Dzhigit | I followed this https://www.devuan.org/os/documentation/dev1fanboy/en/buster-to-beowulf | 03:39 |
fsmithred | yeah | 03:39 |
systemdlete | (closest time zone I could find was "pacific ocean" -- I'm not quite in the ocean, but give it a few more years...) | 03:45 |
fsmithred | I think they're in order | 03:45 |
systemdlete | there was no plain "Pacific" (like the other US time zones). Just "Pacific Ocean" | 03:46 |
systemdlete | I guess if you live on a houseboat near SF that would make sense | 03:47 |
golinux | Hawaii | 03:48 |
systemdlete | I selected write random data to disk drive and dd reports no space left on device. Not sure what to do from here. It just seems to be handing, but I see vbox is doing I/O on the disk. | 03:48 |
systemdlete | golinux: That is HST. | 03:49 |
rwp | Dzhigit, I don't know but all of the error message about the "session" makes me think it need cgmanager or something else installed that perhaps elogind is not faking up sufficiently that is not there for it. | 03:49 |
systemdlete | fsmithred: I chose write random data AND encrypt /home. Maybe that is a bad combo? | 03:49 |
fsmithred | I don't remember what happens when you write random | 03:50 |
rwp | Dzhigit, If it were me I would try XFCE as an alternative that works pretty well for most people. | 03:50 |
fsmithred | I haven't done that in eight or nine years | 03:50 |
fsmithred | encryption I use a lot | 03:51 |
fsmithred | and I'm sure I tested them together, but that was long ago | 03:52 |
rwp | systemdlete, I think the timezone name is not Pacific but US/Pacific. Or America/Los_Angeles | 03:52 |
systemdlete | I'll double check when the system reboots | 03:53 |
systemdlete | rwp: I'm installing refracta, and picking fsmithred's brain while doing it | 03:53 |
rwp | I could tell! Good job! :-) | 03:53 |
systemdlete | :p | 03:53 |
phillipsjk256 | systemdlete, sometimes utilities like that will report done before the physical write takes place. (Due to buffering.) | 03:53 |
systemdlete | well, it is doing something, but it does not reveal what | 03:54 |
rwp | I know that for a while there the US/* timezones went away. I filed a bug and complained. Which was if I recall simply closed, get a life, use one of the Americas/* timezones. | 03:54 |
systemdlete | Ah now it is doing the next step | 03:54 |
systemdlete | (writing zeros) | 03:54 |
rwp | But then later I saw that they came back as US/* again. So that's all I know. | 03:54 |
rwp | systemdlete, Are you doing this on bare metal or a VM? | 03:55 |
systemdlete | VM | 03:55 |
systemdlete | It's just taking some time, that's all. | 03:55 |
systemdlete | The install IS proceeding | 03:55 |
fsmithred | 10 minute install if you don't do the random write | 03:56 |
rwp | In the future I probably would not write random data to a VM image. Because if one is using qcow2 for example that will force it to be fully expanded to the maximum size. All sparseness that we might want will have been removed. | 03:56 |
systemdlete | I'm using fixed-size vbox disks | 03:57 |
fsmithred | dd if=/dev/urandom of="$install_dev" | 03:58 |
fsmithred | same for home_dev | 03:58 |
fsmithred | so yeah, it just runs until it gets to the end | 03:59 |
systemdlete | I've gotten bitten by expanding disks. One day, I ran out of physical space. I find it easier to allocate the space up front. It uses more physical space, but there are fewer surprises. | 03:59 |
systemdlete | (I hate surprises. I prefer known quantities.) | 04:00 |
Dzhigit | rwp does Devuan accept bug reports for GNOME | 04:00 |
systemdlete | My approach uses space unnecessarily perhaps, but I don't have to worry I will kill all my VMs and maybe make the host hang all at once. | 04:01 |
rwp | Dzhigit, I know nothing. Personally I was surprised that it was documented to run. Since I thought the detente was Devuan uses init freedom to avoid systemd and we let GNOME require it and we just don't use it. But there it is saying it can be installed so I don't know anything. | 04:02 |
systemdlete | And with all the disk space I have now, I don't see any reason to be thrifty on disk space. | 04:02 |
Dzhigit | alright, I will see if it works in a fresh install | 04:03 |
rwp | systemdlete, Are you using LVM? For VMs that I want high performance I/O I allocate an LV for the VM and then effectively it has it's own disk. | 04:03 |
Dzhigit | so much for GNOME being the desktop environment of the GNU project when they support systemd instead of GNU's own Daemon Shepherd | 04:04 |
systemdlete | you mean on the host side? Yes, I am doing that. But ALL of my VMs are on one large lvm drive. | 04:04 |
rwp | Dzhigit, GNOME being a GNU Project thing was years and years ago. They still use the name GNOME but there was a falling out and mostly they have gone their own way since years. | 04:04 |
systemdlete | I mean, sure, I could do it that way too. Allocate a LV for each VM. It's not a bad approach either. | 04:04 |
rwp | There is more than one way to do it. | 04:05 |
rwp | For various victim testing situations I use qcow2 images to conserve disk space. As long as I don't enlarge them all at the same time then I can overbook my disk space. Which is only me conflicting with myself so not really a problem if I do. | 04:07 |
Dzhigit | even though GNU still lists GNOME as part of their project it seems like GNOME has a lot more independence | 04:08 |
systemdlete | I run about half a dozen VMs all the time, plus I frequently run multiple test VMs as well. Most of them are idle. | 04:09 |
rwp | Me too. I keep at least one VM of every version of every OS I work with so that I can compare them and test. | 04:11 |
systemdlete | What is our actual exposure to this new slipstream vulnerability? How likely is it that any system would be compromised successfully? | 04:11 |
clort | what slipstream what systemdlete | 04:56 |
systemdlete | It's the buzz all over the internet I think... but maybe it is not as bad as reported? | 04:57 |
systemdlete | idk | 04:57 |
clort | do i have to do anything | 04:58 |
systemdlete | that's what I am wondering also. I'm not sure if there is a mitigation available yet. | 04:59 |
systemdlete | I blew away my root bashrc on refracta. Is there a way to replace it. | 05:00 |
systemdlete | (blame my fingers. They don't always listen to what my brain tells them.) | 05:00 |
clort | is there some quick summary what it is somewhere | 05:00 |
clort | you don't need anything in bashrc that you didn't want in there | 05:01 |
systemdlete | well, my prompt is white, not red, now. | 05:01 |
systemdlete | I just want to put it back, get a backup of it, and proceed. | 05:01 |
clort | if you deleted it, it's deleted | 05:02 |
systemdlete | It came from *somewhere*, right? | 05:02 |
systemdlete | a package, or a copy from, say, /usr/share/base-files (but I tried copying it from there and it did not restore the red prompt) | 05:03 |
mason | clort: https://github.com/samyk/slipstream | 05:03 |
clort | here is a red prompt for root | 05:04 |
clort | export PS1="\[\033[01;33m\]IMROOT! \[\033[01;31m\]\$PWD\[\033[01;33m\]# \[\e[0m\]" | 05:04 |
systemdlete | thanks mason. I had lost the page | 05:04 |
mason | np | 05:04 |
clort | xterm should be able to beep to alsa on ^G | 05:52 |
systemdlete | fsmithred: Does refracta use apt? I tried to apt remove wicd, but it tells me it is not installed. It's there. | 05:59 |
systemdlete | and the /etc/network/interfaces file doesn't look like my network config. It has no eth0 entry, whereas, I really do have a eth0 | 05:59 |
systemdlete | So, again... I'm lost. | 05:59 |
golinux | apt-get I think | 06:04 |
unixbsd | Hello, how to install a printer HLL 2340 D on amd64? | 07:29 |
unixbsd | hll2340dlpr-3.2.0-1.i386.deb I have this for i386, but I need to port it to amd64, how to do so? hll2340dlpr-3.2.0-1.i386.deb hll2340dcupswrapper-3.2.0-1.i386.deb | 07:30 |
Montresor | Install those and libc6-i386. | 07:32 |
gnarface | unixbsd: dpkg --add-architecture i386 && apt-get update | 07:58 |
gnarface | unixbsd: then you should be able to use i386 packages too | 07:58 |
gnarface | Unit193: i don't really know if that will still work or not, i think that is the old way | 07:59 |
Unit193 | gnarface: I have hll2340dcupswrapper:i386, hll2340dlpr:i386, and libc6-i386 installed, the printer works. | 08:01 |
laidback_01 | hey, I've installed beowulf for a friend. I didn't use LVM, but did setup a root mirror with mdadm. the mirrors are in good shape, data is fine. | 08:56 |
laidback_01 | but the machine has a boot issue giving me tons of these: WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds. | 08:56 |
laidback_01 | all about /dev/sda, /dev/sdb, /dev/md0, /dev/md1, etc. they take several minutes each. and when it's done with that error cycle, it will boot, but the mouse and keyboard need to be unplugged and reconnected to function. | 08:57 |
laidback_01 | so... I'm backing this sytem up, his data and all, and am about to rebuild it, but wanted to see if this is something that an lvm2 purge and reinstall should have fixed or not - it didn't . | 08:58 |
laidback_01 | I don't know any other way out of this just now... | 08:58 |
rrq | maybe add "loop" module to /etc/initramfs-tools/modules and run "update-initramfs -u -k all" | 09:07 |
Joril | laidback_01: there was a post somewhere... Let me search for it... | 09:07 |
laidback_01 | okay. I'll take a look at adding loop. something else that kind of strikes me funny - if I purge lvm2, now my network device, eth0, an intel device, will not show up. | 09:08 |
laidback_01 | do I need to remove evdev and switch to regular udev if I remove lvm2? | 09:09 |
Joril | laidback_01: maybe https://bbs.archlinux.org/viewtopic.php?pid=1867015#p1867015 | 09:11 |
laidback_01 | oh, what I mean: I apt purge lvm2, then reboot. that's when my network... which normally loads, now doesn't | 09:11 |
laidback_01 | okay, I'll try. I can't stand lvm, so I never use it. aggravating to have it seem to be so heavily involved. | 09:12 |
laidback_01 | just about to try. backing up the virtual machines now before reboot. much easier to backup data when using a rescue disk rather than a hobbled system ;) | 09:49 |
laidback_01 | nope, no-go. I'm going to sleep. will rebuild as a fresh install later. going to do everything i can to keep lvm out of this system. | 10:01 |
gnarface | laidback_01: not sure what's going wrong but fyi this is why they tell people not to actually boot from the raid array. is that a requirement for the setup? i know what you're trying is possible but it's generally considered not worth it (not only due to the effort level, but due to the catastrophic lack of any recovery path for the install in this case if there were hardware failure) | 10:09 |
gnarface | even if you succeed, you'll eventually regret it over the long run if not the short run | 10:09 |
gnarface | that's the industry best-practice advice on the matter | 10:10 |
gnarface | laidback_01: also, i don't think it really requires LVM either but LVM might make it easier | 10:11 |
gnarface | (LVM is something i avoid myself) | 10:11 |
laidback_01 | oh, I've never had issues with a mirror for root with just ext4 on it | 10:12 |
laidback_01 | and recovery is super easy - but then I don't use anything other than raid 1 | 10:12 |
gnarface | well, raid 1 would be better than raid 0 for that | 10:12 |
gnarface | as long as you know what you're doing, i consider my duty to warn you fulfilled | 10:13 |
laidback_01 | LVM is kind of a nice thing if you use KVM a lot - add a drive as needed to grow your device, and KVM requires you to use LVM if you need snapshots. | 10:13 |
laidback_01 | but, even so, I dislike LVM for the added abstraction layer mostly. | 10:13 |
laidback_01 | warning understood. I'm using twin SSD drives in a simple mirror. it works, and it's safe. | 10:14 |
suavedandy | Guys? | 10:16 |
suavedandy | It seems Micro is not in the Debian repos. | 10:17 |
laidback_01 | what's Micro? | 10:17 |
laidback_01 | https://micro-editor.github.io/ <-- this? | 10:18 |
suavedandy | Yep. | 10:20 |
suavedandy | Seems like they removed it. Probably because it was buggy. | 10:20 |
suavedandy | No wonder why it was glitchy on Devuan. Is Devuan's repo behind Debian's? | 10:21 |
gnarface | yes but usually not by more than a couple hours i think | 10:22 |
gnarface | however i'm not seeing micro-editor or micro-anything-that-looks-like-an-editor in any version of devuan ever | 10:22 |
gnarface | oh | 10:22 |
suavedandy | It's called just micro. | 10:22 |
gnarface | no i'm wrong | 10:22 |
gnarface | it's there | 10:22 |
suavedandy | Indeed. | 10:23 |
gnarface | it is present in beowulf-backports | 10:23 |
suavedandy | Ohhhhhhhhhh. | 10:23 |
gnarface | https://pkginfo.devuan.org/stage/beowulf/beowulf-backports/micro_2.0.6-2~bpo10+1.html | 10:23 |
gnarface | found it for you | 10:23 |
laidback_01 | really though, just go here https://github.com/zyedidia/micro/releases and dpkg -i micro-2.0.8-amd64.deb | 10:23 |
gnarface | my guess based on this evidence is that it probably just didn't make the buster freeze | 10:23 |
gnarface | debian won't add any new programs to the release after it is marked stable | 10:24 |
gnarface | just a policy | 10:24 |
suavedandy | Wait. If I add the backports to the repositories, I automatically get the backported versions of software when installing? | 10:24 |
laidback_01 | no | 10:24 |
gnarface | if they have an old version that works fine and nobody has any complaints about the code quality they'll usually just let it ride, but if they have a version that doesn't build and the maintainer doesn't respond in time they just drop it | 10:25 |
laidback_01 | you have to reference the repo to use it | 10:25 |
suavedandy | Then why did micro install? | 10:25 |
laidback_01 | huh, I'll have to look at this myself. you used to need to reference the repo | 10:25 |
gnarface | it shouldn't have but there are a number of things that can go wrong with dependencies in very normal conditions (more normal for backports because they're less thoroughly tested) that can cause extra packages to be included accidentally | 10:26 |
gnarface | i always recommend only installing specific packages from backports for that reason, and disabling it afterwards immediately | 10:26 |
gnarface | and NEVER do a full upgrade from backports | 10:26 |
suavedandy | Like, I didn't even try installing it from the backports repo deliberately. | 10:27 |
suavedandy | I just "apt install -y micro" | 10:27 |
suavedandy | No "--buster-backports" | 10:27 |
gnarface | well, you should know that this could be a symptom of a package dependency breakage caused by including 3rd party debs from non-devuan repos... | 10:27 |
gnarface | just one of the other possible causes | 10:27 |
xinomilo | why not upgrade from backports? it's official repo... | 10:28 |
gnarface | the command for just micro you'd probably want to use would be "apt-get -t beowulf-backports --no-install-recommends install micro" | 10:28 |
gnarface | try that | 10:28 |
suavedandy | My system was perfectly clean from non-Devuan packages. | 10:28 |
gnarface | could just be fucked up too man i dunno | 10:28 |
gnarface | but i think if you "dist-upgrade" with backports enabled that might override the sanity checks... | 10:29 |
xinomilo | nope | 10:29 |
gnarface | you sure? | 10:29 |
xinomilo | only: apt dist-upgrade -t beowulf-backports | 10:29 |
xinomilo | or if you set it in preferences | 10:29 |
gnarface | suavedandy: i'm not as sure as him about this, double check the output^ | 10:29 |
suavedandy | Oh, sorry, I meant "-t beowulf-backports" | 10:29 |
suavedandy | Not "--buster-backports" | 10:30 |
suavedandy | Anyway, I didn't type either of this. | 10:30 |
laidback_01 | yeah, usually you have to pick to intentionally use a backports repo, devuan/debian both use sane defaults, and pulling at will from a backports repo doesn't fall into that category. | 10:31 |
gnarface | suavedandy: well i can't tell you what went wrong in the past nor do i have a good way to find out, but there should be a log in /var/log/apt/ so at least you can find out what day it happened on and maybe recall something | 10:31 |
suavedandy | I didn't run dist-upgrade, I didn't try to install anything from backports, I have only Devuan's repos. | 10:31 |
laidback_01 | well, anyway, you have micro now, should be good. comment out that backports repo to prevent more surprises. | 10:32 |
xinomilo | beowulf-backports is devuan repo. | 10:32 |
xinomilo | micro is only there, so apt install chose that.. what's the problem? | 10:33 |
suavedandy | Wait. I can't install Debian packages from third-party repos? Well this is unfortunate. | 10:33 |
gnarface | yes, it is, but it comes with the same warnings that debian gives about their corresponding backports | 10:33 |
gnarface | suavedandy: you can it just isn't recommended | 10:33 |
xinomilo | you can install anything you like.. backports is not 3rd party. it's official devuan repo. | 10:33 |
xinomilo | 3rd party repos are just not recommended | 10:34 |
xinomilo | usually.. | 10:34 |
suavedandy | I have a better solution. | 10:34 |
suavedandy | Backports repo goes WHOOSHHHHHHHH. | 10:34 |
laidback_01 | Ah- this makes sense "<xinomilo> micro is only there, so apt install chose that.. what's the problem?" Given a package that exists in both main and backports, it would choose the package in main. | 10:35 |
laidback_01 | unless you override the repo preference | 10:35 |
suavedandy | Micro was only in backports tho. | 10:35 |
laidback_01 | read that whole sentence. | 10:35 |
laidback_01 | particulary what xinomilo said | 10:35 |
suavedandy | You think it's a normal behavior? | 10:36 |
laidback_01 | said another way: if a package exists only in a single repo, including backports, and you request the install of that package, it will install from the only repo found. | 10:37 |
laidback_01 | well, I dunno. will have to read more about it. | 10:37 |
laidback_01 | but it sounds reasonable. | 10:37 |
suavedandy | Also, I added the -y flag. | 10:37 |
laidback_01 | and it's late. | 10:37 |
gnarface | i think it's a snafu | 10:37 |
gnarface | it's normal behavior in the condition where something else had gone wrong previously, and this is their fix | 10:37 |
gnarface | a combination of policy barriers and technical bugs | 10:38 |
gnarface | Ubuntu would just ram the patch into the current version | 10:38 |
gnarface | (after telling people to just blithely install a 3rd party build for several weeks prior) | 10:38 |
Unit193 | Technically Ubuntu would tell you to use the snap. | 10:39 |
gnarface | something about the previous version must have upset workflow or licensing or quality checks or the build or something | 10:39 |
gnarface | and then the fix didn't come in time for the beowulf release | 10:39 |
gnarface | i'm sure debian developers have access to a logged reason... somewhere | 10:40 |
gnarface | sometimes it's just "maintainer couldn't be reached for comment" | 10:41 |
suavedandy | You think this problem is Devuan-specific? | 10:42 |
gnarface | no | 10:42 |
gnarface | it's not an altered package | 10:42 |
suavedandy | Very weird indeed. | 10:43 |
suavedandy | Installed a backport without knowing, wow. | 10:44 |
suavedandy | This is something. | 10:44 |
gnarface | packages.debian.org shows the same situation | 10:44 |
gnarface | https://packages.debian.org/search?keywords=micro&searchon=names&suite=all§ion=all | 10:45 |
gnarface | only exists currently in backports, testing, and unstable | 10:45 |
suavedandy | If even Debian has some bugs then I fear of how broken Arch is. | 10:45 |
suavedandy | Or Fedora. | 10:45 |
gnarface | we're all here because we *know* how broken Arch and Fedora are :) but it's offtopic, really. | 10:46 |
suavedandy | Actually, when I tested SUSE, xrandr could not find my display. This is dumb. | 10:47 |
gnarface | as a transitional fix they may have simply had something else you had installed which depended on micro to refer to the backports version to avoid breaking existing upgrades. i don't know for sure that wouldn't work or wouldn't be allowed by policy | 10:47 |
onefang | I just tried it, on my Beuwolf system, with backports enabled, "apt installl micro" did indeed just install Micro, which only has a backports version. | 10:48 |
gnarface | good to know | 10:48 |
suavedandy | Maybe we should pass this to Debian devs? | 10:50 |
gnarface | i just assume it's expected behavior, but don't let me stop you from asking them. just don't mention my name over there if you want any actual help. | 10:51 |
suavedandy | Do Debian devs not like you? | 10:52 |
onefang | Now that I have installed this Micro editor, what's so good about it that I should keep it? B-) | 10:55 |
* gnarface has no idea | 10:58 | |
suavedandy | It is less broken then the apps from AUR. | 10:59 |
suavedandy | But honestly, I've installed it because it's a little bit more advanced and minimalistic than Nano. | 10:59 |
suavedandy | But God is it buggy. | 11:00 |
suavedandy | Unfortunately. | 11:00 |
suavedandy | Have to learn Vim, I guess. | 11:00 |
gnarface | you could try mg | 11:01 |
onefang | "less broken then the apps from AUR" sounds like a low bar then. I'll stick with mcedit. lol | 11:01 |
macondo123 | hi everybody, how do I chang the word "Debian" tos Devuan? in the starting menu, i've seen it somewhere but i can't remember where... | 18:21 |
macondo123 | anybody? | 18:25 |
fsmithred | you can either edit /etc/default/grub or | 18:25 |
fsmithred | etc/os-release ID=devuan | 18:26 |
fsmithred | then update-grub | 18:26 |
macondo123 | thank you very much, pal | 18:26 |
fsmithred | if you are using uefi AND secure boot... | 18:26 |
fsmithred | then you can't do that. | 18:26 |
macondo123 | ok | 18:26 |
macondo123 | fsmithred, perfect! thanks... | 18:39 |
systemdlete | fsmithred: On refracta, I tried to apt remove wicd, but it says it is not installed. But the files belonging to the wicd package are present, at least in /etc/init.d | 19:55 |
systemdlete | (sorry for double-post, wasn't sure if you saw it the first time) | 20:04 |
systemdlete | oopsy. | 20:13 |
systemdlete | wrong package name | 20:13 |
laidback_01 | yep, full reinstall and restore fixes that goofy LVM issue. | 20:40 |
fsmithred | what goofy lvm issue is that? | 20:41 |
laidback_01 | if you scrollback to about 00:55:12 you'll see the previous conversation. if you don't have the scrollback - it's about WARNING: Device /dev/<MULTIPLE> not initialized in udev database even after | 20:44 |
laidback_01 | waiting 10000000 microseconds. Replace the <MULTIPLE> with sda sdb md0 md1 sdc loop0 etc... for about 10 minutes of repeating messages... every boot | 20:44 |
laidback_01 | and then being useless as a desktop until you disconnect/reconnect usb devices. and the video resolution is wrong. | 20:45 |
laidback_01 | but I digress, a backup of the user dir, reinstall fixed this after all the various attempts at troubleshooting failed. | 20:45 |
fsmithred | O | 20:46 |
fsmithred | I'm curious what the reinstall did differently | 20:46 |
fsmithred | I've gotten that message while doing stuff in chroot (grub-install and update-grub) and fixed it by bind-mounting /run/udev to the chroot | 20:48 |
laidback_01 | fsmithred, no idea. I'm not even sure what update caused this to begin with | 21:23 |
laidback_01 | and yeah, in the chroot, this was all able to be dispensed with (during rescue attempts) - grub install worked fine to both drives, and update-grub worked without complaint also. so it makes you think all is well, but upon reboot, LVM2 starts bellering. | 21:24 |
suavedandy | fsmithred: Dude. Can I get your spin naked from XFCE and pre-installed desktop apps? | 22:26 |
fsmithred | sometimes | 22:26 |
suavedandy | Damn. | 22:26 |
fsmithred | let me see what I have | 22:26 |
suavedandy | And I wanted an encrypted boot. | 22:27 |
fsmithred | yeah, you can do that. Not separate /boot, just as part of the encrypted root | 22:27 |
fsmithred | suavedandy, there are some lighter builds in the experimental directory, I don't have any no-X isos right now | 22:29 |
fsmithred | so that leaves you with having to remove what you don't want | 22:30 |
fsmithred | in the live session, you could drop to console and remove xorg, xfce and whatever else goes with it. Then run the cli installer. | 22:30 |
suavedandy | Lighter? | 22:30 |
fsmithred | yeah, the ones with 'test' in the name have openbox and lxpanel and not a lot of apps. | 22:31 |
fsmithred | and also have nonfree firmware installed | 22:31 |
fsmithred | snapshot_chimaera is similar | 22:32 |
fsmithred | the nodbus build is also openbox | 22:33 |
fsmithred | how light do you want to go? You can do a debootstrap install from the live. | 22:34 |
fsmithred | but that's pure devuan and whatever you do with it | 22:34 |
suavedandy | I just want a tiling WM and some CLI/keyboard-driven apps. | 22:40 |
suavedandy | Mouse bad. | 22:40 |
suavedandy | Click don't want. | 22:40 |
suavedandy | Use keybinds I will. | 22:41 |
suavedandy | Preferably something with nice layouts like DWM or BSPWM. Or at least something in which I can place windows really really fast. | 22:43 |
suavedandy | I mean, if I wanted to use my lame touchpad I would probably want KDE or Pantheon or something. | 22:44 |
fsmithred | suavedandy, I think there's probably a miyolinux blend that you'd like. | 23:08 |
suavedandy | fsmithred: From all the tiling WMs there's only… i3. | 23:31 |
suavedandy | But… fine, I guess. | 23:31 |
suavedandy | Will do. | 23:31 |
suavedandy | It's… based on Buster… | 23:32 |
suavedandy | fsmithred: Do you know how complex NixOS is compared to Devuan? | 23:56 |
fsmithred | never heard of it | 23:56 |
crashoverride | fsmithred: are you related to the hacksmith? :D | 23:56 |
fsmithred | nope. Not my real name. | 23:57 |
laidback_01 | nixos uses systemd.... just fyi | 23:58 |
laidback_01 | or, it's a core dependency that is. | 23:58 |
laidback_01 | https://github.com/NixOS/nixpkgs/issues/24346 | 23:59 |
fsmithred | suavedandy, why not start with the devuan minimal-live? | 23:59 |
crashoverride | nixos is OLD | 23:59 |
crashoverride | but it's not the best distro, by far. | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!