Well, I'm really sick of people complaining about not being able to get
at the things the resource manager knows from userspace. So I've done
something about it.
Please review:
http://ziplok.dyndns.org/msmith/rman.diff
http://ziplok.dyndns.org/msmith/iostat.diff
which adds the new '-r'
> > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
>
> You don't need those; you can get them out of /etc/fstab. In part
On 3 Nov, Alexander Anderson wrote:
> In mailing.freebsd.hackers, you wrote:
>
>> > Is their a tool out their or does anyone have a quick bit of code /
>> > hack that will "probe" all of the irqs on my box and tell me which
>> > ones are used / available??
>>
>> No. You can glean some of this
On Thu, 2 Nov 2000, Don Muller wrote:
> Well, the company did not explain how, or why it happened. The
> programmer I work with suggested BSD.Of course I wanted security!
> Well, they gave me some explanation that the server was hacked at the
> xfs port. But later I was told that the ftp port on
Hi,
I'm just looking at vcount in sys/kern/vfs_subr.c. The comment says that
it works on special devices. Does this mean it wont work if called on a
vnode of a regular file? That seems unlikely but I've no idea what I'm
doing in these regions of code either :-)
Thanks,
Andrew
To Unsubscribe:
On Sat, 4 Nov 2000 [EMAIL PROTECTED] wrote:
> I'm just looking at vcount in sys/kern/vfs_subr.c. The comment says that
> it works on special devices. Does this mean it wont work if called on a
I think I see what it means now. It is meaning that ir works on the file
the vnode is for as opposed
In message <[EMAIL PROTECTED]>, andre
[EMAIL PROTECTED] writes:
>Hi,
>
>I'm just looking at vcount in sys/kern/vfs_subr.c. The comment says that
>it works on special devices. Does this mean it wont work if called on a
>vnode of a regular file? That seems unlikely but I've no idea what I'm
>doing i
Hi,
I just wrote a man page for vcount and count_dev but as you can guess from
my previous questions I'm not to sure its accurate. Could someone take a
glance at if they get a moment? That way less people like me should come
to bug you in the future :-)
I based it off Eivind Eklund's namei.9 and
Hi guys,
I am still trying to create a FreeBSD driver for a D-Link DE620 pocket
ethernet adapter. I've got the thing to attach to ISA and everything,
but then I decided it'd be much handier if I would re-write this thing
so it'd use KLD instead, for easy debugging and on-the-fly usuage of the
In message <[EMAIL PROTECTED]>, Rink Springer さんいわく:
>I got the stuff to compile et al, but I cannot get the darned thing to
>run as a KLD. FreeBSD doesn't appear to try to probe for the interface
>:(. When I tell FreeBSD it's a PCI thing (instead of ISA), it probes for
>it...
>
>How
On Tue, 31 Oct 2000, Terry Lambert wrote:
> not noticing that read was returning 0 (which is returned on EOF,
> but is also returned on perfectly goo non-blocking fds, and in the
If you read from a non blocking fd (and there is nothing to read) don't
you get -1 and errno = EAGAIN?
> case that
On Tue, 31 Oct 2000, Terry Lambert wrote:
> (struct tty *)->t_pgrp->pg_id
>
> Which is the process ID of the group leader of the foregroun
> group.
Isn't this what tcgetpgrp returns? Problem with this is that it probably
isn't the PID of the session leader. Wouldn't I need (struct tty
*)->t_s
Hi,
hm, even if I compile the kernel with options SYSVSHM, I don't seem to
have a working shmget. Did I miss anything important ?
bye,
@rak
<> [EMAIL PROTECTED] <>-<> FreeBSD <>---
jx : yeah im a net-monk
and i pray every day for the soul of interne
John Hay writes:
| > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
| > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
| > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
| >
| > You don't need those; you can get them
> John Hay writes:
> | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> | >
> | > You don't need those; you c
On Nov 04, John Hay wrote:
> > John Hay writes:
> > | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> > |
On Sat, Nov 04, 2000 at 10:47:27AM -0700, Wes Peters wrote:
> It works fine for me. Try this little program and see if it successfully
> attaches the shared memory segment:
thx :) actually I think it might have something to do with jail then,
cause this test works fine on the actual host machin
Stephanie Wehner wrote:
>
> On Sat, Nov 04, 2000 at 10:47:27AM -0700, Wes Peters wrote:
>
> > It works fine for me. Try this little program and see if it successfully
> > attaches the shared memory segment:
>
> thx :) actually I think it might have something to do with jail then,
> cause this
On Sat, Nov 04, 2000 at 03:43:28AM -0800, Mike Smith wrote:
>
> Well, I'm really sick of people complaining about not being able to get
> at the things the resource manager knows from userspace. So I've done
> something about it.
>
> Please review:
>
> http://ziplok.dyndns.org/msmith/rman.
> > Comments? Here's some sample output; the leading index numbers are
>
> Just 2: why are the irqs displayed in hex?
See the following comment regarding "formatting conventions". There's no
easy way for the program to know that they're IRQs (and IMO it shouldn't),
so no way to know that they
In message <[EMAIL PROTECTED]>you write:
} [...]
}The option-128 confuse the pxeboot program. If I put
}
}option root-path "/export/diskless";
}option option-128 "10.1.2.3:/export/shark";
}
}in the dhcpd.conf file, pxeboot tries to mount /export/sharkM-^[^B-i=FF
}as the root filesystem. Removing t
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> > Comments? Here's some sample output; the leading index numbers are
>>
>> Just 2: why are the irqs displayed in hex?
>
>See the following comment regarding "formatting conventions". There's no
>easy way for the program to know that they're
John Hay writes:
| > You don't, it is done via the bootp or dhcp record option 128 for example
| > option option-128 "192.168.2.254:/usr/work/netboot";
| > You then have to make the swap file in that directory of format
| > swap.
| > Use dd to create the file by copying /dev/zero f
> | > You don't, it is done via the bootp or dhcp record option 128 for example
> | > option option-128 "192.168.2.254:/usr/work/netboot";
> | > You then have to make the swap file in that directory of format
> | > swap.
> | > Use dd to create the file by copying /dev/zero for the
> In message <[EMAIL PROTECTED]>, Mike Smith writes:
> >> > Comments? Here's some sample output; the leading index numbers are
> >>
> >> Just 2: why are the irqs displayed in hex?
> >
> >See the following comment regarding "formatting conventions". There's no
> >easy way for the program to kno
> Yes, you are right. Putting the ip number in the root-path cures the
> pxeboot failure. But is still only configure the NFS ROOT according
> to the kernel's output. I had a look at the pxe code in
> /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
> /sys/i386/i386/autoconf.c which
John Hay writes:
| > | > You don't, it is done via the bootp or dhcp record option 128 for example
| > | > option option-128 "192.168.2.254:/usr/work/netboot";
| > | > You then have to make the swap file in that directory of format
| > | > swap.
| > | > Use dd to create the file by
In message <[EMAIL PROTECTED]> Rink Springer writes:
: I got the stuff to compile et al, but I cannot get the darned thing to
: run as a KLD. FreeBSD doesn't appear to try to probe for the interface
: :(. When I tell FreeBSD it's a PCI thing (instead of ISA), it probes for
: it...
:
: How can I
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Rink Springer writes:
> : I got the stuff to compile et al, but I cannot get the darned thing to
> : run as a KLD. FreeBSD doesn't appear to try to probe for the interface
> : :(. When I tell FreeBSD it's a PCI thing (instead of ISA), it probe
In message <[EMAIL PROTECTED]> Sergey Babkin writes:
: Maybe I'm missing something but I think that the point of the identify
: routine is to discover this address whatever it is, so it does not
: have to be fixed.
That doesn't work on the ISA bus too well, unless the card can only be
in a few p
I understand that memory belonged to a buffer will not be paged out by VM
daemon. Now I want protect that memory from being cleaned by VM daemon as
well. Should I use vfs_busy_pages() or just assume that since my pages are
on the active queue, VM daemon will not touch it (it only cleans pages on
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Sergey Babkin writes:
> : In 4.x if you say in config file
> :
> : foo at isa
> :
> : and provide the identify routine in the driver the result should be
> : the same. The "ep" driver does that using a proprietary probe
> : procedure.
>
> Mo
On 2000-11-02 20:56 -0800, Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> * Daniel C. Sobral <[EMAIL PROTECTED]> [001102 19:26] wrote:
> > >
> > > 1) please wrap lines at 70 characters when posting to the list.
> >
> > Furthermore, DO NOT send html-formatted messages. I, for one, delete
> > witho
Stephanie Wehner wrote:
>
> On Sat, Nov 04, 2000 at 10:47:27AM -0700, Wes Peters wrote:
>
> > It works fine for me. Try this little program and see if it successfully
> > attaches the shared memory segment:
>
> thx :) actually I think it might have something to do with jail then,
> cause this
In message <[EMAIL PROTECTED]> Sergey Babkin writes:
: Ah, right. I confused it with another case, where the probe routine
: tries to look for all possible ports. If I remember correctly,
: "aha" is an example of such device.
Yes. aha is pushing the upper limits of what is safe to do.
Warner
In message <[EMAIL PROTECTED]> Mike Smith writes:
: Well, I'm really sick of people complaining about not being able to get
: at the things the resource manager knows from userspace. So I've done
: something about it.
Cool. I've wanted this for some time now.
: 0: Interrupt request lines 0
On Sat, Nov 04, 2000 at 11:52:35 -0800, Mike Smith wrote:
> > I'm wondering if this should have its own program, rather than squat
> > in on iostat ?
>
> Adding yet another program for such a trivial fragment of code seems
> kinda silly. If/when someone uses the other interfaces as well to get
37 matches
Mail list logo
