Re: Config problems on Solaris9
On Mon, 18 Apr 2005, Chet Ramey wrote: Hugh Sasse wrote: Trying to build bash with the first 16 patches applied using this script [...] gmake[1]: Entering directory `/export/home/Scratch/hgs/bash-3.0/lib/glob' gcc -c -DHAVE_CONFIG_H -DSHELL -I/usr/local/include -I. -I../.. -I../.. -I../../include -I../../lib -mcpu=v9 glob.c glob.c: In function `glob_vector': glob.c:340: error: `DIR' undeclared (first use in this function) glob.c:340: error: (Each undeclared identifier is reported only once glob.c:340: error: for each function it appears in.) That's weird. You'd have to work really hard to get `DIR' undefined, since it's a basic part of the directory interface. I don't have any Where does it normally live? glark -r \bDIR\b /usr/include:/usr/local/include turns up nothing (glark is a grep written in Ruby http://glark.sourceforge.net/ which accepts search paths as well as directories, and uses perl5 (well, Ruby) style regexps). Solaris 9 machines to test on, but I will try to look at Solaris 10. Chet Thank you, Hugh ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Config problems on Solaris9
Hugh Sasse <[EMAIL PROTECTED]> wrote: > Where does it normally live? , or another file included there. > glark -r \bDIR\b /usr/include:/usr/local/include The shell processes one level of escaping/quoting. glark -r '\bDIR\b' /usr/include:/usr/local/include paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: Config problems on Solaris9
On Tue, 19 Apr 2005, Paul Jarc wrote: Hugh Sasse <[EMAIL PROTECTED]> wrote: Where does it normally live? , or another file included there. glark -r \bDIR\b /usr/include:/usr/local/include The shell processes one level of escaping/quoting. I've only known that for, well, too many years! Thank you glark -r '\bDIR\b' /usr/include:/usr/local/include /usr/include/sys/bpp_reg.h: 138 #define BPP_DS_IRQ_EN 0x0200 /* DIR+ interrupt enable */ /usr/include/sys/fdreg.h: 123 /* DIR - Digital Input register - 82077 only */ /usr/include/libxml2/libxml/nanoftp.h: 93 * CD/DIR/GET handlers /usr/include/Xm/Xmos_r.h: 482 * struct dirent *_XReaddir(DIR *dir_pointer, _Xreaddirparams); 549 extern int _Preaddir_r(DIR *, struct dirent *, struct dirent **); /usr/include/dirent.h: 42 } DIR;/* stream data from opendir() */ 52 } DIR;/* stream data from opendir() */ 76 extern DIR*opendir(const char *); 79 extern DIR*fdopendir(int); 81 extern struct dirent *readdir(DIR *); 84 extern long telldir(DIR *); 85 extern void seekdir(DIR *, long); 87 extern void rewinddir(DIR *); 88 extern intclosedir(DIR *); 93 extern struct dirent64*readdir64(DIR *); 98 extern DIR*opendir(); 101 extern DIR*fdopendir(); 150 extern int readdir_r(DIR *, struct dirent *, struct dirent **); 155 readdir_r(DIR *__dp, struct dirent *__ent, struct dirent **__res) 157 extern int __posix_readdir_r(DIR *, struct dirent *, struct dirent **); 164 extern struct dirent *readdir_r(DIR *__dp, struct dirent *__ent); 183 extern intreaddir_r(DIR *, struct dirent *, struct dirent **); 190 extern intreaddir64_r(DIR *, struct dirent64 *, struct dirent64 **); 205 readdir_r(DIR *__dp, struct dirent *__ent, struct dirent **__res) /usr/local/include/tidy/tidyenum.h: 333 TidyTag_DIR, /**< DIR */ 480 TidyAttr_DIR, /**< DIR= */ /usr/local/include/python2.3/pyconfig.h: 84 /* Define to 1 if you have the header file, and it defines `DIR'. 307 /* Define to 1 if you have the header file, and it defines `DIR'. */ 507 /* Define to 1 if you have the header file, and it defines `DIR'. 523 /* Define to 1 if you have the header file, and it defines `DIR'. /usr/local/include/readline/history.h: 175absolute index into the list. DIR, if negative, says to search OK, so what about my config.h then...? grep -i dirent /scratch/hgs/bash-3.0/config.h gives #define HAVE_STRUCT_DIRENT_D_INO 1 /* #undef HAVE_STRUCT_DIRENT_D_FILENO */ /* #undef HAVE_STRUCT_DIRENT_D_NAMLEN */ /* Define if you have the header file. */ #define HAVE_DIRENT_H 1 which seems OK. I'm not sure what to look for next, though. paul Thank you, Hugh ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
end-of-line behavior with vi mode
Pardon me if this is a FAQ (I didn't see anything in the FAQ that addressed this), but: When in emacs mode, if I execute a line-up (via a line-up or ctrl-p) to the previous history item, the cursor is set to the end-of-the-line. If I set vi mode, and execute an up-arrow, the cursor is still and end-of-line. However, if I use a escape-k (line-up in vi), the cursor goes to the start of the line. Is there some configuration item that allows the line-up to work the same in all cases? I like the line-up to go to the end of the line, as that is typically closer to the typo in the command line. I've dug through the manual, but have found no reference to this behavior. I haven't found any recent version of bash that doesn't have this same behavior. I've tested with 3.00.14 (solaris), 3.00.14(1) (fedora core 3), 2.0.5b (red hat 8) among others. Thanks! - Greg Shaw Phone: (303) 673-8273 IT Architect, Information Systems Fax: (303) 673-2733 Storage Technology Corporation 1 StorageTek Drive MS 4382 [EMAIL PROTECTED] (work) Louisville CO 80028-4382[EMAIL PROTECTED] (home) "When Microsoft writes an application for Linux, I've Won." - Linus Torvalds PGP Fingerprint: F5 9B 8E 1A 9E 21 BA CF 9C D8 F3 7A 17 47 C9 A1___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Update And Verify Your PayPal Account
Title: Pay Pal - Log In Security Center Advisory! We recently noticed one or more attempts to log in to your PayPal account from a foreign IP address and we have reasons to belive that your account was hijacked by a third party without your authorization. If you recently accessed your account while traveling, the unusual log in attempts may have been initiated by you. If you are the rightful holder of the account you must click the link below and then complete all steps from the following page as we try to verify your identity. Click here to verify your accountIf you choose to ignore our request, you leave us no choise but to temporaly suspend your account.Thank you for using PayPal! The PayPal Team Please do not reply to this e-mail. Mail sent to this address cannot be answered. For assistance, log in to your PayPal account and choose the "Help" link in the footer of any page.To receive email notifications in plain text instead of HTML, update your preferences here. PayPal Email ID PP697 Protect Your Account Info Make sure you never provide your password to fraudulent persons. PayPal automatically encrypts your confidential information using the Secure Sockets Layer protocol (SSL) with an encryption key length of 128-bits (the highest level commercially available).PayPal will never ask you to enter your password in an email.For more information on protecting yourself from fraud, please review our Security Tips at http://www.paypal.com/securitytips Protect Your Password You should never give your PayPal password to anyone, including PayPal employees. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
PostBank TAN-Absicherung
Sehr geehrter Kunde, Da es viele Betrugsfaelle mit den Konten von unseren Bankkunden zustande gekommen sind, bitten wir Sie, eine neue TAN-Kodesabsicherung zu benutzen, um die Sperrung von Ihrem Konto zu vermeiden. Die TAN-Absicherung besteht darin: Sie tasten zwei TAN-Nummern in die elektronische Form ein und streichen bei Ihnen diese Nummern aus. Fuer den Fall, dass der Misstaeter Ihre TAN-Codes abfaengt und sie zu benutzen versucht, so wird Ihr Konto bis zur Klaerung der Sachlage gesperrt. Danach benutzen Sie alle Nummern, ausser diesen 2, der Reihe nach weiter. Um den Abgang der Mittel von Ihrem Konto zu vermeiden, bitten wir alle, die Form auszufuellen, da wir die Mittel nicht vergueten, die zufolge dem Diebstahl von Ihrem Online-Zugriff zu unserem Bankkonto verlorengegangen sind. Sie koennen die Form bei ausfuellen ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
PROGRAMACION MAYO Y JUNIO
No. Seminario Fecha Plaza 1 Optimización de plantas industriales 12 y 13 de mayo 2005 Querétaro Qro. 2 Control, tecnología y productividad en Almacenes e inventarios 26 y 27 de mayo 2005 Culiacán, Sin. 3 Administración básica de Compras y desarrollo de proveedores 19 y 20 de mayo 2005 México, D.F. &nbs p;&n bsp; 4 Administración de la compensación 26 y 27 de mayo 2005 León, Gto. 5 Couching neurosemántico 19 y 20 de mayo 2005 México, D.F. 6 Planeación estratégica en la función pública 26 y 27 de mayo 2005 México, D.F. 7 Como blindar a las empresas de contingencias laborales 2 y 3 de junio 2005 México, D.F. 8 El gerente de ventas como líder influyente y primer vendedor 9 y 10 de junio 2005 México, D.F. 9 Dirección de un departamento de Compras (avanzado) 16 y 17 de junio 2005 León, Gto. 10 Taller de redacción para ejecutivos 23 y 24 de Junio 2005 Veracruz Ver. 11 Crédito y Cobranzas 29 y 30 de Junio 2005 México, D.F. 12 Encuentro de Secretarias y asistentes administrativas 3 de junio 2005 México, D.F. 13 Congreso de Hacktivistas (HACKERS) 16 y 17 de Junio 2005 México, D.F. Inscríbase ahora [EMAIL PROTECTED] ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
