Sorry for the lack of promptness, but they didn't invite me back to work on the server till this afternoon. You're right. In the BIOS, there was a ZIP drive (huh?) as Primary Master. The hard drive is the SATA master. I disabled the ZIP drive in BIOS and now the hard drive is sda like it's supposed to be.What is the HW? Output of dmesg, lsmod and lspci should help here. Perhaps the IDE/SATA bus is misconfigured at the BIOS or you have a CDROM drive as master in the first channel?Something _must_ be appearing as sda, what is it? I saved off the outputs of lsmod, lspci, dmesg, and /var/log/messages if you're still interested, but I did get eth1 working. It wasn't being recognized according to lspci, so I popped open the case and moved it to another slot. Eth1 then initialized on boot, but dummy0 kept getting assigned 172.18.0.1. So, here's what I did: ifdown dummy0 ifconfig eth1 172.18.0.1 netmask 255.255.240.0 service dhcpd restart The two test XOs were able to pull IPs from the XS after that. Like last Friday, I didn't have time to fool around with it anymore or test registration cause they were closing up the school. On my way out, I discovered there's another issue that I'm going to have to find some way to deal with. The school IT personnel is dead set on finding some way to integrate all the wireless access points and the XS/XO into their existing network. Why? I wish I knew. Anyway, they're on their own IP scheme and they're pitching a fit that the XS isn't in line with that. 172.18 stuff is all over the XS and I can't even fathom changing it. I have a real problem with their mentality. First of all, the existing school infrastructure requires an outside connection, even for basic LAN functionality. As in, if the connection to the (Windows, naturally) server room downtown goes down, school staff can't even print. That happens on an appallingly frequent basis. Unless I hear specific, concrete reasons exactly why the XS/XO stuff needs to be integrated into the existing network, I'm going to assume there aren't any and try solidify specific, compelling reasons to not do that. My vision, and this is obviously not shared by the school system IT staff (all Windows guys who hate Linux, but don't get me started), is that the XS/XO LANs will be fully independent, self contained ecosystems that doesn't necessarily require outside access to function. Sure, it'd be nice for the different schools to talk to each other, but it's not vital and if it requires messing around with their existing, unreliable Windows network to get that done, I'd just as soon not have to deal with that headache. Goodness knows I have an annoying enough time setting up Samba to share files with the XP machine (not mine) on my home LAN. Sorry. Kinda venting here. Anna Schoolfield Birmingham |
_______________________________________________ Server-devel mailing list [email protected] http://lists.laptop.org/listinfo/server-devel
