- Talk - lists.gtalug.org

LLVM JIT Talks
by Nicholas Krause 26 May '22

26 May '22

Greetings I've misdeleted the other thread, so sorry for starting a new one. For David, I would be happy to try if you let me know what the interest/use case is. On a side note, for Alan I've asked him to contact you directly. Hopefully he contacts you soon. If he does not in the next few weeks, I will ping him for you. Nick

2 1

Possible Future Talks
by Nicholas Krause 24 May '22

24 May '22

Greetings, I've managed to get in contact with the maintainer for the LLVM RiscV backend. Not sure if it's of interest to the group. But, he can talk about compiler backends in general or related to RiscV. For those who aren't aware as discussed at the RiscV talk, this would be the compiler support for the ISA for RiscV. Or if there is another topic from the LLVM side I can try to find someone there. Take care, Nick

3 2

Ventoy: use single USB stick for multiple installation images
by D. Hugh Redelmeier 17 May '22

17 May '22

"Ventoy" is an open-source tool that allows you to put multiple .iso files on a USB stick. Has anyone tried it? <https://www.ventoy.net/en/index.html> <https://en.wikipedia.org/wiki/Ventoy> Why do I care? When I want to install Fedora, for example, I fetch a .iso file and dd it straight to a USB stick. The result is a bootable live Fedora system that can install Fedora to a disk drive. This same procedure works for Ubuntu and a lot of other distros. One downside is that I have a collection of USB sticks that each has a .iso file. Each USB stick is mostly empty because .iso files are smaller than current USB sticks. Ventoy might allow me to use a single USB stick for my whole collection.

3 2

Sharing EFI partition for multiple distro?
by William Park 16 May '22

16 May '22

Can you use the same EFI partition for multiple distros? Eg. Can you have /dev/sda1 -- /boot/efi /dev/sda2 -- Slackware / /dev/sda3 -- Ubuntu / /dev/sda4 -- Fedora / where /dev/sda1 shared? Or, does distro need its own EFI partitions, like /dev/sda1 -- Slackware /boot/efi /dev/sda2 -- Slackware / /dev/sda3 -- Ubuntu /boot/efi /dev/sda4 -- Ubuntu / /dev/sda5 -- Fedora /boot/efi /dev/sda6 -- Fedora / ?

4 3

Back to basics: upgrading from Windows to Linux
by Evan Leibovitch 12 May '22

12 May '22

Hi all. This topic is one I hope will be on many peoples' minds as they encounter frustration (and in some cases a dead end) moving their Windows 10 systems to Windows 11. This may soon become the source of a multi-stakeholder public campaign, but that's just in the planning stages. Now for the personal angle. Some ago I installed Windows on a desktop I use a lot. It replaced Linux because that was incapable of running the one game I like playing. I even gave a talk to GTALUG about that move, about Windows Subsystem for Linux and the things I thought were better about the Windows desktop. Turns out I was wrong. So very, very wrong. And now I can't wait to go back to my Linux desktop, especially since there's a recent LTS release of Kubuntu, my traditional distro of choice. Plus, according to ProtonDB, my game might just run well natively on Linux <https://www.protondb.com/app/255710>! But it's been a long time since I've done this so I have some remedial questions to ask from this group's wisdom ... to help me change from a Windows install to a dual boot, priority Kubuntu: 1. My motherboard takes a single M.2 SSD for my one and only drive. I have a larger M.2 card that I'd like to replace it with, cloning my existing setup to the new drive (in a temporary USB enclosure) then installing and shrinking the Windows partition in anticipation of the Linux dual-boot install. Can anyone recommend a good tool for doing the disk clone? Or am I better off to just fresh-install Windows on the new drive, and restore my data from the old one? 2. I want to have one partition for data that is visible regardless if I boot Linux or Windows. Previously the most reliable filesystem readable by bothwas FAT32. Should I still do that? Is Linux support for NTFS good enough now? Even better, can Windows be taught to read ext4? 3. I've never used snap or flatpack before. Others have told me to install as much native (ie, .deb packages) as possible, use flatpack when it's the only option and uninstall snap. Any comments or caveats here? And why did app installation sources become needlessly complex? Thanks for any advice. - Evan

12 23

RISC-V talk tonight
by Trevor Woerner 10 May '22

10 May '22

