William Kenworthy wrote:
>
> On 16/6/24 07:07, Mark Knecht wrote:
>>
>> > I still don't understand the efi thing. I'm booted up tho. I'm
>> happy.
>> > Now to get temp sensors and stuff to work. I want to keep a eye on
>> > temps for a bit. I think the boot media was reporting the wrong info.
On 16/6/24 07:07, Mark Knecht wrote:
> I still don't understand the efi thing. I'm booted up tho. I'm happy.
> Now to get temp sensors and stuff to work. I want to keep a eye on
> temps for a bit. I think the boot media was reporting the wrong info.
> Even the ambient temp was to high for
> I still don't understand the efi thing. I'm booted up tho. I'm happy.
> Now to get temp sensors and stuff to work. I want to keep a eye on
> temps for a bit. I think the boot media was reporting the wrong info.
> Even the ambient temp was to high for this cool room. It showed like
> 100F
On Saturday, 15 June 2024 23:00:07 BST Jack wrote:
> A bit of searching found the wiki page for dispatch-conf, which
> includes:
>
> Before running dispatch-conf for the first time, the settings in
> /etc/dispatch-conf.conf should be edited, and the archive directory
> specified in
On 2024.06.15 02:38, Vitaliy Perekhovy wrote:
On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> I don't have any such directory. What package does it belong to,
or is
> it a config setting for portage or another package?
Yes, it is a configuration of portage itself. There is an env
Michael wrote:
> On Saturday, 15 June 2024 12:01:26 BST Dale wrote:
>> Michael wrote:
>>> b) Using a bootloader:
>>>
>>> Mount your ESP under the /efi mountpoint. GRUB et al, will install their
>>> .efi image in the /efi/EFI/ directory. You can have your /boot as a
>>> directory on your /
Hello, Vitaliy.
On Fri, Jun 14, 2024 at 21:25:23 +0300, Vitaliy Perekhovy wrote:
> On Fri, Jun 14, 2024 at 03:53:35PM +, Alan Mackenzie wrote:
> > I think portage is at fault here - it should retain the older standard
> > version of /etc/bash/bashrc so that users can resolve the differences
>
Hello, Netfab.
On Fri, Jun 14, 2024 at 19:52:32 +0200, netfab wrote:
> Le 14/06/24 à 19:33, Alan Mackenzie a tapoté :
> > Are these files freely available, anywhere, perhaps?
> Else, everything is also available from gentoo.org :
>
>
Michael wrote:
> On Saturday, 15 June 2024 19:33:54 BST Dale wrote:
>
>> (chroot) livecd / # cat /etc/env.d/02locale
>> # Configuration file for eselect
>> # This file has been automatically generated.
>> LANG="en_US.UTF8"
>> #LC_ALL="en_US.UTF8"
>> (chroot) livecd / #
>>
>> I commented out the
On 2024-06-15, Michael wrote:
> On Saturday, 15 June 2024 19:20:26 BST Alan Grimes wrote:
>> A number of my softwarez requires the use of the arrow keys and can't
>> use the numpad in edit mode to work around it. So who do I need to kill
>> to get arrow keys to work in x11 again?
>
> I don't
On Saturday, 15 June 2024 19:20:26 BST Alan Grimes wrote:
> A number of my softwarez requires the use of the arrow keys and can't
> use the numpad in edit mode to work around it. So who do I need to kill
> to get arrow keys to work in x11 again?
I don't understand what is the "edit mode" you
On Saturday, 15 June 2024 17:55:17 BST Michael wrote:
--->8
Thanks, but I'll stick to what I know if you don't mind.
--
Regards,
Peter.
Lets go back to square 1.
The keyboard is the most fundamental device ever, it was invented about
80 years before anyone figured out how to connect it to a computer,
before the computer even existed actually
The fundamental AT 101 keyboard, or microsoft's gay variant the PC-104,
and the
On Saturday, 15 June 2024 19:33:54 BST Dale wrote:
> (chroot) livecd / # cat /etc/env.d/02locale
> # Configuration file for eselect
> # This file has been automatically generated.
> LANG="en_US.UTF8"
> #LC_ALL="en_US.UTF8"
> (chroot) livecd / #
>
> I commented out the LC_ALL thinking it might
Michael wrote:
> On Saturday, 15 June 2024 19:09:18 BST Dale wrote:
>> Michael wrote:
>>> On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
Howdy,
I got down to the time zone part. When I try to run emerge --config
sys-libs/timezone-data I get this output.
A number of my softwarez requires the use of the arrow keys and can't
use the numpad in edit mode to work around it. So who do I need to kill
to get arrow keys to work in x11 again?
--
You can't out-crazy a Democrat.
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
On Saturday, 15 June 2024 19:09:18 BST Dale wrote:
> Michael wrote:
> > On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
> >> Howdy,
> >>
> >> I got down to the time zone part. When I try to run emerge --config
> >> sys-libs/timezone-data I get this output.
> >>
> >>
> >>
> >> (chroot)
Michael wrote:
> On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
>> Howdy,
>>
>> I got down to the time zone part. When I try to run emerge --config
>> sys-libs/timezone-data I get this output.
>>
>>
>>
>> (chroot) livecd / # emerge --config sys-libs/timezone-data
>>
>>
>> Configuring pkg...
On Saturday, 15 June 2024 18:24:27 BST Dale wrote:
> Howdy,
>
> I got down to the time zone part. When I try to run emerge --config
> sys-libs/timezone-data I get this output.
>
>
>
> (chroot) livecd / # emerge --config sys-libs/timezone-data
>
>
> Configuring pkg...
>
> Traceback (most
On Saturday, 15 June 2024 18:24:04 BST Walter Dnes wrote:
> On Sat, Jun 15, 2024 at 12:39:09PM +0100, Michael wrote
>
> > The maximum temperature at which your CPU die with its 65W TDP starts
> > throttling to keep its temperatures safe is 100°C TjMax. Look at the
> > TJunction number here:
> >
Howdy,
I got down to the time zone part. When I try to run emerge --config
sys-libs/timezone-data I get this output.
(chroot) livecd / # emerge --config sys-libs/timezone-data
Configuring pkg...
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.12/emerge", line 57,
On Sat, Jun 15, 2024 at 12:39:09PM +0100, Michael wrote
> The maximum temperature at which your CPU die with its 65W TDP starts
> throttling to keep its temperatures safe is 100°C TjMax. Look at the
> TJunction number here:
>
>
On 14/06/2024 18:39, Alan Mackenzie wrote:
Does etc-update or dispatch-conf not give you the option to selectively
update and/or to diff the file?
In theory, yes. In practice, dispatch-conf just offers a single
~130-line long hunk, which is useless for distinguishing wanted pieces of
code
On Saturday, 15 June 2024 16:28:29 BST Peter Humphrey wrote:
> On Saturday, 15 June 2024 13:01:33 BST Dale wrote:
> > Could you share the boot screen again?
>
> New version attached...
>
> > I used lilo ages ago then switched to Grub. Grub is massive but it works
> > well enough.
>
> ...as
On 14/06/2024 16:53, Alan Mackenzie wrote:
I think portage is at fault here - it should retain the older standard
version of /etc/bash/bashrc so that users can resolve the differences
with a 3-way diff.
Is it portage itself that DID the update, or it did it tell you to do
the update with
On Saturday, 15 June 2024 12:01:26 BST Dale wrote:
> Michael wrote:
> > b) Using a bootloader:
> >
> > Mount your ESP under the /efi mountpoint. GRUB et al, will install their
> > .efi image in the /efi/EFI/ directory. You can have your /boot as a
> > directory on your / partition, or on its
On 14/06/2024 14:53, Walter Dnes wrote:
On Thu, Jun 13, 2024 at 10:49:57PM -0500, Dale wrote
model name : Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Specs for your CPU are here:
Peter Humphrey wrote:
> On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
>> Peter Humphrey wrote:
>>> Here's the output of parted -l on my main NVMe disk in case it helps:
>>>
>>> Model: Samsung SSD 970 EVO Plus 250GB (nvme)
>>> Disk /dev/nvme1n1: 250GB
>>> Sector size (logical/physical):
On Friday, 14 June 2024 20:53:04 BST Walter Dnes wrote:
> On Fri, Jun 14, 2024 at 11:54:52AM +0100, Michael wrote
>
> > I would think 46-48°C is refreshingly cool, but it very much depends
> > on the CPU chip, the MoBo and its BIOS/microcode settings.
>
> I looked up my CPU (see my reply to
On Friday, 14 June 2024 18:33:57 BST Alan Mackenzie wrote:
> Are these files freely available, anywhere, perhaps?
Your backup from last week? :)
--
Regards,
Peter.
On Friday, 14 June 2024 16:16:09 BST Michael wrote:
> Liquid cooling would have made it as quiet as a church mouse. ;-)
I have a machine here with liquid cooling, and over its few years it's become
deafening under full load (24 simultaneous floating-point physics
applications). It is quiet
On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
> Peter Humphrey wrote:
> > Here's the output of parted -l on my main NVMe disk in case it helps:
> >
> > Model: Samsung SSD 970 EVO Plus 250GB (nvme)
> > Disk /dev/nvme1n1: 250GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table:
Michael wrote:
> On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
>> Peter Humphrey wrote:
>>> On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
My plan, given it is a 1TB, use maybe 300GBs of it. Leave the rest
blank. Have the /boot, EFI directory, root and maybe put /var on a
On Saturday, 15 June 2024 07:53:06 BST Dale wrote:
> Peter Humphrey wrote:
> > On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
> >> My plan, given it is a 1TB, use maybe 300GBs of it. Leave the rest
> >> blank. Have the /boot, EFI directory, root and maybe put /var on a
> >> separate partition.
-- Original Message --
From "Paul Colquhoun"
To gentoo-user@lists.gentoo.org
Date 15.06.2024 01:43:22
Subject Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc
You edited the old file, not portage.
Why didn't you keep a copy of the old file?
I have this in the crontabs
Peter Humphrey wrote:
> On Sunday, 2 June 2024 16:11:38 BST Dale wrote:
>
>> My plan, given it is a 1TB, use maybe 300GBs of it. Leave the rest
>> blank. Have the /boot, EFI directory, root and maybe put /var on a
>> separate partition. I figure for the boot stuff, 3GBs would be plenty
>> for
On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> I don't have any such directory. What package does it belong to, or is
> it a config setting for portage or another package?
Yes, it is a configuration of portage itself. There is an env variable
CONFIG_PROTECT that contains a list of
37 matches
Mail list logo
