How configure alternative location for uuid file? about wiki HOT 10 OPEN

So you are already installing the feed client, that needs to write to files.
At that point the uuid is also generated so i'm not sure how your'e running into an issue.

The feed client can accept the command line option --uuid-file /etc/default/adsbx-uuid
You could add that to the NET_OPTIONS in /etc/default/adsbexchange

I'll have to fix up the mlat-client so it can accept a command line option for that.

If the uuid is regenerated on boot, this isn't really the aim of the exercise and i'd ask that you don't do that.

from wiki.

Added an option --uuid-file to the adsbexchange fork of mlat-client as well.
Also added an environment variable to the adsbexchange feed scripts.

So no need to fudge with the NET_OPTIONS as described in myh last post.
You'd just add a new line:
UUID_FILE="--uuid-file /etc/default/adsbx-uuid"

from wiki.

Just to stress this again, if you're gonna regenerate the uuid every boot, it would be much preferred not to send an UUID at all.

And in case you use the stats script, you can add to / create /etc/default/adsbexchange-stats

UUID_FILE="/etc/default/adsbx-uuid"

Note that it's without the --uuid-file in this case.

Could you elaborate a bit what your system does?

from wiki.

OK, thanks I will try that.

So you are already installing the feed client, that needs to write to files.
At that point the uuid is also generated so i'm not sure how your'e running into an issue.

/boot is on a different partition from the rest of the file system, and in our setup it is never writeable from a running system. I don't think trying to write to the boot partition is very polite, never had a feed client attempt that before.

Once installed into /etc/defaults, the config files then become read-only so the uuid will not change unless manually updated by setting the ext4 part of the file system temporarily write-enabled, so there is no risk of changing uuids.

from wiki.

Writing to /boot is for people who only use Windows.

Raspbian ssh enable uses boot.
Raspbian wpa_supplicant.conf uses boot.
PiAware config is on /boot as well.

This is not a new thing.

Read only is an new thing for 99% of Pi ADS-B feeders.

from wiki.

The /boot thing wasn't my design decision, it was done for the image.

I'll change the feed client install scripts to use a different location.
If you give me a day, you'll then be able to use the install scripts as they are.

from wiki.

Raspbian ssh enable uses boot. Raspbian wpa_supplicant.conf uses boot. PiAware config is on /boot as well.

Not in this way. Your examples use the principle that a user puts a file on /boot when setting up the system, and then that info is read from or copied from /boot and stored in the normal file structure when the system starts. I have no problem with this and it would work with our image as well. The difference is that now you are trying to write to /boot from within an already running system, which is completely different.

I have never had a problem with Piaware trying to write to /boot.

A more compatible way would be during install check /boot if the file is there, then copy it to /defaults, otherwise create a new in /defaults. That would solve both the user cases.

from wiki.

I'll change the feed client install scripts to use a different location.
If you give me a day, you'll then be able to use the install scripts as they are.

Sounds great. See my idea above that would keep the current possibility as well.

from wiki.

I'm not even gonna use /etc/defaults as we already have /etc/defaults/adsbexchange there.
And yes ... i'll migrate the old file and just check for both paths in all the programs using it, not an issue.

from wiki.

/usr/local/share/adsbexchange/adsbx-uuid

Hope that's alright with you.

Should be all changed over, including the stats script.

from wiki.