I'm writing a kernel module for my own needs. AFAIK the following
methods could be used:
1) allocate not used system call with help of SYSCALL_MODULE macro
2) allocate proprieatry oid via SYSCTL_OID(OID_AUTO) and write an
appropriate sysctl handler(s)
3) add a file in /dev and use ioctl(2) call
On Wednesday 10 August 2005 05:11 pm, Sergey Uvarov wrote:
> John Baldwin wrote:
> > On Wednesday 10 August 2005 04:29 pm, Sergey Uvarov wrote:
> >>Hello hackers,
> >>
> >>I'm writing a kernel module for my own needs. AFAIK the following
> >>methods could be used:
> >>
> >>1) allocate not used syst
John Baldwin wrote:
On Wednesday 10 August 2005 04:29 pm, Sergey Uvarov wrote:
Hello hackers,
I'm writing a kernel module for my own needs. AFAIK the following
methods could be used:
1) allocate not used system call with help of SYSCALL_MODULE macro
2) allocate proprieatry oid via SYSCTL_OID
On Wednesday 10 August 2005 04:29 pm, Sergey Uvarov wrote:
> Hello hackers,
>
> I'm writing a kernel module for my own needs. AFAIK the following
> methods could be used:
>
> 1) allocate not used system call with help of SYSCALL_MODULE macro
>
> 2) allocate proprieatry oid via SYSCTL_OID(OID_AUTO)
On 8/10/05, Sergey Uvarov <[EMAIL PROTECTED]> wrote:
> Hello hackers,
>
> I'm writing a kernel module for my own needs. AFAIK the following
> methods could be used:
>
> 1) allocate not used system call with help of SYSCALL_MODULE macro
>
1 syscall
> 2) allocate proprieatry oid via SYSCTL_OI
Hello hackers,
I'm writing a kernel module for my own needs. AFAIK the following
methods could be used:
1) allocate not used system call with help of SYSCALL_MODULE macro
2) allocate proprieatry oid via SYSCTL_OID(OID_AUTO) and write an
appropriate sysctl handler(s)
3) add a file in /dev a
Whoops, I replied to the first message wrong, so I'll bring it back
to the list...
I don't have access at the moment to a FreeBSD box to point to
specifics, but I'd recommend looking at ifconfig sources (/usr/src/
sbin/ifconfig/ifieee80211.c?) to see which ioctl is being called for
the t
> The above lines came from FreeBSD's /usr/include/sys/stat.h
>
> Note that it includes and not
>
> There are many other examples in the FreeBSD system includes, at
> least once you get to the 5.x-series of FreeBSD. I don't remember
> if we were doing that in the 4.x-series.
In 4.x I
Regrettably, i always encountered this problem. I spoke about that
>>> since the middle of 2004, and didn't really receive feedback on this.
>>> I try a lot of things but none worked better than the other.
>>>
>>> To not forget about it, i filled a bug report on this particular
>>> problem, s
> > Can you point me to a real-life example where such a mechanism is
> > used? I'd like to have a closer look at it.
>
> /usr/include/sys/types.h :-)
Thank you :-) Now, I found the comment in
/usr/include/machine/ansi.h that also describes this mechanism.
Thanks for all other answers, as
I just tried a clean install of 6.0 Beta 2, and still the same problem,
but now with additional error messages:
re0: link state changed to UP
re0: link state changed to DOWN
re0: link state changed to UP
re0: link state changed to DOWN
Over and over and over, whenever the LED on the network j
On Wednesday 10 August 2005 15:09, alexander wrote:
> I tried to write a little C app that uses sysarch and i386_set_ioperm to
> gain access to certain ports and after a bit of testing I'm pretty sure
> that there is a bug or better a timing issue with the sysarch syscall or
> the
> i386_set_ioperm
At 12:06 PM +0200 8/10/05, Dirk GOUDERS wrote:
> To get around this in user-space, we do things like create
> /usr/include/sys/_types.h
>
> And then our include files include *that* file, and do not include
> the standard . This file, in turn, does
> not define any of the actual symbols.
I noticed that when I control the signal strength through
ifconfig, I can effectively reduce the signal when I set it
as something like: ifconfig ath0 txpower 1. I have read
that this input is device driver dependent and I couldn't
find anything in the interface that handles txcontrol. Are
these
On Wednesday 10 August 2005 09:18 am, iv gan wrote:
> I am not so sure because the script cannot detect different devices.
> It can be ad or ar or whatever but it cannot chechk for it. And what I
> would like to do is more to detect the device and then to do something
> like 10% to /, 20% to /tmp 3
I did some more research, it appears that the Abit AA8-DuraMax actually
uses the RealTek RTL8100S chipset, not the 8169.
The hardware compatibility list for 5.4 shows support for the 8110S
chipset, but not my specific motherboard. Perhaps it is a new chip
revision?
I tried the patch by Da
I've been requested (by Fernando) to pass the word that the new Open1X
(802.1x supplicant) has support for FreeBSD "wired" mode (over Ethernet)
built-in! This is important as now both wireless (via builtin WPA support)
and wired modes can be used (client-side).
Here's the announcement:
From:
Hello, hackers :)
I am implementing a custom filesystem, based on nullfs, its purpose is
tracking changes made to the fs,
and the idea is to do that by changing the semantics of (largely unused
anyway) atime attribute of the underlying UFS
(which is mounted -o noatime for that reason. and I don
A number of times yesterday. That's a first on this system, though
I've seen the lock order reversal problem with ffs suspend vs fsync().
Anyhoo, the traces:
Aug 9 15:08:26 wattres kernel: KDB: stack backtrace:
> kdb_backtrace(c0931dd8,2,c5afb0cc,0,22) at kdb_backtrace+0x2f
> getdirtybuf(d0287b
I am not so sure because the script cannot detect different devices.
It can be ad or ar or whatever but it cannot chechk for it. And what I
would like to do is more to detect the device and then to do something
like 10% to /, 20% to /tmp 35% to /var and 35% to /usr or something
like it.
Any suggest
I tried to write a little C app that uses sysarch and i386_set_ioperm to gain
access to certain ports and after a bit of testing I'm pretty sure that there
is a bug or better a timing issue with the sysarch syscall or the
i386_set_ioperm procedure. Please have a look at the following code:
//CODE
On Tue, 9 Aug 2005, Bob Bomar wrote:
> I have a machine that is about to turn 700 days uptime, and I have no
> plans on rebooting it any time soon. I just wanted to see if there was
> any infomation from the machine that anybody wanted.
Its IP address would be a good start :-)
Two years of pa
On Tue, 9 Aug 2005, Bob Bomar wrote:
> I have a machine that is about to turn 700 days
> uptime, and I have no plans on rebooting it any
> time soon. I just wanted to see if there was
> any infomation from the machine that anybody
> wanted.
Well, I think there are enough people around with nnn d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a machine that is about to turn 700 days
uptime, and I have no plans on rebooting it any
time soon. I just wanted to see if there was
any infomation from the machine that anybody
wanted.
[EMAIL PROTECTED] ~>uname -a
FreeBSD bart. 4.8-RELE
At 03:11 AM 8/10/2005, iv gan wrote:
Yep that's write.
but there is no way to script a generic install so to install on
different drives with different sizes.
So for that there is maybe a way to change something in the sysintall
sources. But without any success for the moment
I don't see anythi
At 02:39 AM 8/10/2005, iv gan wrote:
Hi there,
I try to make a custom installation of FreeBSD 5.3 in a way that there
are no questions during the process but rather it detects the hard
disk size makes the partitions etc...
For the moment I smply try to compile sysinstall (cd
/usr/src/usr.sbin/sys
At 12:19 PM 8/9/2005, David Gilbert wrote:
> "Frank" == Frank Mayhar <[EMAIL PROTECTED]> writes:
Frank> On Tue, 2005-08-09 at 14:51 -0400, David Gilbert wrote:
>> But ... since there are long patches of time where I'm not mobile,
>> I was wondering if anyone had looked at using a Bluetooth G
Hi Dirk,
> Can you point me to a real-life example where such a mechanism is
> used? I'd like to have a closer look at it.
/usr/include/sys/types.h :-)
Regards,
--
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >
___
freebsd-hac
On 10 Aug, Dmitry Morozovsky wrote:
> Colleagues,
>
>
> from ffs_alloc.c:
>
> case FS_OPTSPACE:
> /*
> * Allocate an exact sized fragment. Although this makes
> * best use of space, we will waste time relocating it if
> *
On Sat, 2005-Aug-06 21:49:35 +1000, Peter Jeremy wrote:
>I recently upgraded gnucash and dependencies and am now getting SIGILL
>during startup. This originally occurred on 5.3 but I'm getting
>exactly the same thing running on a recent -CURRENT with a freshly
>built (from scratch) ports tree.
We
Yep that's write.
but there is no way to script a generic install so to install on
different drives with different sizes.
So for that there is maybe a way to change something in the sysintall
sources. But without any success for the moment
Thanks
Ivo
On 8/10/05, Glenn Dawson <[EMAIL PROTECTED]> w
> To get around this in user-space, we do things like create
> /usr/include/sys/_types.h
>
> And then our include files include *that* file, and do not include
> the standard . This file, in turn, does
> not define any of the actual symbols. Let's say that some include
> file needs to k
Colleagues,
from ffs_alloc.c:
case FS_OPTSPACE:
/*
* Allocate an exact sized fragment. Although this makes
* best use of space, we will waste time relocating it if
* the file continues to grow. If the fragmentation is
Hi there,
I try to make a custom installation of FreeBSD 5.3 in a way that there
are no questions during the process but rather it detects the hard
disk size makes the partitions etc...
For the moment I smply try to compile sysinstall (cd
/usr/src/usr.sbin/sysintall && make all)
and it compiles wit
>> Regrettably, i always encountered this problem. I spoke about that
>> since the middle of 2004, and didn't really receive feedback on this.
>> I try a lot of things but none worked better than the other.
>>
>> To not forget about it, i filled a bug report on this particular
>> problem, see PR k
On 8/10/05, Julien Gabel <[EMAIL PROTECTED]> wrote:
...
> Regrettably, i always encountered this problem. I spoke about that since
> the middle of 2004, and didn't really receive feedback on this. I try a
> lot of things but none worked better than the other.
>
> To not forget about it, i filled
> I recently installed FreeBSD 5.4 on an ABIT AA-8 DuraMax and all went
> well. All hardware detected properly and everything was running great,
> until I got to configuring my network. ifconfig shows my onboard
> gigabit LAN as "status: no carrier"
>
> I can successfully ping localhost and the I
M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: On Tue, Aug 09, 2005 at 01:37:34PM -0600, M. Warner Losh wrote:
: > I have recently purcahsed a device that comes with a .so for linux,
: > but no sources. Is there any way one can take a
38 matches
Mail list logo
