--- Mike Bristow <[EMAIL PROTECTED]> wrote:
>
> And manual pages in section 9 of the manual, eg:
>
> $ man 9 printf
>
> will give you the docs for the printf that you can call in kernelspace.
Yes, however I can't find a man page that nicely outlines all of the
kernel libc-like functions availab
Hello Paolo,
--- Paolo Pisati <[EMAIL PROTECTED]> wrote:
>
> As a general rule of thumb,
> which are the safe libraries we can link against
> while developing a kernel module?
The standard C libraries that we have all come to know and
love can only be used from user space. This is mainly beca
Hello Jose,
--- Jose Hidalgo Herrera <[EMAIL PROTECTED]> wrote:
> There is something wrong here:
>
> srv0:~# uname -r
> 4.9-RELEASE-p4
>
> srv0:~# df -hi /
> FilesystemSize Used Avail Capacity iused ifree %iused Mounted on
> /dev/ad0s1a 126M 125M -8.9M 108%1364 148908%
Hello Mark,
Use the MAKEDEV script in /dev . Unfortunately I don't have a 4.x
system available to look up the arguments for you, and it has been
removed from 5.x since devfs became mandatory. But the man page
for MAKEDEV(8) on a 4.x system should help.
Cheers,
-brian
--- Mark <[EMAIL PROTECTED
Hello Xin LI,
According to the FreeBSD web site, you can use cvsup to download
the source code for almost any version of FreeBSD that ever existed.
Check this out:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-CONFIG-VERS
However, CVS branch tags only appear to be li
--- GiZmen <[EMAIL PROTECTED]> wrote:
> > On Sunday, 25 April 2004 at 20:42:07 +0200, GiZmen wrote:
> > > Hello,
> > >
> > > I have problem with gdb. When i start gdb as a regular user or even user
> > > i wheel group, i cant debug program that i want. I start gdb with my
> program
> > > and i set
--- Brandon Erhart <[EMAIL PROTECTED]> wrote:
> Not that I know of, but it should be a breeze to write a simple parsing
> engine.
> Just ignore all lines starting with a '#', and break at the '=' sign. The
> first part would be your variable name, the last part your value for it.
Don't forget to
Hello Warner,
--- "M. Warner Losh" <[EMAIL PROTECTED]> wrote:
>
> Basically, you add it to sys/dev/pccard/pccarddevs, run make -f
> Makefile.pccarddevs in that directory, then add the line you talked
> about in your other email to if_wi_pccard.c. The first part of this
> is desirable reguardless
Hello Warner,
Sorry for being unclear. I didn't mean to say that those changes worked,
I was asking if they were correct so far. Also, I asked where I should
specify the product id, because I suspect that I need to add that to
some other table (please see the end of my comments in my previous e-
how it goes.
Thanks for all your help. I'll let you know how it goes, and if it
works, I'll post a diff (from -CURRENT).
-brian
--- "M. Warner Losh" <[EMAIL PROTECTED]> wrote:
> In message: <[EMAIL PROTECTED]>
> "Brian O'Shea&q
Hello Warner,
Thanks for your reply.
--- "M. Warner Losh" <[EMAIL PROTECTED]> wrote:
> In message: <[EMAIL PROTECTED]>
> "Brian O'Shea" <[EMAIL PROTECTED]> writes:
> : pccard0: (manufacturer=0x000b, product=0x7110) at function 0
&
Hello,
I'm running FreeBSD 5.2.1-RELEASE on an HP OmniBook 4150 laptop. I
have a D-Link DWL-650 802.11b wireless ethernet card that doesn't seem
to be recognized. I have built a kernel with the wi and wlan drivers:
devicewlan
devicewi
Relevant boot messages:
cbb0: at device 4
Sorry for the late response on this. I've been trying various combinations
of kernel options in an attempt to narrow down the problem.
--- Don Lewis <[EMAIL PROTECTED]> wrote:
> On 23 Feb, Brian O'Shea wrote:
> > --- Don Lewis <[EMAIL PROTECTED]> wrote:
> >&
--- Brian O'Shea <[EMAIL PROTECTED]> wrote:
> --- Mathew Kanner <[EMAIL PROTECTED]> wrote:
> >
> > Hello Brian,
> > Don Lewis commited changes to the 5.2- tree on 2/14. Could
> > you update and try again, also please do run with witness and
--- Don Lewis <[EMAIL PROTECTED]> wrote:
>
> The cause of deadlocks is more likely to be caught by WITNESS. In this
With WITNESS the hang still occurrs, and still no panic. It's hard to
tell since the problem tends to happen at random times, but it seems like
it happens more quickly with the ke
--- Mathew Kanner <[EMAIL PROTECTED]> wrote:
>
> Hello Brian,
> Don Lewis commited changes to the 5.2- tree on 2/14. Could
> you update and try again, also please do run with witness and
> invariants, and if possible try to get a crashdump so we can see
> what's happening.
Sure. I'l
Hello Hackers,
My system:
$ uname -a
FreeBSD apsara 5.2.1-RC FreeBSD 5.2.1-RC #0: Sat Feb 7 21:38:15 PST 2004
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/APSARA i386
$ dmesg | grep pcm
pcm0: port 0xd400-0xd4ff irq 16 at device 14.0 on pci0
(full dmesg output attached)
Occasionally my sy
--- Peter Pentchev <[EMAIL PROTECTED]> wrote:
> > Here you got sample kernel module which do this:
> >
> > http://garage.freebsd.pl/usmalloc.tgz
> > http://garage.freebsd.pl/usmalloc.README
>
> E... but won't this interfere *badly* with userland programs
> which attempt to allocate me
Hi Poul-Henning,
--- Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED]>, Bernd Walter writes:
> >On Wed, Jun 04, 2003 at 10:44:53PM -0700, Brian O'Shea wrote:
> >> System panics after PQI Travel Flash (USB Compact Flash reader/writer m
--- Bernd Walter <[EMAIL PROTECTED]> wrote:
>
> Considering that we may require quirks for usb-ata converters but see
> the drives in scsi_da I agree.
> In this case it's not critical - the quirks are not wrong for my
> version, just not required.
> Nevertheless: Does it panic without quirk or sim
--- Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED]>, Bernd Walter writes:
> >On Wed, Jun 04, 2003 at 10:44:53PM -0700, Brian O'Shea wrote:
> >> System panics after PQI Travel Flash (USB Compact Flash reader/writer mass
System panics after PQI Travel Flash (USB Compact Flash reader/writer mass
storage device) is plugged in.
This is 5.0-RELEASE on i386.
I built a debug kernel to get a better crash dump and reproduced the problem:
makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols
# Kernel debug
Danny,
If you built your packages from ports, you could always reinstall them.
You just have to check for /usr/ports///work/.install_done.*
It's not perfect, but you could use it to generate a quick list of ports
to selectively re-install.
Good luck,
-brian
--- Kris Kennaway <[EMAIL PROTECTED]>
m
> as far as i am aware. it uses a single large file to emulate (much
> like loopback image) or a disk partition (same a multi-boot).
VMware can use a physical disk or a large file as a virtual disk.
-brian
--
Brian O'Shea(408) 822-3249<[EMAIL PROTECTED]> 3.3.1
you could run VMware [1] on Windows with FreeBSD running in a virtual
machine. It's kind of a round-about way to do it, but it would probably
work.
-brian
1. http://www.vmware.com/
--
Brian O'Shea(408) 822-3249<[EMAIL PROTECTED]> 3.3.163(Pen)
"Stare not to
evens' book explains. Only the signal mask is
copied. The signal mask has nothing to do with the addresses of the
signal handlers.
Hope that helps,
-brian
--
Brian O'Shea "Stare not too deeply into the pen, <[EMAIL PROTECTED]>
3.3.163(PEN) lest the pen stare back int
address of the handler function. It is
the bit mask which determines which signals are blocked.
> 3) Is my using of exec, in fact, the best way to
> reload the program on the fly, from within itself?
> What would be the best, robust, way to do this in the
> future?
I think that ex
put those into /boot/loader.conf
So to clarify, if I just add these lines as-is to /boot/loader.conf,
these sysctl variables will be set on the next boot?
The current contents of loader.conf on this system is:
# -- sysinstall generated deltas -- #
userconfig_script_load="YES"
Thanks,
-STABLE as I have had some bad
experiences doing that. Possibly a monthly upgrade while closely
monitoring the -stable mailing list for known problems would be
feasible.
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
;t know how to
analyze the crash dump to determine where the problem is. Any
suggestions are welcome.
Thanks,
-brian
--
Brian O'Shea
<[EMAIL PROTECTED]>
#
# SHAOLIN -- Kernel based on the GENERIC configuration file for FreeBSD/i386
#
machine i386
cpu I686_CPU
ident
To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
even with select() scenarios. They
> implement the Highlander principle - there can be only one (pcap).
> Sad.
>
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
VMware
virtual disk? Also, what version of FreeBSD are you running?
Thanks,
-brian
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
talled in a virtual machine
Disk type is VMware virtual disk (i.e. not a physical partition)
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
m reponce.
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
--
Brian O'Shea
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
the fork() call. I don't know if gdb has support for
doing this automatically. I don't think it does, but you might be
able to attach to it in another gdb session by having the child
process sleep for a while shortly after the fork() call to give you
enough time to look up the PID of t
e you seriously.
This is a shame considering that you might have important issues to
raise.
Good luck on your talk,
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, Nov 13, 2000 at 11:56:37AM -0700, Nicole H wrote:
>
> On 13-Nov-00 Brian O'Shea wrote:
> > Nicole,
> >
> > Is it a panic, or does it just silently reboot? If it's a panic,
> > what is the panic message, or any other message on the console when
&g
:coredumpsize=infinity:\
> :maxproc-cur=64:\
> :openfiles-cur=64:\
> :priority=0:\
> :requirehome@:\
> :umask=022:\
>
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ps(1), systat(1), pstat(8),
vmstat(8)
What information are you looking for specifically?
Have a look at systat(1). It presents the activity on your system
nicely, breaking it down into several descriptive categories which
are documented in the man page.
Try this:
$ systat -io
Hope that h
nce many of us (perhaps most of us) don't use mailers that can
render HTML. Such messages are often ignored.
Thanks for re-sending it as plain text. :)
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
gt; Regards,
>
> phpStop.com http://www.phpstop.com/
> stop here. start everywhere. mailto:[EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
freed malloc()'ed memory. If it is a memory
leak, the only way to free the memory is to kill the process that is
leaking it.
> --
> Never trust an operating system you don't have sources for. ;-)
Don't get too comfortable. <http://www.acm.org/classics/sep95/>
;)
-
t () from /usr/lib/libc.so.3
#2 0x80484a8 in main (argc=1, argv=0xbfbfd6ec) at handler.c:17
#3 0x8048419 in _start ()
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
at that support is, or how to
> > use it.
>
> That's platform-dependant. On the x86, a conforming APM BIOS is required
> (or a device driver with a suitable hook for some other control
> interface).
apm0: on motherboard
apm: found APM BIOS v1.2, connected at v1.2
Excellent
() system call to power off the
machine when the RB_POWEROFF flag is set? The man page makes mention of
hardware support, but doesn't specify what that support is, or how to
use it.
Thanks,
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
to
their limit of child processes, each child of which will do the same,
ad infinitum (well, until maxproc is reached and you can't create any
more processes and your system is wedged again). The kern.maxprocperuid
sysctl addresses this problem better.
-brian
--
Brian O'Shea
[EMAIL
aftrer this.
> >
> > On Fri, 7 Jul 2000, lgrajales wrote:
> >
> > |>
> > |> What is a Code Pal for VMS?
> > |> thnxs.
> > |>
>
> [snip - sigs]
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscr
On Tue, Jun 13, 2000 at 01:23:15PM -0700, Brian O'Shea scribbled:
>
> ... I will give them contact informatin for Mike Smith and
> David Greenman per Mike's followup).
^^
Oops. I mean David O'Brien.
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Uns
and emulator? I've done
a quick search for information about it and can't find any. I am
posting this question to an internal HP newsgroup (responses to which,
of course, I can not repost here, but I will give them contact
informatin for Mike Smith and David Greenman per Mike's foll
impose on it? Do you want to enforce
unique identifiers? Globally unique or just unique within a section?
Should this be configurable (with a config file?! ;) ? Why not just use
xml? (the token xml suggestion, sorry)
All of this is managable, it just seems like more trouble than it's
worth.
>From the LINT kernel config file:
config kernel root on wd0 dumps on wd0
Maybe you forgot the 's' in "dumps"? I have never tried this so I can't
say for sure. Just noticed this in your post.
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: s
nt.
>
> 2-3 mm is exact enough for this?
Even with SA, much more accurate numbers could be obtained by averaging
several measurements. I think that the speed at which the earth's
plates move is slow enough to get a good average measurement (except
during an earthquake, of course!
ner/Sun, Fyodor Yarochkin/KALUG, Max Vision/whitehats.com
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, Apr 24, 2000 at 09:58:49PM -0500, Chris Costello wrote:
> On Monday, April 24, 2000, Brian O'Shea wrote:
> > Yea, I took a look at lib/libc_r/uthread/uthread_read.c too, but it
> > didn't paint the whole picture for me. Specifically, I couldn't f
me.
Yea, I took a look at lib/libc_r/uthread/uthread_read.c too, but it
didn't paint the whole picture for me. Specifically, I couldn't find
the definition for the _thread_sys_read() function. It looks like the
polling magic to which Jason Evans referred occurs in some interesting
code in uth
there. Call conversion works very well for sockets.
Wow, a page reference to the same book that I am reading. Kind of
embarrassing that the answer to my question was on the page after the
one that I mentioned.
Thanks, that's exactly what I was looking for.
-brian
>
> Jason
>
On Mon, Apr 24, 2000 at 06:13:53AM -0400, Daniel Eischen wrote:
> On Mon, 24 Apr 2000, Brian O'Shea wrote:
> >
> > I was under the impression that, because user thread scheduling is done
> > in user mode, a thread that goes to sleep calling a blocking read()
> >
> rfork(), which can be made to behave like Linux's clone().
>
> Jason
Please correct me if I am wrong.
Thanks,
-brian
--
Brian O'Shea
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
59 matches
Mail list logo
