headers
usenet | 1 Jun 2008 01:53

Re: SOLVED - hostname.pppoe0 with AT&T/SBC debug?

>>>>> "k" == Kareem Kazkaz <kkazkaz <at> gmail.com> writes:
k> Shizzle Cash wrote:
>> 
>> On Wed, 28 May 2008 19:15:39 -0700 (PDT)
>> Kareem Kazkaz <kkazkaz <at> gmail.com> wrote:
>> 
>> I have had similar issues with at&t and their PPPoE.  I've noticed that
>> some devices (such as Belkin wifi routers) require the modem be set to
>> "PPPoE on client".  Others devices (such as Linksys routers) require
>> the modem to be set to Bridged mode while allowing the router to handle
>> the PPPoE connection.  My Linksys running DD-WRT prefers the modem
>> handle the PPPoE connection itself.  I still haven't been able to
>> figure out a pattern for it.

k> Since I run the OpenBSD box headless, it's not as though I have to really
k> deal with all the dmesg pppoe debug updates. Still, this isn't the cleanest
k> way of running pppoe, and I'm a bit miffed that my /var partition is filling
k> up.

k> As far as my own setup goes, I did indeed have to set the DSL modem to
k> bridging mode. I'm running a Netopia 2210 with AT&T if it matters.

k> Shizzle, did you ever solve any of the previous setups that required the
k> debug flag turned on?

I'm not sure how 'debug on' solved your problem.  In my environment,
'debug on' is unbearable as it takes forever to establish the initial
pppoe session.  I assume the slowness is related to usage of a 9600
baud serial console.  One particular repeating refrain, ie. 'pppoe0
(8864) state=3,' overwhelmed that console.  I made the following patch
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Liu | 1 Jun 2008 04:06
Picon

Re: how to upgrade use pkg_add

How to see which package need to be upgraded.
Permalink | Reply | 1 comment |
headers
Rick Aliwalas | 1 Jun 2008 04:43
Favicon

Re: carp log destination

On Sat, 31 May 2008, Stuart Henderson wrote:

> If you touched IP addresses at some point after initially booting
> the system, you are probably bitten by the bug fixed in ip_carp.c r1.134

Looks like we are running v1.130.  Time for me to upgrade.  Thanks much
Stuart/Ryan/Brian.  The extra logging is greatly appreciated.  Aside from
a few MASTER-MASTER incidents this pair has provided years of stable
service.

-rick
Permalink | Reply | 0 comments |
headers
Dan Liu | 1 Jun 2008 04:47
Picon

kill with PHU or HUP

If I need to reload a daemon like sshd,why I should use pkill -HUP sshd not
pkill -PHU sshd.And pkill -PHU will not work.
Permalink | Reply | 2 comments |
headers
Chris Kuethe | 1 Jun 2008 05:05
Picon

Re: kill with PHU or HUP

glycosine:ttyp2# man 2 kill | grep HUP
     SIGTERM, SIGSTOP, SIGTTIN, SIGTTOU, SIGTSTP, SIGHUP, SIGUSR1, SIGUSR2.
glycosine:ttyp2# man 2 kill | grep PHU
glycosine:ttyp2#

"PHU" is not a valid signal name.

why SIGHUP? because that's how it was programmed. programs can be
written to catch and respond to a variety of signals in a variety of
ways. sshd(8) was written to catch SIGHUP and take that as a sign that
it should reload the configuration. If I send an instance of top(1) a
HUP, it'll just quit because the default action upon receipt of a
SIGHUP is to exit, and top wasn't written to handle it any other way.

Please read the kill(2) and signal(3) manpages for for information
about signals.

On Sat, May 31, 2008 at 7:47 PM, Dan Liu <miraclecome <at> gmail.com> wrote:
> If I need to reload a daemon like sshd,why I should use pkill -HUP sshd not
> pkill -PHU sshd.And pkill -PHU will not work.
>
>

--

-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?
Permalink | Reply | 1 comment |
headers
Dan Liu | 1 Jun 2008 06:25
Picon

avoid different Flavors using command

http://www.openbsd.org/faq/faq15.html#NoFun
"Do NOT check out a -current ports tree and expect it to work on a -release
or -stable system. This is one of the most common errors and you will
irritate people when you ask for help about why "nothing seems to work!" *If
you follow -current, you need both a -current system and a -current ports
tree*. Yes, this really does mean a wonderful new port will typically not
work on your "older" system -- even if that system was -current just a few
weeks ago. Keep in mind that if you use X11 as part of your system, it must
also follow the corresponding branch!"

But it have not told any method to avoid it.
Can you tell me the way.I want to know the command?
Like:
#cd /usr/src
#cvs -q up -Pd

Thank you very much!
Permalink | Reply | 0 comments |
headers
Dan Liu | 1 Jun 2008 07:06
Picon

Re: avoid different Flavors using command

> You probably want to have a read through section 5 of the FAQ about
> building from source.
> http://www.openbsd.org/faq/faq5.html
>
> This mentions the use of specific revision tags like "-rOPENBSD_4_3"
> to check out 4.3-stable.

I have read faq5 twice.Maybe I don't need to build a custom kernel.But I
don't quite know whether should I build my userland if I will install some
packages from ports later.
And I can not quite follow below:
"Keeping Things in Sync It is important to understand that OpenBSD is an
Operating System, intended to be taken as a whole, not a kernel with a bunch
of utilities stuck on. You must make sure your kernel, "userland" (the
supporting utilities and files) and
ports<http://www.openbsd.org/faq/faq15.html#Ports>tree are all in
sync, or unpleasant things will happen. Said another way
(because people just keep making the error), you can not run brand new
portson a month old system, or rebuild a kernel from
*-current* source and expect it to work with a *-release* userland. Yes,
this does mean you need to upgrade your system if you want to run a new
program which was added to the ports tree today. Sorry, but again, OpenBSD
has limited resources available.

One should also understand that the upgrade process is supported in *only
one direction: from older to newer*, and from *-stable* to *-current*. You
can not run *4.3-current* (or a snapshot), then decide you are living too
dangerously, and step back to *4.3-stable*. You are on your own if you
choose any path other than the supported option of reloading your system
from scratch, do not expect assistance from the OpenBSD development team.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Dan Liu | 1 Jun 2008 07:30
Picon

upgrade magic comes an error

Follow the current guide.
http://openbsd.org/faq/current.html#20080508

# cd /tmp
# ftp ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/i386/etc43.tgz
# tar xzpf etc43.tgz ./etc/magic
# mv etc/magic /etc

After that I can not use file command.
#cd /
#file bin
file : could not found any magic files!

Please help!
Permalink | Reply | 5 comments |
headers
Marc Espie | 1 Jun 2008 09:10
Favicon

Re: avoid different Flavors using command

Look, if you can't figure out where you are with respect to cvs tags
by just looking at the stuff in your tree, maybe it's not such a good
idea to rebuild stuff from source.
Permalink | Reply | 1 comment |
headers
Marc Espie | 1 Jun 2008 09:08
Favicon

Re: how to upgrade use pkg_add

On Sun, Jun 01, 2008 at 10:06:17AM +0800, Dan Liu wrote:
> How to see which package need to be upgraded.
pkg_add -ui
Permalink | Reply | 0 comments |

Gmane