actually, i will code that as a pseudo device to manage
a small box over serial line that manages some external
devices.
and i was also curious to know how to do it in userland,
but i know i/o feels better in kernel
:-)
On Thu, Nov 07, 2002 at 10:23:16AM -0800, Julian Elischer wrote:
>
>
> On
> > > I'm writing an application that needs info on the machine cpu
> > > architecture, the cpu class, and the cpu features.
Why not just use the 'CPUID' instruction?
07.11.2002; 19:48:41
[SorAlx] http://cydem.zp.ua/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hacker
There is a way how FreeBSD kernel do it - /sys/i386/i386/identcpu.c and some
other files in that directory.
Also there is a port/package - /usr/ports/misc/cpuid
>I'm writing an application that needs info on the machine cpu >architecture,
>the cpu class, and the cpu features.
>
>The machine cpu a
Alex Newman wrote:
> > Yes, you could do this.
> >
> > The Netgraph TCP/IP is a good idea for research work, but a bad
> > idea for general implementation purposes, since it's performance
> > will be very poor, compared to a monolithic TCP/IP implementation.
>
> Interesting, why is click so fast th
On Thu, 7 Nov 2002, Sam wrote:
> On Thursday 07 November 2002 06:37 pm, Terry Lambert wrote:
> > Sam wrote:
> > > I'm writing an application that needs info on the machine cpu
> > > architecture, the cpu class, and the cpu features.
> >
> > Is this a status display (e.g. "About This Computer...")
> > Could we implement {bgp & ospf} in netgraph?
> > What would need to be done assuming the Netgraph TCP/IP happen?
> > Is this a bad idea.
>
> Yes, you could do this.
>
> The Netgraph TCP/IP is a good idea for research work, but a bad
> idea for general implementation purposes, since it's perf
Alex Newman wrote:
> Could we implement {bgp & ospf} in netgraph?
> What would need to be done assuming the Netgraph TCP/IP happen?
> Is this a bad idea.
Yes, you could do this.
The Netgraph TCP/IP is a good idea for research work, but a bad
idea for general implementation purposes, since it's p
On Thursday 07 November 2002 06:37 pm, Terry Lambert wrote:
> Sam wrote:
> > I'm writing an application that needs info on the machine cpu
> > architecture, the cpu class, and the cpu features.
>
> Is this a status display (e.g. "About This Computer...") for a human
> to read? If not, the entire p
Could we implement {bgp & ospf} in netgraph? What would need to be done assuming the
Netgraph TCP/IP happen? Is this a bad idea.
Alex Newman
[EMAIL PROTECTED] http://www.wuli.nu/users/dolemite
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the me
Sam wrote:
> I'm writing an application that needs info on the machine cpu architecture,
> the cpu class, and the cpu features.
Is this a status display (e.g. "About This Computer...") for a human
to read? If not, the entire point of an OS is to hide that information
from you, so that you can wri
Looking through some of the old kern PRs I can across PR kern/5863
(Kernel support for sorted SHUTDOWN & SHUTDOWN_POWEROFF queues).
I haven't looked through the whole thing, but it appears that the
idea behind this PR has committed by msmith@ some four years ago (see rev
1.41 of s
Julian Elischer wrote:
> Also look at ng_etf the ethertype filter..
> it is designed to connect to an ether node and filter out packets
> with a particular ethertype. yuo could alter it to examine for a
> particular tcp port number too.
[ ... ]
A more interesting problem is how to hook an address
I'm writing an application that needs info on the machine cpu architecture,
the cpu class, and the cpu features.
The machine cpu architecture seems to be available through
sysctl CTL_HW HW_MACHINE_ARCH. However, I can't find any mention
of what string values this returns. Is there a list of possib
Christoph Hellwig wrote:
> Umm, ispurely a userland header on linux, so he's probably
> referring to the userland versions of those that are provided by the
> linux ports with PC-like hardware..
Then the answer is even easier: Don't do it from userland, since you
should not be using sys header fi
Lukas Ertl wrote:
> how hard would it be to implement resizing of mounted filesystems?
> Currently, growfs requires the filesystem to be unmounted, and this is
> definitely a showstopper for FreeBSD when it comes to production use.
>
> I'd really like to promote FreeBSD more in my organisation, wh
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:33:02 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45119
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:32:50 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45118
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:32:38 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45117
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:32:22 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45116
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:32:08 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45115
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:31:50 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45114
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:31:38 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45113
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:31:26 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45112
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:31:14 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45111
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:31:00 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45110
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:30:46 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45109
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:30:34 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45108
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Synopsis: New Port: The /. report
State-Changed-From-To: open->closed
State-Changed-By: adamw
State-Changed-When: Thu Nov 7 12:30:18 PST 2002
State-Changed-Why:
Not a PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=45107
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-ha
Thank you very much for your problem report.
It has the internal identification `ports/45119'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45119
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45117'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45117
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45109'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45109
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45110'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45110
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45112'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45112
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45115'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45115
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45118'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45118
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45107'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45107
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45116'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45116
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45114'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45114
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45111'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45111
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45113'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45113
>Category:
Thank you very much for your problem report.
It has the internal identification `ports/45108'.
The individual assigned to look at your
report is: freebsd-ports.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=45108
>Category:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm traying to debug a fork()-ing process, and according the GDB manual pages
setting the 'follow-fork-mode' to 'child' will cause to switch to children.
So this could be the case if I'm attached to some process in GDB but in case
that I'm debu
On Thu, 7 Nov 2002, Steve Tremblett wrote:
> I've been toying with the idea of tackling a Netgraph TCP/IP
> implementation and want to hack out some skeleton netgraph nodes just
> to feel things out and play around with parsing. I'm somewhat confused
> on how to start. I'd like to be able to t
On Thu, 7 Nov 2002, John Baldwin wrote:
>
> On 07-Nov-2002 Julien Mabillard wrote:
> > hi,
> > can anyone tell me where inb(), outb() are defined
> > in the sources (FreeBSD RELENG_4_7 or CURRENT)?
> > on linux systems this is defined in
>
> For FreeBSD should be using bus_space_read_1() and
from memory, however note that outb has the
arguments in the opposite order.
On Thu, 7 Nov 2002, Julien Mabillard wrote:
> hi,
> can anyone tell me where inb(), outb() are defined
> in the sources (FreeBSD RELENG_4_7 or CURRENT)?
> on linux systems this is defined in
>
> thank you.
>
> -
+ Maksim Yevmenkin wrote:
| > I'm in a bit of a bind. I want a sequence of ethernet frames to send
| > up through this framework. Hooking to ng_ether will give me this but I
| > am restricted to taking ALL frames (thus taking the machine offline) or
| > orphaned frames (where I will have to w
Steve Tremblett wrote:
>
> I've been toying with the idea of tackling a Netgraph TCP/IP
> implementation and want to hack out some skeleton netgraph nodes just
> to feel things out and play around with parsing. I'm somewhat confused
> on how to start. I'd like to be able to tinker as I go and I'
I've been toying with the idea of tackling a Netgraph TCP/IP
implementation and want to hack out some skeleton netgraph nodes just
to feel things out and play around with parsing. I'm somewhat confused
on how to start. I'd like to be able to tinker as I go and I'd rather
not have to write 5000 li
FWIW, regarding direct user application access
to I/O space, (a technique to be avoided if at all
possible, but sometimes useful for those "1-hour
emergency" projects, see the question
"How do I directly access I/O devices from an application
program (use in and out instructions)?"
In the
On Thu, Nov 07, 2002 at 10:51:31AM -0500, John Baldwin wrote:
> Doing I/O from userland generally isn't supported. A header with
> is a kernel header though, not a userland one. :)
Only on traditional Unix systems. On Linux it never is.
> For i386-only, if
> you do the right calls to obtain pe
On 07-Nov-2002 Christoph Hellwig wrote:
> On Thu, Nov 07, 2002 at 09:33:29AM -0500, John Baldwin wrote:
>>
>> On 07-Nov-2002 Julien Mabillard wrote:
>> > hi,
>> > can anyone tell me where inb(), outb() are defined
>> > in the sources (FreeBSD RELENG_4_7 or CURRENT)?
>> > on linux systems this is
On Thu, Nov 07, 2002 at 09:33:29AM -0500, John Baldwin wrote:
>
> On 07-Nov-2002 Julien Mabillard wrote:
> > hi,
> > can anyone tell me where inb(), outb() are defined
> > in the sources (FreeBSD RELENG_4_7 or CURRENT)?
> > on linux systems this is defined in
>
> For FreeBSD should be using bus_
great, thanks :-)
On Thu, Nov 07, 2002 at 09:33:29AM -0500, John Baldwin wrote:
>
> On 07-Nov-2002 Julien Mabillard wrote:
> > hi,
> > can anyone tell me where inb(), outb() are defined
> > in the sources (FreeBSD RELENG_4_7 or CURRENT)?
> > on linux systems this is defined in
>
> For FreeBSD s
Hi hackers,
how hard would it be to implement resizing of mounted filesystems?
Currently, growfs requires the filesystem to be unmounted, and this is
definitely a showstopper for FreeBSD when it comes to production use.
I'd really like to promote FreeBSD more in my organisation, where we
currentl
On 07-Nov-2002 Julien Mabillard wrote:
> hi,
> can anyone tell me where inb(), outb() are defined
> in the sources (FreeBSD RELENG_4_7 or CURRENT)?
> on linux systems this is defined in
For FreeBSD should be using bus_space_read_1() and bus_space_write_1()
instead. However, you can find inb() a
hi,
can anyone tell me where inb(), outb() are defined
in the sources (FreeBSD RELENG_4_7 or CURRENT)?
on linux systems this is defined in
thank you.
Key fingerprint = D34A 577C 869B 28A2 3886 4298 50CB DC18 31A4 ACAD
On 14:34+0300, Nov 7, 2002, Mathieu Arnold wrote:
> Hi
>
> I'm having a bit of difficulties with pthreads, lets explain :
>
> $ cat test.c
> #include "pthread.h"
Shouldn't it be ?
> void * test (void* t) {
> while (1) {
> printf("pouet");
Use printf("pouet\n") of fflush stdo
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hi
I'm having a bit of difficulties with pthreads, lets explain :
$ cat test.c
#include "pthread.h"
void * test (void* t) {
while (1) {
printf("pouet");
sleep(1);
}
}
main () {
pthread_t th;
if (pthread_create(&th, NULL, test, NULL
> > Um, why did you reimplement strtoll(3)?
Hmmm, not necessary indeed...
Zlo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Wed, Nov 06, 2002 at 05:14:54PM -0800, Nate Lawson wrote:
> On Thu, 7 Nov 2002, Marc Olzheim wrote:
> > With some minor modifications to disklabel, you can label a 2 Tb disk.
> > We've done it with a 1.4Tb disk:
> >
> > Filesystem Size Used Avail Capacity Mounted on
> >
61 matches
Mail list logo