I tried the “sudo snap install frr”. When I typed “which frr”, I got nothing back. When I type “sudo snap refresh --list”, it tells me that all snaps are up to date. What am I doing wrong or missing?
Mike Mazarick
PS - I am working off of a newly installed Ubuntu 18.04 on an unmanaged VPS.
Please can you post the output of snap version on that machine?
My guess is the VPS is not a vanilla Ubuntu 18.04 but has been modified, perhaps with a different kernel.
In my haste, I typed “service snapd start”. The system asked for my passwd.
After thinking about it, I typed :“sudo service snapd start” and it asked for my passwd. but didn’t say ==== AUTHENTICATION COMPLETE ===== (like it did when I started the service with just my user account.
When I typed “which frr” I didn’t get any response.
When all else fails, read the documentation. I am reading it. There is a very interesting note: The VPS has a black background and a white foreground but the /snap/bin directory has a black foreground and background. When I type “ls -l /snap/bin/” there is a list of links with frr.* going back to /usr/bin/snap. There is no frr binary.
When I type “snap version” (inside putty so I can change the background/foreground colors) I get
snap 2.42.5
snapd 2.42.5
series 16
ubuntu 18.04
kernel 4.15.0-74
When I type “snap list”, I get:
Name Version Rev Tracking Publisher
core 16-2.42.5 8268 stable
(I have figured out how to “cut 'n paste” inside putty, which I hadn’t figured out how to do until just now. This will allow me to run any command inside my VPS and paste the results back to my browser)
When I typed the command you suggested in my VPS, I get back:
channels:
stable: 6.0.2 2019-01-09 (72) 17MB -
candidate: 6.0.2 2019-01-09 (72) 17MB -
beta: 7.2 2019-10-20 (82) 14MB -
edge: 7.2 2019-10-20 (82) 14MB -
installed: 6.0.2 (72) 17MB -
If it is easy to do, I would prefer the beta/edge version. A macro wiped out all of the previous versions of frr, so I’d like a more recent version.
This is the latest “cut 'n paste” from Putty:
mazarick@virtusecure:~$ cd /snap
mazarick@virtusecure:/snap$ ls
bin core frr README
mazarick@virtusecure:/snap$ ls -l
total 16
drwxr-xr-x 2 root root 4096 Jan 17 18:31 bin
drwxr-xr-x 3 root root 4096 Jan 17 18:31 core
drwxr-xr-x 3 root root 4096 Jan 17 18:31 frr
-r–r--r-- 1 root root 548 Dec 16 09:25 README
mazarick@virtusecure:/snap$ more README
This directory presents installed snap packages.
It has the following structure:
/snap/bin - Symlinks to snap applications.
/snap// - Mountpoint for snap content.
/snap//current - Symlink to current revision, if enabled.
DISK SPACE USAGE
The disk space consumed by the content under this directory is
minimal as the real snap content never leaves the .snap file.
Snaps are mounted rather than unpacked.
This means that the snap does run on your system. What was the original problem? What happens when you type frr.<tab> (hit actual tab instead of <tab>)
What was the original problem? The original problem was:
Not have “frr” appear on my system followed by fonts where the backgroud and foreground were the same color.
My VPS has a black background and the fonts are normally colored white, so having founts that were the same color made them invisible to me. The /mnt directory is colored the same way.
The files frr.* are essentially correct, but it is not normal
practice to put ‘.’ in the filename.
This is shown in the documentation with the example
“vlc”. (Getting Started, Commands and Aliases).
I have stated that I would strongly prefer to use a
beta/edge version.
When I type this, I get that:
mazarick@virtusecure:/$ sudo snap refresh --channel=beta frr
[sudo] password for mazarick:
frr (beta) 7.2.1 from Martin Winter (osr) refreshed
mazarick@virtusecure:/$ which frr
mazarick@virtusecure:/$
Perhaps the documentation does not make this sufficiently clear, but the apps are generally named <snapname>.<command>, eg. snap foo with app bar will get a foo.bar command. For simplicity if the app is named like the snap, then it gets a simplified command equal to the app name, eg. snap frob with app frob gets a simple alias frob, just like it is in the case of vlc.
For frr, the output of snap info lists the commands this snap provides. As you’ve already noticed, there’s no frr command, but rather a bunch of commands for specific routing daemons.