<?xml version="1.0" ?>

<kc>

<headquote>
<a href="http://www.slug.org.au/"><img src="../ktimages/slug.gif" height="105"
width="150" border="0" alt="SLUG Logo"/><br />Check out the Sydney Linux User
Group</a>!
</headquote>

<title>SLUG Pearls</title>

<author contact="mailto:jdub@aphid.net">Jeff Waugh</author>

<issue num="2" date="13 Jun 2000 00:00:00 -0800" />

<intro>

<p>This week's edition of SLUG Pearls is late because some old dear in a far
off country didn't have a birthday, and I was celebrating her unbirthday in
that tellingly reverent Australian way: I went to see an action film.</p>

<p>Another blunder: Statistics for this week's SLUG list are sadly
unavailable.</p>

<p>This is due to combination of, um, me catting over my mail file (duh!)
and the stats software returning some pretty wacky stats. No, our glorious
president did <i>not</i> post 1.2MB worth of email this week.</p>

<p>On with the show, eh?</p>

</intro>

<section
  title="Repeaters, Hubs, Blast-off!"
  subject="repeaters &amp; hubs ##"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00196.html"
  posts="27"
  startdate="04 Jun 2000 00:00:00 -0800"
  enddate="07 Jun 2000 00:00:00 -0800"
>

<p>Sometimes it's the simplets of questions that yield the biggest threads
on SLUG, and Minh Van sure knows how to start 'em, <quote who="Minh
Van">what's the difference between a repeater and a hub ? can one be used to
do the job of the other ?</quote></p>

<p>Martin Visser offered this straightforward comparison: <quote who="Martin
Visser"> A "hub" is just a repeater with lots of ports. A repeater
regenerates the incoming EThernet signal and forwards it out all ports.
(This is different from a bridge/switch which makes some smart decisions
about which ports to forward traffic on).</quote></p>

<p>George Vieira added to the desription:</p>

<quote who="George Vieira">

<p>The bonus job of a repeater is also that it can extend the network limit of 100
metres by rebroadcasting the packets onto the other network. Similar to a linux
box with 2 network cards and a route between the two.</p>

<p>The drawback is there are alot more chances of getting collisions and the
delays are larger due to the retransmission.. but really you don't notice
it.</p>

</quote>

<p>DaZZa responds:</p>

<quote who="">

<p>Absolute bollux.</p>

<p>You can extend your network using hubs as well - as long as you apply the
5-4-3 rule to the total segment length and number of repeaters.</p>

</quote>

<p>DaZZa also explained that the amount of collisions would be similar using
either a hub or a repeater. The 5-4-3 rule?</p>

<quote who="">

<p>{groans} I knew someone'd ask me that.</p>

<p>It goes something like you can extend your maximum network cable length by
extending it across 5 hubs with 4 segments and any 3 of those segments
being populated {I.E. having nodes on them}.</p>

</quote>

<p>Read DaZZa's long post - with diagram - <a
href="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00234.html">here</a>.</p>

<p>There were various discussions about maximum cable length, availability of
networking hardware, and a bit of network engineer one-upmanship, but none
quite so scathing as Rodos' comment, <quote who="">
Sheesh, even my 3 year old knows the 5-4-3-2-1 rule, you gotta yell *zero,
blast off* at the end!</quote></p>

</section>

<section
  title="Proxy Passwords and wget"
  subject="wget with proxy authentication"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00204.html"
  posts="8"
  startdate="05 Jun 2000 00:00:00 -0800"
  enddate="05 Jun 2000 00:00:00 -0800"
>

<p>gizmox was looking for a way to wget through an authenticated proxy server,
and hadn't found a commandline or .wgetrc option that helped. When Rodos posted
a portion of the documentation relating to proxies, gizmox clarified his
problem:</p>

<quote who="">

<p>Yes, thanks, but...</p>

