Re: television cable internet service

2003-06-17 Thread chris corayer
To make life easy, I had a windows box laying around for the technician
to verify a live line with.  Once it was live and he was gone, I
switched to using a BSD router on the connection.

I did the same here.  Although to be honest, nothing the tech did here
should have made any difference whatsoever.  He plugged in the modem, booted
the computer ( DHCP ), and went into the browser for a couple of minutes.

Yeah, they are paranoid about servers, but never do anything about them
until it starts to cost them money.  If they were really strict on the
no servers policy, they would be able to allow any windows box to
connect to their network.

The tech didn't mention anything about servers to me.  But in all honesty I
haven't bothered to try and see if they're blocking ports or not.  I would
suspect that they are though.

BSD should work fine with Comcast.  I am not sure how comcast in your
area differs from the seattle area, but they should all be BSD friendly.
The big trouble is that initial service with cable/dsl is rather flaky.
It usually takes the ISP a month or so to figure out how a network is to
be expanded or something.

My BSD stuff works fine here.  And yes, for the first couple of months the
service would flake out daily in the early afternoon.  Lately it's been
solid.  Depending on what your needs are, you could also consider a cheap
router ( linksys or others ) as they're down to ~50$ or so.  That's not much
more than a cheap switch at this point, so even if you don't decide to use
it as a router you can use it for your network anyway.  Much of it is point
and click, which may be useful until you learn more about how to fully set
up your BSD box's firewalling and such.  As the DHCP server and NAT are
already built in, this might also be helpful until you get DHCP server set
up on your BSD box as well.

Hope this helps.

-Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Are there STABLE/CURRENT/RELEASE tags for ports?

2003-06-12 Thread chris corayer
You could try specifying a date in your cvsupfile.  This isn't exactly what
you are looking for but if you tried to update a port and find it no longer
works, you could then roll back the changes made with another cvsup for the
ports.  I have done this in the past but don't recall the exact syntax.  Try
man cvsup.  I would consider setting up another cvsup file for just this
purpose if you think it will happen often.  You could set the date to when
the new version came out, sort of a release date, or just increment it
until you get it to the point where you know it builds and go from there.

Hope this helps a little.

-Chris

- Original Message - 
From: DoubleF [EMAIL PROTECTED]
To: Mark Miller [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, 12 June, 2003 0:23
Subject: Re: Are there STABLE/CURRENT/RELEASE tags for ports?


  Are there any equivalents to STABLE/RELEASE/CURRENT for ports?  I've
been
  cvsup'ing with tag=. for awhile and I keep getting build errors (bug
  reports will be filed soon).  Is there a way to just track -STABLE ports
  (maybe that only have bugfixes and security updates) that are more
likely
  to play nicely with each other?  If not, is there any way to make this
  happen?

 Arghh I wish there were such tags.

 In the meantime you might consider CTM for ports, downloading the deltas
 from the FTP. If you do that and NEVER EVER remove the deltas, you may
 be able to 'roll back' to any date you want to try to find the non-broken
 port version (if there was any, of course...).

 I am also rather tired of build errors. What I can suggest is probably
 kludgy, but it is the least kludgy way I could find to compile some
 ports. Before you install any ports,

 1) Save the deltas...

 hier kludge start
 2) Symlink /usr/X11R6 to /usr/local. Many ports put files in the wrong
 one, and symlinking individual files is, ahm,... AFAIK, there are no
 colliding files in them.

 3) Try putting /usr/local and /var/db/pkg (and /etc/X11, and /usr/ports
 maybe, but I don't) on a separate filesystem. Make two such filesystems,
 current and stable. Make / and the remaining /usr as read-only as
 possible. Make a mountpoint, say, /switch. Symlink /usr/local to
 /switch/usr.local, /var/db/pkg to /switch/var.db.pkg... Then change the
 fstab file to mount stable at startup. You can always mount current
 after boot on top of stable and so emulate what you wish. You may want
 to make the WRKDIRPREFIX to point to a directory shared between the
 current and stable to save compilation time (otherwise you will
 compile each port twice), but I wouldn't recommend it (to be on the safe
 side).
 hier kludge end

 It's just what I do. I know it breaks the normal hierarchy (and takes 2x
 space), but at least it does it in a polite way.

 HTH,
 DoubleF



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: A couple of questions for 5.1rc1....

2003-06-06 Thread chris corayer
- Original Message - 
From: Derrick Ryalls [EMAIL PROTECTED]
To: 'chris corayer' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Friday, 06 June, 2003 2:50
Subject: RE: A couple of questions for 5.1rc1


I run 4.8, but here are my suggestions:


 The final question I have is one that's probably obscure.  I
 remember a switch used to tell the dhcp client to send the
 host name of the laptop to a dhcp server.  While it gets a

man dhclient.conf

 lease perfectly fine, opening up my linksys dhcp table ( at
 home ) or the NT dhcp server at work I can only see that a
 machine has that lease.  The name of the laptop isn't listed.
  I had enabled something on a laptop I had a couple of years
 ago that made it so the name showed up, but I haven't been
 able to find anything on this since and I have no idea how I
 did it before or even where I found it.

I don't think dhclient is the issue.  If you want your machine
to appear on the network, install samba.  You don't need to
share anything out unless you want to, but samba contains the
network name service (nmbd).  Then again, maybe I misunderstood
you.


I neglected to mention that I had read through the dhcp related man pages.
Probably due to my lack of sleep I missed it but I managed to find what I
needed.  It was not what I expected it to be.

I had put in the line   send host-name myhost; into my dhclient.conf
file.  However, the line I was actually looking for wassend
dhcp-client-identifier myhost; I'm not entirely sure why you would use
the first one I tried, perhaps if the server always assigns a particular
system the same IP address?  Then again, wouldn't the line I ended up using
do the same thing?  Anyway, with the dhcp-client-identifier line, the system
now shows up in the NT server/linksys router dhcp clients table.  So that's
one part down.

I will likely be adding samba soon as it will be nice for the laptop to show
up in the browse lists as well.

Now I just need to spend some more time this weekend and see if I can't fix
those ACPI/APM issues.

-Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


A couple of questions for 5.1rc1....

2003-06-05 Thread chris corayer
I am trying to figure out how to fix an niggling dhcp issue and permanently
disable ACPI and enable apm on my HP Omnibook 900.

I'm running 5.1RC1, which is great since this is the first time I've managed
to get 5.x on this unit.  Even my xircom realport cards work.  However, I'm
having trouble figuring out exactly where to put the ACPI disable line as
this machine just crashes and reboots if I leave it enabled.  I think it
should go in loader.conf, but I'm unsure exactly on the syntax or if that's
where it belongs.  Also, I seem to remember that you could enable APM with
the generic kernel by inserting a line into loader.conf as well.

The final question I have is one that's probably obscure.  I remember a
switch used to tell the dhcp client to send the host name of the laptop to a
dhcp server.  While it gets a lease perfectly fine, opening up my linksys
dhcp table ( at home ) or the NT dhcp server at work I can only see that a
machine has that lease.  The name of the laptop isn't listed.  I had enabled
something on a laptop I had a couple of years ago that made it so the name
showed up, but I haven't been able to find anything on this since and I have
no idea how I did it before or even where I found it.

I think I'm missing some probably obvious things.  Can anyone at least point
me in the proper direction?

Thanks.

-Chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]