furrywolf | so, this isn't something devuan caused, but it sure would be nice if we fixed it... | 05:41 |
---|---|---|
furrywolf | menus are utterly fucking broken in ascii vs previous versions. | 05:41 |
furrywolf | having half the packages use the nice, working, properly organized debian menu system, and half using the new, broken, utterly shittily organized new menu system, means you have to look about six places to find where programs ended up when you installed their packages, if anywhere. | 05:42 |
furrywolf | like, why the fuck is freecad under "graphics", oregano under "education" (wtf?), and other idiocy with the new menu system (does it not have supmenus? did something decide more than ten categories would be too confusing?), while other things are only in the old menu system? | 05:45 |
furrywolf | window managers that only use one of the two menu systems end up only showing half your programs | 05:46 |
furrywolf | can we please get rid of the worthless new menu system and stick everything back into the debian menu system? heh | 05:51 |
furrywolf | and, after finally finding an answer googling... there's only ten categories because freedesktop declared there should only be ten categories. | 05:53 |
furrywolf | why the bloody fuck do we put up with fucking anything they do? | 05:53 |
rrq | mmm I'm not a freedesktop fan, but going to their latest spec, I found 13 main categories, 120 or so 'additional categories' and 4 'reserved categories'. https://specifications.freedesktop.org/menu-spec/latest... maybe that's an old spec of course. | 06:21 |
furrywolf | there's only ten... for examle, video and audio are only used if you dont use audio and video, etc... and debian of course went for the least-descriptive set possible. debian only uses the topmost ten, absolutely no subcategories or anything else. | 06:22 |
furrywolf | with the old debian menu system, cad software might be under Science->Engineering or Science->Electronics (depending on the program's focus)... while under the new system, they're randomly put into "Graphics" or "Education". | 06:24 |
rrq | yes, I agree about rather following debuan-menu.. https://www.debian.org/doc/packaging-manuals/menu.html | 06:24 |
furrywolf | regardless of the technical benefits of the menu system, this new cram-everything-into-dictated-categories total mess is stupid. | 06:28 |
Achylles | can devuan run on risc-V? | 12:43 |
Achylles | Or is it to early? Has anyone tested this? | 12:44 |
va7lnx | Achylles: what system use that arch? | 12:53 |
r3boot | Achylles: Debian does seem to support risc-v, e_noclue as to how much of this Devuan has imported (https://wiki.debian.org/RISC-V) | 12:59 |
Achylles | r3boot, I know about debian... | 13:01 |
Achylles | But, I am interested in devuan itself | 13:02 |
Achylles | Thus my question if anyone has tested devuan in risc-v arch... | 13:02 |
r3boot | (I dont know if the URL is used, but the cert for packages.devuan.org has expired) | 13:06 |
r3boot | Achylles: I did a quick check for ISO's / package repo's. It seems that devuan only does i386 and amd64 atm | 13:07 |
r3boot | So .. sounds like a nice project which can be picked up :) | 13:08 |
Achylles | r3boot, if I had the know-how I would pick that up. Perhaps, someone else... | 13:13 |
Achylles | Since devuan is a great distro and on risc-V should attract more users... | 13:14 |
r3boot | Mja, that's part of running a new architecture, making sure that stuff gets ported so over time it can become mainstream | 13:14 |
r3boot | if no-one does the porting, it simply wont happen | 13:14 |
r3boot | (multiple good platforms have died that way btw) | 13:14 |
r3boot | nofi or anything, just a general observation :) | 13:14 |
r3boot | You could try to bootstrap devuan on risc-v using debian as a base, while following the LFS methodology of getting it ported | 13:16 |
Glats | its possible to avoid ssh agent and import the key every time you open a terminal? | 17:33 |
Glats | in bash | 17:33 |
djph | Glats: what do you mean? like it asks you _every_ time you ssh somewhere? | 18:10 |
Glats | djph: look i found this https://github.com/wwalker/ssh-find-agent | 18:12 |
Glats | for my purpose | 18:13 |
Glats | but i dont wanna import that shell | 18:13 |
Glats | i wanna something simple | 18:13 |
djph | I still don't understand what you're asking | 18:13 |
Glats | ok lemme exaplain | 18:14 |
Glats | when you ran eval $(ssh-agent -s) | 18:14 |
djph | I don't use ssh-agent ... | 18:14 |
Glats | oh | 18:14 |
Glats | ok | 18:14 |
Glats | what do you use? | 18:14 |
djph | for the hosts that don't use my main key, have them defined in .ssh/config | 18:15 |
djph | type the password every time | 18:15 |
Glats | yeah | 18:15 |
Glats | i dont wanna do that | 18:16 |
fsmithred | I see Agent pid ### | 18:16 |
fsmithred | you can make a key with no password | 18:16 |
Glats | look http://blog.joncairns.com/2013/12/understanding-ssh-agent-and-ssh-add/ | 18:17 |
Glats | my idea is to use the same agent across terminals | 18:17 |
fsmithred | and you want to do that without running ssh-add? | 18:20 |
Glats | no | 18:20 |
Glats | you cant | 18:20 |
fsmithred | Glats, do you have the same problem as the author? I don't. | 18:20 |
fsmithred | I run ssh-add once, and I can use any terminal until I log out of the desktop. | 18:21 |
Glats | i think is not optimized | 18:22 |
Glats | you have to run ssh-agent then run ssh-add | 18:22 |
fsmithred | oh, ssh-agent starts with the desktop | 18:22 |
Glats | oh | 18:23 |
Glats | ok | 18:23 |
fsmithred | I don't actually understand the author's problem | 18:23 |
Glats | he put in .bashrc | 18:23 |
Glats | so every time he open a terminal | 18:23 |
fsmithred | he says, "the bottom line is that we need to keep track of our agent's file socket to be able to be able to remember the passphrases for our keys across multiple shell sessions." | 18:23 |
fsmithred | and I have no idea what he's talking about | 18:23 |
Glats | yeah. but if you dont have a DE to handle your startup applications | 18:24 |
Glats | you put ssh-agent into .bashrc | 18:24 |
fsmithred | oh, ok | 18:24 |
Glats | so every time you open a terminal the ssh-agent will be executed | 18:24 |
Glats | ok | 18:24 |
fsmithred | I just put -i on the command line in those cases | 18:25 |
Glats | so you put the agent into the startup application | 18:25 |
Glats | alongside ssh right? | 18:25 |
Glats | like | 18:25 |
fsmithred | yes, ssh -i .ssh/id.whatever user@host | 18:26 |
Glats | ssh -i keyring user@ip | 18:26 |
Glats | yeah | 18:26 |
Glats | ok | 18:26 |
Glats | yeah. thats another way | 18:26 |
Glats | fsmithred: but if you use git? | 18:29 |
Glats | you cant pass -i option | 18:29 |
Glats | so thats why i need the ssh-agent | 18:29 |
Glats | (git through ssh) | 18:29 |
fsmithred | there must be some way to put that option into git | 18:30 |
fsmithred | in a config file. But that's a guess. | 18:30 |
fsmithred | so yeah, I understand the problem now | 18:30 |
Glats | no. it doesnt | 18:30 |
Glats | actually they tell you to use the agent hahaha | 18:31 |
fsmithred | I noticed git's also unhappy if I'm connected by ssh to the machine that is communicating with gitlab. It won't let me push. | 18:31 |
Leander | what about if you use your .ssh/config for the git-specific options? | 18:32 |
Glats | look | 18:32 |
Glats | https://unix.stackexchange.com/a/132117 | 18:32 |
Glats | now i get it | 18:33 |
Glats | .bashrc *always* load the environment when you open a new terminal | 18:33 |
Leander | I don't have the example at hand, but I have two different github accounts, and in order to choose one or the other, I use machine names like github-account1 and github-account2 (in the .git/config file) which correspond to github-account1 and github-account2 entries in .ssh/config | 18:38 |
Glats | ok | 18:38 |
Glats | could be a nice aproach | 18:38 |
Glats | https://build-me-the-docs-please.readthedocs.io/en/latest/Using_Git/SetUpSSHForGit.html | 18:40 |
DonkeyHotei | SSH_AUTH_SOCK= ssh foo@bar | 18:41 |
Glats | but my next aproach is to take all my keys saved it in ~/.ssh/ and add it in the agent | 18:43 |
Glats | with a loop or something | 18:43 |
Glats | and with ssh-add -l you can get every key loaded and you cant avoid to load twice the samekey | 18:44 |
Glats | s/samekey/same key/ | 18:44 |
Glats | https://gist.github.com/glats/c0d6107218b6af9c7252bf54f939a322 | 18:54 |
Glats | finally :P | 18:54 |
furrywolf | blarg, this whole menu thing is pissing me off. I spent three hours reading the discussion on it, and it's all the exact same arguments that got us systemd. | 18:59 |
furrywolf | "only 20% of people still use it, and they should get with the program" is _not_ how open-source decisions should be made. | 19:00 |
iovec | meanwhile https://seclists.org/oss-sec/2019/q1/140 | 19:00 |
furrywolf | nor is "another major distro has switched to it, so we should too" | 19:00 |
iovec | aka you never listened to us when we said PID 1 should be simple | 19:00 |
furrywolf | nor is "everyone refusing to switch to something newer is obviously a luddite moron stuck in their ways and refusing to accept any kind of change" | 19:01 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!