[gentoo-user] Re: Switching from eudev to udev, disaster.

[Grant Edwards]

On 2021-11-30, tastytea  wrote:
> On 2021-11-29 22:47-0600 Dale  wrote:
>
>> Now if I can figure out how to reset the list of /dev/sd* names that
>> are lurking about and inconsistent, that would be like striking gold.
>>  Every time I hook up my external drive, it gets a different sd*
>> name.  It does the same on the SD cards from my trail cameras too but
>> I can auto mount those. 
>
> I don't think it is possible to get consistent sd* names for removable
> media.

You can write udev rules that trigger on the manufacturer, model, and
serial numbers. You can then assign consistent symlinks or even mount
them in predictable locations in the udev rules. I don't remember if
you can change the actual sd* names themselves, but there's no real
need to do so.

> But you could use volume labels with `tune2fs -L` or `tune.exfat
> -L` or `fatlabel` and then mount them via /dev/disk/by-label/*.

Re: [gentoo-user] Switching from eudev to udev, disaster.

[tastytea]

On 2021-11-29 23:19-0600 Dale  wrote:

> Matt Connell wrote:
> > On Mon, 2021-11-29 at 22:47 -0600, Dale wrote:  
> >> Now if I can figure out how to reset the list of /dev/sd* names
> >> that are lurking about and inconsistent, that would be like
> >> striking gold.  Every time I hook up my external drive, it gets a
> >> different sd* name.  It does the same on the SD cards from my
> >> trail cameras too but I can auto mount those.   
> > I'd suggest using the UUIDs for the disks (acquired via the blkid
> > command) and adding them to your /etc/fstab ... That's always been
> > my solution to commonly-connected-but-never-permanently external
> > disks.
> >
> > It won't ensure the same sd* name, but it will ensure that they get
> > mounted consistently where you expect them to be.
> >
> >
> >  
> 
> 
> Thanks to both for the idea.  My problem isn't mounting, it's
> decrypting the drive.  I use cryptsetup and I have to give the sd*
> name for both my external drives.  The way I do now, I type in the
> command to the sd point and hit tab twice.  Once the drive gets spun
> up, I hit tab again. Whichever one adds a 1 on the end is the one
> picked.  Thing is, it's rarely the same one so I have to test to see
> which one it picks.  I wish it would either reset itself or pick the
> same one each time.  I already know to ignore sda, sdb, sdc, sdd and
> sde. 
> 
> If it wasn't encrypted, it would be a good idea.  I sometimes wish
> there was a GUI way to do it that allows me to set my own mount
> point.  There are GUI crypt programs but they set their own mount
> points.  Plus, the command line is fairly easy.  The password is the
> hard part.  Good luck NSA.  ROFL 

If the partition table is GPT (instead of msdos compatible), you can
set a label to the partition itself with gparted (right click →
name partition) and then access it via /dev/disk/by-partlabel/. That
works for encrypted partitions too, since the name is stored in the
partition table and not the file system.

Kind regards, tastytea


-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpvHFgnrSW0v.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] Switching from eudev to udev, disaster.

[Wols Lists]

On 30/11/2021 04:47, Dale wrote:

Now if I can figure out how to reset the list of /dev/sd* names that are
lurking about and inconsistent, that would be like striking gold.  Every
time I hook up my external drive, it gets a different sd* name.  It does
the same on the SD cards from my trail cameras too but I can auto mount
those.


ls -al /dev/disk/by-uuid

That's a bunch of symlinks. The uuid part is guaranteed to be 
consistent, and the link points to the correct sdXn.


Try using that instead, and see if it works. It's supposed to ...

Cheers,
Wol

Re: [gentoo-user] Switching from eudev to udev, disaster.

[Dale]

Matt Connell wrote:
> On Mon, 2021-11-29 at 22:47 -0600, Dale wrote:
>> Now if I can figure out how to reset the list of /dev/sd* names that
>> are lurking about and inconsistent, that would be like striking
>> gold.  Every time I hook up my external drive, it gets a different
>> sd* name.  It does the same on the SD cards from my trail cameras too
>> but I can auto mount those. 
> I'd suggest using the UUIDs for the disks (acquired via the blkid
> command) and adding them to your /etc/fstab ... That's always been my
> solution to commonly-connected-but-never-permanently external disks.
>
> It won't ensure the same sd* name, but it will ensure that they get
> mounted consistently where you expect them to be.
>
>
>


Thanks to both for the idea.  My problem isn't mounting, it's decrypting
the drive.  I use cryptsetup and I have to give the sd* name for both my
external drives.  The way I do now, I type in the command to the sd
point and hit tab twice.  Once the drive gets spun up, I hit tab again. 
Whichever one adds a 1 on the end is the one picked.  Thing is, it's
rarely the same one so I have to test to see which one it picks.  I wish
it would either reset itself or pick the same one each time.  I already
know to ignore sda, sdb, sdc, sdd and sde. 

If it wasn't encrypted, it would be a good idea.  I sometimes wish there
was a GUI way to do it that allows me to set my own mount point.  There
are GUI crypt programs but they set their own mount points.  Plus, the
command line is fairly easy.  The password is the hard part.  Good luck
NSA.  ROFL 

Dale

:-)  :-)

Re: [gentoo-user] Switching from eudev to udev, disaster.

[Matt Connell]

On Mon, 2021-11-29 at 22:47 -0600, Dale wrote:
> Now if I can figure out how to reset the list of /dev/sd* names that
> are lurking about and inconsistent, that would be like striking
> gold.  Every time I hook up my external drive, it gets a different
> sd* name.  It does the same on the SD cards from my trail cameras too
> but I can auto mount those. 

I'd suggest using the UUIDs for the disks (acquired via the blkid
command) and adding them to your /etc/fstab ... That's always been my
solution to commonly-connected-but-never-permanently external disks.

It won't ensure the same sd* name, but it will ensure that they get
mounted consistently where you expect them to be.

Re: [gentoo-user] Switching from eudev to udev, disaster.

[tastytea]

On 2021-11-29 22:47-0600 Dale  wrote:

> Now if I can figure out how to reset the list of /dev/sd* names that
> are lurking about and inconsistent, that would be like striking gold.
>  Every time I hook up my external drive, it gets a different sd*
> name.  It does the same on the SD cards from my trail cameras too but
> I can auto mount those. 

I don't think it is possible to get consistent sd* names for removable
media. But you could use volume labels with `tune2fs -L` or `tune.exfat
-L` or `fatlabel` and then mount them via /dev/disk/by-label/*.

Kind regards, tastytea

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpwc3q7qeVz5.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] Switching from eudev to udev, disaster.

[Dale]

Neil Bothwick wrote:
> On Sun, 28 Nov 2021 11:02:17 -0600, Dale wrote:
>
>> I'm not completely opposed to switching to the new name method.  Your
>> info about it being in dmesg is helpful.  Now I know where that name is
>> exactly.  ;-)  Do I just rename my current net.eth* files to the new way
>> and it works or do I need to do something else or is there a automatic
>> way to do this? 
> Add net.ifnames=0 to kernel boot parameters.
>
>


I've already switched to the new naming method.  I'm not real big on it
but its been that way for a while so not likely to change again anytime
soon.  That said, they will likely announce a change in a month or so
just to rub my nerve the wrong way.  ROFL  At least it isn't as big a
deal as hal was.  ;-)  My biggest problem, I wasn't sure where to start
looking.  For some reason searching dmesg just escaped me. 

Now if I can figure out how to reset the list of /dev/sd* names that are
lurking about and inconsistent, that would be like striking gold.  Every
time I hook up my external drive, it gets a different sd* name.  It does
the same on the SD cards from my trail cameras too but I can auto mount
those. 

I'd also like for kwin to stop resetting every once in a while.  I
toggled the compositor(sp?) setting and that seems to have helped, so
far anyway. 

Dale

:-)  :-) 

Re: [gentoo-user] Git change logs

[Rich Freeman]

On Mon, Nov 29, 2021 at 11:43 AM Peter Humphrey  wrote:
>
> On Monday, 29 November 2021 16:32:45 GMT Rich Freeman wrote:
> > On Mon, Nov 29, 2021 at 11:17 AM Peter Humphrey
>  wrote:
> > > # (cd /var/db/repos/gentoo/sys-devel/gcc && git whatchanged)
> >
> > You'd get just as much output from git log - you didn't restrict the
> > output so it ran on the entire repository.  The current working
> > directory has no impact on the function of either git log or git
> > whatchanged.
>
> See what I mean about counter-intuitive?

You won't get any arguments from me that git is not a very refined
piece of software.  The other glaring flaw is inconsistencies in
command line options between various subcommands.

It is a beautiful concept, with a rough implementation.

>
> > You could append a . to just run git whatchanged on the current
> > directory.  I run "git whatchanged ." all the time.
>
> Thanks. I will. But how do I find the real change log of a package? The sort 
> of
> stuff I used to include in a software release bulletin when I was running the
> show. What has changed, and why? What fault reports have been closed? What
> new behaviour can be expected?

If there are any gentoo bugs resolved by a commit they're likely to
show up in the log (or with whatchanged), unless you ask for a oneline
version which will only show the first line of the log.  The bugs
would include links but obviously you'd have to hunt down what they
actually are.

Usually if a commit fixes some sort of serious issue it is going to
end up in the text of the commit description, especially if that were
the only change.  If it is a version bump and it happened to also
update the EAPI or fix a URL or something minor that might not get
mentioned.

As far as upstream behavior changes goes, don't expect to see this in
the commit log unless it is incredibly impactful, in which case you
might get news (like some big ABI break in the toolchain or
something).  In general Gentoo does not really do handholding with
release notes with upstream changes, or even provide more than a basic
level of integration across packages.  As was mentioned in another
recent discussion, don't expect that the latest stable kernel is
guaranteed to work with the latest stable zfs-kmod package, etc.  A
more release-based distro would be better equipped to do that but
actually doing a serious job of upstream release notes would  be a LOT
of work.

The Gentoo commit log is going to be more about changes in how
something is packaged.  Some are more detailed than others.  I know I
personally try to mention things like EAPI changes but I'm not sure
that everybody does.

Unfortunately since most changes create new revisions the diff
capabilities of git tend to be limited in usefulness.

-- 
Rich

Re: [gentoo-user] tor-browser does not start any more

[gevisz]

вс, 28 нояб. 2021 г. в 13:20, Poncho :
>
> On 28.11.21 12:09, gevisz wrote:
> > I have just noticed that the tor-browser I downloaded from its
> > official site does not start any more. :(
> > However, it started just a few weeks ago, before a few previous updates.
> > Downloading its latest version has not changed anything in this respect.
> >
>
> do you get any error message if you launch torbrowser from your terminal?

After "launching" the tor-browser in the terminal, I get only the
return value 255 instead of 0.

> just a guess... but you probably need to enable wayland for x11-libs/gtk+:3

Yes, Wayland is completely disabled in my system as I use Awesome.

> https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40693

Thank you.

Re: [gentoo-user] Gordian knot systemd / hwids

[Helmut Jarausch]

Many thanks Arve,

reemerging sys-apps/hwids with -udev -systemd use flags solved it.
Helmut

On 11/29/2021 04:18:59 PM, Arve Barsnes wrote:
On Mon, 29 Nov 2021 at 16:11, Helmut Jarausch   
wrote:

>
> Hi
> systemd-249.6-r1  conflicts with sys-apps/hwids[udev]
>
> But when I remove the udev use flag,
> emerge sys-apps/hwids gives
>
>The following REQUIRED_USE flag constraints are unsatisfied:
>  systemd? ( udev )
>
>
> So, I would have to remove sys-apps/systemd-249.6 first.
> Is it save to
> emerge -C sys-apps/systemd
>
> ?
> Thanks for a hint,

It seems like systems-249.6-r1 has removed support for hwids. There
are references in the ebuild to systemd-hwdb, so I guess they have
their own version. You need to remove the systemd USE flag from hwids
to solve your knot.

Regards,
Arve

Re: [gentoo-user] Git change logs

[Peter Humphrey]

On Monday, 29 November 2021 16:32:45 GMT Rich Freeman wrote:
> On Mon, Nov 29, 2021 at 11:17 AM Peter Humphrey 
 wrote:
> > # (cd /var/db/repos/gentoo/sys-devel/gcc && git whatchanged)
> 
> You'd get just as much output from git log - you didn't restrict the
> output so it ran on the entire repository.  The current working
> directory has no impact on the function of either git log or git
> whatchanged.

See what I mean about counter-intuitive?

> You could append a . to just run git whatchanged on the current
> directory.  I run "git whatchanged ." all the time.

Thanks. I will. But how do I find the real change log of a package? The sort of 
stuff I used to include in a software release bulletin when I was running the 
show. What has changed, and why? What fault reports have been closed? What 
new behaviour can be expected?

> > I've always found git counter-intuitive and I've resisted trying to
> > understand it, so far. Maybe I should make a little more effort.
> 
> IMO time spent understanding git is highly rewarded.  It isn't going
> anywhere.
> 
> I've heard it said that git is a data model masquerading as an SCM,
> and that is very accurate.  If you don't understand how it works
> you're going to be fighting it.
> 
> I get that you shouldn't have to know how the data model works to use
> a piece of software, but git runs pretty close to the metal.  Sure,
> you can always just copy/paste some one-liner that you read on a
> website, but you're always going to feel like you're wrestling it.
> Linus basically built it for himself and a handful of people like him,
> and it shows.  It is very powerful, but it is a bit like trying to use
> binutils without wanting to know what an ELF is.

:)

-- 
Regards,
Peter.

Re: [gentoo-user] Git change logs

[Rich Freeman]

On Mon, Nov 29, 2021 at 11:17 AM Peter Humphrey  wrote:
>
> On Monday, 29 November 2021 16:03:25 GMT Rich Freeman wrote:
> > On Mon, Nov 29, 2021 at 5:39 AM tastytea  wrote:
> > > If you want the history for a file, you need to specify the full path:
> > >
> > > git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild
> >
> > You can also point it at a directory and get changes for the entire
> > directory.  I also suggest trying "git whatchanged" as an alternative
> > to "git log."
>
> I didn't know about whatchanged. I tried it like this and got 120k lines of
> output:
>
> # (cd /var/db/repos/gentoo/sys-devel/gcc && git whatchanged)

You'd get just as much output from git log - you didn't restrict the
output so it ran on the entire repository.  The current working
directory has no impact on the function of either git log or git
whatchanged.

You could append a . to just run git whatchanged on the current
directory.  I run "git whatchanged ." all the time.

> I've always found git counter-intuitive and I've resisted trying to understand
> it, so far. Maybe I should make a little more effort.

IMO time spent understanding git is highly rewarded.  It isn't going anywhere.

I've heard it said that git is a data model masquerading as an SCM,
and that is very accurate.  If you don't understand how it works
you're going to be fighting it.

I get that you shouldn't have to know how the data model works to use
a piece of software, but git runs pretty close to the metal.  Sure,
you can always just copy/paste some one-liner that you read on a
website, but you're always going to feel like you're wrestling it.
Linus basically built it for himself and a handful of people like him,
and it shows.  It is very powerful, but it is a bit like trying to use
binutils without wanting to know what an ELF is.

-- 
Rich

Re: [gentoo-user] Git change logs

[Peter Humphrey]

On Monday, 29 November 2021 16:03:25 GMT Rich Freeman wrote:
> On Mon, Nov 29, 2021 at 5:39 AM tastytea  wrote:
> > If you want the history for a file, you need to specify the full path:
> > 
> > git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild
> 
> You can also point it at a directory and get changes for the entire
> directory.  I also suggest trying "git whatchanged" as an alternative
> to "git log."

I didn't know about whatchanged. I tried it like this and got 120k lines of 
output:

# (cd /var/db/repos/gentoo/sys-devel/gcc && git whatchanged)

I've always found git counter-intuitive and I've resisted trying to understand 
it, so far. Maybe I should make a little more effort.

> I'm guessing you could get git log to display the same
> info but I find whatchanged to be more useful, at least for
> directories.  There wouldn't be much point in running it on a single
> file since the main benefit is showing what files changed in each
> commit.
> 
> Keep in mind that git knows nothing about gentoo package atoms/syntax.
> It just sees a directory tree and files...

Yes, I did know that.

-- 
Regards,
Peter.

Re: [gentoo-user] Git change logs

[Peter Humphrey]

On Monday, 29 November 2021 10:39:15 GMT tastytea wrote:

> If you want the history for a file, you need to specify the full path:
> 
> git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild

That's the one I didn't try, of course. Thank you kind sir.

-- 
Regards,
Peter.

Re: [gentoo-user] Git change logs

[Rich Freeman]

On Mon, Nov 29, 2021 at 5:39 AM tastytea  wrote:
>
> If you want the history for a file, you need to specify the full path:
>
> git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild
>

You can also point it at a directory and get changes for the entire
directory.  I also suggest trying "git whatchanged" as an alternative
to "git log."  I'm guessing you could get git log to display the same
info but I find whatchanged to be more useful, at least for
directories.  There wouldn't be much point in running it on a single
file since the main benefit is showing what files changed in each
commit.

Keep in mind that git knows nothing about gentoo package atoms/syntax.
It just sees a directory tree and files...

-- 
Rich

Re: [gentoo-user] Gordian knot systemd / hwids

[Arve Barsnes]

On Mon, 29 Nov 2021 at 16:11, Helmut Jarausch  wrote:
>
> Hi
> systemd-249.6-r1  conflicts with sys-apps/hwids[udev]
>
> But when I remove the udev use flag,
> emerge sys-apps/hwids gives
>
>The following REQUIRED_USE flag constraints are unsatisfied:
>  systemd? ( udev )
>
>
> So, I would have to remove sys-apps/systemd-249.6 first.
> Is it save to
> emerge -C sys-apps/systemd
>
> ?
> Thanks for a hint,

It seems like systems-249.6-r1 has removed support for hwids. There
are references in the ebuild to systemd-hwdb, so I guess they have
their own version. You need to remove the systemd USE flag from hwids
to solve your knot.

Regards,
Arve

[gentoo-user] Gordian knot systemd / hwids

[Helmut Jarausch]

Hi
systemd-249.6-r1  conflicts with sys-apps/hwids[udev]

But when I remove the udev use flag,
emerge sys-apps/hwids gives

  The following REQUIRED_USE flag constraints are unsatisfied:
systemd? ( udev )


So, I would have to remove sys-apps/systemd-249.6 first.
Is it save to
emerge -C sys-apps/systemd

?
Thanks for a hint,
Helmut

Re: [gentoo-user] preserved-rebuild displays an error message only

[Helmut Jarausch]

On 11/22/2021 03:08:46 PM, Julien Roy wrote:

emerge -pv --depclean dev-libs/imath


Many thanks,
Helmut

Re: [gentoo-user] Git change logs

[tastytea]

On 2021-11-29 10:26+ Peter Humphrey  wrote:

> Hello list,
> 
> Today's update includes sys-devel/gcc-11.2.1_p20211127, up from
> 11.2.1. I wanted to find out what changes had been introduced, so I
> went searching for the change log. I sync gentoo with git, so it
> should be easy to find the log. Google found references to git log,
> but when I tried it I got this:
> 
> /var/db/repos/gentoo # git log sys-devel/gcc-11.2.1_p20211127
> fatal: ambiguous argument 'sys-devel/gcc-11.2.1_p20211127': unknown
> revision or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git  [...] -- [...]'
> 
> So I did that, but whatever I tried returned 'bad revision'. What's
> the proper syntax?

If you want the history for a file, you need to specify the full path:

git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild

Kind regards, tastytea

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpeGvLWoh8Fd.pgp
Description: Digitale Signatur von OpenPGP

Re: [gentoo-user] Git change logs

[Arve Barsnes]

On Mon, 29 Nov 2021 at 11:26, Peter Humphrey  wrote:
> /var/db/repos/gentoo # git log sys-devel/gcc-11.2.1_p20211127
> fatal: ambiguous argument 'sys-devel/gcc-11.2.1_p20211127': unknown revision
> or path not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git  [...] -- [...]'
>
> So I did that, but whatever I tried returned 'bad revision'. What's the proper
> syntax?

It lists the syntax right there. I don't sync with git, so I can't
check this with my repo, but it seems like you need to refer to an
actual path or file, so one of these:
$ git log sys-devel/gcc
$ git log sys-devel/gcc/gcc-11.2.1_p20211127.ebuild

Regards,
Arve

[gentoo-user] Git change logs

[Peter Humphrey]

Hello list,

Today's update includes sys-devel/gcc-11.2.1_p20211127, up from 11.2.1. I 
wanted to find out what changes had been introduced, so I went searching for 
the change log. I sync gentoo with git, so it should be easy to find the log. 
Google found references to git log, but when I tried it I got this:

/var/db/repos/gentoo # git log sys-devel/gcc-11.2.1_p20211127
fatal: ambiguous argument 'sys-devel/gcc-11.2.1_p20211127': unknown revision 
or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'

So I did that, but whatever I tried returned 'bad revision'. What's the proper 
syntax?

-- 
Regards,
Peter.