• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle

  • BB_C@programming.devtoLinux@lemmy.mlLadybird announcement
    link
    fedilink
    arrow-up
    34
    arrow-down
    2
    ·
    1 day ago

    A reminder that the Servo project has resumed active development since the start of 2023, and is making good progress every month.

    If you’re looking for a serious in-progress effort to create a new open, safe, performant, independent, and fully-featured web engine, that’s the one you should be keeping an eye on.

    It won’t be easy trying to catch up to continuously evolving and changing web standards, but that’s the only effort with a chance.



  • start a process within a specific veth

    That sentence doesn’t make any sense.

    Processes run in network namespaces (netns), and that’s exactly what ip netns exec does.

    A newly created netns via ip netns add has no network connectivity at all. Even (private) localhost is down and you have to run ip link set lo up to bring it up.

    You use veth pairs to connect a virtual device in a network namespace, with a virtual device in the default namespace (or another namespace with internet connectivity).

    You route the VPN server address via the netns veth device and nothing else. Then you run wireguard/OpenVPN inside netns.

    Avoid using systemd since it runs in the default netns by default, even if called from a process running in another netns.

    The way I do it is:

    1. A script for all the network setup:
    ns_con AA
    
    1. A script to run a process in a netns (basically a wrapper around ip netns exec):
    ns_run AA <cmd>
    
    1. Run a termnal app using 2.
    2. Run a tmux session on a separate socket inside terminal app. e.g.
    export DISPLAY=:0 # for X11
    export XDG_RUNTIME_DIR=/run/user/1000 # to connect to already running pipewire...
    # double check this is running in AA ns
    tmux -f -f <alternative_config_file_if_needed> -L NS_AA
    

    I have this in my tmux config:

    set-option -g status-left "[#{b:socket_path}:#I] "
    

    So I always know which socket a tmux session is running on. You can include network info there if you’re still not confident in your setup.

    Now, I can detach that tmux session. Reattaching with tmux -L NS_AA attach from anywhere will give me the session still running in AA.



  • Meh, everyone scaring you into thinking you don’t own your own mind.

    Assuming your boss is not the dangerous kind (beyond legal threats), and if the goal is to make it FOSS, then do it using an alias first. Do it differently. Use components/libs/algos from other people at first, even if they are not perfect. Make those parts easily pluggable/replaceable which would be good design anyway. The code then wouldn’t be wholly yours, not even your alias self.

    You can join the project later with your real identity as an interested domain expert (maybe a bit after not working for the same boss). Start contributing. Become a maintainer. And maybe take over after a while. You can start replacing non-optimal components/libs/algos with better ones piecemeal.

    Oh, and if Rust wasn’t the choice of implementation, use it this time.