unfortunately I have no control over NAT. company network, meh!plugwash wrote:Do you control the nat?
If so then just forward a port and use ssh or whatever.
If not then what I personally do is setup a tunnel using vtund. Of course this is only practical if you have somewhere you can use as the other end of the endpoint.
hadi, I would recommend reading this link on the difference between armhf and armel:hadi wrote:is there anyway to use armel packages?
I don't exactly know what is the difference between armhf and armel.
mpthompson wrote:BTW, I also have a Mele A1000 on order to see if I can get a basic port of Debian armhf running on it.
It runs the AllWinner A10 (Cortext A8) SOC which seems to be the hottest chip coming out of China these days. Being half the cost of the iMX53, a 1 GHz processor, a decent 512M RAM and a real SATA interface, I'm hoping these can be converted into inexpensive build machines if there is enough interest in pushing through a full Debian armhf port for the Raspberry Pi. A number of these along with a few iMX53 systems for heavy lifting could probably make a nice build cluster for Debian ARM.
I've enabled your wiki account as an editor. Once you log into the wiki you should see you can now edit the FAQ and most every other page with a few exceptions.Nexy wrote:Thanks, I've created a "Start Here!" thread here:
http://www.raspberrypi.org/phpBB3/viewt ... =66&t=9951
Any suggestions, additions and edits you'd like, let me know and I'll change it. Once it's ok, I'll ask ukscone to sticky it.
I've also registered for the wiki (WillDerrick). To update it (specifically the FAQ page) is it better to request edit permissions or PM someone who already has permission?
Michael, very nice. Perhaps we should create a "RaspbianHistory" page on the wiki and add this as contents to the page. It's interesting to see in your graph how fast the packages all seemed to build. Didn't feel that fast at the time.mdewey wrote:I have been amusing myself while I am still RPi-less by re-reading this thread and making a Raspbian timeline.
I have an unmet training need for wiki-editing but am willing to give it a go.mpthompson wrote:Michael, very nice. Perhaps we should create a "RaspbianHistory" page on the wiki and add this as contents to the page. It's interesting to see in your graph how fast the packages all seemed to build. Didn't feel that fast at the time.mdewey wrote:I have been amusing myself while I am still RPi-less by re-reading this thread and making a Raspbian timeline.
Create an account on the Wiki and let me know your username and I'll enable you as an editor.mdewey wrote:I have an unmet training need for wiki-editing but am willing to give it a go.
[email protected]:~$ sudo apt-cache search libssln0thing wrote:I tired install aircrack-ng suite but it seem like I can't run it and it gave me the following output:
aircrack-ng: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
Anyone know how to fix it?
Try having a read through this thread: http://www.raspberrypi.org/phpBB3/viewt ... 66&t=10304. There are even some pre-configured image files you can downloadjose1711 wrote:i am really looking forward for xbmc enabled with armhf. openelec is nice, but it's very specialized distro - i would really like to have one sd card with more universal installation.
I'm sorry, I don't quite follow what your question is. Debootstrap is a Debian tool that works within Raspbian that can be used to create an initial root file system. However, I don't understand the part about your own compiler configuration. Can you give me an example of what your are trying to do?m][sko wrote:How can I make my own base rootfs with my own compiler configuration?
You wrote here that you compile every single package from start.
Users browsing this forum: rpdom and 28 guests