[11:30] <twojukeboksi> y0 and BIG thanks for the awesome studio OS. I've installed it for a couple of friends and my own dedicated machine, but my main machine is in need of some OS that will actually sleep (US does this well, KDE neon not at all). Do I have a correct recollection that US can be used for everyday laptop, so that one must just remember to shut down JACK to put machine to sleep and restart it after wakeup if one wants to do studio-y things?
[11:31] <twojukeboksi> 'scuse my dyslexia
[11:33] <twojukeboksi> I'm thinking I want to be able to dual boot (got 150GB set aside for /-partitions). The users of different OS accoding to my understanding need to have different home-dirs or the confs will get messed up, can I just symlink all the directories in the home-dir to the different user, or does that cause complications too?
[11:50] <jojo[m]> I finally should get around and update my 18.04 studio to 20.10.......only thing is I have a very old machine (not sure about the processor) and only 2GB of ram......is it a very bad idea to update to kde plasma based studio? i read that it shouldn't bother with gaining a lot more resources than xfce based did.
[11:52] <jojo[m]> <twojukeboksi "I'm thinking I want to be able t"> generally it sounds like an adventurous, if not to say "bad" idea but let me think about it more closely. which different OS's are you talking about?.
[12:04] <twojukeboksi> jojo[m]: In my opinion the 20.10 is very frugal regarding RAM. Firefox, Ardour6 and Carla up it is using only under 2GB of RAM, but then again Linuxen seem to grind down when they hit 75% of RAM occupied.
[12:06] <twojukeboksi> jojo[m]: I'm thinking I remove all the non-dotdirectories from the /home/ubuntustudiousername and symlink them from the old home-dir. I've never tried symlinking like this, but I'm inclined to think that the dual-boot will be just fine with the symlinks. Not sure though
[12:07] <twojukeboksi> then again this KDE neon seems like an human testing farm. In #kde-neon-users one rarely gets help and in #kde-neon they tell users to bugger off
[12:53] <jojo[m]> <twojukeboksi "jojo: I'm thinking I remove all "> still it feels like an adventourus idea if you know what you are doing and how to fix it if it doesn't work (back up before! snapshot), work away 🙂 again: which operating systems are you talking about? two exact same versions of ubuntu studio?
[12:53] <jojo[m]> > <@freenode_twojukeboksi:matrix.org> jojo: I'm thinking I remove all the non-dotdirectories from the /home/ubuntustudiousername and symlink them from the old home-dir. I've never tried symlinking like this, but I'm inclined to think that the dual-boot will be just fine with the symlinks. Not sure though
[12:53] <jojo[m]>  * still it feels like an adventourus idea but if you know what you are doing and how to fix it if it doesn't work (back up before! snapshot), work away 🙂 again: which operating systems are you talking about? two exact same versions of ubuntu studio?
[12:53] <jojo[m]>  * still it feels like an adventourus idea but if you know what you are doing and know how to fix it if it doesn't work (back up before! snapshot), work away 🙂 again: which operating systems are you talking about? two exact same versions of ubuntu studio?
[12:55] <jojo[m]> <twojukeboksi "jojo: In my opinion the 20.10 is"> i think I'll give it a try :-)
[12:57] <twojukeboksi> Yes, I am using Timeshift to make backups of the /-partition always before I do anything that could put the system in an unreliable state. I guess I need to backup the .dotdirectories by hand too, before I try the symlinking. There are programs that keep locks on open files e.g. LibreOffice, which could cause problems if I _really_ start to dualboot. Probably just migrate all my stuff to the US and never boot the KDE neon again
[12:59] <twojukeboksi> jojo[m]: yeah, this is the most frugal US I've ever seen. But it would seem the KDE neon is frugal also when it comes to RAM, so this leads me to think that they've optimized the DE a lot
[13:00] <twojukeboksi> If the deactivate-JACK, put to sleep, wake-up from sleep and reactivate JACK in case I need to do audio stuff.
[13:03] <twojukeboksi> .. so if that works without problems, then I think I'll start using US as my main OS
[13:49] <jojo[m]> <twojukeboksi "Yes, I am using Timeshift to mak"> migrating and leaving it behind sounds good! rsync might help with that! to test stuff user the -n (dry-run) option
[16:07] <OvenWerks> twojukeboksi: In my case I leave the .dir alone and symlink everything else
[16:08] <OvenWerks> So each partition with it's own distro has a home directory with it's .dirs and sysmlinks to the directories I keep stuff in.
[16:11] <OvenWerks> not the .dirs are that much of a problem. In general each DE uses it's own set of files in .config, etc. anyway. I mainly do this because often each partition has a different version of the same DE where there may be slight differences in the config files that may go forward ok but not backwards
[16:13] <OvenWerks> jojo[m]: you need to be aware if your very old machine is 32bit cpu, 20.02 may not work for you. put the iso on a usb stick and make sure you can boot.
[16:16] <jojo[m]> <OvenWerks "jojo: you need to be aware if yo"> ahh crap i didnt think of cpu, yes it is 32bit definitely. that not supported anymore? at least for upgrading? i wont fresh install
[16:17] <OvenWerks> I think 20.04 is 64bit only. Maybe look at the ubuntu info, Studio will be the same
[16:17] <OvenWerks> (same repos after all)
[16:24] <OvenWerks> jojo[m]: I have an older laptop that has only 2gram and 32 bit cpu. I find it works just fine for recording with Ardour
[16:26] <OvenWerks> I don't do mixdown with it, so I don't know how well that works but recording up to at least 12 or so tracks works fine (I have heard 24 or 32 tracks is fine as well)
[16:27] <OvenWerks> I just added a larger drive to it so I can have two partitions, one with the old Studio 18.04 and another will be debian going forward
[16:29] <OvenWerks> interestingly, armhf (also 32 bit) is supported.