- Dockstar openwrt install#
- Dockstar openwrt password#
- Dockstar openwrt plus#
- Dockstar openwrt mac#
Install ddclient if you are going to want to access the machine over the internet with a DHCP address. Dockstar openwrt password#
Change ssh login password for security (optional: install ssh public key in ~/.ssh/authorized_keys for more security ). Install openntpd (automatic time sync client) and start it before the password change below, to avoid lockout due to password aging (30+ years will seem to have passed between the default date in 1970 and now). The easiest way is to set up a network time protocol client. The Dockstar does not have a hardware clock, so it will always be off at start up unless you take action to fix that. => Pre-3.5 database format detected - upgrading. !!!!!! SERIOUSLY! Run pacman-db-upgrade or PACMAN WILL NOT WORK! ~]# pacman-db-upgrade > You will need to run `pacman-db-upgrade` as root. 
> The pacman database format has changed as of pacman 3.5.0. :: Do you want to cancel the current operation :: The following packages should be upgraded first :
Dockstar openwrt mac#
make the system survive a power outage -> install ( what?) to NAND? or simply configure a static IP locked to MAC address on router and reboot from pogo OS if stuck?įrom default installation of the owfs package on /]# find. generate temploggerd templates (reclaim from NSLU2 installation?), or do I want to use another prettier graphing toolset like (A: stay with temploggerd for now). determine what web server to use – thttpd? something light weight but secure! (A: Cherokee is available, installed easily and works well with little load on server. figure out temploggerd operation – can it be verified without web server access at start? (A: Yes, but web server is now set up). does my application require FUSE and the sensor array to be mounted as a file system? (A: YES, it is handy and by using owserver as a front end it does not cause a burden.) if not, skip owfs itself, otherwise script creation of /tmp/1wire and do related stuff to make the array available (A: will need to script this, it will be part of the rc.d script). under PlugApps based on prior work with NSLU2 (these were in /opt/etc/owfs there) figure out the option/config files for owserver, etc. Currently have verified that owserver and owhttpd can be started with the applicable options from command line and those basically work. No similar files are created for the core owfs stuff. Dockstar openwrt plus#
The owfs package now created for PlugApps includes the owfs core application/commands PLUS temploggerd but only creates the related option and template files for temploggerd. Config files and similar stuff appear to be are normally set/stored in /etc/_. The daemons exist as bash scripts in the directory /etc/rc.d. Daemons are initiated based on an array entered at the bottom of that file.
The file /etc/rc.conf is where a lot of the main settings are made. PlugApps is based on Arch Linux, follows their start-up sequence – which is loosely based on BSD’s.
Hopefully this will be completed and cleaned up shortly. Ignore for now, unless you like just reading random technical thoughts from someone puzzling their way through something they don’t know a lot about… I’ve started a true step-by-step description at the end below as I make my way through this for a second time. This post is currently just a set of notes as I blaze the trail to get this working.
0 kommentar(er)