<p>My username contain the '@' character (I can't change it) and wget responds
with invalid port specification or not recognized it at all. How to solve the
problem?</p>

</quote>

<p>Rodos directed gizmox, not to the documentation, man files or web page, but
<a href="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00217.html">The
Source</a>. Whilst gizmox couldn't actually read the source, the problem
was solved:</p>

<quote who="">

<p>You should therefore be able to use %40 instead of your @ character.</p>

<p>Give http://user%40domain:mypassword@proxy.company.com:8001/</p>

</quote>

<p>Like the end of a Saturday morning cartoon, Rick chimes in with the moral of
the story:</p>

<quote who="Rick Welykochy">

<p>Interesting example of how The Source can solve a seemingly intractable
problem.</p>

<p>Compare this to the same problem using a closed product, like a utility from
Microslop.</p>

<p>Q: How many phone calls and credit card charges would it take to find out if
MS's "wget" utility allows an "@" in the username of a proxy URL?</p>

<p>A: More than you could afford.</p>

</quote>

</section>

<section
  title="More Briefcase-Penguin Banter"
  subject="Dell + Notebook + Linux - Latest"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00260.html"
  posts="7"
  startdate="05 Jun 2000 00:00:00 -0800"
  enddate="05 Jun 2000 00:00:00 -0800"
>

<mention>Matt Allen</mention>
<mention></mention>

<p>David Sainty gave us an update on his efforts to find a laptop with Linux
pre-installed. He was a bit miffed at the lack of a Linux-certified notebook
here, whilst there was a model available in the US. A few choice quotes:</p>

<quote who="David Sainty">

<p>"I'm left thinking to myself: 'Oh crap! They're gonna take the Linux notebook
into .... the SOUTHERN HEMISPHERE!!! Its gonna blowwwww!!!!
&lt;BOOM!!!&gt;'"</p>

<p>"M$ Tax Minimisation: 'The conscious decision to purchase Windoze 98 instead
of Windoze NT or Windoze 2000 because less money exits your pocket to
M$.'"</p>

<p>"M$ Tax CuT: 'The introduction of a new version of Windoze cheaper than
those presently available.'"</p>

</quote>

<p>Aravind Naidu replied:</p>

<quote who="Aravind Naidu">

<p>When Linux comes pre-installed, they are obliged to answer some questions if
say something does not work.
It is more like they are dragging their feet getting it up as the perception
is that there is not much of a market here. More enquires like this and they
will bring it down here.</p>

<p>I long for the day of the 'naked' machine. No OS !!!!</p>

</quote>

<p>To be sure, Aravind, to be sure. Matt Allen wondered if Dell was
receiving money from M$, and if not, whether they'd save money by not
installing the Seattle Stifler. Jeff Waugh thought not:</p>

<quote who="Jeff Waugh">

<p>They've got a much bigger bargaining tool: Windows itself.</p>

<p>Can you imagine what would happen if Gateway couldn't sell computers with
Windows?</p>

<p>Now you know why they're so shitscared.</p>

</quote>

<p>Simon Rumble replied, <quote who="Simon Rumble">
Well if they refused to sell someone a copy of Windows, they'd get even
more hammered by the Justice Dept.  However they do have individual and,
of course, "commercial in confidence" pricing agreements with each of the
vendors.  So they could always just start charging them all RRP...</quote></p>

<p>In other news, Microsoft being hammered by the DOJ.</p>

</section>

<section
  title="WinModems - The Profit Motive &amp; Hardware"
  subject="Rockwell HCF Modem on linux?"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00331.html"
  posts="6"
  startdate="07 Jun 2000 00:00:00 -0800"
  enddate="07 Jun 2000 00:00:00 -0800"
>

<mention></mention>
<mention>Tim Sutton</mention>

<p>Tim Sutton wondered whether the great Rockwell HCF PCI modem would work
under Linux. Sadly, this particular modem is one of the most frustrating
examples of proprietary hardware specifications. The hardware in itself may
not be all that bad, but the drivers for it have only ever been written for
Windows (thus the monkier WinModems), and the specs have never been
released.</p>

<p>This isn't a new thing spurred on by the Microsoft oligarchy: Richard
Stallman created the GPL, the Free Software Foundation and countless pieces
of software at the heart of our OS... inspired by a printer.</p>

<p>And they tell us not to sweat the small stuff...</p>

</section>

<section
  title="Warning: Do Not Dig - Network Cables"
  subject="Home Network"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00351.html"
  posts="17"
  startdate="07 Jun 2000 00:00:00 -0800"
  enddate="08 Jun 2000 00:00:00 -0800"
>

<mention>Simon Rumble</mention>
<mention>Jim Clark</mention>

<p>Whilst this thread was not specifically Linux-oriented, there were too
many good ideas to waste! Jim Clark asked for tips and suggestions for
installing network cables and the like in his not-yet completed home.</p>

<p>Simon Rumble suggested conduit instead of cabling, to preempt new kinds
of cables coming out to ruin the fun.</p>

<p>Jamie Honan commented that taking photos of cabling before it's covered
by gyprock, and installation of draw-wires are useful resources when upgrading. In an attempt to keep the thread
on-topic, <quote who="Jamie Honan">
ObLinux: (scratches round) Home is so I keep my Linux boxes dry.</quote></p>

<p>David added to Simon and Jamie's ideas, <quote who="">
Talking of concrete slabs... another trick that I have used succesfully is
to lay 100mm pvc drainage pipe under the slab, with risers up to the
surface at strategic spots around the building. You can cap the risers
easily enough. These can be used for running everything from cat5 to front
door bells and speaker leads. Draw wires are a good idea, but
electrician's eels will do the job if necessary. The last time I did this
I ended up with about 15 circuits passing through one pipe. Concrete slabs
are very unforgiving if you overlook the need for a particular circuit.
</quote></p>

<p>Various vendors and prices for the components were mentioned.</p>

</section>

<section
  title="PABX Hell (and Minicom)"
  subject="Force Minicom to dial sans dial-tone,"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00496.html"
  posts="4"
  startdate="09 Jun 2000 00:00:00 -0800"
  enddate="09 Jun 2000 00:00:00 -0800"
>

<mention></mention>

<p>Peter Rundle was trying to dial out through a PABX that made non-standard
noises, confusing Minicom.</p>

<p>DaZZa and Rodos suggested using ATX0, which makes the modem ignore the
dial-tone.</p>

</section>

<section
  title="Apache Virtual Hosts on a Dynamic IP"
  subject="Virtual hosts on a dynamic IP"
  archive="http://www.progsoc.uts.edu.au/lists/slug/2000/June/msg00529.html"
  posts="11"
  startdate="10 Jun 2000 00:00:00 -0800"
  enddate="12 Jun 2000 00:00:00 -0800"
>

<mention></mention>

<p>Paul Robinson wanted to know if he could run a number of domains from his
dial-up line. His Apache configuration was correct, but he would have to
keep changing the ip address in it for the domains to resolve correctly.</p>

<p>ENTERforNone suggested using 127.0.0.1, but noted that it wouldn't be
visible to the rest of the 'net, which was a requirement. After various
comments, Paul was under the impression that a permanent IP was the only way
of making it work.</p>

<p>Angus Lees - who could probably build a nuclear reactor with sed -
offered:</p>

<quote who="Angus Lees">

<p>nonsense - in your ip-up script (or some dhcp script or something for
cable), just put something like this:</p>

<p>

<blockquote><tt>
   myip=$4  # for ip-up, `hostname -i` or something otherwise<br />

   sed "s/@MYIP@/$myip/g" &lt; /etc/apache/httpd.conf.orig &gt; /etc/apache/httpd.conf<br />

   /etc/init.d/apache/reload
</tt></blockquote>

</p>

<p>and httpd.conf.orig is just a copy, with @MYIP@ instead of any
specific ip address</p>

</quote>

<p>Which, with a few small changes for Paul's distribution, worked.</p>

</section>

</kc>

