Re: [gentoo-user] bad $PATH
On Thu, 2 May 2024 at 14:09, Peter Humphrey wrote: > On Thursday, 2 May 2024 13:55:42 BST Jorge Almeida wrote: > > I have > > /var/lib/bin > > in my $PATH (both as root and as normal user) > > > Anyone with the same problem/weirdness? > > Nope. Have you tried 'grep -r var/lib/bin /etc' ? > > I tried now: /etc/profile.env:export PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin' /etc/environment.d/10-gentoo-env.conf:PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin /etc/env.d/99xstow:PATH=/var/lib/bin /etc/csh.env:setenv PATH '/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin' So, it seems I have at least one package which I wouldn't expect to have: app-admin/xstow I seem to remember I installed a long time ago. It is in the world file, hence emerge -c wouldn't clean it. I don't have csh but think I had it once upon a time. Removing... Ok, done, and the PATH is fine now. Thanks, Jorge
Re: [gentoo-user] bad $PATH
On Thu, 2 May 2024 at 15:07, Petr Vaněk wrote: > On Thu, May 02, 2024 at 01:55:42PM +0100, Jorge Almeida wrote: > > I have /var/lib/bin in my $PATH (both as root and as normal user) > > > Do you have app-admin/xstow installed? This seems to be the (only) > Indeed, I had it in the world file, currently unused and long forgotten. Solved.. Thanks, Jorge
Re: [gentoo-user] bad $PATH
On Thu, May 02, 2024 at 01:55:42PM +0100, Jorge Almeida wrote: > I have /var/lib/bin in my $PATH (both as root and as normal user) > > [snip] What could be setting this? (grep /var/lib/bin /etc/conf.d/* > returns nothing) Do you have app-admin/xstow installed? This seems to be the (only) package which adds /var/lib/bin to the PATH, see [1]. At least, I was able to grep -F var/lib/bin pattern only in this package in ::gentoo overlay. [1] https://github.com/gentoo/gentoo/blob/c2fb597e863fb296b5cdaf36e8b258b20c47d4a1/app-admin/xstow/xstow-1.1.0.ebuild#L51-L52 Petr
Re: [gentoo-user] bad $PATH
On Thursday, 2 May 2024 13:55:42 BST Jorge Almeida wrote: > I have > /var/lib/bin > in my $PATH (both as root and as normal user) > > That directory does not exist. Should it exist!? > What could be setting this? > (grep /var/lib/bin /etc/conf.d/* returns nothing) > > Anyone with the same problem/weirdness? Nope. Have you tried 'grep -r var/lib/bin /etc' ? -- Regards, Peter. signature.asc Description: This is a digitally signed message part.
[gentoo-user] bad $PATH
I have /var/lib/bin in my $PATH (both as root and as normal user) That directory does not exist. Should it exist!? What could be setting this? (grep /var/lib/bin /etc/conf.d/* returns nothing) Anyone with the same problem/weirdness? Thanks Jorge Almeida
Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.
On Thursday, 2 May 2024 00:45:29 BST Dale wrote: > Grant Edwards wrote: > > OK, so 'boot' is for the Linux /boot directory. I was just curious > > since I had never used one. When I started using Linux, the received wisdom was to keep a separate /boot, and leave it unmounted during normal operation. The idea was that a successful hacker would not, supposedly, be able to corrupt the kernel ready for a reboot into their system. Old habits die hard, though, and besides, a separate /boot has been handy in the copious reinstallations I've been through. > I've used one ever since I started using Linux and it's as much habit as > anything. Given the size of drives nowadays, I have started putting > /usr and /var on the root partition. When I build my new rig tho, odds > are /var will be on its own partition. That way if a log file goes > wonky, it can fill it up and not really do any harm. I do that too. It also helps with backups and new installations. -- Regards, Peter. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.
Michael wrote: > On Thursday, 2 May 2024 00:45:29 BST Dale wrote: >> Grant Edwards wrote: >>> On 2024-05-01, Dale wrote: Grant Edwards wrote: > The partition type code for 'swap' is wrong -- it should be > 8200. According to the gdisk help info Linux /home is supposed to be > 8302, but I've always used the same generic "Linux filesystem" type > for both /home and root. > > Is the 'boot' partition for future possible UEFI use, for Linux /boot, > or both? [I've never used a separate partition for Linux /boot, I > just use a /boot directory on the root FS.] I noticed the other day that some new ones was added. I always leave it as 8300 and it works. It even works for swap. I dunno. > In the legacy DOS partition tables the space available was limited to 32 > bits, > while the GPT table specification provides 128 bytes for each block entry. > The extra space can be used to store information related to the intended OS > usage of each partition, by adding the corresponding Partition Type UUID. > > This has a number of benefits, described here: > > https://uapi-group.org/specifications/specs/ > discoverable_partitions_specification/ > > Besides the automation this feature affords, I find it useful to know what a > partition contains without having to mount it. On GPT labelled disks I make > use both of the Partition Type UUID and the Partition Name. A quick glance > at > the gdisk output and if need be its 'i' option has saved my day from > formatting the wrong partition more than once! ;-) I always use labels which show up with cgdisk. If I'm unsure how I partitioned a drive for some reason, I just check it with cgdisk to see what is what. I use labels even tho a lot of the time I put UUIDs in fstab. I do similar when using LVM as well. There is more than one way to organize things tho. ;-) Dale :-) :-)
Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.
On Thursday, 2 May 2024 00:45:29 BST Dale wrote: > Grant Edwards wrote: > > On 2024-05-01, Dale wrote: > >> Grant Edwards wrote: > >>> The partition type code for 'swap' is wrong -- it should be > >>> 8200. According to the gdisk help info Linux /home is supposed to be > >>> 8302, but I've always used the same generic "Linux filesystem" type > >>> for both /home and root. > >>> > >>> Is the 'boot' partition for future possible UEFI use, for Linux /boot, > >>> or both? [I've never used a separate partition for Linux /boot, I > >>> just use a /boot directory on the root FS.] > >> > >> I noticed the other day that some new ones was added. I always leave it > >> as 8300 and it works. It even works for swap. I dunno. In the legacy DOS partition tables the space available was limited to 32 bits, while the GPT table specification provides 128 bytes for each block entry. The extra space can be used to store information related to the intended OS usage of each partition, by adding the corresponding Partition Type UUID. This has a number of benefits, described here: https://uapi-group.org/specifications/specs/ discoverable_partitions_specification/ Besides the automation this feature affords, I find it useful to know what a partition contains without having to mount it. On GPT labelled disks I make use both of the Partition Type UUID and the Partition Name. A quick glance at the gdisk output and if need be its 'i' option has saved my day from formatting the wrong partition more than once! ;-) signature.asc Description: This is a digitally signed message part.
