On Wed, 2007-12-26 at 09:49 -0700, Robert Citek wrote:
> On Dec 26, 2007 8:38 AM, tms <[EMAIL PROTECTED]> wrote:
> > On Sun, 2007-12-23 at 09:59 -0600, Robert Citek wrote:
> > > - the restore script does not wipe out the /home/student folder.
> >
> > If you could clarify -- does that mean that there is a difference in the
> > hard drive image on the instructor machine, or does that mean that the
> > restore script is coded to handle the instructor machine differently?
> > If so, how does it identify which machine on the network is the
> > instructor machine?
>
> Cloning is the same. After cloning, the script
> /root/bworks/bin/upgrade.new-class.sh is either deactivated, deleted,
> or modified so that the student account is not removed.
That is easy enough to fix, but we'll probably keep the old one for now
(see below).
> > > Some other items that may need to be addressed on the classroom machines:
> > >
> > > - the pseudo-static DHCP assignments on the mini-server need to be
> > > updated with the new machine's MAC addresses
> > > - on Windows, hostnames need to be adjusted
> >
> > Will you be in on Wednesday evening?
>
> Tonight? Can't -- out of town. As for future Wedesdays, probably not
> for the next several months. However, I can remotely log in. If
> anyone wants to kibitz[1] some evening, just e-mail this list.
Well, we need to finish getting the classroom up and running before
January 5th, when the next childrens class starts (at least, I am
assuming that adult classes do NOT start on January 2).
> > Can you do these things then?
>
> I can do the Linux part, but it would probably be a good idea for
> others to do this. I'd be happy to walk someone through it via
> kibitz.
Although I am not the volunteer "in charge" of the classroom migration
(I think that may be Dan?), I am helping out as I can. If/when said
kibitz takes place, I'd love to be in on it.
> > If not, can you leave specific instructions so we can try to get them done
> > on Saturday?
>
> Here's one way:
>
> 1) figure out which machine will be Instructor, #1, #2, #3, etc.
> 2) turn them all on
> 3) determine the MAC address from each using ifconfig
> 4) adjust the stanzas in the /etc/dhcp3/dhcpd.conf on the mini-server
> (192.168.0.2). For example,
>
> host STUDENT001 {
> hardware ethernet 00:01:02:2C:1B:37;
> fixed-address 192.168.0.201;
> }
>
> 5) restart the dhcpd service: sudo /etc/init.d/dhcp3-server restart
Should be able to do this. Also, since we are keeping the old
instructor machine for now, that MAC address won't change yet. So, only
need to fix for the new student machines for now. Yes?
> As for the Windows machine, there's some setting in Control Panel >
> Networking ...???
Yeah, we can sort out the Windoze thing. I believe you can also
right-click My Computer, go to Properties, then something something
something from there (don't remember all the steps offhand, but should
be able to sort it out Saturday).
> > > Is anyone documenting how this project is progressing?
Sounds as if we should definitely document this. Not so much
clone/assemble, as those are pretty basic steps, but certainly the
post-install stuff (i.e., updating new MAC addresses for dhcp server,
removing/modifying scripts for instructors machine, Windoze tweaks,
etc.).
> > Have not been so far. The only issues to date:
> >
> > 1. No one other than Dan (and Robert) knew where to find the appropriate
> > clone script to create the triple-boot drives.
>
> I believe all the scripts are in ~/Desktop/bworks/scripts/ Some solutions:
>
> - put them on the wiki
> - put them in cvs/svn
>
> cvs/svn would probably be the best place to store scripts and code.
> Anyone want to install svn on the mini-server? Or perhaps we should
> create a Sourceforge project?
Frankly, I don't think we have the bodies right now. Please, someone,
prove me wrong -- step up and take on this project!! :-)
> > 3. ... If we can't get that working, then I suggest we
> > take one of the newer, faster, donated machines and make that into an
> > instructor machine. Or, leave the old instructor machine in place, it
> > will just be slower than all the other classroom machines.
>
> I'd go with the older machine and then phase it in over time. In
> fact, we may want to phase in all the new machines.
We already removed all the old machines (although they are stored in one
location downstairs, so worst case scenario, we can put them back in
place) with the exception of the instructor machine.
> Other features that would be nice to implement:
>
> - modify the classroom cloning script to adjust for disk size
> - restructure grub and the disk partitions
> - enable Wake-on-LAN on the classroom machines, if possible
Sounds like good ideas to me. The Wake-on-LAN may be possible, have to
check BIOS settings ...
Thanks for your input -- enjoy your holidays!!
t.
--
*** Propositions arrived at purely by logical
means are completely empty as regards
reality. - Albert Einstein ***
