Re: openSUSE Factory Digest, Vol 193, Issue 1
Hi Fritz,
Are you sharing the /home directory between all those linux distros?
No.
I have a dozen or so VMs right now and 7 different distros installed.
None are better than TW in my opinion, but, I like to see what the other distros are doing.
IMHO, this simple solution would resolve your issue.
Regards,
Joe
Joe: Thanks for the suggestion, so far I have not liked the "window in a window" aspect of a VM, but instead prefer the "bare metal" install, each distro has its own / partition, and some of them share the partition for the /home.
I think you can see the mail list via news. And least you could.
<https://lars.ingebrigtsen.no/2020/01/15/news-gmane-org-is-now-news-gmane-io/>
Otherwise, change your subscription to normal while you are participating actively.
OK, thanks, I think this little bubble of activity is winding down???
This means that grub doesn't have to point at the actual kernel name, like "vmlinuz-5.14.21-150400.24.46-default", but point to "vmlinuz" which is _always_ the current kernel.
Carlos: Got it, that does sound better than the weekly #update-bootloader I have been running as of late.
Obviously, you'd have to adjust for your case. They are simply two entries from my system. I have no idea how it would be for Mac partitions, but you can find that information in the automatic configuration file, /boot/grub2/grub.cfg
Subject: Re: TW slow to process "post trans script" grub2-i386???? Carlos E. R. composed on 2023-03-18 13:21 (UTC+0100):
Telcontar:~ # ls -l /boot/vmlinuz lrwxrwxrwx 1 root root 36 Feb 19 22:27 /boot/vmlinuz -> vmlinuz-5.14.21-150400.24.46-default Telcontar:~ # ls -l /boot/initrd lrwxrwxrwx 1 root root 35 Feb 19 22:27 /boot/initrd -> initrd-5.14.21-150400.24.46-default Telcontar:~ #
This means that grub doesn't have to point at the actual kernel name, like "vmlinuz-5.14.21-150400.24.46-default", but point to "vmlinuz" which is _always_ the current kernel.
Usually it points to the most recently installed kernel from a standard location (for Leap: distribution/leap/15.4/repo/oss/, or update/leap/15.4/sle/), but /not/ always. --
Felix Miata
Felix: Beginning to see the distinction, and the benefit of trying that approach. In deference to your suggestion that I "modify my dysfunctional behaviors" . . . I nuked an errant system that seemed to be using a lot of time to upgrade itself AND had also adjusted its EFI to another disk . . . so now we are back to 7 . . . one for each day. Might be another one to snip off. <baby steps>
Hi Fritz,
Hi Fritz,
Are you sharing the /home directory between all those linux distros? No.
I have a dozen or so VMs right now and 7 different distros installed.
None are better than TW in my opinion, but, I like to see what the other distros are doing.
IMHO, this simple solution would resolve your issue.
Regards,
Joe Joe:
Thanks for the suggestion, so far I have not liked the "window in a window" aspect of a VM, but instead prefer the "bare metal" install, each distro has its own / partition, and some of them share the partition for the /home.
Your first answer says you do not share the /home partition but this answer says Yes. Sharing is a recipe for headaches. Instead I put all my personal files on a separate drive ( or even a partition ) and then you can symlink those into the home directories of different linux installs. Now you avoid the headaches with sharing home between different distros which are running different sw versions but still have access to your personal files. This is not perfect and I can think of one situation you could have issues but in general it is much safer route IMHO. You do NOT have to run the VMs in a Window, you can run them full screen with VMWare and there is NO indication you are not running on bare metal unless you drop down the VM menu in the middle of the screen. KVM/QEMU can also go full screen too. Just my $0.02 but I do most of the same stuff you are doing but without the headaches :-)
On 3/18/23 21:16, Joe Salmeri wrote:
You do NOT have to run the VMs in a Window, you can run them full screen with VMWare and there is NO indication you are not running on bare metal unless you drop down the VM menu in the middle of the screen. KVM/QEMU can also go full screen too.
VirtualBox can as well. Larry
participants (3)
-
Fritz Hudnut -
Joe Salmeri -
Larry Finger