First off if this shows up as html, I apologize, I'm temporarily using a
web based client. This email contains my configuration files so is kind of
long but I hope this will give as much information as possible.
I just got DSL after riding myself of my cable modem. The DSL I have is
using pppoe.
At 04:58 20-1-2002 -0600, [EMAIL PROTECTED] wrote:
>First off if this shows up as html, I apologize, I'm temporarily using a
>web based client. This email contains my configuration files so is kind of
>long but I hope this will give as much information as possible.
MIME-Version: 1.0
Content-Type:
> ---SNIP---
>
>>gateway_enable="YES"
>
> good
>
>>hostname="PITA.the-rob.com"
>>network_interfaces="xl0 dc0 lo0"
>>ifconfig_dc0="inet 192.168.1.1 netmask 255.255.255.0"
>>ifconfig_lo0="inet 127.0.0.1"
>>ifconfig_xl0="inet 10.0.0.1 netmask 255.255.255.0"
>
> still looking good
>
>>ipfilter_enable
sometimes the modem will refuse to talk to a second MAC address, once one
has been used.. you need to turn such modems off and on again when changng
machines..
(It could be talking to your laptop only)
On Sun, 20 Jan 2002 [EMAIL PROTECTED] wrote:
>
> > ---SNIP---
> >
> >>gateway_enable="YES"
>
Florent Parent writes:
> This is what I did to make it work for me. A better fix would probably be
> around the struct proc definition. If fact, you had noted "broken"
> probably as a memo to fix something here...
>
> struct proc *p = curproc ? curproc : &proc0;/* XXX broken */
>
>
--On 2002-01-20 11:30:01 -0800 [EMAIL PROTECTED] wrote:
>
> So this 'struct proc' argument can be NULL now?
> What about when calling other socket functions like socreate(), et. al.?
'struct proc' member in the struct sockopt can be NULL. As per the comment
in that structure, NULL means that
Florent Parent writes:
> 'struct proc' member in the struct sockopt can be NULL. As per the comment
> in that structure, NULL means that the calling entity is the kernel, not a
> user process (my interpretation):
>
> struct sockopt {
> enumsopt_dir sopt_dir; /* is this a get or a set?
< said:
> But it's interesting the soalloc() is called with 'p != 0'
> as an argument. p is never 0 or else you would have already
> panic'd... you'd panic later on, too, referencing 'p->p_ucred'.
All of the credential frobbing stuff was added much later. At the
time I wrote that `p != 0', it w
Florent Parent writes:
> 'struct proc' member in the struct sockopt can be NULL. As per the comment
> in that structure, NULL means that the calling entity is the kernel, not a
> user process (my interpretation):
>
> struct sockopt {
> enumsopt_dir sopt_dir; /* is this a get or a set?
