Commit Graph

10 Commits

Author SHA1 Message Date
e4ece4494f Updated version 2015-05-31 16:53:56 +02:00
bf9a685cf8 document the new shortcuts 2015-05-31 13:33:19 +02:00
f725556ecd create the symlinks in post-build.sh. 2015-05-31 13:30:41 +02:00
9a6c527d20 update documentation 2015-05-31 13:08:22 +02:00
231350a726 all mounts with -n ; document tab + escape on N900 keyboard 2015-05-31 13:00:18 +02:00
add2f9b166 disable autostart questions. autostart telnetd. shortcuts for /rescueOS/ scripts. 2015-05-31 12:43:04 +02:00
Daniel Gnoutcheff
9f262fde9d Sync udhcpc script from RescueOS v1.1
When using the script from this repo, 'udhcpc -i wlan0' would error out
with this:

> Recreating /etc/resolv.conf
> /usr/share/udhcpc/default.script: line 37: /etc/resolv.conf-8352: Read-only file system
>  Adding DNS server 192.168.7.1
> /usr/share/udhcpc/default.script: line 41: /etc/resolv.conf-8352: Read-only file system
> mv: can't rename '/etc/resolv.conf-8352': No such file or directory
2015-04-02 21:16:33 -04:00
Daniel Gnoutcheff
8f1eabb7c9 Update wl1251 firmware loading path
The wl1251 driver in upstream linux kernels expects its firmware files
to live at
  ti-connectivity/wl1251-fw.bin
  ti-connectivity/wl1251-nvs.bin
and the linux-firmware package uses the same names for these files.
However, our current (older) kernel still expects them to be named
  wl1251-fw.bin
  wl1251-nvs.bin
and so firmware loading would fail.

RescueOS v1.1 included these files under the older filenames, but we'd
like to use the official (upstream) names.  Patch our kernel to match.

Also remove the unnecessary (and now erroneous) firmware check from
setup-wpa-wifi.sh.
2015-04-02 21:16:33 -04:00
Daniel Gnoutcheff
5ef586619b Add mountpoint directories
Oops, git ignores empty directories.  Add '.empty' files to force git to
create the desired moutpoint directories in our filesystem overlay.
Fortunately, buildroot helpfully discards '.empty' files.
2015-04-02 21:16:32 -04:00
Daniel Gnoutcheff
be8a7817dd Create fs-overlay, post-build
Setup buildroot filesystem overlay and move our custom scripts/configs
into it.  Setup a post-build script and have it delete files generated
by buildroot that aren't in RescueOS v1.1.

This gets us closer to a buildroot configuration that will automatically
generate RescueOS images.  For now, we're using RescueOS v1.1 as a
reference.
2015-04-02 21:16:02 -04:00