Re: atapicam and cd-rw problem, no cd0 but acd0 some error

2007-06-14 Thread Joe Altman
On Thu, Jun 14, 2007 at 02:36:39PM -0600, Scott Long wrote: > > The atapicam problems were extensively discussed on this list last > month. I know; I griped rather a lot about the whole thing. I think the maintainer is back from vacation now, if anyone feels a need to drop him a line and ask him

Re: atapicam and cd-rw problem, no cd0 but acd0 some error

2007-06-14 Thread Joe Altman
On Thu, Jun 14, 2007 at 12:00:22PM +, [EMAIL PROTECTED] wrote: > 13. atapicam and cd-rw problem, no cd0 but acd0 some error > (Momchil Ivanov) > 22. Re: atapicam and cd-rw problem, no cd0 but acd0 some error > (Tom Evans) > -- > > Message: 13 > Date

Re: atapicam cd error

2007-05-25 Thread Joe Altman
On Fri, May 25, 2007 at 06:30:00PM +0200, Oliver Fromme wrote: > Joe Altman wrote: > > You have atapicam as a kernel module; and what version of atapi-cam.c? > > No, I've always compiled it statically in my kernel. That's what I meant to say; that it was a device in the

Re: atapicam cd error from; was: freebsd-stable Digest, Vol 207, Issue 9

2007-05-25 Thread Joe Altman
On Fri, May 25, 2007 at 12:00:28PM +, [EMAIL PROTECTED] wrote: > > Today's Topics: > > 14. Re: atapicam cd error from freebsd-stable Digest, Vol 207, > Issue 6 (Oliver Fromme) > -- > > Date: Fri, 25 May 2007 12:21:24 +0200 (CEST) > From: Oliver Fromme <[EMA

Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6

2007-05-24 Thread Joe Altman
then my query on -questions in May. I've been waiting for it to bite someone else, so that I could offer this: I wrote to the maintainer for atapi-cam.c, and here is his reply: * Joe Altman, 2007-05-19 : > My apologies for disturbing you; I imagine that you are quite busy, > but I wond

Re: FreeBSD 4.x EoL (FreeBSD Security Officer)

2006-10-17 Thread Joe Altman
>From the list digest: > 23. FreeBSD 4.x EoL (FreeBSD Security Officer) A few things immediately jumped out at me, and so I've elided everything around them so that they stand out; which I believe to be proper: > From: FreeBSD Security Officer <[EMAIL PROTECTED]> > Subject: FreeBSD 4.x EoL

I thought I had waited until a patch was issued for the SHA256 issue...

2006-10-10 Thread Joe Altman
to update world...I was it was recently committed, and ran an update at approximately 10 AM EDT. Here is where 'make buildworld' stopped: cc -pg -O -pipe -march=pentiumpro -I/usr/src/secure/lib/libssh/../../../crypto/openssh -include ssh_namespace.h -c /usr/src/secure/lib/libssh/../../../crypto/

Re: help ith burncd (Input/output error, 6.1-RC, plextor PX-740a)

2006-04-13 Thread Joe Altman
>3. Re: help ith burncd (Input/output error, 6.1-RC, plextor > PX-740a) (George Hartzell) >5. Re: help ith burncd (Input/output error, 6.1-RC, plextor > PX-740a) (George Hartzell) > > -- > > Message: 3 > Date: Wed, 12 Apr 2006 09:13:03 -0700 > From:

Re: Problem with Razer Copperhead (USB-mouse)

2006-04-04 Thread Joe Altman
On Tue, Apr 04, 2006 at 11:07:24AM +, [EMAIL PROTECTED] wrote: > 14. Problem with Razer Copperhead (USB-mouse) (Christian Baer) > > -- > > Message: 14 > Date: Tue, 4 Apr 2006 01:37:42 +0200 (CEST) > From: Christian Baer <[EMAIL PROTECTED]> > Subject: Problem wit

Re: freebsd-stable Digest, Vol 147, Issue 4

2006-02-22 Thread Joe Altman
ark X1100 series), mustek_usb2 (Mustek BearPaw 2448 TA Pro) * Updated backends: artec_eplus48u, avision, canon, epson, fujitsu, genesys, gt68xx, microtek2, mustek_pp, plustek, plustek_pp, sm3600, snapscan, umax_pp. >From <http://www.sane-project.org>. I'd give you the

Re: USB changes

2005-05-02 Thread Joe Altman
It did go somewhere; Julian altered two files in the relevant source and after I updated the issue was resolved. > 13. Re: USB changes. (Joel) > > Message: 13 > Date: Mon, 02 May 2005 12:20:30 +0900 > From: Joel <[EMAIL PROTECTED]> > Subject: Re: USB changes. > To: freebsd-stable@freebsd.org >

Re: USB changes

2005-04-29 Thread Joe Altman
> -- > > Message: 9 > Date: Thu, 28 Apr 2005 11:23:14 -0700 > From: Julian Elischer <[EMAIL PROTECTED]> > Subject: Re: USB changes. > To: freebsd-stable@freebsd.org, Joe Altman <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTE

Re: USB changes.

2005-04-28 Thread Joe Altman
On Thu, Apr 28, 2005 at 01:40:50PM -0700, Julian Elischer wrote: > > Since I can't make this happen here, I'm going to need help.. What do you need? Relatively speaking, I'm sort of a newbie at the more complex aspects of bugs, and this strikes me as somewhat complex. But if you are willing to t

Re: USB changes.

2005-04-28 Thread Joe Altman
On Thu, Apr 28, 2005 at 01:23:25PM -0700, Julian Elischer wrote: > > > Joe Altman wrote: > > >On Thu, Apr 28, 2005 at 12:55:31PM -0700, Julian Elischer wrote: > > > > > >>>>Can you confirm that usb.c ends with: > >>>>SYSIN

Re: USB changes.

2005-04-28 Thread Joe Altman
On Thu, Apr 28, 2005 at 12:55:31PM -0700, Julian Elischer wrote: > >> > >>Can you confirm that usb.c ends with: > >>SYSINIT(usb_cold_explore, SI_SUB_INT_CONFIG_HOOKS, SI_ORDER_FIRST, > >> usb_cold_explore, NULL); > > /usr/sr/sys/dev/usb/usb.c > > >Aha...maybe this is it: > > > >/usr/src/usr.sbin

Re: USB changes.

2005-04-28 Thread Joe Altman
On Thu, Apr 28, 2005 at 11:23:14AM -0700, Julian Elischer wrote: > > >+++ > > > >Currently, I find my P4 hanging just after discovering the parallel > >port and mounting disk; in other words, just here: > > > >ppc0: parallel port not found. > >ad0: 28629MB [58168/16/63] at ata0-master UDMA100 > >

USB code changed, right? Perhaps an unchange is in order?

2005-04-27 Thread Joe Altman
I was pretty sure I saw a heads-up, and lo I did: +++ I have just merged in most of the lowest level changes to 4.x from 6.x. If you use USB on 4.x machines and are planning on following RELENG_4 then I suggest you test the latest sources to avoid nasty surprises later. I will probably merge so