slvr | Hmmmm. Super glitchy graphics after upgrading from ascii to beowulf | 03:59 |
---|---|---|
slvr | I think display compositing got enabled.... Menus keep moving around and the edges where shadows would be are flickering.... | 04:01 |
slvr | My solution last time was to use fluxbox but maybe I'll fix it the right way this time. Any idea how to make mate work again? | 04:02 |
fsmithred | turn off compositing? | 04:03 |
slvr | "comp" returns no results in control center | 04:03 |
fsmithred | they might have some clever name for it | 04:03 |
slvr | lucky me | 04:03 |
slvr | I love "clever" software | 04:03 |
fsmithred | I don't know mate very well | 04:03 |
fsmithred | lol, I understand | 04:04 |
slvr | ha. we're both here, after all. | 04:04 |
fsmithred | good point | 04:05 |
fsmithred | there's always xfce | 04:05 |
slvr | oh god no that's even worse | 04:05 |
slvr | mate is Old Gnome. XFCE is a lightweight core with lots of New Gnome bolted on. | 04:05 |
fsmithred | yeah, it's a basic desktop. I use it mostly. | 04:06 |
slvr | It's sloooooooooooow though | 04:06 |
fsmithred | oh, everyone who comes from another linux or from windows says it's fast. | 04:06 |
slvr | I ran xfce on a pentium 133 before they started adding gnome components | 04:06 |
fsmithred | you got spoiled by fluxbox. | 04:06 |
slvr | fluxbox and icewm are very nice | 04:07 |
fsmithred | lol, it works better on newer computers | 04:07 |
fsmithred | I ran gnome on a p166 | 04:07 |
slvr | I disagree. The computer works better. The desktop is stil la dog. | 04:07 |
fsmithred | but only a couple times | 04:07 |
fsmithred | it was painful | 04:07 |
slvr | kde 2 ran pretty ok on a pentium. 3 needed more oomph | 04:07 |
slvr | I have a p75 here, if anyone is remotely interested in devuan running on it. | 04:08 |
slvr | slackware works. :) | 04:08 |
fsmithred | I'm sure you could do it. Just be selective about software. | 04:08 |
slvr | vim took 5 minutes to start | 04:09 |
fsmithred | ouch | 04:09 |
slvr | I got it down to 30 seconds by switching to a kernel that used less memory | 04:09 |
gnarface | oh they took 586 support out of the debian kernels didn't they? | 04:09 |
slvr | yeah | 04:09 |
gnarface | bummer | 04:09 |
slvr | 686 and up now | 04:09 |
slvr | I have a box that is SOOOOO CLOOOOOSE but not quite there. p200 mmx | 04:10 |
slvr | a year newer and it'd be a ppro | 04:10 |
gnarface | i think it might be a fairly easy thing to recompile it back in | 04:11 |
slvr | yeah the kernel is cake | 04:11 |
slvr | userland.... takes a while | 04:11 |
gnarface | hmm | 04:11 |
gnarface | i bet with distcc you could use both of them at once | 04:11 |
gnarface | maybe cut the time to compile userland in half? | 04:12 |
slvr | I work at a cloud provider.... Compiling on a few dozen modern intel cores at once might be faster. | 04:13 |
Digit | what are devuan release names based on? can someone remind me? | 04:31 |
* Digit failing to find answer expediently enough for conversation eleswhere | 04:31 | |
Digit | minor planets, nm, got it. | 04:32 |
Digit | amusing when you try dive deeper for the info, when it's the sort of info that's presented on the main page of the website. n_n | 04:33 |
bleb | for some reason a mail sent from my new devuan install says User-Agent: NeoMutt/20170113 (1.7.2) | 06:12 |
bleb | i'm certain i did apt install mutt | 06:12 |
bleb | and there's no neomutt package | 06:12 |
bleb | so is devuan's mutt package really neomutt? | 06:12 |
golinux | bleb: https://pkginfo.devuan.org/cgi-bin/d1pkgweb-query?search=neomutt&release=any | 06:38 |
golinux | https://pkginfo.devuan.org/cgi-bin/d1pkgweb-query?search=mutt&release=any | 06:39 |
bleb | so the mutt in ascii is 1.7.2 | 06:42 |
bleb | question remains why does it say neomutt in my user agent header | 06:42 |
bleb | mutt -v prints this: http://ix.io/1ImY | 06:47 |
gnarface | bleb: is it possible you inherited that value from an old config file? | 07:07 |
gnarface | (i'm not actually using it so i don't know for sure neomutt isn't in the mutt package) | 07:08 |
bleb | not possible | 07:09 |
bleb | i never did anything neomutt | 07:09 |
gnarface | either way, it looks like you should be able to set it to something else | 07:09 |
bleb | yeah | 07:09 |
bleb | i don't so much mind the user agent, i'm just concerned that the mutt package is actually neomutt | 07:09 |
KatolaZ | bleb: IIRC the mutt packahe in debian has merged stuff from neomutt for quite a while | 07:22 |
KatolaZ | and IIRC, mutt is actually neomutt in Debian | 07:23 |
bleb | oh man | 07:29 |
bleb | classic debian, shoulda known | 07:29 |
bleb | it does look like they've diverged in buster though, as there's a neomutt package | 07:30 |
xinomilo | https://jmtd.net/log/mutt_year_zero/ | 09:32 |
* enyc meows | 10:26 | |
reubyawn | hi | 21:14 |
Hund | reubyawn: Hey! | 21:15 |
reubyawn | does devuan fully function using a macbook pro laptop? | 21:17 |
gnarface | probably not "fully" but probably mostly, on some of them. it probably really depends a lot on exactly which macbook | 21:18 |
reubyawn | how could I test it on my late 2013 hardware and does ISO have the UEFI package? | 21:22 |
gnarface | hmmm, good question... | 21:22 |
gnarface | late 2013 should be intel hardware | 21:23 |
gnarface | shouldn't be a problem to just try a live image | 21:23 |
gnarface | but i admit i'm not sure it'll work | 21:23 |
reubyawn | yes, 64-bit | 21:23 |
gnarface | not sure about the UEFI thing either. some people disable secure-boot, but you can provide your own key too if the firmware allows it | 21:25 |
gnarface | i think the correct way to say that is that it should work with EFI but you might need to intervene manually to make UEFI work | 21:25 |
gnarface | but macs are different, openfirmware might complicate things | 21:26 |
gnarface | https://files.devuan.org/devuan_ascii/desktop-live/devuan_ascii_2.0.0_amd64_desktop-live.iso | 21:26 |
gnarface | try booting this live image | 21:26 |
reubyawn | I tried ubuntu and the mac overheated, so would like to try debian, which devuan is, correct? | 21:26 |
Hund | Yes. | 21:27 |
gnarface | it's basically like debian was up through wheezy | 21:27 |
gnarface | that's where debian diverged from it's own path | 21:27 |
gnarface | devuan preserved the original direction | 21:27 |
reubyawn | I did not know that, thx | 21:28 |
Hund | reubyawn: Why did you choose Devuan over Debian then? :P | 21:29 |
gnarface | there's no need to even ask. guaranteed he asked about a mac in #debian and they were dicks to him. | 21:31 |
Hund | :) | 21:31 |
reubyawn | now, how is ISO written to a stick or does it need to be CD/dVd? | 21:31 |
Hund | I use dd. | 21:31 |
gnarface | reubyawn: they're all hybrid-iso format now, so you don't have to do anything special. dd is popular, but cp is smart enough to do it too. it should work from any usb stick just as easily as a optical disk. | 21:32 |
gnarface | reubyawn: assuming the live image boots, the first thing you'll want to do to verify it's not going to overheat is probably install "lm-sensors" if it's not included on the live image already, then run "sensors-detect" as root | 21:34 |
reubyawn | what syntax works with dd & cp? I recently switched from m$ | 21:34 |
stiltr | When I installed Kali on a MBP, I had to add a couple packages to get it to control the fans. That may be your issue. | 21:35 |
gnarface | reubyawn: cp [in file] [out file] | 21:35 |
gnarface | reubyawn: dd if=[in file] of=[out file] | 21:35 |
fsmithred | the amd64 desktop-live should boot on the macbook | 21:36 |
gnarface | reubyawn: in this case, [in file] would be devuan_ascii_2.0.0_amd64_desktop-live.iso and [out file] would be the /dev/sdc or whatever your usb key is showing up as. it is very important to make sure you get [out file] correct or you can easily hose your entire existing install pointing it at the wrong device. | 21:37 |
gnarface | (there will be no safety check or confirmation of this action) | 21:37 |
gnarface | microsoft software tends to train you to expect warnings when you're about to do something dangerous. linux generally will not. | 21:39 |
stiltr | I like to add status=progress to dd calls. (dd status=progress [in] [out]) | 21:39 |
reubyawn | I like the debian net install concept, where ISO fits on a CD and build from there. | 21:39 |
gnarface | yea since the copy will be very slow, that's not a bad idea. cp can give progress too though. | 21:40 |
gnarface | reubyawn: (there are netinstall images just like theirs here https://files.devuan.org/devuan_ascii/installer-iso/ ... but i advised the live image first just as a way for you to test hardware compatibility without committing to anything first) | 21:41 |
reubyawn | I don’t see the difference between netinstall/live? It will fly or not. | 21:44 |
gnarface | live will let you test out all the hardware more easily without actually writing anything to the harddrive | 21:44 |
gnarface | it's not just as simple as it booting or not booting | 21:45 |
reubyawn | solved, will give live a go. | 21:46 |
gnarface | audio device support, loading the right video drivers, laptop keyboard function key mappings, etc... all that stuff is a lot more difficult to verify from the netinstall without actually completing an install first. don't let me stop you from using the netinstall first instead, i was just trying to minimize risk for whatever your previous install was | 21:47 |
gnarface | i wouldn't want you to overwrite the whole thing and then realize you hate it because there's no hardware opengl acceleration available for your video card or something like that (i don't know, just an example) | 21:47 |
gnarface | it's common these days to actually have partial functionality | 21:48 |
gnarface | like generic framebuffer drivers or something like that in lieu of something that supports the hardware fully | 21:48 |
reubyawn | also, I’m new to IRC and do I sign into this room using ‘#devuan’ w/o any password? | 21:49 |
gnarface | /join #devuan | 21:49 |
gnarface | you might want to register your handle with NickServ but that's a IRC network-level thing, not specific to this channel | 21:49 |
reubyawn | Is that from the freenet console? | 21:50 |
gnarface | freenode*, yes | 21:50 |
gnarface | you can get all kinds of help with /help | 21:50 |
reubyawn | thx, bye | 21:51 |
gnarface | no problem, good luck | 21:51 |
gnarface | let us know how it works out | 21:51 |
cosurgi | question: what's the best way to backport latest g++ version to ascii ? | 21:57 |
cosurgi | is the some release-backports to put into /etc/apt/sources.list ? | 21:57 |
cosurgi | Or maybe not the latest, just a package with some relatively recent version of g++ | 21:57 |
gnarface | there is ascii-backports. did you check there for it? | 21:58 |
gnarface | oh, nevermind, it's probably not there actually | 21:58 |
gnarface | i did this once before and ended up backporting half the next release to make it work | 21:58 |
gnarface | it might not be worth it, if you can get away with just installing testing or unstable in a chroot and building whatever it is you need the new g++ version for in there | 21:59 |
gnarface | that's what i've been doing anyway | 21:59 |
cosurgi | Hmm.. yeah. I already have 7 chroots: bionic buster cosmic disco sid stretch xenial | 22:00 |
gnarface | the technique is also useful for building for foreign architectures | 22:00 |
cosurgi | and a nice script to start screen in all of them. I wanted it localy though | 22:00 |
gnarface | that way you don't muck up your main install though | 22:00 |
cosurgi | yeah. I checked. It;s not in ascii-backports | 22:01 |
gnarface | mixing stuff created for different releases tends to cause weird problems | 22:02 |
cosurgi | I'll check if I can backport it with simple `apt-get build-dep` and `dpkg-buildpackage -rfakeroot -b -j32` | 22:02 |
gnarface | it might work, but what i discovered previously is that you have to recursively do that for all the dependencies down to libc first, and by the time you've done that, you might as well have just upgraded to the next release | 22:03 |
cosurgi | But did you rebuild g++ or install *deb ? | 22:04 |
gnarface | i was actually building something else that needed a newer [everything] including g++ | 22:04 |
gnarface | the dpkg-buildpackage method did work | 22:04 |
cosurgi | and..? | 22:05 |
cosurgi | if you installed the package built on local system... | 22:05 |
cosurgi | ahh! ok. | 22:05 |
gnarface | well like i said, when i was done i realized i'd replaced like 80% of the installation with hand-backported packages | 22:05 |
cosurgi | I get it. | 22:05 |
cosurgi | All the library.so were linked with wrong linker version. | 22:05 |
gnarface | it wasn't worth it. but i was following orders | 22:05 |
cosurgi | thanks! | 22:05 |
cosurgi | So I can't do that. | 22:05 |
cosurgi | OK. I will export DISPLAY from chroot. And will have my gvim in there. | 22:06 |
gnarface | i think that will work | 22:07 |
gnarface | you could always use virtualization too, then just ssh in | 22:07 |
cosurgi | nah | 22:07 |
gnarface | but that might be overcomplicating things | 22:07 |
cosurgi | I have done a (nearly) perfect chroot automaton. | 22:07 |
cosurgi | Will put it on some wiki somewhere later. It's worth sharing. | 22:08 |
gnarface | cool | 22:08 |
cosurgi | oh, btw, does devuan have some wiki? I was thinking about wiki for my software: https://yade-dem.org/wiki/Yade | 22:12 |
cosurgi | I could put it on devuan wiki :) | 22:12 |
gnarface | there's this forum here: https://dev1galaxy.org/ | 22:12 |
cosurgi | oh! I didn't know about that. Cool! | 22:13 |
cosurgi | I guess that wold go into a DIY section :) | 22:13 |
reubyawn | LIVE flies OOTB | 23:28 |
fsmithred | reubyawn, if your hardware wants 32-bit grub, the package is in / | 23:30 |
fsmithred | you can install it before running the installer or else do it in chroot in the middle of the install | 23:30 |
reubyawn | why 32-bit grub when LIVE/macbook is 64-bit? | 23:32 |
gnarface | he said "if" | 23:32 |
gnarface | it's not uncommon for some ARM hardware to be 64-bit but still need to boot in 32-bit mode. i don't know if that's the case for macbooks | 23:33 |
gnarface | also note that the live installer won't have the same flexibility as the debian-style netinstall images. it basically just mirrors the live install to the drive | 23:33 |
gnarface | so if you want more flexibility at install time, use the netinstall image | 23:34 |
reubyawn | For now, I’ll burnin LIVE, but can LIVE incorporate persistance, so data can survive reboot? | 23:35 |
gnarface | live can incorporate persistence, but if you use the installer that's included on the live desktop, you don't need to bother with that, it will still make a regular install. i didn't mean it literally mirrors the live image to the disk, i mean it just uses the same package selection and base configurations for those packages. | 23:36 |
gnarface | so it won't ask you questions | 23:36 |
gnarface | it'll just replicate (uses refracta) | 23:37 |
reubyawn | one subtle issue is the small desktop icons. how are they enlarged? | 23:37 |
gnarface | uh, i don't know. i think that's probably a xfce setting in this case | 23:38 |
gnarface | make sure your DPI is set right too | 23:38 |
gnarface | or, make sure the DPI is set right first, i mean | 23:38 |
gnarface | but i do think there's an icon size setting in there somewhere also | 23:38 |
reubyawn | I found text, but not icon zoom | 23:39 |
gnarface | settings->desktop->icons ? | 23:40 |
gnarface | menu->settings->display? | 23:40 |
gnarface | something like that? | 23:40 |
gnarface | a quick google search suggests to me that maybe people are using the whisker menu plugin to get control over icon sizes | 23:41 |
gnarface | i believe it's not installed by default, but it is in the repo | 23:42 |
gnarface | you might be used to some other distro that included it by default | 23:42 |
reubyawn | I guess DPI would be trial-n-error | 23:42 |
golinux | Xfce does it in settings > appearance > settings | 23:42 |
gnarface | eh, the manufacturer should have provided accurate screen DPI values in the user manual or the specs on the box... | 23:43 |
gnarface | in a worst-case scenario you can get out a ruler and do some math | 23:43 |
gnarface | for something like a macbook, the internet should already know this though | 23:44 |
gnarface | that is something Apple customers care about | 23:44 |
reubyawn | other question, which IRC app does LIVE like for this room? | 23:44 |
gnarface | i don't know if there is one | 23:45 |
fsmithred | there are icons on desktop for larger/smaller font | 23:45 |
fsmithred | and icons | 23:45 |
gnarface | i like hexchat for IRC | 23:45 |
gnarface | (it's just a fork of xchat because xchat went non-free) | 23:46 |
reubyawn | is hexchat CLI | 23:46 |
gnarface | no | 23:46 |
gnarface | if you want a command-line irc client, i think irssi is popular | 23:46 |
reubyawn | the plan is not to mess with internal SSD, only use USB 3.0 external | 23:48 |
FlibberTGibbet | weechat is also great if you adore lots of hair-trigger options :) | 23:48 |
gnarface | you can pass simple regexp patterns to "apt-cache search" to find stuff. try: apt-cache search irc.*cli | 23:48 |
reubyawn | NO bloat here | 23:48 |
FlibberTGibbet | weechat is cli | 23:49 |
FlibberTGibbet | it was just written by someone who found emacs to be a bit unconfigurable for their taste | 23:49 |
gnarface | reubyawn: note that the install feature in the live image may not even give you a choice of target disk. it might just pick the first one it finds | 23:50 |
gnarface | it would be a good idea to use the netinstall if you need to pick a specific disk and preserve another OS install | 23:50 |
gnarface | though i guess nothing really is stopping you from doing a chroot + debootstrap install from the live image either | 23:51 |
reubyawn | Then I’d want to add persistence to the existing stick, if possible . . . | 23:51 |
gnarface | that'll slow you way down but it is possible. afaik it works just like persistence on the debian live images | 23:52 |
fsmithred | can't add persistence to the stick if you used dd to create it | 23:52 |
gnarface | oh, well you have to repartition | 23:52 |
gnarface | i think you could do it with gparted though, no? | 23:53 |
fsmithred | that works on the 32-bit isos, but not on the 64 | 23:53 |
fsmithred | has to do with the uefi stuff | 23:54 |
gnarface | oh | 23:54 |
reubyawn | did you post a netinst ISO for starters | 23:54 |
denPes | hello | 23:56 |
denPes | anyone here using beowolf release? | 23:56 |
gnarface | yes, in here reubyawn https://files.devuan.org/devuan_ascii/installer-iso/ | 23:56 |
gnarface | https://files.devuan.org/devuan_ascii/installer-iso/devuan_ascii_2.0.0_amd64_netinst.iso | 23:56 |
denPes | can i just use beowolf, or is it better to stick to ascci, when it comes to issues and stuff | 23:57 |
gnarface | a few people are, denPes. i'm not sure exactly who. you might have to wait a while to talk to them. if you have to ask that question though, you're better off sticking with ascii and using ascii-backports for newer drivers and mesa etc. | 23:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!