20101110-0037 Build broken
-
Hi,
Here is my today little story…
I wanted to try the IPv6 branch and it require that you upgrade to a later version that I had, so I tried the online update, at first the update on my 512 MB CF was unsuccessful (not enough free space), then I hacked into the system and deleted pearl5 to make room and launched the update from ssh using a url and it went well, rebooted and everything is working as it should, the problem is in the ssh/console interface, nothing is working but the shell option 8, the DevShell wasn't launching properly to gitsync. So I tough that my pearl5 hack broke something up, so I dig up a 2 Gb CF card and download the full image and write it from scratch and booted it on my Soekris net5501, it boot normally, but then I want to assign interface and change ip address to restore my handy backup, but the option to assign interface doesn't work, it seem it takes the command (changes line in the console), but the screen stay still, then I hit CTRL+C and I'm back to the menu, same thing goes for every option that is not 8 for the Shell.
So I putted back my 512 MB and booted the old splice (that I duplicated before upgrading) and I'll wait until this is resolved...
MageMinds, the story teller...
-
Sounds like you hit an image that accidentally had output buffering turned on with PHP due to another component that was activated. That should be fixed in subsequent snapshots.
-
By the way, currently gitsync will only work on regular installs, not nanobsd images because git won't install (don't remember the reason).
I have at least a couple ideas for how to make it possible to gitsync on nanobsd and I'll implement at least one of them sometime. One involves just packaging up the files needed to manually install git and the other involves using a different computer to run gitsync and automatically transfer the updated files to the system over ssh.
-
@Efonne:
By the way, currently gitsync will only work on regular installs, not nanobsd images because git won't install (don't remember the reason).
I think it was because of the size of /var, and/or /tmp, it couldn't populate all of the files/directories it wanted there to get the package installed.