Was tonight's talk announced on this list? My friend Drew Fustini, who is a "RISC-V Ambassador" for RISC-V International, will be giving a talk on Linux and RISC-V at tonight's GTALUG meeting at 7:30 https://gtalug.org/meeting/2022-05/

2 1

RISC-V
by Ivan Avery Frey 10 May '22

10 May '22

"RISC-V chip designed with open source tools - eeNews Europe" https://www.eenewseurope.com/en/risc-v-chip-designed-with-open-source-tools/

5 5

FYI: Redhat + General Motors
by William Park 10 May '22

10 May '22

FYI, https://finance.yahoo.com/news/red-hat-general-motors-collaborate-130000468…

1 0

Installing Linux: Still a PITA, continued
by Evan Leibovitch 09 May '22

09 May '22

Or maybe I'm not keeping track of chapters. As some of you know, I've been on a quest to upgrade my daily desktop from Windows to a dual-boot Linux system (and eventually, I hope, to eliminate Windows). As some of you know, I've been replacing systems with dual-boot (first Unix, then Linux) on systems for almost 30 years, though I don't have that technical a bent. But I swear, things are getting harder rather than easier for the non-technical. First step was backing up the Windows and getting ready on my newer, double-the-size M.2 drive. Cloning the old drive was the best option, but not using Clonezilla which was absolutely useless to me. Couldn't find the Windows drive, despite multiple tries. Maybe it did, but its UI is beyond awful. Tried many hours before giving up. I had considerably greater success with the free version of Macrium Reflect, which knew exactly what I wanted to do and did it with ease. Swapping the hardware was easy enough, given that my system's motherboard has two M.2 sockets even though it's several years old. System boots Windows just fine, identical to what I had before except I now have 250GB unallocated. Online help about how to partition a Linux system is as confused as ever, some saying a single partition will do for everything, and others saying that even a UEFI system needs a separate ext4 partition for /boot even if there is an existing EFI one already there. And then the final step (i thought) -- installing. I decided, after hearing from everyone here, that MX Linux KDE would be the best combination of things I needed and things I didn't. Downloaded the bootable image and used Rufus, where I had to decide if the bootable USB stick would be GPT or MBR (not obvious to a newcomer). All loaded, reboot, and .... no graphics. The mouse pointer shows up for a half second and vanishes, with the screen at alt-F1 inviting me to do a CLI install whose partition choices threaten to wipe out my windows system and don't have an intuitive way to customize. Thankfully (I think), I was able to scp the X.org log file to another computer so I wouldn't lose it on the USB stick's live boot. I attach it below, and ask assistance from anyone who can read these files so I can understand why it's dying. My graphics card is a fairly recent AMD RX 6500 XT which works fine under Windows and is claimed to be supported by X. Or do I just give up on MX? A search on its forum appears to draw blanks, except for me to boot in failsafe mode which didn't change anything. Will this be better on another distro? One option is to boot a gparted live stick, partition as I want, install Linux VIA MX's CLI and pray it updates with current graphics drivers. But sheesh. One would think that given 20 years to improve the install experience, it can be more confusing than ever. Any help is appreciated. Evan Leibovitch, Toronto Canada @evanleibovitch / @el56

6 9

[GTALUG-Announce] Reminder: May Meeting, Tomorrow Night.
by Alan Heighway 09 May '22

09 May '22

Linux on RISC-V <https://gtalug.org/meeting/2022-05/> with Drew Fustini <https://gtalug.org/> 10 May, 2022 at 07:30 PM It is an exciting time for Linux on RISC-V, the open instruction set (ISA) that is quickly gaining critical mass. I will introduce the pieces needed to boot Linux on RISC-V including the Privileged Architecture, OpenSBI and U-Boot, and how that fits into the upcoming RISC-V Platform Specification. I will break down support for existing hardware and current upstreaming efforts. We're going to use Big Blue Button for this meeting: *Time:* May 10, 2022 07:30 PM Eastern Time *Join Big Blue Button:* https://blue.lpi.org/b/eva-zjc-gjy-kgl *A*lan *H*eighway <http://heighway.ca/> heighway.ca VA3WAH / VA3YKZ [image: Please consider the environment before printing] --- GTALUG Announce mailing list announce(a)gtalug.org https://gtalug.org/mailman/listinfo/announce

1 0