Re: Latest on rewrite of pkg_install tools.
Hi! This is great! However, the patch has some whitespace-fubars: diff -urN -x CVS pkg_install/info/main.c pkg_install.jdl/info/main.c --- pkg_install/info/main.c Tue Dec 12 10:07:19 2000 +++ pkg_install.jdl/info/main.c Sat Jan 6 02:13:47 2001 @@ -7,10 +7,10 @@ * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright - *notice, this list of conditions and the following disclaimer. + * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright - *notice, this list of conditions and the following disclaimer in the - *documentation and/or other materials provided with the distribution. + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. * * Jordan K. Hubbard * 18 July 1993 @@ -19,168 +19,227 @@ * */ And similar, everywhere. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem
too.
I don't know if there was any fix as such
I have a -current system from Dec. 7 on which I'm trying to do
a cvs update in preparation of make world, and am seeing wierd
stuff like this:
cvs server: Updating crypto/kerberosIV/appl/afsutil
U crypto/kerberosIV/appl/afsutil/Makefile.in
U crypto/kerberosIV/appl/afsutil/aklog.c
U crypto/kerberosIV/appl/afsutil/kstring2key.c
U crypto/kerberosIV/appl/afsutil/pagsh.c
cvs server: Updating crypto/kerberosIV/appl/bsd
U crypto/kerberosIV/appl/bsd/Makefile.in
U crypto/kerberosIV/appl/bsd/README.login
U crypto/kerberosIV/appl/bsd/bsd_locl.h
U crypto/kerberosIV/appl/bsd/encrypt.c
U crypto/kerberosIV/appl/bsd/forkpty.c
U crypto/kerberosIV/appl/bsd/kcmd.c
U crypto/kerberosIV/appl/bsd/klogin.c
U crypto/kerberosIV/appl/bsd/krcmd.c
U crypto/kerberosIV/appl/bsd/login.c
U crypto/kerberosIV/appl/bsd/login_access.c
U crypto/kerberosIV/appl/bsd/login_fbtab.c
U crypto/kerberosIV/appl/bsd/osfc2.c
U crypto/kerberosIV/appl/bsd/pathnames.h_
U crypto/kerberosIV/appl/bsd/rcmd_util.c
cvs update: warning: unrecognized response ` If there are any IP options on
`sock', die.' from cvs server
cvs update: warning: unrecognized response ` */' from cvs server
cvs update: warning: unrecognized response `' from cvs server
cvs update: warning: unrecognized response `void' from cvs server
cvs update: warning: unrecognized response `ip_options_and_die (int sock, struct
sockaddr_in *fromp)' from cvs server
cvs update: warning: unrecognized response `{' from cvs server
cvs update: warning: unrecognized response `#if defined(IP_OPTIONS)
defined(HAVE_GETSOCKOPT)' from cvs server
cvs update: warning: unrecognized response ` u_char optbuf[BUFSIZ/3], *cp;' from
cvs server
cvs update: warning: unrecognized response ` char lbuf[BUFSIZ], *lp;' from cvs
server
The file data is somehow getting mixed into the "control stream"
or something. The cvs server is a 5.0-2506-CURRENT machine
that has been working fine for many months (and I don't see the
same problem when cvs updating from other machines).
I notice that "cvs" was updated to version 1.11 on 10/31/00...
Has anyone else seen this, and if so, what's the fix??
Thanks,
-Archie
__
Archie Cobbs * Packet Design * http://www.packetdesign.com
--
Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org
http://www.Awfulhak.org brian@[uk.]OpenBSD.org
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
John Polstra writes: U crypto/kerberosIV/appl/bsd/login_fbtab.c U crypto/kerberosIV/appl/bsd/osfc2.c U crypto/kerberosIV/appl/bsd/pathnames.h_ U crypto/kerberosIV/appl/bsd/rcmd_util.c cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server cvs update: warning: unrecognized response ` */' from cvs server [...] It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the CVS server. Just a guess. I haven't seen the problem here. Don't think so.. this happens rather randomly for random files (i.e., more than one). The same file will update correctly on the second try (but then it barfs on another one). It doesn't seem to happen for patched files, only for files that are downloaded whole.. ie, if you blow away an entire directory and then download it again. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cardbus installs on -current
is installing FreeBSD-CURRENT with sysinstall using a cardbus supported card (such as a 3com cardbus 3cfe575 or something) working yet? Just wondering because I want to get windows off my laptop, and this will bring me one step closer... (with support for my ess maestro3 chip being the last step) Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : is installing FreeBSD-CURRENT with sysinstall using a cardbus supported : card (such as a 3com cardbus 3cfe575 or something) working yet? Just : wondering because I want to get windows off my laptop, and this will bring : me one step closer... (with support for my ess maestro3 chip being the : last step) I don't think anybody has ever gone down this path. If you do, please drop a note to -current and/or -mobile telling about your woes and wonders. I'd suspect that it would just work *IF* the card probes before sysinstall's device harvesting mechanism kicks in. Of course, pccardd will not start, but don't worry too much about that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
U crypto/kerberosIV/appl/bsd/login_fbtab.c U crypto/kerberosIV/appl/bsd/osfc2.c U crypto/kerberosIV/appl/bsd/pathnames.h_ U crypto/kerberosIV/appl/bsd/rcmd_util.c cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server cvs update: warning: unrecognized response ` */' from cvs server [...] It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the CVS server. Just a guess. I haven't seen the problem here. Don't think so.. this happens rather randomly for random files (i.e., more than one). The same file will update correctly on the second try (but then it barfs on another one). It doesn't seem to happen for patched files, only for files that are downloaded whole.. ie, if you blow away an entire directory and then download it again. Just a question. Are you using any sort of transport mechanism (besides rsh) in the middle? I had problems like this when using F-Secure's Windows client using compression, which blew up. We switched the users to SecureCRT and the problems went away. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
Brian Somers [EMAIL PROTECTED] wrote: ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem too. Sorry, you're misremembering. I've never seen anything like this. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
: is installing FreeBSD-CURRENT with sysinstall using a cardbus supported : card (such as a 3com cardbus 3cfe575 or something) working yet? Just : wondering because I want to get windows off my laptop, and this will bring : me one step closer... (with support for my ess maestro3 chip being the : last step) I don't think anybody has ever gone down this path. If you do, please drop a note to -current and/or -mobile telling about your woes and wonders. I'd suspect that it would just work *IF* the card probes before sysinstall's device harvesting mechanism kicks in. Of course, pccardd will not start, but don't worry too much about that. Is the cardbus stuff in the GENERIC kernel, or will I have to change it and build my own release or custom sysinstall? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
Nate Williams writes: U crypto/kerberosIV/appl/bsd/login_fbtab.c U crypto/kerberosIV/appl/bsd/osfc2.c U crypto/kerberosIV/appl/bsd/pathnames.h_ U crypto/kerberosIV/appl/bsd/rcmd_util.c cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server cvs update: warning: unrecognized response ` */' from cvs server [...] It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the CVS server. Just a guess. I haven't seen the problem here. Don't think so.. this happens rather randomly for random files (i.e., more than one). The same file will update correctly on the second try (but then it barfs on another one). It doesn't seem to happen for patched files, only for files that are downloaded whole.. ie, if you blow away an entire directory and then download it again. Just a question. Are you using any sort of transport mechanism (besides rsh) in the middle? I had problems like this when using F-Secure's Windows client using compression, which blew up. We switched the users to SecureCRT and the problems went away. Nope.. just using cvs in pserver mode to a server on the same subnet, not encrypted or compressed or anything. Once I actually get all of the -current sources I'll rebuild world and see if the problem still exists. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Debugging...
On Sun, Jan 07, 2001 at 03:09:40PM -0500, Justin/Mike Ovens wrote: I compiled my kernel with Debuggin symols.. how do i debug the running kernel? gdb -k /kernel.debug /dev/mem and can i make it log the info to a file? Log what into a file? Syslog can log the messages the kernel produces into a file. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : Is the cardbus stuff in the GENERIC kernel, or will I have to change it : and build my own release or custom sysinstall? You'll have to build a NEWCARD kernel, and put it on the install disk. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
Brian Somers [EMAIL PROTECTED] wrote: ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem too. Sorry, you're misremembering. I've never seen anything like this. You're right you know - my apologies ! -- Christian "naddy" Weisgerber [EMAIL PROTECTED] -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest on rewrite of pkg_install tools.
Hi, On Sun, Jan 07, 2001 at 11:15:23AM +0100, Alexander Langer wrote: This is great! Thanks. With a litle bit more work, I'm hoping to have solved all of my current peeves with ports/packages. Then it'll be time to look for new peeves... However, the patch has some whitespace-fubars: Sorry about that... I've corrected the patch (and also removed the CVS .#* leftovers...). The current source uses a wierd 8 space tab and 4 hard space indentation, which I just wacked with perl, and I've been editting the code using 4 space tabs. Before this gets committed, I'll make sure that the indentation is correct, although I'll probably keep it at 4 space tabs, and not 8 space like style(9), because I prefer that, and I know Jordan does too. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SCSI CD recorder no longer attached; minor issues
Dear FreeBSD'ers, I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can see the following (a # sign precedes my comments): Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad2s1a # YAMAHA CRW4416S: it is correctly recognized by -STABLE. # OTOH, the archives seem to report just *minor* SCSI issues. (cd0:ahc0:0:3:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:3:0): error code 0 (cd0:ahc0:0:3:0): fatal error, failed to attach to device (cd0:ahc0:0:3:0): lost device (cd0:ahc0:0:3:0): removing device entry # My cd player works cd1 at ahc0 bus 0 target 6 lun 0 cd1: PLEXTOR CD-ROM PX-40TS 1.00 Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present # It is unusual on this system pcm0: hwptr went backwards 20 - 12 pcm0: hwptr went backwards 2072 - 2048 pcm0: hwptr went backwards 2184 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2068 - 2048 pcm0: hwptr went backwards 2240 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2204 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2068 - 2048 pcm0: hwptr went backwards 2068 - 204 I forgot to reboot via 'shutdown -r now' *sigh* On a couple of subsequent occasions, however, shutdown -r now was timed out, and no entropy file was created; 'dd if=/dev/random of=/entropy bs=4096 count=1' (within the shutdown sequence) did NOT create anything. In s.u.m., I issued it as an ordinary explicit command, but it stalled. So... workaround: 'dd if=/dev/urandom of=/entropy bs=4096 count=1'. Then /dev/random, asked again to do its duty, helped dd (to) create an entropy file. I was wondering whether such a sanity check would be worth adding (in rc.shutdown ?) in order to prevent the above entropy (minor) issue. Does this make sense at all? Is this just a little temporary problem ? Thanks for your patience and best regards,. Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
Alright, will do. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 7 Jan 2001, Warner Losh wrote: In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : Is the cardbus stuff in the GENERIC kernel, or will I have to change it : and build my own release or custom sysinstall? You'll have to build a NEWCARD kernel, and put it on the install disk. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
on another note, did you ever get a chance to look at that code that supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I believe. I could still find it for you if you want. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 7 Jan 2001, Warner Losh wrote: In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : Is the cardbus stuff in the GENERIC kernel, or will I have to change it : and build my own release or custom sysinstall? You'll have to build a NEWCARD kernel, and put it on the install disk. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cardbus installs on -current
In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : on another note, did you ever get a chance to look at that code that : supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I : believe. I could still find it for you if you want. I believe that those issues have been fixed with the pmtimer device. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SCSI CD recorder no longer attached; minor issues
Dear FreeBSD'ers,
I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can
see the following (a # sign precedes my comments):
Can you see if this patch corrects the problem?
--
Justin
Index: dev/aic7xxx/aic7xxx.c
===
RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx.c,v
retrieving revision 1.63
diff -c -r1.63 aic7xxx.c
*** dev/aic7xxx/aic7xxx.c 2001/01/05 19:15:36 1.63
--- dev/aic7xxx/aic7xxx.c 2001/01/08 04:48:36
***
*** 487,494
printf("Sending Sense\n");
}
#endif
! sg-addr = ahc-scb_data-sense_busaddr
! + (hscb-tag*sizeof(struct scsi_sense_data));
sg-len = ahc_get_sense_bufsize(ahc, scb);
sg-len |= AHC_DMA_LAST_SEG;
--- 487,493
printf("Sending Sense\n");
}
#endif
! sg-addr = ahc_get_sense_bufaddr(ahc, scb);
sg-len = ahc_get_sense_bufsize(ahc, scb);
sg-len |= AHC_DMA_LAST_SEG;
Index: dev/aic7xxx/aic7xxx_freebsd.c
===
RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx_freebsd.c,v
retrieving revision 1.16
diff -c -r1.16 aic7xxx_freebsd.c
*** dev/aic7xxx/aic7xxx_freebsd.c 2000/12/20 01:11:37 1.16
--- dev/aic7xxx/aic7xxx_freebsd.c 2001/01/08 04:46:28
***
*** 337,343
*/
memset(ccb-csio.sense_data, 0, sizeof(ccb-csio.sense_data));
memcpy(ccb-csio.sense_data,
! ahc-scb_data-sense[scb-hscb-tag],
(scb-sg_list-len AHC_SG_LEN_MASK)
- ccb-csio.sense_resid);
scb-io_ctx-ccb_h.status |= CAM_AUTOSNS_VALID;
--- 337,343
*/
memset(ccb-csio.sense_data, 0, sizeof(ccb-csio.sense_data));
memcpy(ccb-csio.sense_data,
! ahc_get_sense_buf(ahc, scb),
(scb-sg_list-len AHC_SG_LEN_MASK)
- ccb-csio.sense_resid);
scb-io_ctx-ccb_h.status |= CAM_AUTOSNS_VALID;
Index: dev/aic7xxx/aic7xxx_inline.h
===
RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx_inline.h,v
retrieving revision 1.9
diff -c -r1.9 aic7xxx_inline.h
*** dev/aic7xxx/aic7xxx_inline.h2000/12/20 01:11:37 1.9
--- dev/aic7xxx/aic7xxx_inline.h2001/01/08 04:55:49
***
*** 200,205
--- 200,211
static __inline void ahc_swap_with_next_hscb(struct ahc_softc *ahc,
struct scb *scb);
static __inline void ahc_queue_scb(struct ahc_softc *ahc, struct scb *scb);
+ static __inline struct scsi_sense_data *
+ ahc_get_sense_buf(struct ahc_softc *ahc,
+ struct scb *scb);
+ static __inline uint32_t
+ ahc_get_sense_bufaddr(struct ahc_softc *ahc,
+ struct scb *scb);
/*
* Determine whether the sequencer reported a residual
***
*** 344,349
--- 350,374
if ((ahc-features AHC_AUTOPAUSE) == 0)
unpause_sequencer(ahc);
}
+ }
+
+ static __inline struct scsi_sense_data *
+ ahc_get_sense_buf(struct ahc_softc *ahc, struct scb *scb)
+ {
+ int offset;
+
+ offset = scb - ahc-scb_data-scbarray;
+ return (ahc-scb_data-sense[offset]);
+ }
+
+ static __inline uint32_t
+ ahc_get_sense_bufaddr(struct ahc_softc *ahc, struct scb *scb)
+ {
+ int offset;
+
+ offset = scb - ahc-scb_data-scbarray;
+ return (ahc-scb_data-sense_busaddr
+ + (offset * sizeof(struct scsi_sense_data)));
}
/** Interrupt Processing **/
Re: cardbus installs on -current
oh ok, sounds good then... I'll definitly try it out soon then. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 7 Jan 2001, Warner Losh wrote: In message [EMAIL PROTECTED] Kenneth Wayne Culver writes: : on another note, did you ever get a chance to look at that code that : supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I : believe. I could still find it for you if you want. I believe that those issues have been fixed with the pmtimer device. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
