On Wednesday, February 15, 2023 10:56:22 AM CET Peter Humphrey wrote:
> Hello list,
>
> Not long ago I read that we should allow 2GB RAM for every emerge job - that
> is, we should divide our RAM size by 2 to get the maximum number of
> simultaneous jobs. I'm trying to get that right, but I'm not
On Wed, Feb 15, 2023 at 07:20:37PM +, Wol wrote
> what are they going to do about "eselect kernel set ..." then?
>
> It's bad enough depclean deleting the active kernel if you don't watch
> out, without something deciding to install a non-existent kernel and
> deleting the live one :-)
Hi,
Wol writes:
> On 15/02/2023 15:51, Daniel Frey wrote:
>> On 2/15/23 06:10, Michael Orlitzky wrote:
>>> On 2023-02-15 08:11:46, Neil Bothwick wrote:
If, as you say, it will eventually replace eselect, there is no more
bloat, just different bloat. It's still just a bunch of
On 15/02/2023 15:51, Daniel Frey wrote:
On 2/15/23 06:10, Michael Orlitzky wrote:
On 2023-02-15 08:11:46, Neil Bothwick wrote:
If, as you say, it will eventually replace eselect, there is no more
bloat, just different bloat. It's still just a bunch of symlinks, but
managed differently.
On 2023-02-15, Grant Edwards wrote:
> [1] For this purpose you want a plain old UART on the motherboard type
> seial port. You'd be surprised how many motherboards still have
> them. Even though they're never brought out to a DB9 connector on
> the back panel, there's often an 8-pin
On 2/15/23 06:10, Michael Orlitzky wrote:
On 2023-02-15 08:11:46, Neil Bothwick wrote:
If, as you say, it will eventually replace eselect, there is no more
bloat, just different bloat. It's still just a bunch of symlinks, but
managed differently.
Should be less, since you already have
On Wednesday, 15 February 2023 15:12:28 GMT Michael wrote:
> You can have both a generic MAKEOPTS in make.conf, which suits your base
> case of emerge operations and will not cause your PC to explode when
> combined with EMERGE_DEFAULT_OPTS, as well as package specific MAKEOPTS in
> package.env
On Wed, 15 Feb 2023 09:50:27 -0500,
Grant Edwards wrote:
>
> On 2023-02-14, Rich Freeman wrote:
>
> > Where are you getting this from, the system log/journal? This doesn't
> > seem like a clean shutdown, so if it is a kernel PANIC I wouldn't
> > expect the most critical info to be in the log
On Wednesday, 15 February 2023 14:31:25 GMT Peter Humphrey wrote:
> On Wednesday, 15 February 2023 13:18:24 GMT Rich Freeman wrote:
> > On Wed, Feb 15, 2023 at 4:56 AM Peter Humphrey
>
> wrote:
> > > Not long ago I read that we should allow 2GB RAM for every emerge job -
> > > that is, we should
On 2023-02-14, Rich Freeman wrote:
> Where are you getting this from, the system log/journal? This doesn't
> seem like a clean shutdown, so if it is a kernel PANIC I wouldn't
> expect the most critical info to be in the log (since it will stop
> syncing to protect the filesystem). The details
On Wed, Feb 15, 2023 at 9:10 AM Michael Orlitzky wrote:
>
> On 2023-02-15 08:11:46, Neil Bothwick wrote:
> >
> > If, as you say, it will eventually replace eselect, there is no more
> > bloat, just different bloat. It's still just a bunch of symlinks, but
> > managed differently.
> >
>
> Should
On Wednesday, 15 February 2023 13:18:24 GMT Rich Freeman wrote:
> On Wed, Feb 15, 2023 at 4:56 AM Peter Humphrey
wrote:
> > Not long ago I read that we should allow 2GB RAM for every emerge job -
> > that is, we should divide our RAM size by 2 to get the maximum number of
> > simultaneous jobs.
On 2023-02-15 08:11:46, Neil Bothwick wrote:
>
> If, as you say, it will eventually replace eselect, there is no more
> bloat, just different bloat. It's still just a bunch of symlinks, but
> managed differently.
>
Should be less, since you already have portage installed but not
necessarily
On Wed, Feb 15, 2023 at 4:56 AM Peter Humphrey wrote:
>
> Not long ago I read that we should allow 2GB RAM for every emerge job - that
> is, we should divide our RAM size by 2 to get the maximum number of
> simultaneous jobs. I'm trying to get that right, but I'm not there yet.
>
> I have these
On Wednesday, 15 February 2023 11:31:49 GMT Peter Böhm wrote:
> Am Mittwoch, 15. Februar 2023, 10:56:22 CET schrieb Peter Humphrey:
> > Hello list,
> >
> > Not long ago I read that we should allow 2GB RAM for every emerge job -
> > that is, we should divide our RAM size by 2 to get the maximum
On Wednesday, 15 February 2023 09:56:22 GMT Peter Humphrey wrote:
> EMERGE_DEFAULT_OPTS="--jobs=16 --load-average=32 --autounmask=n --quiet-
> unmerge-warn --ke>
That should have been:
EMERGE_DEFAULT_OPTS="--jobs=16 --load-average=32 --autounmask=n --quiet-
unmerge-warn --keep-going
Am Mittwoch, 15. Februar 2023, 10:56:22 CET schrieb Peter Humphrey:
> Hello list,
>
> Not long ago I read that we should allow 2GB RAM for every emerge job - that
> is, we should divide our RAM size by 2 to get the maximum number of
> simultaneous jobs. I'm trying to get that right, but I'm not
Hello list,
Not long ago I read that we should allow 2GB RAM for every emerge job - that
is, we should divide our RAM size by 2 to get the maximum number of
simultaneous jobs. I'm trying to get that right, but I'm not there yet.
I have these entries in make.conf:
EMERGE_DEFAULT_OPTS="--jobs=16
Hi,
"Walter Dnes" writes:
> A whole bunch of busy-work for emerge, and nothing in the news item
> indicates it's really necessary for the average user. Howsabout...
It's definitely necessary. Those packages provide links for vital parts
of the filesystem, like /bin/sh.
Why do you want to
On Wed, 15 Feb 2023 02:44:47 -0500, Walter Dnes wrote:
> After thoroughly reading the docs at...
> https://www.gentoo.org/support/news-items/2022-12-27-alternatives-introduction.html
> it looks like the hand of him-who-must-not-be-named. Rather than
> provide special support for the 1% extreme
20 matches
Mail list logo
