I’m playing with a couple of routers and comparing proprietary to open source on the same hardware. I miss my .bashrc functions and aliases… and compgen, tree, manpages, detailed help, etc; the little things that get annoying when they are missing.

I was thinking about trying to mount the embedded system on my workstation (while it is running?), but I’m not clear how this would work in practice with permissions, users, groups, root, etc. I’m curious how others do this kind of development/screwing around, or if this is a crazy idea.

  • bus_factor@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    If you have ssh/SCP you can use sshfs to mount the remote host as a fuse filesystem. That would let you edit files on your workstation, but more or less all other commands would still need to happen on the remote system.

  • pixelscript@lemmy.ml
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    I am not quite yet st the level where I have a ton of user scripts I’d be lost without, so SSHing into a box is hardly a speed bump for me.

  • Ramin Honary@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 year ago

    This is probably not a solution you would want, but I will mention it anyway…

    Emacs has a built-in app called “TRAMP mode”, what it does is it works as back-end for all of Emacs’s own built-in text editing and file browsing commands, then it uses ordinary SSH and POSIX shell commands on a remote host as the primitive APIs for this back-end. You could say it uses SSH and a POSIX shell as a RPC mechanism.

    What this means is you can use the ordinary Emacs editor with the entirety of your usual Emacs configuration, but all filesystem changes (including editing files, directories, and running shell processes) occur on the remote host via SSH. In order to activate it, you just use Emacs’s special TRAMP URL scheme as the file path you want to edit, and it works seamlessly, (especially if you setup your SSH agent so you don’t need a password). An example of such a URL would be /ssh:user@remote-host:/etc/hosts.

    • NanoooK@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’ve discovered this not long ago and it makes my work way easier. Also, using the dired mode on the remote is useful.

  • toastal@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    You can use something like Nix + home-manager & take your environment with you.