Re: Support for atapi cdrw as scsi in -current?
Hi, i tested your patch onn 4.5-stable with TOSHIBA SD-M1502 (master) and PIONEER DVR-103 (slave). Unfortunately the system hangs at boot time after (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 Any ideas? Lutz -- Lutz Bichler Institute for Software Technology, Department of Computer Science University of the Federal Armed Forces Munich, D-85577 Neubiberg, Germany TEL/FAX: +49(0)89 6004-2261/-4447, NET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: function name collision on getcontext with ports/editors/joe
On Mon, 11 Feb 2002, Daniel Eischen wrote: On Mon, 11 Feb 2002, Garrett Wollman wrote: On Mon, 11 Feb 2002 12:16:44 -0500 (EST), Daniel Eischen [EMAIL PROTECTED] said: How do you easily forward declare something that is a typedef? There is a reason style(9) says not to use such typedefs. Unfortunately, this one it written into a standard. Since We Are The Implementation, there is no difficulty in simply writing the appropriate structure type into the relevant declarations. OK, thanks. I believe there is a difficulty: POSIX at least used to require applications to be able to declare prototypes for functions in POSIX headers using lexically the same definition as in the standard. In the case of ucontext_t, this might not be a problem, since the implementation can declare ucontext_t as an incomplete struct type. The both the implementation and applications can use ucontext_t * in prototypes. OTOH, sigreturn() is not a POSIX function so the POSIX rules don't apply directly. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: function name collision on getcontext with ports/editors/joe
On Mon, 11 Feb 2002, Daniel Eischen wrote: On Mon, 11 Feb 2002, Terry Lambert wrote: Daniel Eischen wrote: Removing sys/ucontext.h from sys/signal.h prevents ucontext_t from being defined, so all users of signal.h would choke. We can change the prototype of sigreturn back to struct sigcontext *, or just forward declare ucontext_t in signal.h or sys/signal.h. Forward declare it. People who need its internals will include the proper header. That header is traditionally signal.h :-). How do you easily forward declare something that is a typedef? You could forward declare struct __ucontext and use a pointer to that as the argument to sigreturn, but that doesn't seem right as it is relying on how ucontext_t is defined. This is OK for the implementation -- see other followups. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
procfs.o undef'd refs
I dared to cvsup -current yesterday to my notebook computer (had 4.4 R installed before that) and now being half there (did a buildworld already successfully) kernel compilation fails with a lot of undefined references in procfs.o: pfs_create_file pfs_create_link pfs_mount pfs_init pfs_unint pfs_unmount pfs_root pfs_statfs Am I missing a new config option? -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: procfs.o undef'd refs
On Tue, Feb 12, 2002 at 11:18:59AM +0100, Christoph Kukulies wrote: I dared to cvsup -current yesterday to my notebook computer (had 4.4 R installed before that) and now being half there (did a buildworld already successfully) kernel compilation fails with a lot of undefined references in procfs.o: pfs_create_file pfs_create_link pfs_mount pfs_init pfs_unint pfs_unmount pfs_root pfs_statfs Am I missing a new config option? From GENERIC: options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework (ie try adding PSEUDOFS :) -- Simon Dick [EMAIL PROTECTED] Why do I get this urge to go bowling everytime I see Tux? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Ethernet tunnel device
On Mon, Feb 11, 2002 at 12:14:32PM -0800, Brooks Davis wrote: It sounds like there's some sort of a bug in the close code. You are sure the previous instance is really gone, right? If it is, that's another issue. The tapclose() function is not called at all in this case. (I've put some debugging statement in the tap driver) I don't understand because I do see a successful close() from vmware (using ktrace). Writing a simple app that opens '/dev/vmnet1' and closes it again works fine. What would be the difference for this simple case and the vmware case? (I also made a linux binary of the same simple program and that one works too, just to be sure) Making a simple (and very possible wrong) conclusion is that the open call gets lost between userland and the driver. (vfs layer?) Any hints on where too look further would be very helpful. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
undef'd nfs_dskless symbol when no NFS option defined
When migrating a 4.4 kernel to -current it happened that I had no NFSCLIENT or NFSSERVER option defined because I took out the offending obsolete NFS option when trying to tweak my old kernel config file so that it got through without synrax or obsolete option errors. I then only had the FFS option in it. This lead to nfs_dskless (or something like that) being undefined in locore.o. I'm just mentioning it. Maybe it also came from not purging ../compile/CONFIG everytime I made a new config and not doing a fresh make depend everytime. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| : When my laptop is booting (Toshiba with ToPIC97, NoteWorthy modem, | : LinkSys modem card) something odd happens: | : | : IP packet filtering initialized, divert disabled, rule-based forwarding | : disabled | : , default to accept, unlimited logging | : pccard: card inserted, slot 0 | : pccard: card inserted, slot 1 | : pccard: card removed, slot 1 | : pccard: card inserted, slot 0 | : pccard: card inserted, slot 1 | | That's odd. | | : You can see slot 1 acts like it was removed and reinserted. To make it | : even more interesting... | | You are right. | | : Mounting root from ufs:/dev/ad0s1a | : sio1 at port 0x2f8-0x2ff irq 11 flags 0x4 slot 0 on pccard0 | : sio1: type 16550A | : sio1: unable to activate interrupt in fast mode - using normal mode | : ed1 at port 0x240-0x25f iomem 0xd4000-0xd7fff irq 11 slot 1 on pccard1 | : ed1: address e2:0c:0f:05:6d:54, type NE2000 (16 bit) | : | : You can see the NIC comes up as ed1. This used to be ed0 around 4.3, | : IIRC. Is this related to the problems with slot 1 under ToPIC97? | : I could be wrong, but I believe my modem used to be sio0 as well. I | : remember having to change it in my ppp script after a build world some | : time ago. | | Maybe hints consume ed0 and sio0 likely. So, the game is afoot! Is there anything I can do to help track this down? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: procfs.o undef'd refs
On 11:18+0100, Feb 12, 2002, Christoph Kukulies wrote: I dared to cvsup -current yesterday to my notebook computer (had 4.4 R installed before that) and now being half there (did a buildworld already successfully) kernel compilation fails with a lot of undefined references in procfs.o: pfs_create_file pfs_create_link pfs_mount pfs_init pfs_unint pfs_unmount pfs_root pfs_statfs Am I missing a new config option? more /usr/src/UPDATING, 20011203 -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| In -current look at /boot/device.hints. In stable this is still in | the kernel config file. Is the hints file going to become standard, or is it just a tool to help developers writing drivers for -current? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
In message: [EMAIL PROTECTED] j mckitrick [EMAIL PROTECTED] writes: : | Maybe hints consume ed0 and sio0 likely. : : So, the game is afoot! Is there anything I can do to help track this : down? In -current look at /boot/device.hints. In stable this is still in the kernel config file. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
In message: [EMAIL PROTECTED] j mckitrick [EMAIL PROTECTED] writes: : : | In -current look at /boot/device.hints. In stable this is still in : | the kernel config file. : : Is the hints file going to become standard, or is it just a tool to : help developers writing drivers for -current? It is standard in current, so in 5.0-release and newer people will have to cope. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
| : Is the hints file going to become standard, or is it just a tool to | : help developers writing drivers for -current? | | It is standard in current, so in 5.0-release and newer people will | have to cope. So the idea is that drivers will be modules dynamically loaded based on the hints file? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
In message: [EMAIL PROTECTED] j mckitrick [EMAIL PROTECTED] writes: : So the idea is that drivers will be modules dynamically loaded based on : the hints file? Not currently. But someone could come in and do that project. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Where to find docs on newbus vs. cardbus vs. newcard
On Tue, Feb 12, 2002 at 10:33:25AM -0700, M. Warner Losh wrote: | In message: [EMAIL PROTECTED] | j mckitrick [EMAIL PROTECTED] writes: | : So the idea is that drivers will be modules dynamically loaded based on | : the hints file? | | Not currently. But someone could come in and do that project. Hint, hint. :-) No pun intended. Well, I helped convert a few of the ppbus drivers to modules, maybe I could help? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
urio driver
The urio driver appears to call make_dev, discarding the returned dev_t, and never bothers to call destroy_dev. Although this is presumably broken, it did _work_ previously. however, there is now a 'panic(don't do that);' call in make_dev (and destroy_dev) to prevent duplicate calls, thus the machine will crash if you attach/detach/re-attach a rio. This has been happing for quite a while now, but I've never been bothered enough to actually try to fix it, until now. :) I have approximately no experience with FreeBSD device drivers, but I'm currently attempting to see if I can figure out how the other u*.c files handle detaching... any hints would be appreciated :) -- 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
Re: Where to find docs on newbus vs. cardbus vs. newcard
| It isn't a huge effort conceptutally, but there is a lot of | infrastructure that CardBus depends on that isn't in -stable or only | partially MFC'd. If someone wanted to start cranking on it, they | could get it done in a few weeks worth of work. Where would be a good place to start? jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
I broke make world
I apparently broke the build of libkvm (again) I will fix it shortly. I'm in transit right now. Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: urio driver
On Tue, 12 Feb 2002, David Taylor wrote:
I have approximately no experience with FreeBSD device drivers, but I'm
currently attempting to see if I can figure out how the other u*.c files
handle detaching... any hints would be appreciated :)
Well. I managed to create a patch which _works_. I have some serious
doubts about its correctness, however.
--
David Taylor
[EMAIL PROTECTED]
The future just ain't what it used to be
--- urio.c.old Tue Feb 12 22:31:14 2002
+++ urio.c Tue Feb 12 22:02:03 2002
@@ -160,6 +160,8 @@
int sc_refcnt;
#if defined(__NetBSD__) || defined(__OpenBSD__)
u_char sc_dying;
+#elif defined(__FreeBSD__)
+dev_t dev;
#endif
};
@@ -271,8 +273,7 @@
#if defined(__FreeBSD__)
#if (__FreeBSD__ = 4)
- /* XXX no error trapping, no storing of dev_t */
- (void) make_dev(urio_cdevsw, device_get_unit(self),
+ sc-dev = make_dev(urio_cdevsw, device_get_unit(self),
UID_ROOT, GID_OPERATOR,
0644, urio%d, device_get_unit(self));
#endif
@@ -633,22 +634,25 @@
}
return (0);
}
+#endif
USB_DETACH(urio)
{
USB_DETACH_START(urio, sc);
- struct urio_endpoint *sce;
- int i, dir;
- int s;
+ struct vnode *vp;
+
#if defined(__NetBSD__) || defined(__OpenBSD__)
- int maj, mn;
+ struct urio_endpoit *sce;
+ int i, dir;
+ int s;
+ int maj, mn;
DPRINTF((urio_detach: sc=%p flags=%d\n, sc, flags));
+ sc-sc_dying = 1;
#elif defined(__FreeBSD__)
DPRINTF((urio_detach: sc=%p\n, sc));
#endif
- sc-sc_dying = 1;
/* Abort all pipes. Causes processes waiting for transfer to wake. */
#if 0
for (i = 0; i USB_MAX_ENDPOINTS; i++) {
@@ -668,7 +672,7 @@
usb_detach_wait(USBDEV(sc-sc_dev));
}
splx(s);
-#else
+/* #else */
if (sc-sc_pipeh_in)
usbd_abort_pipe(sc-sc_pipeh_in);
@@ -692,25 +696,20 @@
/* Nuke the vnodes for any open instances (calls close). */
mn = self-dv_unit * USB_MAX_ENDPOINTS;
vdevgone(maj, mn, mn + USB_MAX_ENDPOINTS - 1, VCHR);
-#elif defined(__FreeBSD__)
- /* XXX not implemented yet */
-#endif
- usbd_add_drv_event(USB_EVENT_DRIVER_DETACH, sc-sc_udev,
- USBDEV(sc-sc_dev));
+ usbd_add_drv_event(USB_EVENT_DRIVER_DETACH, sc-sc_udev,
+ USBDEV(sc-sc_dev));
+#elif defined(__FreeBSD__)
+ device_set_desc(self, NULL);
+ vp = SLIST_FIRST(sc-dev-si_hlist);
+ if (vp)
+ VOP_REVOKE(vp, REVOKEALL);
- return (0);
+ destroy_dev(sc-dev);
+#endif
+ return (0);
}
-#endif /* defined(__NetBSD__) || defined(__OpenBSD__) */
-
#if defined(__FreeBSD__)
-Static int
-urio_detach(device_t self)
-{
- DPRINTF((%s: disconnected\n, USBDEVNAME(self)));
- device_set_desc(self, NULL);
- return 0;
-}
#if (__FreeBSD__ = 4)
DRIVER_MODULE(urio, uhub, urio_driver, urio_devclass, usbd_driver_load, 0);
FW: Re: windbindd
Is there any way to impliment dl_open in our nsswitch for -current so that samba's winbindd can work on FreeBSD? - Forwarded message from Richard Sharpe [EMAIL PROTECTED] - Date: Wed, 13 Feb 2002 11:29:24 +1030 Reply-To: [EMAIL PROTECTED] From: Richard Sharpe [EMAIL PROTECTED] To: David W. Chapman Jr. [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], SAMBA TECH List [EMAIL PROTECTED] Subject: Re: windbindd User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205 David W. Chapman Jr. wrote: On Wed, Feb 13, 2002 at 10:48:09AM +1030, Richard Sharpe wrote: David W. Chapman Jr. wrote: Is there any reason winbindd is not supported on FreeBSD? I'm just curious of the hold ups, maybe I can get things rolling from the FreeBSD team if there is anything we need to do? This is an interesting question. Here at Panasas we have rolled our own support by communicating directly using TCP. The issue, when I last looked at it, was a good nsswitch implementation. I would be interested in keeping across this issue. Well FreeBSD-STABLE (4.x) doesn't have nsswitch, but FreeBSD-current (5.x) does. That may be part of the problem. That was the first problem I encountered ... I suspect that, barring some screwed up tests in configure, it will work. I guess I should update my repository and check out FreeBSD-current and see. I would appreciate it if you could let me know what you find. As the maintainer of the FreeBSD samba port I have received a few requests about this. Hmmm, having had a brief look at what I think is FreeBSD-current, it seems that the nsswitch implementation does not use dl_open to pick up shared libs so that it can be extended ... :-( This is a crucial piece of functionality for winbindd, it seems. -- Richard Sharpe, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba - End forwarded message - -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
OpenPAM Caliopsis + integration patches
OpenPAM Caliopsis and accompanying FreeBSD integration patches are now available from URL:http://openpam.sourceforge.net/. A fully patched tree is also available from the p4 depot, under //depot/user/des/pam/. Please see the release notes and change log for information about known and resolved issues. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
