Jarkko Sakkinen
Posts
3399Following
203Followers
340
Jarkko Sakkinen
jarkko
Edited 4 months ago
I wonder if #NetworkManager will integrate as client of networkd? People like to hate NM but I actually like nmcli.
For instance, if I need to throw a bridge, I simply just:
nmcli connection add type bridge ifname br0 stp no
nmcli connection add type bridge-slave ifname enp63s0 master br0
nmcli connection up bridge-br0
NM is just an interface for whatever shenanigans below so I guess it should be possible to interface it to networkd, right?
Is #GNOME going to move forward with this eventually, or is NM going to be ditched? I don’t actually care how soon such thing might happen, I’m just worried about loosing good old NM ;-)
1
0
1
@vbabka anyway it is updated and I don't think Linus has yet checked my PR thanks to 10h difference between Finland and West Coast ;-) https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/keys/3AB05486C7752FE1.asc
1
0
1
@vbabka yeah, this is like only small portion. there's bunch of records like depeche mode, KLF, bunch of 80s new wave / synth pop alike stuff, mike oldfield, some really old hard trance ep's, and yeah total unsorted collection of random EP's and LP's. Has been more like diary than a record collection. When I've been somewhere and seen a cool record I've bought is a memory. Some people buy postcards for that purpose, I prefer vinyl ;-)
Only track I listened was this one from the golden age of Bonzai Records: https://www.youtube.com/watch?v=sHVdb8s_ijk
Only track I listened was this one from the golden age of Bonzai Records: https://www.youtube.com/watch?v=sHVdb8s_ijk
1
0
1
@duxsco primary key migration is something I've never even looked at. It's essentially a new identity. I e.g. wonder can you migrate the trust from one primary key to another, if I ever need to do that. I guess my RSA-4096 identity will hold for some time tho :-)
0
0
0
@kernellogger Also this is the reason why sometimes there should more emphasis on commit message than code change itself. Commit message is not only a notification that "I added this pile of crap here". It's also micro-instructions for maintainer how to take care of the changes in the future. In the case on this patch set, I have no complains on this.
0
0
1
Jarkko Sakkinen
jarkko
@kernellogger np, it was on me :-) If I ack something, in the end of the day that's my responsibility, e.g. not even in original author's responsibility.
This is also main reason why people should not get offended if a maintainer does not take their changes in. It's also commitment for some extra work... even sometimes when you're on holiday ;-)
This is also main reason why people should not get offended if a maintainer does not take their changes in. It's also commitment for some extra work... even sometimes when you're on holiday ;-)
1
0
1
@kernellogger Put out a PR: https://lore.kernel.org/linux-integrity/D2HKE740MWCK.2O7S4KF56L929@kernel.org/
I did all three QA rounds running selftests, creating some trusted keys etc. for all three combinations mentioned in the cover letter, and also Michael Ellerman tested this on PPC so it should be pretty solid fix.
I did all three QA rounds running selftests, creating some trusted keys etc. for all three combinations mentioned in the cover letter, and also Michael Ellerman tested this on PPC so it should be pretty solid fix.
1
0
0
@duxsco I've considered unlimited expiration dates but this enforces me to do inventory for my db ;-) so i bump them like 2-3 years in future when this happens. e.g. now i revoked couple of keys that i no longer possess, now that i had anyway had to do this dance.
0
0
0
