On Wed, 2002-02-06 at 13:48, Jima wrote: > On 6 Feb 2002, John Scherer wrote: > I also somewhat wonder how efficient read-only NFS would be, compared to > FTP/HTTP. > Anyway, that would work so long as you mirrored most of the > distributions, hopefully including updates. NFS requires at a minimum nfs support in kernel, nfs-utils, portmap. Not all machines have this. NFS sucks rancid monkey chunks. > > My thought was having the router be the InstallNET backbone, with one > > 10/100 enet drop to each switch. one switch per table. Then if they > > need more drops at a table than the switch has available, they just add > > a hub/switch to the existing switch at the table (under InstallFest > > NetAdmin supervision) > > I had a similar idea, but at the base level, the same: segmenting the > network. > Also a good idea on the switches; there was some question as to whether > all of the hubs we were stringing together were causing problems. (I then > noticed that someone failed to correctly set the mode of the uplink port > on the particular hub, but it was still a concern!) And obviously having > 10/100 would help, especially if we actually used the server for network > installs. (How prevalent was this on Saturday? I'd say I personally saw > more CD media than network installs, but I didn't move around much.) At > any rate, though, the lack of availability of such equipment is what keeps > the networks from working too well. Offering to lend equipment certainly > helps. > > > This setup would help debug network problems as well. We would easily > > be able to tell what enet port the problem is originating from and > > isolate the problem if necessary. > > Yep. > > > This could also be a learning tool for others to learn from. As an > > installfest NetAdmin you could use this as a teaching tool to help > > educate others with more advanced aspects of networking. > > True. Perhaps difficult, but it is possible. > > > PS: Someone though of adding something to the nametags at future > > installfests to identify those who are “helpers” or “admins”, great > > idea. I did the nametags you saw at the past weekends fest, and could > > add other info to the tags if desired. I would just need to know who > > and what. > > Probably a good idea. At the installfest at CodeWeavers, we wrote an > (A) on our nametags to indicate we were helpers, but a number of people > (myself included) have said that they'd like something more specific than > "helper," that is, their area of expertise. (Asking a RedHat expert for > assistance on a Debian install? BAD idea.) > What's up with those control characters around "helpers" and > "admins?" ^S for left quote, and ^T for right quote. It's weird. Came > from Evolution, too. > > > Any thought? > > I try to avoid it whenever possible. > > Jima > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list > -- Ben Lutgens http://people.sistina.com/~blutgens/ Sistina Software Inc. pub 1024D/9A0DDC59 2001-12-12 Ben Lutgens <blutgens at sistina.com> Key fingerprint = 8FCD A1EE CEA7 DEE1 9361 F32C 0A90 30D1 9A0D DC59 sub 1024g/1FC75C99 2001-12-12 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20020206/6e388cc6/attachment.pgp