klib.so
-
Posts
2 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by klib.so
-
-
Ok so did a bit of testing on a local funtoo container and it seems to just work if the module has been loaded in the bare metal OS.
emerge wireguard-tools
nano /etc/wireguard/wg0.conf
wg-quick up wg0
Works perfectly and didn't seem to mess with the parent OS who has an interface with the same name.
So do you think we could have this added to the kernels? It's as simple as: emerge wireguard; modprobe wireguard and I suppose add to /etc/conf.d/modules for reboots.
-
Just wanted to start a conversation about the possibility of having individual wireguard interfaces in the containers. Obviously we're all sharing the same couple of running kernels, but a cursory search would seem to suggest it's possible. I think there would have to be some permissions/scoping kind of setup, but I'm not seeing why it would be too difficult beyond that. Also from an admittedly limited understanding of the internals I can't see why it would add significant load to the system either, but I'm open to correction haha
Thoughts?
-
That's the way I was thinking too. Something similar to the old news bulletins. Also a great idea about making them publicly available. Would have the added benefit of letting aspiring contributors see where they might be useful by seeing what the less maintained and less used packages are.
-
I'm not against the idea at all, but these things always start out meaning well using nice terms like metrics and having extremely valuable uses; like delivering an all round better experience, or freeing up devs for better features and so on. However, with the current feeling in the world today this is going to be a much bigger deal than you might originally think, especially considering the type of individual who ends up using a distro such as this—meaning smart not shady. To my mind it absolutely has to be opt-in, and extremely well advertised to the users. That way you send a very clear message of intent, and avoid the situation where user-x suddenly finds out one day, that his favourite distro—the last place he thought was sacred—started spying on him six months ago without his consent. I think in that situation all those extra stats that you gained would walk away with a bad taste in their mouth. After all opt-io is a metric in and of itself.
It should also be said that that information is far from being anonymous. It is always the same idea: the information sent to microsoft is anonymised, but completely trivial to fingerprint in a heartbeat. One bug report or forum post including emerge --info and I have little doubt any one of us who loves to configure so much would be uided.
I'm not intentionally trolling the idea, I'm highly aware of how important statistics are, but yes I realise I am trolling somewhat just the same :P So what's next? Why not go with the flow and move to systemd? ...and now that I think of it, binary packages would make things a little smoother... :D
[SOLVED] System update problem
in General Discussion
Posted
Are you a kde user?
Or what is the output of
For me, this is a dependency conflict between nvidia-drivers and kinfocenter.
Disabling opencl use flag for nvidia-drivers would likely work, but maybe, like me, you don't really want to do that.
Otherwise, for the time being, need to remove kinfocenter (or whatever package wants clinfo) as it is a static dependency. That could be non-trivial if it is pulled in as part of a meta package.