:don't think there's any way to get rid of the warning without changing
:the declarations.
:
:In my opinion, the use of -Wcast-qual is bogus. Often the whole
:point of a cast is to remove a qualifier such as const. It's one
:thing to warn when that's done implicitly, and quite another thing to
../../dev/usb/ukbd.c: In function `ukbd_detach':
../../dev/usb/ukbd.c:373: warning: cast discards `const' from pointer
target type
...
It is a consequence of the following type definition:
(sys/bus_private.h)
struct device {
...
const char* desc; /* driver specific description */
Hello! Five minutes ago I type 'nfsstat' and got:
nfsstat: sysctl: No such file or directory
I take a look at the source and that's what I found:
Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS,
but name[1] has a value of vfc.vfc_typenum, returned by getvfsbyname(3).
It sounds like a good idea, and it is. What I want to see is scsi_da use
this automatically. I have never liked the punch it, Chewey! approach
CAM has been taking.
What do you mean scsi_da use this automatically?
All of the tagged queueing stuff is controlled in the transport
Mr. Rabson-
Sorry it's been so long for me to get back to you about the patch you sent.
The machine is located accross country 3 time zones away, so coordinating
with the people at the console has been tedious.
In any case, the patch worked brilliantly. The machine is now running a 4.0
Anyone care to look at LINT and GENERIC and in particular at the ppc0 line?
GENERIC lists ppc0 as a device, LINT as a controller.
Since config accepts GENERIC's format I'm inclined to think that's the
correct one. But one of my own files has controller in it and is also
accepted, but I don't
parts of proc (p_vmspace etc.) For that matter, does any of kern_exit.c:exit1()
need to be spl()d? It sure seems like it to me. Along with other parts of
kern_exit.c, and many other things having to do with refcnt's. Is it just my
paranoia, or have I got this spl concept correct?
spl is for
On Sun, 21 Feb 1999, Benjamin Lewis wrote:
Mr. Rabson-
Sorry it's been so long for me to get back to you about the patch you sent.
The machine is located accross country 3 time zones away, so coordinating
with the people at the console has been tedious.
In any case, the patch worked
On Sun, 21 Feb 1999, Bruce Evans wrote:
Hello! Five minutes ago I type 'nfsstat' and got:
nfsstat: sysctl: No such file or directory
I take a look at the source and that's what I found:
Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS,
but name[1] has a value
On Sun, 21 Feb 1999, Bruce Evans wrote:
Hello! Five minutes ago I type 'nfsstat' and got:
nfsstat: sysctl: No such file or directory
I take a look at the source and that's what I found:
Nfsstat gets statistic via sysctl(3). name[0]=CTL_VFS, name[2]=NFS_NFSSTATS,
but name[1] has a value
Now that it is possible to change the sysctl tree at runtime, the changes
are not actually (completely) made for vfs sysctls. Special code for
making impossible changes for vfs sysctls went away.
Oh. Thats nasty. I don't want to allocate special oids for 'privileged'
nodes. I think the
In message 199902211232.xaa05...@godzilla.zeta.org.au, Bruce Evans writes:
Index: nfsstat.c
===
RCS file: /home/ncvs/src/usr.bin/nfsstat/nfsstat.c,v
retrieving revision 1.12
diff -u -r1.12 nfsstat.c
--- nfsstat.c 1998/10/25 10:59:44
Maxim Sobolev wrote:
I had the same problem, when first installing SO5, and found workarround. W
hen
you start SO and get question do you want to register now, reply no, then
select menu Tools-Macro...-Organazer.. select Libraries tab and ena
ble
all libraries (by checking checkboxes).
The old interface is the standard one (although the above code shows how
inconvenient it is). mountd uses it too.
There is nothing less standard about sysctlbyname to my knowledge...
sysctl() is in Linux (starting in 2.1.x), BSD4.4, NetBSD, OpenBSD, etc.
sysctlbyname() is in FreeBSD (starting
On Mon, 22 Feb 1999, Bruce Evans wrote:
The old interface is the standard one (although the above code shows how
inconvenient it is). mountd uses it too.
There is nothing less standard about sysctlbyname to my knowledge...
sysctl() is in Linux (starting in 2.1.x), BSD4.4, NetBSD,
In message pine.bsf.4.05.9902211322320.82049-100...@herring.nlsystems.com, Do
ug Rabson writes:
Since
sysctlbyname exists and is obviously a better mechanism for reading the
variable (based on code complexity), then why not use it?
I support this. It was the intention of sysctlbyname() to
On Sun, Feb 21, 1999 at 12:19:08PM +0100, Jeroen Ruigrok/Asmodai wrote:
Anyone care to look at LINT and GENERIC and in particular at the ppc0 line?
GENERIC lists ppc0 as a device, LINT as a controller.
GENERIC wins.
Since config accepts GENERIC's format I'm inclined to think that's the
On Sun, 21 Feb 1999, Bruce Evans wrote:
parts of proc (p_vmspace etc.) For that matter, does any of
kern_exit.c:exit1()
need to be spl()d? It sure seems like it to me. Along with other parts of
kern_exit.c, and many other things having to do with refcnt's. Is it just my
paranoia, or have I
spl is for blocking interrupts. Process-related things shouldn't be and
mostly aren't touched by interrupts.
But without an spl, couldn't multiple processes do Very Bad Things in a
partially shared proc context?
They can do that with or without an spl if they don't lock things properly
spl
On Mon, 22 Feb 1999, Bruce Evans wrote:
spl is for blocking interrupts. Process-related things shouldn't be and
mostly aren't touched by interrupts.
But without an spl, couldn't multiple processes do Very Bad Things in a
partially shared proc context?
They can do that with or without
On Sun, 21 Feb 1999, Doug Rabson wrote:
Oh. Thats nasty. I don't want to allocate special oids for 'privileged'
nodes. I think the userland code should use sysctlbyname() instead.
This patch seems to fix it for me:
Works for me too. This problem exists not only in -current, i believe.
On Sat, Feb 20, 1999 at 08:02:17PM +, Lyndon Nerenberg wrote:
I've been trying to get some progamming doc out of TI for
the PCI1200 PCI/Cardbus bridge (used in the Dell Inspiron
7000), however they cannot seem to understand that I'm not
asking for a pre-written device driver :-(
Does
On Thu, 18 Feb 1999, Lyndon Nerenberg wrote:
Basically, it is a patch into libkvm and w, that will allow a user (with
the exception to the super user, naturally) to only view processes or
information belonging to him/herself.
The only problem with this is setuid binaries. The
Matthew Dillon wrote:
:
:In my opinion, the use of -Wcast-qual is bogus. Often the whole
:point of a cast is to remove a qualifier such as const. It's one
:thing to warn when that's done implicitly, and quite another thing
:to warn when the programmer has clearly expressed his intent through
There are PDF and zipped PostScript data sheets for these
parts on TI's web page:
http://www.ti.com/sc/docs/folders/analog/pci1211.html
Ya, I found those by doing a search inside the TI site. The
problem is the data sheets those URLs point to only
describe the hardware side of things.
While CardBus isn't supported, this controller (in my Fujitsu Lifebook 280dx)
works with PAO because the PCI-CardBus bridge supposedly uses some kind
of Intel-compatible mode. I've been unable to get it to work under stock
pccard without PAO (look at my post to -hackers yesterday), but it
Sorry it's been so long for me to get back to you about the patch you sent.
The machine is located accross country 3 time zones away, so coordinating
with the people at the console has been tedious.
In any case, the patch worked brilliantly. The machine is now running a 4.0
generic
I've noticed that as I'm constantly syncing my /usr/ports directory and
upgrading programs, the old packages stay there. If I pkg_delete them and
there's an unchanged file that exists in both the update and the original then
tat gets deleted too. Any way of cleanly removing old packages?
Matthew Jacob wrote...
It sounds like a good idea, and it is. What I want to see is scsi_da use
this automatically. I have never liked the punch it, Chewey! approach
CAM has been taking.
What do you mean scsi_da use this automatically?
All of the tagged queueing stuff is
On Sun, Feb 21, 1999 at 06:27:59PM +, Lyndon Nerenberg wrote:
While CardBus isn't supported, this controller (in my Fujitsu Lifebook
280dx)
works with PAO because the PCI-CardBus bridge supposedly uses some kind
of Intel-compatible mode. I've been unable to get it to work under
On Sun, 21 Feb 1999, Nathan Dorfman wrote:
# I looked at PAO, but it doesn't appear to support the 3.X
# branch, which I'm running. If there's a PAO for 3.X, please
# let me know where it is (!).
#
# That's why I can't run PAO (and consequently no PCMCIA working on my
# laptop at the
Hi All,
Anyone have any objections (now that we have dhclient in the tree)
to pointing pccard_ether at its new home?
-steve
Index: pccard_ether
===
RCS file: /home/ncvs/src/etc/pccard_ether,v
retrieving revision 1.10
diff -u -r1.10
Your bug fix is in my queue.
Alan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
I update 3-Stable nearly weekly, and have been experiencing the same problem
for quite a while now. NFS imports, on the client side appear to be losing
data. When this occurs, I see .nfs78969 files on the server side. The
program on the client side always freezes (top reports it's STAT as 'D').
Dennis Glatting wrote...
On the ST410800W I am getting, according to iozone:
FWIW, several people have reported bad performance with that
drive when tagged queueing is enabled. Their firmware
revisions, however, were 71xx, not 45xx. Apparantly drives
with firmware that starts with
Was the 3.0-RELEASE I got ~Dec 30 aout kernel? 'file /kernel' gives
/kernel: unknown pure executable
but 'strings /kernel | grep -i elf' gives
FreeBSD ELF
among other stuff.
So far, I just did 'make world' in /usr/src/, updated my
config per GENERIC diff, and built the kernel. The
So, should I send-pr?
-mi
Rahul Dhesi once stated:
=Many years ago I posted a shell script to Usenet in which I prepended a
=line with 'exec', in an attempt to avoid having a shell process hanging
=around doing a wait(). David Korn himself (of Korn shell fame)
=responded saying this
I update 3-Stable nearly weekly, and have been experiencing the same problem
for quite a while now. NFS imports, on the client side appear to be losing
data. When this occurs, I see .nfs78969 files on the server side.
These files exist because they've been deleted but not closed; this is
I fixed this a while back to use sysctlbyname, as it should have been
done. Bruce subsequently backed it out (bad idea, IMO).
You should file a PR or otherwise petition b...@freebsd.org to un-revert
his change.
Hello! Five minutes ago I type 'nfsstat' and got:
nfsstat: sysctl: No such
According to Wilson S. Ross:
Was the 3.0-RELEASE I got ~Dec 30 aout kernel? 'file /kernel' gives
Yes, the default kernel format was changed to ELF on Jan., 6th. 3.0-RELEASE
builds a.out kernel but you can generated ELF ones if you want.
- need to see req'd changes to /etc by inspecting
I fixed this a while back to use sysctlbyname, as it should have been
done. Bruce subsequently backed it out (bad idea, IMO).
You only worked around the previous breakage of vfs sysctls for the
statically configured case. The dynamically configured case was more
fundamentally broken (sysctls
41 matches
Mail list logo
