Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
In message [EMAIL PROTECTED], Bruce Evans writes: This was decreed but not agreed to. I don't use devfs and don't plan to use it until it works at least as well as specfs (if this is possible). I have noticed about 10 minor bugs in it despite only running it to test it every 6 months or so. Examples: Why don't you report such findings then ? - file time updates are broken in several ways. Details ? - stat() doesn't work right on devfs directories (st_size and st_blocks zero for all devfs files, but should be nonzero for directories). Where is this requirement from ? - pathconf() doesn't work right on devfs directrories (_PC_NAME_MAX and _PC_PATH_MAX are unsupported, but must be supported for directories). OK, that's a bug. - acd devices still have insecure modes (world readable). That is not a fault in DEVFS but in the driver. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
On Tue, Sep 04, 2001 at 01:33:30AM -0700, Poul-Henning Kamp wrote: phk 2001/09/04 01:33:30 PDT Modified files: sys/dev/ccd ccd.c sys/modules/ccd Makefile sys/sys ccdvar.h Log: Kill the NCCD constant by modernizing the ccd driver. This broke `ccd' for me. When ccdconfig runs, I get /dev/ccd0f: device not configured. I do not have ccd compiled into my kernel, but rather use ccd.ko. I also don't use DEVFS on this box. My device node is: crw-r- 1 root operator 74, 5 Apr 6 2000 /dev/ccd0f Backing out the changes to ccd.c and ccdvar.h fixed things for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
In message [EMAIL PROTECTED], David O'Brien writes: On Tue, Sep 04, 2001 at 01:33:30AM -0700, Poul-Henning Kamp wrote: phk 2001/09/04 01:33:30 PDT Modified files: sys/dev/ccd ccd.c sys/modules/ccd Makefile sys/sys ccdvar.h Log: Kill the NCCD constant by modernizing the ccd driver. This broke `ccd' for me. When ccdconfig runs, I get /dev/ccd0f: device not configured. I do not have ccd compiled into my kernel, but rather use ccd.ko. I also don't use DEVFS on this box. Use DEVFS and it will work. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
On Wed, Sep 05, 2001 at 09:35:41PM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David O'Brien writes: On Tue, Sep 04, 2001 at 01:33:30AM -0700, Poul-Henning Kamp wrote: phk 2001/09/04 01:33:30 PDT Modified files: sys/dev/ccd ccd.c sys/modules/ccd Makefile sys/sys ccdvar.h Log: Kill the NCCD constant by modernizing the ccd driver. This broke `ccd' for me. When ccdconfig runs, I get /dev/ccd0f: device not configured. I do not have ccd compiled into my kernel, but rather use ccd.ko. I also don't use DEVFS on this box. Use DEVFS and it will work. Then it needs to be backed out. This is the first thing that does not work w/NODEVFS and I don't believe the Project has agreed that absolutly requiring DEVFS is OK at this time. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/ccd ccd.c src/sys/modules/ccd Makefile src/sys/sys ccdvar.h
In message [EMAIL PROTECTED], David O'Brien writes: Use DEVFS and it will work. Then it needs to be backed out. This is the first thing that does not work w/NODEVFS and I don't believe the Project has agreed that absolutly requiring DEVFS is OK at this time. No, in fact, clearcut warnings has been sent for over half a year that after july 1st 2001 !DEVFS compatibility were no longer a requirement and that DEVFS should be considered mandatory. Due to my trying to get my new house into shape before winter the progress on DEVFS has been slower than projected, but the goal is still to make DEVFS entirely mandatory. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
