sparc64 tinderbox failure
Thu Jun 13 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Permission denied To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: looking for warn quota tools
Terry Lambert wrote: > For this to work, you would have to serialize access to maildrops > by receiver SMTPs (this is an intractable problem), AND you would > need to reject mail sent without the "SIZE" extension, or mail > whose actual size exceeded that specified by the "SIZE" extension > (you are not permitted to do this last, since the "SIZE" extension > is defined, by standard, to be advisory, not regulatory). This is > on top of the other coupling requirements. To elaborate a little on why this is bad, consider the delivery of a message to (A,B,C) that lock maildrops, but occurs concurrently with another deliver to (C,H,I,J,K,L,M,N,O,P,A). Thus, a deadlock may occur during the locking stage. The problem with this is that for each "RCPT TO:" line, you must respond with a success/failure notification to the peer SMTP server, so if you depend upon the locking occurring, then the only method you have of rejecting in the case noted above is to fail the DATA request, since the "MAIL FROM:" and one or more "RCPT TO:" have already been accepted. Thus the very design of the protocol is antithetical to the locking of maildrops to provide the enforcement which you seek. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: looking for warn quota tools
David Taylor wrote:
> > FWIW: It's kind of a dumb idea to send email warning about a
> > condition which is caused by having too much email. We did
> > this on the InterJet, and it was actually a pretty dumb thing
> > to do; you end up with a recursive problem that's unsolvable
> > -- you basically have to let certain cenders be "priviledged"
> > for the delivery of the messages, which means hacking both
> > the MDA ("deliver") and "warnquota".
>
> In that case, why not just hack pop3d/imapd/whatever to display a
> 'virtual' e-mail of some type when the user connects. It could be
> complicated to avoid simply generating a new message every time the user
> connects without storing the time the last warning was received, I guess.
I already suggested that at the end of my email from which you are
quoting. 8-).
> > Another issue is that quota enforcement only occurs *after*
> > you exceed the quota, not *when* you exceed the quota. This
> > is because email messages must be treated as atomic units; so
> > if you are within 3k of a 100k quota, and you get an 80k message,
> > you can't not accept it.
>
> Why not? I can't see how you can't just bounce it. You may have accepted
> it, but that doesn't guaranteee delivery, just that you won't drop it on
> the floor.
The quotas in the Cyrus IMAP are implemented differently than you
appear to believe they are. I've already indicated why messages
must be treated as atomic units, and that quotas are enforced after
the fact, because that's often the only time that you can have an
accurate size measurement available.
Your idea of bouncing the message to the sender is flawed, unless
you are willing to drop the message on the floor.
Consider the case of two accounts. The first account is over quota.
It sends a message to the second account. The message would put
that account over quota (this scenario is to pay homage to your idea
that you could bounce instead of determine after the fact; even so,
if both accounts are over quota, the same logic applies). So you
bounce the message back to the first account. Only the first account
can not accept the bounce, because it is over quota.
Thus you must explicitly allow administrative messages to bypass
quota, in your scenario, if you accept responsibility for a message
that it turns out that it's impossible for you to deliver.
So... you avoid being screwed at one level, only to be screwed as
a result of a cascade failure.
> > The way "HotMail" handles this condition is to drop email that
> > it has accepted to delivery, if it can't be delivered to the
> > user because of them being over quota. But since it has
> > already accepted the email for delivery (by sending "250 OK"
> > to the remote SMTP client or MTA, it has pledged to deliver
> > the message, or give failure notification, so the message
>
> So why not give failure notification?
I thought I made this clear: because the addresses are responded
to as valid before the message size is known. The only recourse
is to fail the message atomically, regardless of the number of
recipients, after the size is known -- after the "DATA" command,
the "354 Continue" response, and the acceptance of data, followed
by the ".", but *before* you return a "250 OK" or, in your suggested
case, a "451 One of the recipients specified has exceeded quota".
Please see RFC-1870 "SMTP Service Extension for Message Size
Declaration" and RFC-2821 "Simple Mail Transfer Protocol (SMTP)".
It's only in the case that the "SIZE" extension is utilized, the
sender has not lied, and another delivery does not complete
simultaneously before the message is complete, that permits you
to do what you want. Even so, it rtequires the much tighter
MSA/MTA/MDA coupling I described previously.
For this to work, you would have to serialize access to maildrops
by receiver SMTPs (this is an intractable problem), AND you would
need to reject mail sent without the "SIZE" extension, or mail
whose actual size exceeded that specified by the "SIZE" extension
(you are not permitted to do this last, since the "SIZE" extension
is defined, by standard, to be advisory, not regulatory). This is
on top of the other coupling requirements.
Your performance would go into the toilet very quickly, if you did
this, particularly your agregate througput for a random (standard)
message load.
--
It's possible to construct examples, but this is not a mailing list
for discussion of SMTP server and protocol issues. Probably it
would be a good idea to take this discussion to http://www.imc.org/ ,
one of the mailing lists specific to your SMTP server software, or
one of the IETF lists, e.g. http://www.imc.org/ietf-smtp/index.html ;
the archive hoted there goes all the way back to 27 Dec 1990.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
subscribe
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Support for USB devices out-of-the-box in -current?
On Thu, 2002-06-13 at 14:38, Wilkinson,Alex wrote: > By who ? The USB maintainer.. Who's name escapes me at this point :) > - Alex > > Don't think so, but I am fairly sure it's being worked on. > -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Support for USB devices out-of-the-box in -current?
By who ? - Alex Don't think so, but I am fairly sure it's being worked on. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Support for USB devices out-of-the-box in -current?
On Thu, 2002-06-13 at 14:07, Wilkinson,Alex wrote: > Does -CURRENT support USD 2.0 yet ? Don't think so, but I am fairly sure it's being worked on. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Support for USB devices out-of-the-box in -current?
Does -CURRENT support USD 2.0 yet ? - Alex I believe that is already the case. If it doesn't find a ps/2 keyboard it will assume USB and wait until such a device is attached. (Which really sucks when your PS/2 keyboard isn't detected, but I digress...) usbd is run by sysinstall when it starts and I believe the right stuff is in the kernel to support mice as well, but I don't think it is 100% integrated (eg with the mouse setup widget). Note that these observations are based on -stable sources, so YMMV :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Support for USB devices out-of-the-box in -current?
On Thu, 2002-06-13 at 13:04, Jordan Breeding wrote: > number of systems ship with USB keyboards these days and it would be > nice to be able to use it during sysinstall if no PS/2 keyboard is > found. Thanks for any information about whether this will be a reality > in 5.0-RELEASE. I believe that is already the case. If it doesn't find a ps/2 keyboard it will assume USB and wait until such a device is attached. (Which really sucks when your PS/2 keyboard isn't detected, but I digress...) usbd is run by sysinstall when it starts and I believe the right stuff is in the kernel to support mice as well, but I don't think it is 100% integrated (eg with the mouse setup widget). Note that these observations are based on -stable sources, so YMMV :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Support for USB devices out-of-the-box in -current?
Hello, By the time -current turns into -release later this year will FreeBSD have support in sysinstall and in the GENERIC kernel and have all the right settings so that systems which only have USB keyboards and USB mice can work out-of-the-box even during installation from the CDROM? I don't know if it is really considered an issue or not but an increasing number of systems ship with USB keyboards these days and it would be nice to be able to use it during sysinstall if no PS/2 keyboard is found. Thanks for any information about whether this will be a reality in 5.0-RELEASE. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
#1 DIET PILL! LOSE 10-15 LBS PER WEEK+"BONUS" 6983
Hey there, If you're like me, you've tried EVERYTHING to lose weight. I know how you feel - the special diets, miracle pills, and fancy exercise equipment never helped me lose a pound either. It seemed like the harder I tried, the bigger I got, until I heard about a product called Extreme Power Plus. You're probably thinking to yourself, "Oh geez, not another miracle diet pill!" Like you, I was skeptical at first, but my sister swore it helped her lose 23 pounds in just two weeks, so I told her I'd give it a shot. I mean, there was nothing to lose except a lot of weight! Let me tell you, it was the best decision I've ever made. Period. Six months later, as I'm writing this message to you, I've gone from 355 pounds to 210 pounds, and I haven't changed my exercise routine or diet at all. Yes, I still eat pizza, and lots of it! I was so happy with the results that I contacted the manufacturer and got permission to resell it - at a BIG discount. I want to help other people lose weight like I did, because it does so much for your self-esteem, not to mention your health. I give you my personal pledge that Extreme Power Plus absolutely WILL WORK FOR YOU. If it doesn't, you can return it any time for a full refund. Interested, visit http://2002marketing.com/affiliate3/index.htm If you are frustrated with trying other products, not having any success, and just not getting the results you were promised, then I recommend the only product that worked for me - EXTREME POWER PLUS. You're probably asking yourself, "Ok, so how does this stuff actually work?" Extreme Power Plus contains Lipotropic fat burners and ephedra which is scientifically proven to increase metabolism and cause rapid weight loss. No "hocus pocus" in these pills - just RESULTS, RESULTS, RESULTS!! Here is the bottom line ... I can help you lose 10-15 pounds per week naturally, without exercising and without having to eat rice cakes all day. Just try it for one month - there's nothing to lose, and everything to gain. You will lose weight fast - GUARANTEED. That is my pledge to you. To order Extreme Power Plus on our secure server, just click on the link below: http://2002marketing.com/affiliate3/index.htm If you have difficulty accessing the website above, please try our mirror site by clicking on the link below: http://2002marketing.com/affiliate3/index.htm To see what some of our customers have said about this product, visit http://2002marketing.com/affiliate3/index.htm To see a list of ingredients and for more information on test studies and how it will help you lose weight, visit http://2002marketing.com/affiliate3/index.htm * If you do not wish to receive any more emails from me, please send an email to "[EMAIL PROTECTED]" requesting to be removed. * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Broken world in rtld-elf...
On Wed, 12 Jun 2002, Alex Zepeda wrote: > So what's up with -current? > > I had to install gawk to get the kernel to build (and world too for that > matter).. I haven't had the balls to put the "one true awk" back in place. > > But now whether in world mode or not I get: > > blarf:/usr/src/libexec/rtld-elf#make > cc -O0 -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386 ^^^ > -I/usr/src/libexec/rtld-elf -elf -fpic -DPIC -Wformat=2 > -Wno-format-extra-args -c /usr/src/libexec/rtld-elf/rtld.c > /usr/src/libexec/rtld-elf/rtld.c: In function `atomic_decr_int': > /usr/src/libexec/rtld-elf/i386/rtld_machdep.h:58: inconsistent operand > constraints in an `asm' > *** Error code 1 rtld still uses asms with the old, broken/fragile "0" constraint. This constraint is especially broken/fragile if things are pessimized by compiling without optimizations. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCMCIA 32-bit Cardbus Network Card
On Wed, Jun 12, 2002 at 07:24:49PM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "David W. Chapman Jr." <[EMAIL PROTECTED]> writes: > : I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to > : work on -stable or 5.0DP1 > : > : The error I get is kernel: pcic1: Card type 32-bit cardbus is > : unsupported. Luckily I have a linksys laying around somewhere, but > : has anyone tried to get this card to work under FreeBSD? > > You need to run a NEWCARD kernel. > I got it working pretty good with NEWCARD. The network card seems to hang sometimes and I lose connection. What's the best way to debug this when it happens, I think it may be a conflict with acpi, so I currently have it disabled. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCMCIA 32-bit Cardbus Network Card
In message: <[EMAIL PROTECTED]> "David W. Chapman Jr." <[EMAIL PROTECTED]> writes: : I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to : work on -stable or 5.0DP1 : : The error I get is kernel: pcic1: Card type 32-bit cardbus is : unsupported. Luckily I have a linksys laying around somewhere, but : has anyone tried to get this card to work under FreeBSD? You need to run a NEWCARD kernel. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: looking for warn quota tools
On Tue, 11 Jun 2002, Terry Lambert wrote:
> "Paul S. Puth" wrote:
> >
> > On Linux, there is a tool called "warnquota" that fits my need but I am
> > running FreeBSD 4.5 -RELEASE so I can't utilize that tool. Also, from
> > searching on google, I've found a tool called "psntools" that has the
> > warnquota feature but it doesn't work on a filesystem that has a mailspool.
> >
> > Can someone help me?
[snip]
> FWIW: It's kind of a dumb idea to send email warning about a
> condition which is caused by having too much email. We did
> this on the InterJet, and it was actually a pretty dumb thing
> to do; you end up with a recursive problem that's unsolvable
> -- you basically have to let certain cenders be "priviledged"
> for the delivery of the messages, which means hacking both
> the MDA ("deliver") and "warnquota".
In that case, why not just hack pop3d/imapd/whatever to display a
'virtual' e-mail of some type when the user connects. It could be
complicated to avoid simply generating a new message every time the user
connects without storing the time the last warning was received, I guess.
>
> Another issue is that quota enforcement only occurs *after*
> you exceed the quota, not *when* you exceed the quota. This
> is because email messages must be treated as atomic units; so
> if you are within 3k of a 100k quota, and you get an 80k message,
> you can't not accept it.
Why not? I can't see how you can't just bounce it. You may have accepted
it, but that doesn't guaranteee delivery, just that you won't drop it on
the floor.
[snip]
> The way "HotMail" handles this condition is to drop email that
> it has accepted to delivery, if it can't be delivered to the
> user because of them being over quota. But since it has
> already accepted the email for delivery (by sending "250 OK"
> to the remote SMTP client or MTA, it has pledged to deliver
> the message, or give failure notification, so the message
So why not give failure notification?
> contents are not lost), the email is basically lost with no
> recourse. The inability to guarantee delivery is the basis
> for the liability disclaimer, and the terms of service not
> allowing business use of the service (i.e. to prevent legal
> liability problems).
>
--
David Taylor
[EMAIL PROTECTED]
"The future just ain't what it used to be"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Broken world in rtld-elf...
So what's up with -current? I had to install gawk to get the kernel to build (and world too for that matter).. I haven't had the balls to put the "one true awk" back in place. But now whether in world mode or not I get: blarf:/usr/src/libexec/rtld-elf#make cc -O0 -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386 -I/usr/src/libexec/rtld-elf -elf -fpic -DPIC -Wformat=2 -Wno-format-extra-args -c /usr/src/libexec/rtld-elf/rtld.c /usr/src/libexec/rtld-elf/rtld.c: In function `atomic_decr_int': /usr/src/libexec/rtld-elf/i386/rtld_machdep.h:58: inconsistent operand constraints in an `asm' *** Error code 1 Stop in /usr/src/libexec/rtld-elf. blarf:/usr/src/libexec/rtld-elf# eek? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCMCIA 32-bit Cardbus Network Card
I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to work on -stable or 5.0DP1 The error I get is kernel: pcic1: Card type 32-bit cardbus is unsupported. Luckily I have a linksys laying around somewhere, but has anyone tried to get this card to work under FreeBSD? --- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Total lockup
Edwin Culp wrote: > Today's current seems to be ok. I had the same problem yesterday, booted > a 5 day old kernel, did a cvsup, made a new world and kernel, rebooted > and haven't had any problems, yet. As far as I know, this has been affecting -stable, not -current. At least, that's what I'm running. I'm virtually certain it has to do with IRQ sharing. So far, though, no one has had any effective suggestions. I want to check commits from late April to early May for any possible culprit, when and if I have time... -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Total lockup
Quoting Munish Chopra <[EMAIL PROTECTED]>: | On Wed, Jun 12, 2002 at 06:14:24PM +0200, John Angelmo wrote: | > Hello | > | > I updated world yesterday afternoon now everything bootsup just fine | > But after I have done dhclient and my card (rl0 or wi0) got an IP an I | > want to check it with ifconfig I get a total lockup this appens if I try | > to use startx after I have aquierd an IP | > | > anyone got any idea? | > | > /John | | This is currently being covered in another thread on this list (unless | someone picks it up here again that is). | Today's current seems to be ok. I had the same problem yesterday, booted a 5 day old kernel, did a cvsup, made a new world and kernel, rebooted and haven't had any problems, yet. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Total lockup
On Wed, Jun 12, 2002 at 06:14:24PM +0200, John Angelmo wrote: > Hello > > I updated world yesterday afternoon now everything bootsup just fine > But after I have done dhclient and my card (rl0 or wi0) got an IP an I > want to check it with ifconfig I get a total lockup this appens if I try > to use startx after I have aquierd an IP > > anyone got any idea? > > /John This is currently being covered in another thread on this list (unless someone picks it up here again that is). -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Device cloning
About 1 year ago, I ported a proprietary linux driver to FreeBSD 4.x.
I needed to support linux binaries which use device cloning. I came
up with the following hack. The Linux driver code I ported from is
under NDA, but I feel safe in posting this with the names obscured.
The just of it is that on open, I create a new vnode and struct file
which holds a pointer to a unique (per-instance) data structure. This
allows me to track the private data associated with each open.
Its ugly, but it works for what this driver needs to do. Perhaps
something like this might work for you.
Cheers,
Drew
/*
* Open method, corresponds to most of XXXNicOpen. Allocates an owner
* id and a private data structure.
*
* Each time FOO is opened, a new file and vnode is allocated to it.
*/
static int
foo_open(dev_t kdev, int oflags, int devtype, struct proc *p)
{
int priv_id = -1;
foo_private *priv = NULL;
int num, error;
int fd;
struct file *fp;
struct vnode *vn = NULL, *vd = NULL;
if (p->p_dupfd >= 0)
return ENODEV;
num = 0;/* xxx one NIC only */
error = foo_open_connection(num, (void **)&priv, &priv_id,
oflags, NULL);
if (error)
return error;
priv->p = p;/* process */
if ((error = falloc(p, &fp, &fd)) != 0)
return error; /* XXX leaks priv */
vd = SLIST_FIRST(&kdev->si_hlist);
/*
* Conjure up our own vnode out of thin air. We need the
* vnode so that we can stash a pointer to the per-connection
* priv struct for use in open/close/ioctl and mmap. This is
* tricky, because we need make it look enough like the device
* vnode so that VOP_GETATTR() works on the slave vnode in mmap()
*/
if ((error = getnewvnode(VT_NON, (struct mount *)0,
vd->v_op, &vn)))
return error; /* XXX leaks fp & priv */
vn->v_type = VCHR;
/* really should clone v_vdata & not copy pointer */
vn->v_data = vd->v_data;/* for VTOI in ufs_getattr() */
insmntque(vn, vd->v_mount); /* for VFSTOUFS in ufs_getattr() */
/* allocate our own rdev & save the uniq priv */
vn->v_rdev = malloc(sizeof(struct specinfo), M_DEVBUF, M_WAITOK);
bcopy(vd->v_rdev, vn->v_rdev, sizeof(struct specinfo));
vn->v_rdev->si_drv2 = (void *)priv;
fp->f_data = (caddr_t)vn;
fp->f_flag = FREAD|FWRITE;
fp->f_ops = &foo_fileops;
fp->f_type = DTYPE_VNODE; /* so that we can mmap */
/*
* Save the dup fd in the proc structure then return the
* special error code (ENXIO) which causes magic things to
* happen in vn_open. The whole concept is, well, hmmm.
*/
p->p_dupfd = fd;
return ENXIO;
}
/*
* File operations on FOO device instances
*
* Each FOO instance has a separate file, vnode, devnode, and specinfo
* structures associated with it (see foo_open).
* Private device data are stored with the specinfo (si_drv2)
*/
#include
#include
int foo_fileread __P((struct file *fp, struct uio *uio, struct ucred *cred,
int flags, struct proc *p));
int foo_filewrite __P((struct file *fp, struct uio *uio, struct ucred *cred,
int flags, struct proc *p));
int foo_fileclose __P((struct file *fp, struct proc *p));
int foo_fileioctl __P((struct file *fp, u_long cmd, caddr_t data,
struct proc *p));
int foo_filepoll __P((struct file *fp, int events, struct ucred *cred,
struct proc *p));
int foo_filestat __P((struct file *fp, struct stat *ub, struct proc *p));
int
foo_fileread(fp, uio, cred, flags, p)
struct file *fp;
struct uio *uio;
struct ucred *cred;
struct proc *p;
int flags;
{
return 0;
}
int
foo_filewrite(fp, uio, cred, flags, p)
struct file *fp;
struct uio *uio;
struct ucred *cred;
struct proc *p;
int flags;
{
return 0;
}
int
foo_fileioctl(fp, cmd, data, p)
struct file *fp;
u_long cmd;
register caddr_t data;
struct proc *p;
{
struct vnode *vn;
struct specinfo *si;
foo_private *priv;
struct foo_softc *sc;
int val = 0;
vn = (struct vnode *)fp->f_data;
si = vn->v_rdev;
priv = si->si_drv2;
sc = priv->sc;
switch (cmd) {
<...>
default:
return -EINVAL;
}
return val;
}
int
foo_filepoll(fp, events, cred, p)
struct file *fp;
int events;
struct ucred *cred;
struct proc *p;
{
return EOPNOTSUPP;
}
int
foo_filestat(fp, ub, p)
struct file *fp;
struct stat *ub;
struct proc *p;
{
return EOPNOTSUPP;
}
void insmntque __P((struct
Total lockup
Hello I updated world yesterday afternoon now everything bootsup just fine But after I have done dhclient and my card (rl0 or wi0) got an IP an I want to check it with ifconfig I get a total lockup this appens if I try to use startx after I have aquierd an IP anyone got any idea? /John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Broken World in xlint/llib
Seeing some errors trying to buildworld with the xlint/llib-lposix. It appears the error is in stdarg.h. I am running version 1.14 of stdarg.h Line 43 in /usr/include/stdarg.h and /usr/include/machine/stdarg.h states: typedef _BSD_VA_LIST_ va_list; but in /usr/src/contrib/gcc/ginclude/stdarg.h it's version 1.5 (from latest CVSUP) it states #ifndef __GNUC_VA_LIST Not sure what I can do to fix this problem...I did a "make includes" before issuing the make buildworld. Any help would be appreciated. -Troy ===> usr.bin/xlint/llib lint -cghapbx -Cposix /usr/src/usr.bin/xlint/llib/llib-lposix llib-lposix: stdarg.h:43: syntax error [249] stdarg.h:110: syntax error [249] time.h:141: warning: conversion from 'unsigned long long' may lose accuracy [132 ] time.h:158: warning: conversion from 'unsigned long long' may lose accuracy [132 ] time.h:165: warning: conversion from 'long' may lose accuracy [132] llib-lposix:306: syntax error [249] llib-lposix:307: syntax error [249] llib-lposix:308: syntax error [249] llib-lposix:308: cannot recover from previous errors [224] *** Error code 1 Stop in /usr/src/usr.bin/xlint/llib. *** Error code 1 Stop in /usr/src/usr.bin/xlint. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 top in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Looking for comments on a new utility...
Julian Elischer <[EMAIL PROTECTED]> writes: > we need to extend this to handle a full thread table per process.. > anyone have any ideas on how to do this? Unfortunately, I think we're going to end up reimplementing procfs in the sysctl tree... DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** Approved. **
Warning Unable to process data: multipart/mixed;boundary="=_NextPart_000_00E5_84A70E3A.C4515B83"
Re: Perl Location pseudo-hardcoded for ports
On Wed, 12 Jun 2002, Andrew Kenneth Milton wrote:
> The perl location for OSVERSION >= 500036 is 'hardcoded' to be
> ${LOCALBASE}/bin/perl in bsd.port.mk. Effectively /usr/local/bin/perl
>
> Shouldn't it use the perl wrapper in /usr/bin/perl ?
The fate of the wrapper in the system has not been conclusively
determined. It's both reasonable and appropriate for the ports team to
proceed with their own solutions while we sort it all out.
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Looking for comments on a new utility...
Cyrille Lefevre wrote: > On Tue, Jun 11, 2002 at 05:15:17AM -0700, Juli Mallett wrote: ... > > would like to see done to ps(1) :) The most notable request was for a > > feature I've missed having in our ps(1) for a while, the ability to get a > > tree of processes printed so you can tell who is whose child, etc. Yes, I still missed that one. Go for it. > how about this one ? > > 1 ?0 \_ init > 2814 ttyp00 \_ sh > 2816 ttyp00 | \_ sh > 57423 ?0 | \_ sleep > 2596 ?0 \_ inetd > 24834 ?0 | \_ rlogind > 24838 ttyp00 | | \_ ksh > 24912 ttyp00 | | \_ ksh > 57504 ?0 | \_ telnetd > ^^ command tree > standard ps fields > taken from ast-open `ps -T'. Also nice (why no UID field ?) I use ps trees like these to quickly find out who is misusing what ;-) > for fun, how about a simple awk script like the one in attachment ;^) :) Hans Lambermont -- http://lambermont.webhop.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
