On 28/04/2024 17:40, Grant Edwards wrote:
On 2024-04-28, Grant Edwards wrote:
With DOS disk lables, Grub uses empty space between the boot sector
and the first partition as a location to store it's core image file.
That empty space does not exist when using GPT disk label. When using
a GPT
Dale wrote:
> Michael wrote:
>> On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
>>> Grant Edwards wrote:
On 2024-04-28, Grant Edwards wrote:
> With DOS disk lables, Grub uses empty space between the boot sector
> and the first partition as a location to store it's core image file.
Michael wrote:
> On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
>> Grant Edwards wrote:
>>> On 2024-04-28, Grant Edwards wrote:
With DOS disk lables, Grub uses empty space between the boot sector
and the first partition as a location to store it's core image file.
That empty
On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
> Grant Edwards wrote:
> > On 2024-04-28, Grant Edwards wrote:
> >> With DOS disk lables, Grub uses empty space between the boot sector
> >> and the first partition as a location to store it's core image file.
> >> That empty space does not exist
Grant Edwards wrote:
> On 2024-04-28, Grant Edwards wrote:
>
>> With DOS disk lables, Grub uses empty space between the boot sector
>> and the first partition as a location to store it's core image file.
>> That empty space does not exist when using GPT disk label. When using
>> a GPT disk label,
On 2024-04-28, Grant Edwards wrote:
> With DOS disk lables, Grub uses empty space between the boot sector
> and the first partition as a location to store it's core image file.
> That empty space does not exist when using GPT disk label. When using
> a GPT disk label, Grub requires that you need
On 2024-04-27, Michael wrote:
> On Saturday, 27 April 2024 17:53:25 BST Dale wrote:
>> Howdy,
>>
>> I'm installing Gentoo on another old box. To be consistent I like
>> to use cgdisk, GPT I think it is called, to partition all my
>> drives, regardless of size.
>
> GPT is the partition table
Grant Edwards wrote:
> On 2024-04-17, Dale wrote:
>
>> I still use Nvidia and use nvidia drivers. I to run into problems
>> on occasion with drivers and kernels. When you switched from
>> Nvidia, what did you switch too? Do you still use drivers you
>> install or kernel drivers?
> All in-tree
On 2024-04-17, Frank Steinmetzger wrote:
>> If you don't play games, then definitely get integrated graphics.
>> Even if the CPU costs a tiny bit more, it will give you a free empty
>> 16x PCIe slot at whatever speed the CPU supports (v5 in this case -
>> which is as good as you can get right
On 2024-04-17, Dale wrote:
> I still use Nvidia and use nvidia drivers. I to run into problems
> on occasion with drivers and kernels. When you switched from
> Nvidia, what did you switch too? Do you still use drivers you
> install or kernel drivers?
All in-tree kernel drivers for integrated
Grant Edwards wrote:
>
> 2) Lack of support for old hardware when running a newer kernels.
>
> I used to run into this when running nvidia-drivers.
> Gentoo-sources would mark a new kernel stable, but my video board
> would not be supported by nvidia-drivers versions that were
>
On 2024-04-17, Dr Rainer Woitok wrote:
> Grant,
>
> On Wednesday, 2024-04-17 14:11:21 -, you wrote:
>
>> ...
>> If what you want is access to all upstream longeterm kernel versions,
>> then you should be using sys-kernel/vanilla-sources.
>
> I was not aware of this package. Excatly what
On 17/04/2024 10:10, Michael wrote:
I am not sure the assumption "... aging hardware possibly can less and less
cope with newer and newer kernels" is correct. As already mentioned newer
kernels have both security and bug fixes. As long as you stick with stable
gentoo-sources you'll have these
Grant,
On Wednesday, 2024-04-17 14:11:21 -, you wrote:
> ...
> If what you want is access to all upstream longeterm kernel versions,
> then you should be using sys-kernel/vanilla-sources.
I was not aware of this package. Excatly what could come in handy, if
everything else fails. Thank
Michael,
On Wednesday, 2024-04-17 10:10:56 +0100, you wrote:
> On Tuesday, 16 April 2024 20:26:25 BST Grant Edwards wrote:
> > On 2024-04-16, Dr Rainer Woitok wrote:
> > ...
> > > But, to get back to the beginning of this discussion: if there is a
> > > risk that my aging hardware possibly can
On 2024-04-17, Dr Rainer Woitok wrote:
> Grant,
>
> On Tuesday, 2024-04-16 19:26:25 -, you wrote:
>
>> ...
>> That means that all gentoo-sources stable kernels are "longterm"
>> kernel versions on kernel.org. It does not mean that all "longterm"
>> kernel versions from kernel.org are
On 2024-04-17, Michael wrote:
>> > But, to get back to the beginning of this discussion: if there is a
>> > risk that my aging hardware possibly can less and less cope with
>> > newer and newer kernels, should I put something like
>> >
>> >>=sys-kernel/gentoo-sources-6.7.0
>> >
>> > into
On Wednesday, 17 April 2024 11:37:04 BST Dr Rainer Woitok wrote:
> Grant,
>
> On Tuesday, 2024-04-16 19:26:25 -, you wrote:
> > ...
> > That means that all gentoo-sources stable kernels are "longterm"
> > kernel versions on kernel.org. It does not mean that all "longterm"
> > kernel versions
Grant,
On Tuesday, 2024-04-16 19:26:25 -, you wrote:
> ...
> That means that all gentoo-sources stable kernels are "longterm"
> kernel versions on kernel.org. It does not mean that all "longterm"
> kernel versions from kernel.org are available as "stable" in
> gentoo-sources.
>
> It is a
On Tuesday, 16 April 2024 20:26:25 BST Grant Edwards wrote:
> On 2024-04-16, Dr Rainer Woitok wrote:
> > Arve,
> >
> > On Tuesday, 2024-04-16 15:53:48 +0200, you wrote:
> >> ...
> >> Only LTS kernels get stabilised, so this information is readily
> >> available.
> >
> > I'm sure I don't
On 2024-04-16, Dr Rainer Woitok wrote:
> Arve,
>
> On Tuesday, 2024-04-16 15:53:48 +0200, you wrote:
>
>> ...
>> Only LTS kernels get stabilised, so this information is readily available.
>
> I'm sure I don't understand this: According to "https://www.kernel.org/;
> kernel 6.6.27 is "longterm",
Arve,
On Tuesday, 2024-04-16 15:53:48 +0200, you wrote:
> ...
> Only LTS kernels get stabilised, so this information is readily available.
I'm sure I don't understand this: According to "https://www.kernel.org/;
kernel 6.6.27 is "longterm", but according to "eix" the most recent
6.6.*
On 2024-04-16, Dale wrote:
> I've never understood what is supported long term either. I use
> gentoo-sources. I've never figured out just how to pick a kernel that
> is supposed to be stable for the larger version. In other words, only
> security and bug fixes, no new hardware. Right now,
Grant Edwards wrote:
> On 2024-04-16, Arve Barsnes wrote:
>> On Tue, 16 Apr 2024 at 15:29, Dr Rainer Woitok
>> wrote:
My understanding is the gentoo-sources kernels are aligned with the LTS
upstream releases.
>>> Right, they use the same version numbers. But you can't see from just
Arve Barsnes wrote:
> On Tue, 16 Apr 2024 at 15:29, Dr Rainer Woitok
> wrote:
>>> My understanding is the gentoo-sources kernels are aligned with the LTS
>>> upstream releases.
>> Right, they use the same version numbers. But you can't see from just
>> looking at the available
On 2024-04-16, Arve Barsnes wrote:
> On Tue, 16 Apr 2024 at 15:29, Dr Rainer Woitok
> wrote:
>> > My understanding is the gentoo-sources kernels are aligned with the LTS
>> > upstream releases.
>>
>> Right, they use the same version numbers. But you can't see from just
>> looking at the
On 4/16/24 7:15 AM, Michael wrote:
On Tuesday, 16 April 2024 11:55:20 BST Dale wrote:
If you update often, it shouldn't take long answer the questions. If
you do like me and don't update often, it may take longer but no more
time than it would if you updated often and added all the time
On Tue, 16 Apr 2024 at 15:29, Dr Rainer Woitok wrote:
> > My understanding is the gentoo-sources kernels are aligned with the LTS
> > upstream releases.
>
> Right, they use the same version numbers. But you can't see from just
> looking at the available "gentoo-sources" which one is LTS and
Michael,
On Tuesday, 2024-04-16 11:15:07 +0100, you wrote:
> ...
> > But this brings up two related questions:
> >
> > 1. Why does Gentoo not somehow mark LTS kernels either in the version
> >number or in the slot name? This would make it easier to prevent the
> >installation of too
Michael wrote:
> On Tuesday, 16 April 2024 11:55:20 BST Dale wrote:
>
>> If you update often, it shouldn't take long answer the questions. If
>> you do like me and don't update often, it may take longer but no more
>> time than it would if you updated often and added all the time
>> together. As
On Tuesday, 16 April 2024 11:55:20 BST Dale wrote:
> If you update often, it shouldn't take long answer the questions. If
> you do like me and don't update often, it may take longer but no more
> time than it would if you updated often and added all the time
> together. As far as I know, if one
Dr Rainer Woitok wrote:
> Michael,
>
> On Monday, 2024-04-15 12:48:34 +0100, you wrote:
>
>> ...
>> Why have you set your /boot to be mounted at boot?
> Well, I think, I then just followed the Gentoo Handbook. But I see your
> point of saving time which could be better used to successfully
On Tuesday, 16 April 2024 10:04:43 BST Dr Rainer Woitok wrote:
> Michael,
>
> On Monday, 2024-04-15 12:48:34 +0100, you wrote:
> > ...
> > Why have you set your /boot to be mounted at boot?
>
> Well, I think, I then just followed the Gentoo Handbook. But I see your
> point of saving time which
Michael,
On Monday, 2024-04-15 12:48:34 +0100, you wrote:
> ...
> Why have you set your /boot to be mounted at boot?
Well, I think, I then just followed the Gentoo Handbook. But I see your
point of saving time which could be better used to successfully unmount
the "/home/" partition. I'll
Am Sun, Mar 31, 2024 at 08:33:20AM -0400 schrieb Rich Freeman:
> (moving this to gentoo-user as this is really getting off-topic for -dev)
> […]
> We're going on almost 20 years since the Snowden revelations, and back
> then the NSA was basically doing intrusion on an industrial scale.
Weeaalll,
On Sunday, 14 April 2024 19:41:41 BST Dr Rainer Woitok wrote:
> Greetings,
>
> On Friday, 2024-01-05 18:46:09 +0100, I myself wrote:
> > ...
> > since a few month or so off and on my laptop fails to resume from hiber-
> > nation due to the "dirty bit" being set on the ext4 "/home" partition.
>
Greetings,
On Friday, 2024-01-05 18:46:09 +0100, I myself wrote:
> ...
> since a few month or so off and on my laptop fails to resume from hiber-
> nation due to the "dirty bit" being set on the ext4 "/home" partition.
I was reading this flickering by on the screen, and it wasn't quite cor-
On Saturday, 30 March 2024 19:34:42 CEST Walter Dnes wrote:
> Thanks for the help. I've migrated my 3 operating Gentoo machines;
> main desktop, backup desktop, and an old used Lenovo Thinkpad X201. The
> poor thing was thrashing away for over 18 hours with 657 packages on the
> emerge
On 3/31/24 14:32, Alexandru N. Barloiu wrote:
I think in the past, the service file had a -v. Somewhere near the
present, they reverted to a non -v service file. So if you keep
upgrading distcc, prolly the service file still has a -v from past
installations. If you uninstall it, and install it
No argument from me. That JiaTan dude had other projects forked he was
looking at. And none of them are good news. zstd. lz4. libarchive.
squashfs-tools. But still, I think its good news if people already
figured how to turn it off in a few days.
On 4/1/2024 1:36 AM, Michael Orlitzky wrote:
On Mon, 2024-04-01 at 01:32 +0300, Alexandru N. Barloiu wrote:
> https://piaille.fr/@zeno/112185928685603910
>
> There's an ENV var you can set that is a kill switch for the whole thing :)
>
For the part that we found :)
The author of the backdoor had commit access to the upstream repository
https://piaille.fr/@zeno/112185928685603910
There's an ENV var you can set that is a kill switch for the whole thing :)
On 4/1/2024 1:29 AM, Michael Orlitzky wrote:
On Sun, 2024-03-31 at 18:19 -0400, Michael Orlitzky wrote:
The old version will show up as liblzma.so.5.6.1. Restart anything
On Sun, 2024-03-31 at 18:19 -0400, Michael Orlitzky wrote:
>
> The old version will show up as liblzma.so.5.6.1. Restart anything that
> uses it.
Or liblzma.so.5.6.0
On Sun, 2024-03-31 at 12:04 -0400, Rich Freeman wrote:
>
> It is not necessary to rebuild anything, unless you're doing something
> so unusual that you'd already know the answer to the question.
>
You should probably reboot afterwards though.
For a more fine-grained approach, you can check for
On Sun, Mar 31, 2024 at 5:36 PM Wol wrote:
>
> On 31/03/2024 20:38, Håkon Alstadheim wrote:
> > For commercial entities, the government could just contact the company
> > and apply pressure, no need to sneak the backdoor in. Cf. RSA .
>
> Serving a "secret compliance" notice on a third party is
On 31/03/2024 20:38, Håkon Alstadheim wrote:
For commercial entities, the government could just contact the company
and apply pressure, no need to sneak the backdoor in. Cf. RSA .
Apply pressure to who? At the end of the day, the only people the
government can trust are their own agents.
I think in the past, the service file had a -v. Somewhere near the
present, they reverted to a non -v service file. So if you keep
upgrading distcc, prolly the service file still has a -v from past
installations. If you uninstall it, and install it again, then prolly
you got the new service
/etc/systemd/system/distccd.service.d/00gentoo.conf or the service file.
has to be. there cant be anything else. that's how distcc behaves when
started with -v. do a ps axw. figure out where the -v is coming from.
maybe a systemctl daemon-reload && systemctl restart distccd. cant be
anything
On 3/31/24 13:59, Alexandru N. Barloiu wrote:
think the distcc.service file has an extra -v (--verbose). if you remove
that, it will behave as expected.
I checked all the units on one of the machines still showing the problem
and an extra '-v' is not present in any of the files.
That's a
think the distcc.service file has an extra -v (--verbose). if you remove
that, it will behave as expected.
On 3/31/2024 11:57 PM, Daniel Frey wrote:
On 3/29/24 22:38, Daniel Frey wrote:
Hi all,
I've moved a couple of machines from openrc to systemd.
I have discovered this odd problem. On
On 3/29/24 22:38, Daniel Frey wrote:
Hi all,
I've moved a couple of machines from openrc to systemd.
I have discovered this odd problem. On openrc, distcc was quiet during
building packages. It would obey environment variable set in /etc/env.d:
DISTCC_DIR=/var/distcc
Den 31.03.2024 14:33, skrev Rich Freeman:
(moving this to gentoo-user as this is really getting off-topic for -dev)
It might also happen with commercial software, but the challenge there
is HR as you can't just pay 1 person to masquerade as 10 when they all
need to deal with payroll taxes.
On Sun, Mar 31, 2024 at 10:59 AM Michael wrote:
>
> On Sunday, 31 March 2024 13:33:20 BST Rich Freeman wrote:
> > (moving this to gentoo-user as this is really getting off-topic for -dev)
>
> Thanks for bringing this to our attention Rich.
>
> Is downgrading to app-arch/xz-utils-5.4.2 all that is
On 3/31/24 07:59, Michael wrote:
On Sunday, 31 March 2024 13:33:20 BST Rich Freeman wrote:
(moving this to gentoo-user as this is really getting off-topic for -dev)
Thanks for bringing this to our attention Rich.
Is downgrading to app-arch/xz-utils-5.4.2 all that is needed for now, or are
we
On Sunday, 31 March 2024 13:33:20 BST Rich Freeman wrote:
> (moving this to gentoo-user as this is really getting off-topic for -dev)
Thanks for bringing this to our attention Rich.
Is downgrading to app-arch/xz-utils-5.4.2 all that is needed for now, or are
we meant to rebuilding any other/all
(moving this to gentoo-user as this is really getting off-topic for -dev)
On Sun, Mar 31, 2024 at 7:32 AM stefan1
wrote:
>
> Had I seen someone say that a bad actor would spend years gaining the
> trust of FOSS
> project maintainers in order to gain commit access and introduce such
>
Thanks for the help. I've migrated my 3 operating Gentoo machines;
main desktop, backup desktop, and an old used Lenovo Thinkpad X201. The
poor thing was thrashing away for over 18 hours with 657 packages on the
emerge --emptytree!!! And that's after using a homebrew bash script to
select the
On Thursday, 28 March 2024 14:51:42 CET Grant Edwards wrote:
> On 2024-03-27, Mark Knecht wrote:
> > On Wed, Mar 27, 2024 at 11:59 AM J. Roeleveld wrote:
> >> I am looking for a way to synchronise a filesystem between 2
> >> servers. Changes can occur on both sides which means I need to
> >>
On 2024-03-27, Mark Knecht wrote:
> On Wed, Mar 27, 2024 at 11:59 AM J. Roeleveld wrote:
>> I am looking for a way to synchronise a filesystem between 2
>> servers. Changes can occur on both sides which means I need to
>> have it synchronise in both directions.
>
> How synchronized? For
On 2024-03-26, Walter Dnes wrote:
> On Tue, Mar 26, 2024 at 04:21:23PM +, Michael wrote
>> On Tuesday, 26 March 2024 15:21:32 GMT Walter Dnes wrote:
>> > I assume my system is already "merged-usr". Current profile...
>> >
>> > [12] default/linux/amd64/17.1/no-multilib (exp) *
>> >
On 2024-03-26, Walter Dnes wrote:
> I'm AMD64 stable OpenRC. I got tired of dicking around resizing
> partitions years ago, so I have all data and binaries in one honking
> big partition. Also separate partitions for UEFI and swap. I assume
> my system is already "merged-usr". Current
On 2024-03-25, Michael wrote:
> On Monday, 25 March 2024 21:48:24 GMT Peter Humphrey wrote:
>> On Monday, 25 March 2024 16:52:19 GMT Michael wrote:
>>
>>> The default OpenRC installation now assumes a merged-usr fs structure -
>>> therefore make sure you select the appropriate profile in a new
On 2024-03-23, Mickaël Bucas wrote:
> I think it's not a terminal emulator feature, but rather a shell
> feature.
>
> Some terminal programs are designed to interact with the mouse, but
> bash command line, based on readline, doesn't react to mouse clicks.
Agreed.
> I've tried Midnight
On 2024-03-11, Grant Edwards wrote:
> I upgraded gentoo-sources from 5.15.147 to 5.15.151 this morning and
> amdgpu support is now borked on my system with an AMD Ryzen 5 3400G
> with Radeon Vega Graphics.
>
> Everything worked fine with 5.15.147, but when 5.15.151 (built with
> same .config via
On 10/03/2024 22:44, Carsten Hauck wrote:
The CPU of the machine in question is in deed an old AMD. It's good to
know the reason for that build-failures, thanks a lot.
I certainly will stick to "-clang" in my package.use.
Interesting. I'm not at all sure how old my CPU is, but at four cores
Good tips, thank you.
On 3/10/24 22:53, Walter Dnes wrote:
On Sun, Mar 10, 2024 at 06:43:56PM -, Grant Edwards wrote
Just back up your user data and re-install.
Also back up /etc/ for your app configs and stuff like hosts and
resolve.conf and make.ccnf and package.use and package.mask
On 10/03/24 at 01:50, mp666 wrote:
On Sat, 9 Mar 2024 08:04:06 +, Wols Lists wrote:
For anyone else who hits this sort of problem, I did an
USE=-clang emerge --update @world
(firefox and thunderbird were the only programs I thought this would
touch), and it worked.
There were a couple
On Sun, Mar 10, 2024 at 06:43:56PM -, Grant Edwards wrote
> Just back up your user data and re-install.
Also back up /etc/ for your app configs and stuff like hosts and
resolve.conf and make.ccnf and package.use and package.mask etc. And
remember /var/lib/. /var/lib/portage/ has your
On 2024-03-09, Walter Dnes wrote:
> On Sat, Mar 09, 2024 at 07:55:13PM +0100, n952162 wrote
>> I just synced my system after a long delay,
>
> That's your problem right there.
Yep, to quote Olivia Rodrigo...
Bad idea, right?
>> Is there a way to do it globally?
>
> First of all python
On 2024-03-10, Michael wrote:
> Perhaps I'm picking up on semantics, but shouldn't this sentence:
>
> "... The gap between the DOS disklabel and the first partition"
>
> read:
>
> "The gap between the MBR and the first partition"?
Yes, thanks -- MBR is more accurate, I've changed that sentence.
On Sat, 9 Mar 2024 08:04:06 +, Wols Lists wrote:
> For anyone else who hits this sort of problem, I did an
>
> USE=-clang emerge --update @world
>
> (firefox and thunderbird were the only programs I thought this would
> touch), and it worked.
>
> There were a couple of other programs that
On Friday, 8 March 2024 23:24:02 GMT Grant Edwards wrote:
> On 2024-02-22, Grant Edwards wrote:
> > For many years, I've used a hard drive on which I have 8-10 Linux
> > distros installed -- each in a separate (single) partition.
> >
> > [...]
> >
> > Is there an easier way to do this?
>
>
On 2024-02-22, Grant Edwards wrote:
> For many years, I've used a hard drive on which I have 8-10 Linux
> distros installed -- each in a separate (single) partition.
>
> [...]
>
> Is there an easier way to do this?
After some additional studying of UEFI and boot managers like rEFInd,
I decided
On 2024-03-06, Walter Dnes wrote:
> I've got a UEFI system. According to the news item...
>
>> Re-runing grub-install both with and without the --removable option
>> should ensure a working GRUB installation.
>
> I tried that...
>
> [i3][root][~] grub-install
I believe you have to run
On 2024-03-04, Alexander Puchmayr wrote:
> On Sonntag, 3. März 2024, 18:45:16 CET Alexander Puchmayr wrote:
>> Am Sonntag, 3. März 2024, 14:32:41 CET schrieb Andreas K. Huettel:
>> > > I set CFLAGS="-O2 -pipe march=x86-64-v2" on the buildhost and
>> > > performed a emerge -ev @world, re-creating
Il 02/03/24 18:17, Holger Hoffstätte ha scritto:
> On 2024-03-02 18:12, ralfconn wrote:
>> I have a build error with latest gentoo-sources (~amd64): # eix -I
>> gentoo-sources Installed versions: 6.7.6(6.7.6)^bs(10:37:31
>> 02/24/24)(-build -experimental -symlink) 6.7.7(6.7.7)^bs(18:43:20
>>
On 2024-03-02 18:12, ralfconn wrote:
I have a build error with latest gentoo-sources (~amd64): # eix -I
gentoo-sources Installed versions: 6.7.6(6.7.6)^bs(10:37:31
02/24/24)(-build -experimental -symlink) 6.7.7(6.7.7)^bs(18:43:20
03/01/24)(-build -experimental -symlink) # eix -I gcc Installed
On Tuesday, 27 February 2024 00:12:07 GMT Mark Knecht wrote:
> I have no experience beyond three operating systems on a single machine
> but if you grabbed just 2 or 3 USB flash drives then I would think you
> could test it pretty easily. I believe the UEFI boot procedures are
> storing a unique
On Mon, Feb 26, 2024 at 4:45 PM Grant Edwards
wrote:
>
> On 2024-02-26, Wol wrote:
> > On 26/02/2024 20:51, Grant Edwards wrote:
> >
> >> The simple answer is to quit wasting time trying to multi-boot like
> >> that and just buy a dozen USB flash drives.
> >>
> > And then, if USB isn't the
On 2024-02-26, Wol wrote:
> On 26/02/2024 20:51, Grant Edwards wrote:
>
>> The simple answer is to quit wasting time trying to multi-boot like
>> that and just buy a dozen USB flash drives.
>>
> And then, if USB isn't the default boot media, he might as well sort out
> UEFI boot, and multi-boot
On 26/02/2024 20:51, Grant Edwards wrote:
On 2024-02-26, eric wrote:
I agree, using the custom.cfg file would not work if needing to boot
different kernels of the same OS and those kernels were being updated.
The simple answer is to quit wasting time trying to multi-boot like
that and just
On 2024-02-26, eric wrote:
> I agree, using the custom.cfg file would not work if needing to boot
> different kernels of the same OS and those kernels were being updated.
The simple answer is to quit wasting time trying to multi-boot like
that and just buy a dozen USB flash drives.
--
Grant
On 2/26/24 11:01, Grant Edwards wrote:
On 2024-02-26, eric wrote:
On 2/26/24 04:57, gentoo-u...@krasauskas.dev wrote:
You could also write a script that keeps all the distros up to date
from within whichever one you're currently booted by mounting
subvolumes to /mnt or wherever, chrooting in
On 2024-02-26, eric wrote:
> On 2/26/24 04:57, gentoo-u...@krasauskas.dev wrote:
>> You could also write a script that keeps all the distros up to date
>> from within whichever one you're currently booted by mounting
>> subvolumes to /mnt or wherever, chrooting in and running the update.
>
> To
On 2024-02-23, Mark Knecht wrote:
> The only other idea I had was to install to a different
> disk and then use something like Clonezilla to move it to the partition
> you want it in on your system.
>
> While I suspect you were being sarcastic I do not think any solution
> that involves a
On Fri, Feb 23, 2024 at 12:52 PM Grant Edwards
wrote:
>
> On 2024-02-23, Mark Knecht wrote:
> > On Fri, Feb 23, 2024 at 11:59 AM Grant Edwards <
grant.b.edwa...@gmail.com>
> > wrote:
> >>
> >> The simple solution is to give up on multi-booting a dozen different
> >> distros on a single disk and
On 2024-02-23, Mark Knecht wrote:
> On Fri, Feb 23, 2024 at 11:59 AM Grant Edwards
> wrote:
>>
>> The simple solution is to give up on multi-booting a dozen different
>> distros on a single disk and buy a pocketful of USB 3 thumb drives.
>>
>
> Given performance does drop a bit and there can be
On Fri, Feb 23, 2024 at 11:59 AM Grant Edwards
wrote:
>
>
> The simple solution is to give up on multi-booting a dozen different
> distros on a single disk and buy a pocketful of USB 3 thumb drives.
>
Given performance does drop a bit and there can be issues with allocating
hardware, why not use
On 2024-02-23, Wols Lists wrote:
> On 23/02/2024 00:28, Grant Edwards wrote:
>> In my experience, 's bootloader does not boot other
>> installations by calling other bootloaders. It does so by rummaging
>> through all of the other partitions looking for kernel images,
>> intird files, grub.cfg
On 23/02/2024 00:28, Grant Edwards wrote:
In my experience, 's bootloader does not boot other
installations by calling other bootloaders. It does so by rummaging
through all of the other partitions looking for kernel images, intird
files, grub.cfg files, etc. It then adds menu entries to the
On 2024-02-23, Michael wrote:
> The problem starts if/when kernel images are overwritten by
> successive Linux OS distros. This is likely when derivatives of the
> same main distros e.g. Ubuntu all create a directory called
> /EFI/ubuntu/ in the ESP and drop their kernels & initrd images in
>
On 2024-02-23, Wojciech Kuzyszyn wrote:
> I guess most (all) of the distro's you are talking about use GRUB (or
> at least they allow to do it).
Yes, I belive that they are all now using Grub2.
> If that's true, I'm pretty sure you can happily let them overwrite
> the GRUB in MBR as many times
On Friday, 23 February 2024 00:28:59 GMT Grant Edwards wrote:
> On 2024-02-22, Wol wrote:
> > On 22/02/2024 21:45, Grant Edwards wrote:
> >> I've been reading up on UEFI, and it doesn't seem to be any
> >> better. People complain about distro's stomping on each other's files
> >> in the ESP
Hello!
I guess most (all) of the distro's you are talking about use GRUB (or
at least they allow to do it). If that's true, I'm pretty sure you can
happily let them overwrite the GRUB in MBR as many times as they want,
since it's the same (or just probably minor version differences)
bootloader.
On 2024-02-22, Wol wrote:
> On 22/02/2024 21:45, Grant Edwards wrote:
>> I've been reading up on UEFI, and it doesn't seem to be any
>> better. People complain about distro's stomping on each other's files
>> in the ESP partiton and multiple distro's using the same name in the
>> boot slots
On 22/02/2024 21:45, Grant Edwards wrote:
I've been reading up on UEFI, and it doesn't seem to be any
better. People complain about distro's stomping on each other's files
in the ESP partiton and multiple distro's using the same name in the
boot slots stored in NVM. And then the boot choice
On 2024-02-22, Wol wrote:
> On 22/02/2024 19:17, Grant Edwards wrote:
>
>> However, the choice to install bootloaders in partitions instead of
>> the MBR has been removed from most (all?) of the common installers.
>> This forces me to jump through hoops when installing a new Linux
>> distro:
>
>
Grant Edwards wrote:
> On 2024-02-17, Dale wrote:
>> Grant Edwards wrote:
>>> Today's routine update says:
>>>
>>> Re-run grub-install to update installed boot code!
>>>
>>> Is "sudo grub-install" really all I have to do? [...]
>>>
>>> Or do I have to run grub-install with all the same
On 2024-02-17, Dale wrote:
> Grant Edwards wrote:
>> Today's routine update says:
>>
>> Re-run grub-install to update installed boot code!
>>
>> Is "sudo grub-install" really all I have to do? [...]
>>
>> Or do I have to run grub-install with all the same options that
>> were originally used
On 2024-02-17, Peter Humphrey wrote:
> On Saturday, 17 February 2024 17:03:09 GMT Dale wrote:
>> Howdy,
>>
>> I posted about this once before but also included pipewire and others.
>> We addressed the other problems but this wasn't really fixed it would
>> seem. I found the old thread. This
1 - 100 of 35131 matches
Mail list logo
