owfs, 1-wire file system and related apps

[kmihelich]

You should probably put them under /etc. nslu2 uses /opt for everything since it's a hack, this is the real thing now.

[pepedog]

I think you meant /opt/PWRs/etc but either way it is ok.

Edit: iPad auto-correct, it should have read /opt/owfs/etc, but probably kmihelich's build will make it somewhere in /etc?

[kmihelich]

Found the source for temploggerd. Since it seems to be just an extension to owfs, I think I'll work that into the owfs PKGBUILD so it's all there together under one install.

[donv]

Great, let me know when that's added and I'll reload the package to test it.
$this->bbcode_second_pass_quote('kmihelich', 'F')ound the source for temploggerd. Since it seems to be just an extension to owfs, I think I'll work that into the owfs PKGBUILD so it's all there together under one install.

[kmihelich]

pacman -Syu

You should see the new owfs package come in. temploggerd is now available, I assume you know what to do with it because I have no idea

[donv]

Thanks, I can confirm it is there and the command is seen on my box. I hope to work with this tomorrow to get it all going for real. Will let you know how it turns out.

$this->bbcode_second_pass_quote('kmihelich', 'p')acman -Syu

You should see the new owfs package come in. temploggerd is now available, I assume you know what to do with it because I have no idea

[donv]

OK, so tomorrow was a long time coming , but I'm back working on this project. I've established that several of the temploggerd config/option/template files were created through the package installation, but that no owfs, etc. related files were. In checking with the owfs author, this appears to be the default, and some other distributions augment this by creating these other files (eg: my experience with uNSLUNg linux having done so). Noticed also that no daemon files (rc.d scripts?) were created for either owfs, etc. or temploggerd. I am working on defining defaults for my installation and wonder whether these would become part of the Arch Linux ARM packages.

BTW, I am not familiar with Arch/Arch Linux ARM daemon files (bash syntax), but on the surface they seem very consistent/generic. I looked at the Arch wiki page (and referenced BSD) on them which indicated they were "easy", but I guess that is the case only if you know bash. I can figure out much of it, but not all. Is it as simple as using the generic one and changing simply the DAEMON= and ARGS= lines and above to create a new one? What do the lines starting with a dot (.) do?

$this->bbcode_second_pass_quote('donv', 'T')hanks, I can confirm it is there and the command is seen on my box. I hope to work with this tomorrow to get it all going for real. Will let you know how it turns out.

[pepedog]

If you are prepared to have a go-
in the rc.d script (which you will call owfs) it gets args from a file in the /etc/conf.d (which you will call owfs too)
Just look at other startup scripts in /etc/rc.d/ to get an idea.
Then create your conf files (what would be default, not just your installation)

Now go to https://github.com/Arch Linux ARM/Arch Linux ARM and ask, letting them have the files (conf and script), say where they install to, and it will get packaged.

A file stating with a period is just a hidden file

[kmihelich]

When you see lines that are like..
$this->bbcode_second_pass_code('', '. /etc/conf.d/somefile')
what that dot represents is a shortcut for the bash command 'source'. Sourcing another bash script brings all its variables and functions into the current bash script/environment. This is done in the context of rc.d scripts for bringing in user-defined settings from a file in /etc/conf.d, which is the "proper" way to do things. In theory, rc.d scripts shouldn't be modified by the users to achieve the results they want when starting a daemon. The rc.d script should source user configured variables from an /etc/conf.d script, do sanity checking to be sure the variables are OK, then apply those variables in the rc.d script.

For example.. in an /etc/rc.conf/myprogram:
$this->bbcode_second_pass_code('', 'PORT=3945')

Then, in an /etc/rc.d/myprogram:
$this->bbcode_second_pass_code('', '. /etc/conf.d/myprogram
run_myprogram --port ${PORT}')

That is a very very limited and basic example, but should give you the idea.

[donv]

Thanks, I will give it a go. The github page seems to have a lot of possibilities - where do I file/ask, under "Pull Requests"?