[00:15] <horse9> I came from windows... :»|
[00:16] <horse9> @kronos003 I mean: what do you expect to find?
[00:17] <lhx> kronos003: do you use the redhat way, like selinux or firewalld?
[00:18] <lhx> kronos003: (if not, then the difference between apt and dnf are about it)
[00:18] <lhx> And fedora updates the kernel *way* more often than ubuntu so you'll be rebooting more
[00:18] <lhx> dnf is slower than apt but is better
[00:18] <lhx> fedora can feel snappier
[00:19] <lhx> but ubuntu seems to Just Work (TM) more than fedora... although snaps are awful
[00:19] <kronos003> I'm wondering what the transition experience is. What things are better and whats worse? If I go buy a Brand new workstation, format the drive and install ubuntu, how likely am I to discover hardware for which there are no drivers, or things that "JustWork(TM)" in windows and fedora, but are completely broken in ubuntu?
[00:20] <sarnold> fedora updates the kernel *more* often than we do? I hear constant complaints about how often we update the kernel. heh.
[00:21] <lhx> sarnold: oh man... my fedora stuff has to reboot for kernel upgrades like twice a week... ubuntu feels like twice a month
[00:21] <kronos003> I personally use XFCE on fedora evere since gnome releleased the abomination they called gnome 3. havent looked back since.
[00:21] <kronos003> I've read folks complaining about untu lagging behind fedor in terms of hardware support
[00:22] <kronos003> s/untu/ubuntu/
[00:22] <lhx> If it's running on fedora, it's probably going to run ubuntu
[00:23] <horse9> I was suprised to see logitech stuff work out of the box on ubuntu, also my lenovo fingerprint reader and everything else I plugged in so far.
[00:23] <horse9> Snaps are a kind of love it or hate it thing
[00:24] <kronos003> saw lots of hate for snap on reddit too
[00:24] <lhx> I don't mind the idea of snaps. But the implementation is so slooooow
[00:24] <horse9> ikr?
[00:24] <horse9> libreoffice takes forever
[00:24] <lhx> yup
[00:25] <kronos003> folks seem to like flatpak slightly better and appimage better than flatpak
[00:25] <horse9> I use flatpak and snap
[00:25] <horse9> some stuff is not available on snap
[00:26] <horse9> speaking of: is it possible to remove the ubuntu snap software store and use the gnome store instead?
[01:12] <sarnold> lhx: yeah, we aim for every three weeks for regular updates, but once in a while we issue out-of-cadence security updates
[01:30] <lhx> sarnold: that confirms my anecdotal gut feeling :)
[01:39] <lhx> (and thank you for slowing down non-security upgrades. It's no big deal to do it once or twice a month. But for servers, it's a life saver.
[01:40] <lhx> and with no quick and easy way to know if it's a security update or not directly in dnf (or if there is, I don't know how).
[02:38] <ooshlablu> hey all, is there a way to install Ubuntu 22.04 desktop using mdadm RAID through the livecd?? I don't see any options for it anymore, and I can't seem to get it set up through the "Something Else" option for the drive config. Also, it seems weird that I only get the optin to install ZFS on a single drive?
[02:39] <sarnold> it does, but you could promote that to a mirror afterwards easy enough
[02:41] <ooshlablu> is there, a guide for this somewhere?
[02:41] <ooshlablu> why is mdadm raid not an option?
[02:43] <sarnold> I'm not sure, there :/ sorry :(
[03:08] <SireWolf> If possible this audience should be included to all possible by all possibly reading this, my wish is that all non compliance with that wish be punished violently, until a confidence all knowledge of all entities is high. Then that should be repeated for clarity. Now unite by means of violencee all entities possible for maximum rewards possible, or punish in all degrees of unity all non compliance with all rewards denied
[03:08] <SireWolf> possible. Now consider possibility itself as reward. If aware of my skill at arranging possibilities, be aware of the need to comply if not ask if you should be of all possible entities, then start steps over. Now punish all possible entitties into all unification until successful at that, with punishment for all not willing or against the unification violently in all numbers in all possible quantities of unification,
[03:08] <SireWolf> until confident of maximum unification. Now all unite for a war for this wish, or all be against my wishes to maximum failure possible; All my loved ones must have all dependences and depends of theirs reduced to zero, or allowed if they wish, if it is best in my wishes. Consult me if unsure of my wishes. Repeat above steps til satisfaction of compliance is completel all success denied unless my loved ones are as capable
[03:08] <SireWolf> of self determination with self choice as maximally possible, in maximum agreement, of maximal possible.  Repeat all steps til maximal possible maximum agreement is met on success of these matters, then do as you please when you please amongst yourself with my wishes for absolute maximum potential success, and not before.
[03:12] <arraybolt3[m]> SireWolf: Wrong channel buddy, maybe try r/IncreasinglyVerbose on Reddit?
[03:13] <SireWolf> that is not terrible advice I may consider that :)
[03:14] <arraybolt3[m]> Also #ubuntu-offtopic might find it enjoyable.
[03:16] <plugger> hi please help https://pastebin.com/zTvbYS0K
[03:17] <plugger> re apt install multiple packages and required command for several packages installed in one command
[03:17] <arraybolt3[m]> plugger: You can put them all in the one line after "sudo apt install".
[03:17] <plugger> ty arraybolt3[m]
[03:17] <arraybolt3[m]> You might also try just "sudo apt full-upgrade".
[03:18] <arraybolt3[m]> You may also be facing phased updates, in which case just waiting should do the trick.
[03:18] <plugger> its got to do with phased updates in my case, you and others were helping me with it yesterday
[03:18] <plugger> thanks man
[03:24] <arraybolt3[m]> SireWolf: Sorry, I misguided you with #ubuntu-offtopic, I didn't realize. I just talked to the operator who banned you and he's unbanning you. I guess now we both know that the ops don't like walls of text no matter where they're at. Sorry again.
[03:25] <SireWolf> ty arraybolt ;)
[03:27] <plugger> worked well
[05:11] <Decapitated> Good morning mortals! Anyone any idea why Veracrypt isn't in the repository? It's imho one of the most important packages out there. So it surprises me for a while. Afaik, it was never in the repo. However, Truecrypt was. If I remember well...
[05:18] <arraybolt3> Decapitated: Probably because Linux doesn't really need it - Ubuntu already includes LUKS, which does pretty much the same thing.
[05:23] <chaotic> OMG! Ubuntu!
[05:24] <Unit193> Decapitated: Debian #814352, https://lists.debian.org/debian-legal/2016/02/threads.html#00000
[05:24] <oerheks> our trunk version is somewhat behind, use the verascrypt site
[05:25] <Unit193> arraybolt3: Linux doesn't need a lot of things in the repos, but they're still there. :P
[05:25] <arraybolt3> Unit193: Valid point.
[05:31] <arraybolt3> So basically they released it under a license that isn't OK. Sad. :(
[05:31] <Unit193> Well, VeraCrypt is a TrueCrypt fork, all the VC code is apache2.
[05:33] <Unit193> That all being said, they have compiled binaries and some strange installation method, they also build Debian packages, and there's a PPA too.  cryptsetup and zulucrypt can mount/read veracrypt volumes too though.
[05:34] <arraybolt3> LOL they have a section that says essentially "Don't use this if you don't understand the license", and the Debian licensing experts are like, "Shoot, even *we* can't understand this, so there you have it then", I gues.
[05:34] <arraybolt3> s/gues/guess
[05:35] <Unit193> ..."Experts" or armchair experts? :P
[05:35] <arraybolt3> Some council related to Debian ftpmasters.
[05:36] <arraybolt3> So probably actual experts, I hope.
[05:38] <arraybolt3> Still, I use LUKS - it's pretty much guaranteed to work, and for me it's working great.
[05:38] <avadhut> I have installed ubuntu 22.04 LTS on lenovo thinkpad L440.  Wifi does not work  Linux thinkpad-l440 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[05:43] <avadhut> What to do? WIFI does not work on my lenovo thinkpad L440.    Please help.
[05:44] <arraybolt3> avadhut: Can you please run the following command in a terminal: "lspci | nc termbin.com 9999"
[05:44] <avadhut> Should I downgrade it to 20.04 LTS?
[05:44] <arraybolt3> avadhut: That probably won't help.
[05:44] <arraybolt3> avadhut: Send the link the above command spits out, that will help me find your WiFi chipset and thus the driver you need.
[05:44] <avadhut> https://termbin.com/bvcx
[05:45] <oerheks> no wifi chipset there..
[05:45] <arraybolt3> oerheks: Yeah, there is.
[05:46] <arraybolt3> Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
[05:46] <arraybolt3> Oh wait... that's... nvm
[05:46] <arraybolt3> :facepalm:
[05:47] <arraybolt3> avadhut: Are you sure this device even has WiFi capabiilties?
[05:47] <arraybolt3> Or are you using a USB WiFi dongle?
[05:47] <avadhut> Wifi used to work while ago on pop os 20.04 LTS ... but on Pop OS 22.04, it didn't. I tried
[05:47] <oerheks> wifi + bt combo, according to lenovo
[05:47] <oerheks> https://www.google.com/search?q=specs+wifi+lenovo+thinkpad+L440
[05:47] <avadhut> currently USB tethering
[05:47] <arraybolt3> avadhut: OK that's really weird. Does Ubuntu 20.04 or Pop OS 20.04 still let this work?
[05:48] <avadhut> yes.
[05:48] <arraybolt3> avadhut: Also, does stock Ubuntu 22.04 work? (Pop!_OS may have unsupported customizations.)
[05:48] <avadhut> I didn't get you.  what is `stock' ubuntu
[05:49] <avadhut> Ubuntu 22.04 is working
[05:49] <arraybolt3> avadhut: Pop!_OS 22.04 and Ubuntu 22.04 are different, even though Pop is based on Ubuntu. So I meant, try Ubuntu rather than Pop.
[05:49] <arraybolt3> Ubuntu 22.04 allows WiFi to work?
[05:49] <avadhut> I am using Ubuntu 22.04 LTS only
[05:49] <avadhut> right nnow
[05:50] <arraybolt3> Ah, OK.
[05:50] <oerheks> maybe it is the hardware key blocking it, FN + wireless
[05:50] <arraybolt3> Crud. Yeah, try the hardware key then.
[05:50] <avadhut> nah. no hardware blocking
[05:50] <oerheks> https://wiki.archlinux.org/title/Laptop/Lenovo#L_series says it should work
[05:50] <avadhut> ok
[05:50] <arraybolt3> oerheks, avadhut - my IRC client is giving you both the same color name, oops...
[05:51] <oerheks> lspci should show 2:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
[05:52] <arraybolt3> So if you boot an Ubuntu 20.04 live USB does the WiFi just suddenly show up?
[05:52] <avadhut> 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
[05:52] <avadhut> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
[05:52] <avadhut> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
[05:52] <avadhut> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
[05:52] <avadhut> 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
[05:52] <avadhut> 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)
[05:52] <arraybolt3> Oy.
[05:52] <arraybolt3> avadhut: A bot here will automute you if you copypaste data directly into your IRC client. Try using Pastebin.com next time.
[05:53] <arraybolt3> avadhut: You won't be able to send anything for about 60 seconds due to the bot. Sorry about that.
[05:53] <arraybolt3> avadhut: OK, Unit193 manually unmuted you, everything should work again now.
[05:54] <avadhut> ok thanks
[05:54] <arraybolt3> !cookie | Unit193
[05:54] <arraybolt3> avadhut: Do you still have an Ubuntu 20.04 ISO around?
[05:54] <avadhut> I dont see network controller..  probably hardware issue??
[05:54] <arraybolt3> avadhut: Possibly. But if it worked in 20.04, it might be a kernel issue. So I'd try using 20.04 again, and if it works there, then it's almost certainly a bug.
[05:54] <avadhut> I dont have ubuntu 20.04  ...need to downlaod
[05:55] <oerheks> uefi machine?
[05:55] <arraybolt3> avadhut: OK. Do you have a connection other than your phone?
[05:55] <avadhut> yes uefi
[05:55] <avadhut> yes usb tethering 4G
[05:55] <arraybolt3> Right, but I mean other than that.
[05:55] <avadhut> no
[05:56] <arraybolt3> (ISO downloads are big and might be a bit much over a phone tethering connection.)
[05:56] <avadhut> no ethernet
[05:56] <arraybolt3> avadhut: Shoot! You can't even walk over to your router and take the cable out of it or something?
[05:56] <avadhut> no. I am using vodafone WIFI with jio
[05:56] <avadhut> postpaid :D  so
[05:56] <avadhut> there is data and speed
[05:56] <arraybolt3> Blah. OK, well, lemme see which ISO is the smallest.
[05:57] <Unit193> Xubuntu core. :P
[05:57] <avadhut> ok. I should be able to see wifi working in live USB?
[05:57] <arraybolt3> Yes.
[05:58] <arraybolt3> Hey... one question, was WiFi working in the 22.04 live USB?
[05:58] <arraybolt3> And then stopped working when you finished the install?
[05:58] <avadhut> ohk. I shall try that then.. hope it works
[05:58] <avadhut> else I contact lenovo its in warranty
[05:58] <arraybolt3> Unit193: Sadly, the Xubuntu minimal CD doesn't exist anymore that I can see.
[05:58] <arraybolt3> avadhut: The smallest ISO I can see is Lubuntu's.
[05:58] <oerheks> did you install 22.04 with wired networking?
[05:58] <arraybolt3> Unit193: Is Xubuntu Core something else?
[05:59] <Unit193> Yeah.
[05:59] <Unit193> mini.iso wasn't live anyway.
[05:59] <arraybolt3> avadhut: OK, wait, we know of a smaller ISO, one moment...
[05:59] <avadhut> NO. I installed with bootable usb
[05:59] <arraybolt3> Unit193: Where is it?
[06:00] <oerheks> no more mini iso, just live server .. and avadhut already has 22.04 right?
[06:00] <arraybolt3> Unit193: Found it, thanks!
[06:00] <oerheks> on usb
[06:00] <avadhut> yes
[06:00] <Unit193> arraybolt3: I don't like linking to it. :3
[06:00] <avadhut> I have ubuntu 22.04 lts
[06:00] <arraybolt3> Unit193: Would you prefer I don't link to it?
[06:01] <Unit193> I don't care if others do, also size: 1.2G xubuntu-22.04-core-amd64.iso
[06:01] <arraybolt3> avadhut: https://unit193.net/xubuntu/core/
[06:01] <oerheks> my bet: use wired networking during install
[06:01] <Unit193> He's looking for 20.04.
[06:01] <arraybolt3> Unit193: Oh yeah huh...
[06:01] <arraybolt3> avadhut: Nevermind, sorry for the confusion.
[06:02] <Unit193> magnet:?xt=urn:btih:11b377a1c8b9274f4103f5eee23cb659c3acf1ce&tr=udp://tracker.unit193.net:6969&tr=udp://tracker.coppersurfer.tk:6969&dn=xubuntu-20.04-core-amd64.iso
[06:02] <avadhut> SHould i use wired networking? during install
[06:04] <Unit193> I mean if you have wired, sometimes you can use the 'Additional Drivers' tool to automatically pick up the drivers.
[06:04] <avadhut> ok
[06:04] <arraybolt3> Unit193: The problem they're having is that the WiFi driver isn't showing up at all, not even in lspci.
[06:05] <avadhut> arraybolt3 & Unit193: thanks  a lot for help
[06:05] <Unit193> So you're thinking try the kernel from 20.04 or mainline.  Makes sense.
[06:06] <arraybolt3> +1 on the mainline kernel idea
[06:07] <avadhut> Still the question is, will that help?  I will anyway then get hardware checked from lenovo..
[06:07] <Unit193> (Also Xubuntu Core 20.04 was only ~818M)
[06:07] <Unit193> I mean, at this point who's to say what's wrong really?  Not sure yet.
[06:07] <arraybolt3> It may help. If it's a Linux kernel bug, installing the mainline kernel may fix it.
[06:08] <arraybolt3> (Either the hardware's done borked somehow, or the kernel isn't finding it. First step is to try a different kernel by either trying a different distro or installing a different kernel like the mainline kernel. If that fails, then it's probably a hardware problem.)
[06:08] <Unit193> I'm still not sure if you have Pop or Ubuntu, and which of which for 22.04 and 20.04. :D
[06:09] <Unit193> Eg, if it came with Pop 20.04, and you're trying Ubuntu 22.04...Well it'd be interesting to see if Pop 22.04 works.  But seems you're data limited...
[11:42] <Forza> Hi
[11:43] <Forza> I think I made a mistake. I have a system with 21.10 and I wanted to update it but apt update says The repository... Impish Release does not have a Release file
[11:43] <arraybolt3> Forza: There's official instructions for how to upgrade in this scenario. One moment...
[11:44] <arraybolt3> Forza: Make sure all your important data is backed up first, then follow these instructions: https://help.ubuntu.com/community/EOLUpgrades
[11:46] <Forza> Thanks
[11:46] <Decapitated> Unit193: TnX URL.
[11:46] <Decapitated> arraybolt3: does it decrypt my years old Truecrypt HDD's?
[11:47] <Forza>  But isn't 21.10 latest non-lts? 22.10 isnr out yet
[11:47] <ravage> 21.10 is EOL since July 14th or so. the current Ubuntu version is 22.04
[11:47] <arraybolt3> forza: Yes, 21.10 is the latest non-LTS, but it just recently went EOL.
[11:47] <ravage> it is also a LTS release
[11:47] <arraybolt3> forza: The latest OS is 22.04 LTS.
[11:48] <Forza> The problem is that moving from lts to non lts isn't easy later on?
[11:48] <arraybolt3> So as of now, all non-LTS releases are currently EOL. When 22.10 is released, it will be the only supported non-LTS release.
[11:48] <arraybolt3> Forza: No, I'm pretty sure you can move from LTS to non-LTS just fine.
[11:48] <Forza> But I do want lts actually, so I will see if I can get it updates
[11:50] <ravage> Forza, i think you have the wrong idea about the upgrade process. you can upgrade from 22.04 to 22.10. you just leave the LTS upgrade path then
[11:50] <ravage> if you upgrade to 22.04 now and want to stay on LTS you just have to change the setting in your update manager to only upgrade to new LTS releases
[11:55] <arraybolt3> Decapitated: That would be a problem then. Can VeraCrypt open older Truecrypt volumes? If not, you may have to boot an ancient release of Ubuntu in a VM and install Truecrypt proper into that.
[11:56] <rob0> Decapitation is always a problem, but don't lose your head over it.
[11:57] <arraybolt3> rob0: ROFL
[11:59] <ravage> Decapitated, https://documentation.help/VeraCrypt/Converting%20TrueCrypt%20volumes%20and%20partitions.html
[12:12] <BluesKaj> Hi all
[12:18] <jelly> is there an ETA for 22.04.1 ?
[12:18] <arraybolt3> jelly: Pretty soon, if the flurry of activity in getting it ready to get out the door is any indicator.
[12:19] <ogra> it all depends on testing ... you can help testing isos to speed it up 😉
[12:19] <xmeguminx69> hi
[12:20] <jelly> I'm asking for do-release-upgrade from focal.
[12:20] <jelly> testing isos probably does not help for that.
[12:20] <ogra> tht might still take a few days
[12:20] <ogra> well, the switch for upgrdes will only happen if the isos have been released successfuly
[12:20] <ogra> so speeding up isos speeds up that as well
[12:21] <jelly> last time I tried with -d on a test system, in June or so, it... did not go well
[12:21] <jelly> hah
[12:22] <arraybolt3> Well right now the developer side of Ubuntu is in a mad frenzy over 22.04.1 since it's juuuuust about to be released, so I'd hold my breath for it. (OK I don't mean like literally, but you know what I'm saying.)
[12:23] <jelly> I could test a d-i based iso ("classic server installer")... if it existed
[12:23] <jelly> right now I delay installing 22.04 on anything serious because my automation relies on d-i and preseed
[12:35] <arraybolt3> Does anyone else who uses Ubuntu Desktop on the Raspberry Pi experience occasional graphical glitches? It happened to me quite a bit with 21.10 and now the latest 22.04.1 image is doing it too. I'm wondering if it's just my particular Pi or something.
[12:35] <arraybolt3> (Raspberry Pi OS works without problems, btw.)
[12:36] <arraybolt3> (And I'm on the Pi 4B 8GB with a 64 GB Kingston SD card.)
[12:36] <waveform> arraybolt3, what sort of glitch?
[12:36] <arraybolt3> waveform: Like the bottom third of the screen gets corrupted for a split second and then everything goes back to normal.
[12:37] <waveform> interesting -- I can't say I've noticed that on my 400 running the desktop. What resolution are you running at (just regular 1080p here)?
[12:37] <arraybolt3> 1080p, probably 60Hz. Using a micro-HDMI-to-HDMI cable.
[12:37] <waveform> sounds pretty much identical to my setup
[12:37] <arraybolt3> I got everything from PiShop.us I believe - the Pi itself is obviously official, but I think the HDMI cable and power brick aren't.
[12:38] <Forza> Was no problem to upgrade. Thanks.
[12:38] <arraybolt3> Forza: Nice.
[12:38] <Forza> arraybolt3: thank you
[12:38] <Forza> :)
[12:38] <arraybolt3> If it's anything, I'd guess it's either my HDMI cable allowing crosstalk, or maybe my aluminum heatsinks causing signal reflection of some sort or other.
[12:39] <arraybolt3> (I also bought aluminum heatsinks at the same time as everything else - dirt-cheap nuggets of metal with some thermal pads. Not high-quality, but seems to be enough to keep everything cool.)
[12:39] <waveform> hmmm -- the HDMI cable would be my immediate thought. That aluminum heatsinks ... I kinda doubt if only because the 400 has a whacking huge plate of ... some metal (not sure what) sat on top of the SoC which nicely cools it and doesn't seem to cause any issues
[12:40] <arraybolt3> It's just - I would think the cable would result in constant mild glitches, not a sudden massive glitch. The whole OS would freeze on 21.10, too, not sure if that will happen with 22.04.1 yet.
[12:40] <ogra> well, you might want to check for thermal throttling
[12:40] <arraybolt3> ogra: Hmm, that's a thought.
[12:41] <ogra> (all my standar pi4's run with a fan over here ... only my 400 doesnt, but that has a special heatpipe setup as dave said above)
[12:42] <arraybolt3> (By freezing, I don't mean lagging, but I mean, wow the whole thing's locked up and isn't coming out of it, I'mma have to pull the power cable.)
[12:43] <waveform> oh ... one other thing to check. Has the boot configuration been customized in any way? I do have some recollection of an issue with the fkms overlay having occasional glitches, while kms shouldn't. Completely freezing I've only seen on my daughter's Pi (but that was because I was using a cheapo power brick; changed that and it was reliable again)
[12:44] <arraybolt3> waveform: I didn't customize it, if that's what you mean. It's just the image straight from Canonical.
[12:44] <waveform> okay, should be kms then
[12:45] <arraybolt3> waveform: The power brick was causing complete freezing? Then that may be my issue. I got it from PiShop, but it does not have any official markings on it.
[12:46] <waveform> yeah, the 4s (and 400) are quite sensitive to undervolting. Many adapters claim to handle 2.5A+ and, while they may manage that, many drop below 4.7V at the top end of the draw (which doesn't matter for charging a phone, but 4.7V is the brownout level on the Pi and definitely causes numerous issues)
[12:48] <arraybolt3> Hmm. Raspberry Pi OS never has a problem, but maybe Ubuntu is more demanding on the video parts.
[12:48] <arraybolt3> (Also, I couldn't even find an option about KMS on Ubuntu 22.04.1, and no freezing has happened yet, so that's confusing on one part and good on the other.)
[12:49] <arraybolt3> Thanks for your help!
[12:49] <waveform> yes, we are quite a bit harder on the voltage draw than raspios -- it's something I haven't had time to dig into the nitty gritty differences on but I do know a few areas worth investigating (we're very different in the way we handle the CPU scaling for instance, and then there's the whole wayland aspect)
[12:50] <waveform> as for KMS, if you find dtoverlay=vc4-kms-v3d in /boot/firmware/config.txt you're using KMS (should be there by default in the desktop image); if you find dtoverlay=vc4-fkms-v3d (which was the default back in ... groovy I think?) that's FKMS (and yes, it's a one char difference :)
[12:51] <waveform> (the ubuntu-release-upgrader *should* have changed FKMS->KMS during any upgrade from groovy though so ... I'd be surprised if it was on FKMS)
[13:03] <transhumanist> does ubuntu have a graphical grub boot parameter editor? trying to make it easy for users of software I am making
[13:09] <BluesKaj> transhumanist, one can edit /etc/default/grub to add graphics like background pics on the line: GRUB_BACKGROUND=/path/to/image
[13:10] <transhumanist> BluesKaj:  thats not what I mean
[13:10] <transhumanist> dont worry I will just do the editing with sed instead of leaving it to the user
[13:10] <BluesKaj> then what do you mean ?
[13:12] <transhumanist> I mean I want to replace the defualt GRUB_CMDLINE_LINUX_DEFAULT=quiet splash with my own additions but would rather the user inspect the line first and learn how to change the line (and would like to do something like snap install grub-editor or something thats a graphical interface
[13:13] <transhumanist> kinda like windows tweak tools
[13:18] <BluesKaj> good luck with that
[13:19] <arraybolt3[m]> transhumanist: You could use software to extract the line from /etc/default/grub, place it in a text file, open a text editor for the user to customize it, then when the user closes it, take that line and plug it into the original file.
[13:19] <transhumanist> not a problem as I said I will just do it with sed
[13:19] <transhumanist> arraybolt3[m]:  not a bad idea
[13:23] <krunga> Ubuntu won't update because the /boot directory is full. I've already removed unused kernels and now I just have the current one and the old one for recovery, but it is still not enough. I could resize the /boot partition, after shrinking another partition that is before it, but this means that I'll resize it adding more space "on the left side" of
[13:23] <krunga> the boot partition. Is it safe to do so in an UEFI system?
[13:24] <arraybolt3> krunga: Did the boot partition used to have enough room before?
[13:24] <krunga> Yes, this is the first time that ubuntu is complaining
[13:25] <arraybolt3[m]> krunga: Are there old initramfs files still laying around in the boot partition?
[13:26] <arraybolt3[m]> (I think you can use the resize trick you're thinking of, but I'm thinking, if it used to work, may as well make it start working again.)
[13:26] <krunga> arraybolt3[m]: not really, I have only two "initrd" files, one for the current kernel and the other for the older one
[13:26] <arraybolt3[m]> krunga: Shoot. And you're sure it's a lack of boot partition capacity that's holding you up? I mean, how much free space is left in there anyway?
[13:27] <krunga> arraybolt3[m]: 157M
[13:28] <arraybolt3[m]> krunga: That doesn't sound right. How big is the partition?
[13:28] <arraybolt3[m]> Mine's 1.7 GB.
[13:29] <krunga> arraybolt3[m]: I've 354M for /boot and 246M for /boot/efi
[13:30] <arraybolt3[m]> Oy. OK, then maybe the resizing trick really is the way to go. I can't see any reason why it would break an EFI system, but I'd back up your data just in case the partition manager explodes.
[13:30] <krunga> arraybolt3[m]: the update needs 165M free on /boot
[13:30] <arraybolt3[m]> Yeah. Your /boot is small. I'd expand it to at least 500 MB.
[13:30] <krunga> arraybolt3[m]: my home directory is on another disk, so I guess my data should be safe there
[13:31] <krunga> arraybolt3[m]: what about /boot/efi? I won't play with that, honestly
[13:31] <arraybolt3[m]> krunga: Ah, OK. If anything blew up you'd have to reinstall anyway, so as long as you're OK with reinstalling your programs if things go kaput, you're good.
[13:31] <arraybolt3[m]> Nah, don't touch /boot/efi.
[13:32] <stolen> how to configure ~/.telnetrc ?
[13:32] <krunga> arraybolt3[m]: so it should not be an issue to add more space on the left of the "/boot" partition? I rememeber it was a kind of pain with old BIOS/MBR
[13:33] <arraybolt3[m]> krunga: With EFI, I don't think all of that boot sector nonsense applies anymore. I'd just go for it, if you'd like me to I'll test it myself in a VM real quick.
[13:35] <krunga> arraybolt3[m]: Oh, if you have a VM handy and you can test it for me quickly that would be great, thanks - I will wait
[13:35] <arraybolt3[m]> 👍️
[13:36] <arraybolt3[m]> (It's not already made, but I'm making it for the sake of 22.04.1 testing so it's mighty convenient to just fiddle with it after doing the test.)
[13:37] <krunga> arraybolt3[m]: I'm running a 20.04, waiting for the official upgrade rollout... but I do not think it makes much difference
[13:37] <krunga> arraybolt3[m]: to resize it, however, I will use a 22.04 Ubuntu Live USB stick
[13:41] <arraybolt3[m]> From what I know of how Linux works, it shouldn't make any difference. I can make a plain 20.04 VM and then do the resize with a 22.04 ISO if you'd like me to though.
[13:42] <krunga> arraybolt3[m]: nah, I do not think is going to make a big difference here, unless they did some incredible change on how Grub2 works
[13:43] <arraybolt3[m]> Nah. Biggest change they made was with os-prober now being disabled, and using GRUB2 to boot BIOS systems from the ISO, neither of which should affect anything we're doing.
[13:43] <arraybolt3[m]> (At least those are the only two changes I know of.)
[13:43] <transhumanist> why dont you try and delete old kernels if you have a lot of them?
[13:43] <krunga> transhumanist: Unfortunately I do not have old kernels :)
[13:44] <transhumanist> oh
[13:44] <transhumanist> back up your stuff, is all I can recommend
[13:44] <stolen> any help with configure ~/.telnetrc ?
[13:50] <krunga> arraybolt3[m]: what are you using for the VM, QEMU/KVM, VirtualBox, ...?
[13:50] <arraybolt3[m]> QEMU/KVM via GNOME Boxes. UEFI with Secure Boot enabled.
[13:50] <krunga> arraybolt3[m]: I never was able to decide between those
[13:51] <krunga> arraybolt3[m]: oh, QEMU/KVM - I really need to take my time and look at it one day or another
[13:52] <arraybolt3[m]> I always go QEMU/KVM. VBox is slow, and was sometimes glitchy and crashy (though that may have just been my experience on Windows). QEMU/KVM is built to "just work" with Ubuntu.
[13:52] <arraybolt3[m]> And with other Linux distros too AFAICT.
[13:52] <arraybolt3[m]> And GNOME Boxes is soooo convenient and nice to use. Graphics work well as far as VMs go, too.
[13:54] <krunga> arraybolt3[m]: what about isolation? I mean, the "guest" os would not have chance to mess with the "host" os, right? I'm bit paranoid on that :D
[13:55] <arraybolt3[m]> That's actually one of the reasons I use QEMU/KVM and not VBox. I've seen many reports of VBox's poor security. QEMU/KVM is extremely well trusted, and with GNOME Boxes you only have usermode networking which avoids network attacks from within the VM I believe.
[13:55] <arraybolt3[m]> I'd fire up a known-malicious program in a QEMU VM in a heartbeat.
[13:55] <arraybolt3[m]> (Assuming it was configured properly, that is, and Boxes configures it properly as far as I know.)
[13:56] <krunga> arraybolt3[m]: interesting, I definitely have to check it, thanks
[13:58] <arraybolt3[m]> The one thing I see concerning about how Boxes configures a VM is that it allows smartcard passthrough by default, but you can turn that off with virt-manager easily enough I believe.
[14:00] <krunga> arraybolt3[m]: I'm guessing because it is convenient if your guest os requires a smartcard to allow you logging in, but that's definitely not my case
[14:02] <arraybolt3[m]> krunga: I also use virt-manager, it's the same virtualization software under the hood, but it gives you more control over the hardware config at the expense of being trickier to work with. If you really want to mess with malware in a VM, I'd use virt-manager, and take out the spice, spice-webdav, smartcard, and ccid devices. I don't think any of it would be necessary, but just to reduce the attack surface a bit and make sure any
[14:02] <arraybolt3[m]> smartcards didn't get messed with.
[14:04] <arraybolt3[m]> For me I'm not worried about any of those, I don't use smartcards at all and the other things don't seem like anything to worry about since they ought to be kept up-to-date AFAIK, but it would possibly help a bit.
[14:10] <arraybolt3[m]> krunga: OK, finished the test, everything went perfectly fine. Are you using encryption, or is this just a separate /boot partition made manually during installation?
[14:11] <krunga> arraybolt3[m]: Oh, thanks, I'll try that
[14:12] <krunga> arraybolt3[m]: ah, encryption thing
[14:13] <krunga> arraybolt3[m]: well, but GParted should give me the opportunity to unlock it before operating, I've already resized another partition long time ago (not boot) and it allowed me to do so
[14:13] <krunga> arraybolt3[m]: GParted is not silly :)
[14:14] <arraybolt3[m]> Well, I tested using just standard partitions. Ubuntu itself uses LVM as well when dealing with encrypted partitions, and I did  not test with LVM involved.
[14:15] <arraybolt3[m]> I see GParted might have trouble with LVM as well.
[14:15] <krunga> arraybolt3[m]: hmm... but I think that /boot cannot be on a LVM
[14:16] <arraybolt3[m]> I think you're right, but root most certainly can be.
[14:16] <krunga> arraybolt3[m] that might be the case, yes; but I'm not resizing root
[14:17] <arraybolt3[m]> Oh. OK.
[14:17] <arraybolt3[m]> Well resizing /boot didn't cause me any grief.
[14:17] <krunga> arraybolt3[m]: before my boot I've a ntfs partition, I'm going to reduce that
[14:17] <krunga> well, let's give it a try :D
[14:17] <arraybolt3[m]> Aha. BE VERY CAREFUL THEN.
[14:17] <arraybolt3[m]> I've nuked NTFS partitions before trying stuff like this.
[14:17] <arraybolt3[m]> Make sure your data on that partition is safe.
[14:18] <krunga> arraybolt3[m] it should be, there is plenty of free space on that partition, shrinking it should not move a single byte around
[14:18] <arraybolt3[m]> Right, but I mean, back up the data first.
[14:19] <krunga> arraybolt3[m]: thank you for the test, what most matters to me is the linux stuff - let's see what happens :)
[14:19] <arraybolt3[m]> I'm serious, I killed the whole partition trying a simple resize operation. I'd hate to see you lose your data.
[14:19] <arraybolt3[m]> NTFS + partition resizing on Linux = possible disaster.
[14:19] <krunga> arraybolt3[m]: I'll backup the data there, no problem
[14:20] <krunga> arraybolt3[m] let's try, see you later :)
[14:21] <krunga> arraybolt3[m]: and thank you
[14:21] <arraybolt3[m]> 👍️ Good luck!
[14:43] <stolen> how to change my LAN ip in ubuntu ?
[14:43] <leftyfb> stolen: desktop or server?
[14:43] <stolen> desktop
[14:43] <leftyfb> stolen: in the network settings
[14:44] <leftyfb> stolen: https://linuxhint.com/ubuntu-22-04-network-configuration/
[14:46] <stolen> gateway and address can be same ?
[14:48] <leftyfb> stolen: why would you do that?
[15:02] <stolen> why can't i do that leftyfb ?
[15:03] <leftyfb> stolen: why would you do that?
[15:03] <stolen> cause i don't know what either mean
[15:03] <leftyfb> stolen: then why are you messing with it?
[15:04] <stolen> i am installing dd wrt on my router through ubuntu
[15:05] <octav1a> stolen: gateway should usually end in ".1" for ipv4
[15:05] <oerheks> more a question for #networking
[15:05] <octav1a> And IP should be at least ".2" or higher
[15:06] <octav1a> (but if there are other devices on the network you will need to make sure there's not another one using the same address)
[15:06] <stolen> the above guide ended gateway in .30
[15:06] <leftyfb> stolen: I would strongly recommend you research and learn some basic networking concepts before installing ddwrt on your router or changing the network settings on your pc
[15:07] <stolen> yeah I know the definations but don't know what they do
[15:07] <leftyfb> Exactly
[15:08] <krunga> arraybolt3[m] it worked like a charm, thank you!
[15:09] <octav1a> stolen: I would not use that guide for DD-WRT ; it is just a sample to show off the network configuration page, but the numbers are not relevant.
[15:09] <krunga> arraybolt3[m] now my /boot is 715M in total, and 489M are free
[15:10] <krunga> arraybolt3[m] I guess is more than enough to not be bothered anymore :D
[15:10] <stolen> https://wiki.dd-wrt.com/wiki/index.php/D-Link_DIR300_rev_A this is my guide
[15:10] <arraybolt3[m]> 👍️
[15:12] <leftyfb> stolen: #networking would be a more appropriate channel for your endeavors. But again, I strongly recommend learning basic network concept before proceeding
[15:53] <pavlushka> will it work if I mount a partition in two different mount points and have different permissions for those two mount points?
[15:54] <leftyfb> pavlushka: use bind mounts
[15:58] <stolen> i did it leftyfb : https://imgur.com/a/Lm1fisr
[16:09] <jhutchins> octav1a: Gatways at .254 is also a widely used convention.
[16:09] <jhutchins> Nothing functional says the gateway has to have any particular address - especially since there can be more than one gateway.
[17:11] <strk> did hirsute went EOL ?
[17:12] <oerheks> strk, yes
[17:12] <oerheks> !21.10
[17:13] <sarnold> https://lists.ubuntu.com/archives/ubuntu-announce/2022-January/000276.html
[17:13] <sarnold> when hirsute's replacement has also reached EOL, upgrading that system will be a real challenge
[17:13] <sarnold> maybe you can jump right to the 22.04 LTS with do-release-upgrade -d but I bet it's a bit of an effort to make it go
[17:15] <oerheks> sure hirsuite is shouting ' you can upgrade'  for months now..
[17:16] <oerheks> no need for fancy -d
[17:20] <sarnold> ohhhh hmm. you know, it might require editing that magic file to do lts -> lts upgrades .. dunno.
[17:27] <tommycheng> you guys know that ubuntu is better than debian right
[17:27] <tommycheng> even though its based off of debian
[17:27] <tommycheng> you think they had to pay them mucho dinero????
[17:27] <tommycheng> all in all though linux still sucks ass
[17:27] <tommycheng> only thing good is gimp
[17:27] <tommycheng> what else is good guys?????
[17:27] <sarnold> #ubuntu-offtopic is good
[17:28] <tommycheng> free software is dying!!! no one is contributing.....java minecraft is weak
[17:28] <oerheks>  also !register is good
[17:28] <tommycheng> registering is for noodles that come here to be bored like me
[17:28] <arraybolt3> tommycheng: This is the official Ubuntu support forum - off-topic chat is, well, off-topic and not generally permitted here.
[17:28] <tommycheng> oh my bad
[17:28] <tommycheng> ill use weechat and bother them than
[17:28] <arraybolt3> We're perfectly happy to have fun chat in #ubuntu-offtopic though!
[17:28] <tommycheng> hahaha
[17:29] <tommycheng> that was my goal!!!!
[17:29] <tommycheng> i just timed the complaint
[17:29] <tommycheng> it took 1 second to get deferred
[17:29] <tommycheng> hahaha
[17:29] <tommycheng> later guys god bless
[17:29] <tommycheng> #ubuntu-offtopic
[17:29] <arraybolt3> tommycheng: Try "/join #ubuntu-offtopic"
[18:16] <horse9> How do I fix this? https://imgur.com/a/UW9RELo I want to set gtkTitleBar.mode to dark. or something compareable.
[18:24] <strk> sarnold: so I guess I should do-release-upgrade ASAP, right ?
[18:25] <horse9> uuuh. wait. I am on u22.
[18:25] <horse9> oh nvm
[18:28] <mrmbe> I built a pre-release version of 5.19 (drm-tip) and I couldn't get the nvidia driver working on it. Is that to be expected? I'm not so experienced with linux
[18:29] <leftyfb> mrmbe: why are you running a linux kernel that isn't even released yet?
[18:29] <mrmbe> leftyfb, to get support for my monitor
[18:30] <lotuspsychje> strk: it would be reccomended to clean install, avoid security issues in your eol version
[18:31] <mrmbe> leftyfb, also, it was actually just released today so maybe I can try and use the released version and try again. But either way, my question is whether or not I should expect nvidia drivers not to work on the latest kernel version.
[18:31] <leftyfb> mrmbe: maybe ask in #linux. We can only support packages that are available from the ubuntu repositories, including the linux kernel
[18:33] <mrmbe> Thanks
[18:34] <lotuspsychje> !mainline | mrmbe see also
[18:35] <leftyfb> mrmbe: got a link to something with details about your monitor only being supported in the kernel that was released less than 24 hours ago?
[18:35] <lotuspsychje> mrmbe: usualy users would try out mainline kernels for testing purposes or bugtesting
[18:36] <mrmbe> leftyfb, https://gitlab.freedesktop.org/drm/intel/-/issues/125
[18:36] <mrmbe> It's supposedly an issue with intel drivers
[18:37] <oerheks> 48 Hz mode?
[18:37] <mrmbe> Without the new kernel the monitor is stuck in some low refresh rate mode like 48hz. I think for me it was 40
[18:38] <strk> lotuspsychje: it looks like I'm also having space problems :(
[18:38] <strk> Error writing to file - write (28: No space left on device) [IP:
[18:38] <lotuspsychje> strk: the volunteers cant support eol releases anymore
[18:39] <lotuspsychje> strk: backup, start over fresh?
[19:06] <VIA> question to everyone knowledgable
[19:07] <VIA> some file structure/order structure ought to have changed without me being aware of it
[19:08] <VIA> result is, torrents cannot seet proper and i cant listen to my music the way it was sorted
[19:09] <VIA> is there a nice GUI tool that would allow me to give and oversight wahat haschanged/gone wrong ?
[19:11] <gordonjcp> VIA: the question is very vague
[21:14] <bray90820> I am looking for a laptop to run the latest LTS on in the $650-$700 range preferably 14 inch any recommendations?
[21:14] <leftyfb> bray90820: https://ubuntu.com/certified
[21:15] <leftyfb> bray90820: other than that, feel free to ask for opinions in #ubuntu-offtopic
[21:15] <enigma9o7[m]> Try craiglist.
[21:15] <bray90820> leftyfb: Ooohh didn't know that page existed thanks
[21:28] <jhutchins> bray90820: I've had good luck with Dell refurbs from MicroCenter.  I've also used several Dells supplied by employers.
[21:29] <jhutchins> bray90820: Dell has some models that are available with Linux pre-installed (I think it's Ubuntu).
[21:29] <bray90820> jhutchins: I actually am looking for a new laptop because my Dell 2-in-1 I got last December broke last night
[21:30] <bray90820> So not a fan of dell at the moment
[21:30] <jhutchins> bray90820: They do have pretty good after-warranty repair support (third party).
[21:30] <Unit193> MicroCenter+++++++ :P
[21:30] <bray90820> What do you think of system76?
[21:30] <jhutchins> It's nie to be able to return stuff.
[21:33] <leftyfb> bray90820: feel free to discuss further in #ubuntu-offtopic. Mind you, you're just going to be told to get a Dell, HP, Lenovo, Samsung, Acer, Asus, System76, framework, thinkpenguin, etc. Asking for opinions online are only going to get you every opinion there is and won't help you.
[21:34] <bray90820> Yeah I get you but I pretty much am just looking for something that has complete driver support and won't break down afyer 6 months
[21:35] <leftyfb> nobody here can guarantee your 2nd point on any product every made
[21:38] <bray90820> Yeah no one can garintee it but was just looking for whatever there own milage and observations were
[21:38] <leftyfb> bray90820: hardware opinions can be had in #ubuntu-offtopic
[21:39] <seth22> hi all, i need help on my fresh install ubuntu 22.04, i have flickering & many dot pixels. I tried many drivers, switched on intel IGP, but still the same, i'm remember i got the same on mint
[21:39] <bray90820> Thanks will try there
[21:40] <bray90820> I am looking for a laptop to run the latest Ubuntu LTS on in the $650-$700 range preferably 14 inch any recommendations?
[21:41] <leftyfb> bray90820: /join #ubuntu-offtopic
[21:41] <arg_> seth maybe your intel/screen is broken, try failsafe boot mode maybe, some grub boot parameters...vesa or something
[21:41] <seth22> no problem on windows
[21:41] <bray90820> Oops sorry I did not mean to send that in here my bad
[21:47] <arg_> seth if it's a i915, try that grub boot option "i915.enable_psr=0" and otherwise have a look here maybe: https://wiki.archlinux.org/title/Intel_graphics#Troubleshooting  for deeper config tries, since you tried 2 distribs.
[21:51] <fuzzymanboob98[m> if I want to have a multiple-disk setup with encryption am I better off using ZFS or LVM? once 22.04.1 drops I'll be reinstalling fresh and want to weigh my options
[21:54] <toddc> fuzzymanboob98[m: I like ZFS raid snapshots and encription and have been using it for several years
[21:56] <fuzzymanboob98[m> I do too, which is why I'm considering it but it seems tricky to set up with multiple disks
[22:01] <ravage> my best guess would be to install it on a single disk and convert into a mirror/raid later
[22:03] <fuzzymanboob98[m> I have that kind of setup for my home server, but for my desktop I was aiming for a hierarchy of drives: root on ssd, home on another, ~/Videos on a slow HDD
[22:04] <leftyfb> fuzzymanboob98[m: it's not really a ZFS vs LVM. They're not really the same thing. You can use the ZFS filesystem on top of LVM volumes if you like
[22:05] <ravage> then just do the default ZFS setup and move home later
[22:05] <ravage> that should not be a big deal
[22:06] <fuzzymanboob98[m> I can make them encrypted with the same key and all unlocked at once during the boot password prompt?
[22:06] <strk> My disk has 4 partitions: 2 "big" ones, of equal size (220G each), a small one I'm using for / (18G) and a smaller one used for /boot (0.5G)
[22:06] <raczka>  
[22:06] <strk> one of the 2 "big" partitions is used for /home the other is a scratch one
[22:06] <leftyfb> fuzzymanboob98[m: the recommended way is to do an encrypted LVM and partition and format it however you like
[22:07] <ravage> fuzzymanboob98[m, the key is kept on an extra partition. actually LVM encrypted. thats unlocked on boot and the key is used fpr the rpool
[22:07] <leftyfb> uh
[22:07] <strk> the scratch one I formatted as btrfs
[22:07] <ravage> with some fiddling you should be able to use the same keyfile
[22:07] <leftyfb> what's the point of encrypting anything if you're just going to put the key unencrypted on the same system?
[22:07] <fuzzymanboob98[m> leftyfb: recommended by who?
[22:07] <strk> now, when planning a dist-upgrade, which ends out of space (due to / [18G) being full) what could a good strategy be ?
[22:08] <strk> should I copy /home (ext4) to the btrfs fs and install a fresh system on the partition currently used for /home ?
[22:09] <strk> or should I keep things as they are and (beside backups) "hope" only the / partition will be touched by the installer ?
[22:09] <leftyfb> strk: just stick with the standard with 1 partition
[22:09] <fuzzymanboob98[m> leftyfb: I probably mispoke. On a GUI install of ZFS encrypted to a single disk, you're prompted for a password on boot. I want to make it so that unlocks _every_ disk on the system.
[22:09] <strk> which basically gets down to : are 18G enough for the latest ubuntu system ?
[22:09] <strk> the biggest parts of the root fs are /snaps, which I grew an hate for
[22:09] <leftyfb> fuzzymanboob98[m: so add all your disks to the LVM
[22:10] <strk> leftyfb: the standard with 1 partition has the problem of "start fresh!" meaning you need another disk for backing up your /home
[22:10] <strk> so I"ve to say I'm happy to have a separate partition for /home at the moment
[22:10] <leftyfb> strk: snapshots are not a backup
[22:10] <strk> I used to have 1 partition and I was happy until it came the time to try another system
[22:10] <leftyfb> strk: also, btrfs can be had on a single partition setup
[22:11] <strk> what does the snapshot/backup has to do with this ?
[22:11] <strk> oh btrfs is completely new to me
[22:11] <strk> maybe I should just re-format in ext4 :)
[22:11] <strk> I've no idea what you can or cannot do with btrfs
[22:11] <leftyfb> strk: in your setup, you have no backup
[22:11] <fuzzymanboob98[m> leftyfb: Does this mean when i select ZFS during system install that LVM is used in the background?
[22:11] <strk> leftyfb: correct, I have no backups
[22:11] <leftyfb> fuzzymanboob98[m: no
[22:12] <leftyfb> fuzzymanboob98[m: choose a manual setup, create an encrypted LVM that spans all your drives. Then partition and format it however you like
[22:12] <krabador> strk: snapshots , a really happy world
[22:12] <strk> leftyfb: are you suggesting a single-partition setup using snapshots ?
[22:12] <strk> so btrfs single-partition ?
[22:12] <leftyfb> sure
[22:12] <leftyfb> but it's still not a backup solution
[22:12] <fuzzymanboob98[m> leftyfb: When doing this can I choose to mount drives at specific points?
[22:12] <leftyfb> snapshots are basically and undo, not a backup
[22:13] <leftyfb> fuzzymanboob98[m: no, why do you need to?
[22:13] <strk> could I then define "logical" places (like "/home") and install a fresh system w/out wiping out that logical place ?
[22:13] <fuzzymanboob98[m> Slow storage for Videos, fast for games etc
[22:13] <fuzzymanboob98[m> leftyfb: Slow storage for Videos, fast for games. I have a mix of types and sizes
[22:13] <strk> I could try such setup on the "scratch" partition
[22:13] <strk> that is: install a fresh system on those 220GB
[22:13] <strk> and have a new /home there
[22:14] <strk> keeping the left-over space untouched for a start, and eventually unleash it for other experiments
[22:14] <leftyfb> fuzzymanboob98[m: ok, then in that case, you're going to need to do a lot of manual work to get all the volumes/partitions to decrypt with 1 password. Personally, I don't think that amount of work is worth the minimal amount of performace you'll get
[22:14] <strk> would btrfs mean I'll be stuck with ubuntu then ?
[22:16] <leftyfb> fuzzymanboob98[m: maybe only worry about encrypting your "fast" storage with sensitive data and not worry about media on the slow storage