wont not use a svn host then, there are plenty free ones and the source is available at the same time.
you can give invites to a torrent site , but , as for links .....that won't fly here
Not trying to compete with Trinux or anything, but I also have plans to port my OS kernel to the Espresso in vWii mode. I figure it's a good way to combine the two programming projects I'm currently involved with. Right now, DarkSide only supports x86 PCs, but I've designed it portably so it shouldn't be too hard to add PowerPC support as well.
The disk images are corrupted for me... Does the normal wiilinux install booted with the launcher work?
Had this laying around, too, might be of some use, might even be the final product i worked on
https://www.dropbox.com/s/s279kdjkacykuoj/trinux-0.5a.7z
Those LAN adapters use an ASIX chipset. There are 2 different chips that are used. One is having an A extension on it's chipnumber.
They enumerate as different devices. Most generic ASIX drivers seem to be able to work with both chipsets. I asked ASIX for their program to change the usb PID and VID, but they refused to give it as I am no huge integrator (buyer) of their chips.
I don't have a Wiiu, but I know that the wii only works with the older chipset using the chip without that A extension.
However, if you are able to ping your router from within linux, you should be able to ping to the outside as well (it means it has a working driver installed.)
Routers don't block outgoing traffic on their own. They use rules for that and those can be adjusted in the router configuration page.
Some things that can go wrong with external ethernet access are the dns server settings. If those are incorrect in your linux setup, you will only be able to ping ip's like
google's 8.8.8.8 dns server. Another important thing to use the apt-get command is the file that contains the location where apt-get is looking for packages.
Ya I forgot to mention, I tried to use apt-get update to update all my repo's but that didn't work either .
As for the router configuration, I'll see if I can get it working by fooling around with that, but seeing as I hooked it directly into my cable modem, and it still didn't work, i'm not very hopeful that this will resolve my issue.
deb http://archive.debian.org/debian/ lenny main non-free contrib
deb-src http://archive.debian.org/debian/ lenny main non-free contrib
# Volatile:
deb http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free
deb-src http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free
# Backports:
deb http://archive.debian.org/debian-backports lenny-backports main contrib non-free
# Previously announced security updates:
deb http://archive.debian.org/debian-security lenny/updates main
Ok thx . I will give this a goThe repos are dead, you need to use the archive. This goes in /etc/apt/sources.list
Code:deb http://archive.debian.org/debian/ lenny main non-free contrib deb-src http://archive.debian.org/debian/ lenny main non-free contrib # Volatile: deb http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free deb-src http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free # Backports: deb http://archive.debian.org/debian-backports lenny-backports main contrib non-free # Previously announced security updates: deb http://archive.debian.org/debian-security lenny/updates main
Ok thx . I will give this a go
The repos are dead, you need to use the archive. This goes in /etc/apt/sources.list
Code:deb http://archive.debian.org/debian/ lenny main non-free contrib deb-src http://archive.debian.org/debian/ lenny main non-free contrib # Volatile: deb http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free deb-src http://archive.debian.org/debian-volatile lenny/volatile main contrib non-free # Backports: deb http://archive.debian.org/debian-backports lenny-backports main contrib non-free # Previously announced security updates: deb http://archive.debian.org/debian-security lenny/updates main
you also have to bring the interface 'up', if I recall correctly. once that's done you have to run dhclient to obtain an IP via DHCP.
try,
# ifconfig eth0 up
# ifconfig <--- do you now see eth0 listed?
# dhclient eth0
this will bring up the interface and run the dhcp client to configure your NIC.
if it can't find eth0, try # dmesg | grep ASIX or # dmesg | grep eth