Re: Opera for FreeBSD
On Fri, Nov 01, 2002 at 10:25:57PM +0100, Marc Schneiders wrote: I am glad that my visit to websites is no longer recorded as being from a Linux machine. But there is a price: good bye to the Linux plugins (flash, acrobat...). -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvs commit: ports/mail/mutt-devel Makefile
On Sun, May 05, 2002 at 03:31:47PM -0400, Andy Sparrow wrote: Both of which are specifically stated to be incorrect (with an explanation why) by the maintainer of XFree86 xterm on his web page. XFree86's 'xterm' is a color xterm, and has been for years. We don't ship their termcap entry. Substituting the XFree86 termcap/terminfo entries for ours apparently fixes the currently broken behaviour. Yes, but other people does not like some features of the xterm termcap entry supplied by XFree86. Other OSen do not have xterm-color, though (as has already been mentioned, Solaris), so this breaks as soon as you ssh to one of these remote machines. As someone who runs Solaris servers from a FreeBSD desktop I do this a lot. What he said :) Also, some OS's have an entry for 'xterm-color' that is NOT the XFree86 xterm, but an obsolete xterm variant, and this will also break. And I absolutely agree. In fact we also have Solaris and Irix machines, which I hacked (adding a xterm-color entry, or redefining TERM in the session startup scripts). What I wanted to say is that defining termName in XTerm-color is *coherent* with FreeBSD having two distinct termcap xterm entries: mono and color. However, I also think that having those two entries is *bad*. IMHO, the xterm and xterm-color entries should be merged in only one xterm supporting color. Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: apropos Euro
On Tue, Jan 01, 2002 at 07:39:48PM +0100, Oliver Fromme wrote: Finally, many programs should respect the locale settings of your environment. The environment variable LC_CTYPE is responsible for declaring your character set to programs and applications that are l10n/i18n compliant. You can see all locales in the /usr/share/locale directory. For example, put the following in your shell's startup script if you use some kind of bourne shell (sh, ksh, zsh, bash): export LC_CTYPE=en_US.DIS_8859-15 For csh or tcsh, use this one: setenv LC_CTYPE en_US.DIS_8859-15 Note that the locale name was changed recently from DIS to ISO. Look at the /usr/share/locale directory for the right name. The change from DIS to ISO only happened in -CURRENT. Moreover, the '_' character was stripped from the ISO_8859 string . These changes in the locale names have not been MFC'd yet; as a consequence, the alias definition es_ES.DIS_8859-15:es_ES.ISO8859-15 must be added to /usr/X11R6/lib/X11/locale/locale.alias in order to get X11 working with the ISO8859-15 locale. Unfortunately, 4.5-RELEASE will be released with the old-fashioned locale names. I have just sent the patch for locale.alias to the x11/XFree86-4 port maintainer. Just my 0,02¤ ^- euro symbol ;-) Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Realtek 8139
On Thu, Nov 29, 2001 at 10:13:41AM -0200, Luiz Gustavo (Berrão) wrote: I'm still having problems with the realtek ethernet card. One of my friends told me that the rl0 module doesn't work fine with other modules (like, if I want two ethernet cards or both are rl0 or none is). Is it true? You did not give any details about your problems with the rl8139. Anyway, these cards usually have problems with autonegotiation. Try to force the medium using ifconfig(8) (ifconfig -m shows all possible media choices). Cheers, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: /usr/src/UPDATING
On Sat, Nov 03, 2001 at 09:11:36AM -0800, Bruce A. Mah wrote: If memory serves me right, Jose M. Alcaide wrote: Hmmm... what about dirpref and UFS_DIRHASH? And the recent MFC of ipfw also comes to my mind. UPDATING lists potential breakages: This file contains a list, in reverse chronologocal order, of major breakages in tracking -stable. Not all things will be listed here, UPDATING != release notes. You are right, of course, respecting dirpref and UFS_DIRHASH. However, the ipfw MFC require a rebuild of ipfw.ko. Here is a excerpt from the recent HEADSUP sent by Luigi Rizzo to -stable: * the merge of ipfw rule descriptor and chain pointer. No functional change, but the internal data structures and code are way more readable; * Bill Fenner's code to make ipfw/dummynet/bridge KLD'able BOTH THESE THINGS REQUIRES REBUILDING OF ipfw.ko and /sbin/ipfw I am not sure if that should be added to UPDATING. After all, it was not added to -CURRENT's /usr/src/UPDATING neither ;-) Regards, JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.4rc4 now on ftp-master.freebsd.org
On Thu, Sep 06, 2001 at 04:43:55PM -0700, Jordan Hubbard wrote: I'll make a symlink for the packages now that it's been properly mirrored, thanks for the reminder. I am somewhat confused about the 4.4-RCx package collections: $ rsync ftp-master.freebsd.org::FreeBSD/ports/i386/ ... drwxr-xr-x1536 2001/09/07 02:02:56 packages-4.4-rc3 drwxr-xr-x1536 2001/09/05 06:59:47 packages-4.4-rc4 lrwxr-xr-x 16 2001/09/07 09:12:56 packages-4.4-release ... and packages-4.4-release is a symlink to packages-4.4-rc4, as expected. However, based on the modification times, packages-4.4-rc3 is newer that packages-4.4-rc4. In addition, the package collection symlinked from 4.4-RC4 is packages-4.4-rc3. Strange... JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Audio problem in 4.4-RC3
On Thu, Sep 06, 2001 at 09:30:06AM -0400, Christopher M. Giordano wrote: Playing .wav files using waveplay port - the majority of the file plays normally, except the ending is clipped off. Similar results using the wavplay port (the one with no e in wave). This started happening after the August 2 /sys/dev/sound commits, and continues even with Cameron's subsequent commits from Aug. 31. Initially there was also a hiccup or dropout in the first second or so of play, but the latest round of commits seems to have eliminated that. I think I am seeing the same problem. I am using a Maestro-2E soundchip, however. Please, try to play the splat.au file attached (µ-law encoding, 8 bit/8 KHz) and let me know if you hear something (type cat splat.au /dev/audio). I don't, but it was played before the August 2 commits. Even if I load the snd_pcm.ko and snd_maestro.ko modules, borrowed from a 4.3-RELEASE system, audio playing works fine. I reported the problem to both -multimedia and Cameron Grant, but I didn't receive any feedback :-( JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** splat.au
Re: Via KT133 chipset and DMA diskaccess
Marc Albers wrote: I'm have not been able to get DMA disk access to work ( DMA33 or DMA66 ) on my new Abit KT7. I have heard of several people having it working perfectly on their KA133 based motherboards. Therefore I am curious: Is there anyone who has this working on an VIA KT133 based motherboard? If so, can this person assist me in taming my beast? Works here: atapci0: VIA 82C686 ATA66 controller port 0xffa0-0xffaf at device 7.1 on pci0 [...] ad0: 9768MB ST310212A [19846/16/63] at ata0-master using UDMA66 acd0: CDROM CRD-8482B at ata1-master using WDMA2 The MB is a Gigabyte GA-7ZX. However, I had problems when the CD-ROM was connected as primary slave: it was not detected, and the ATA probe routine reported that the cable is not ATA66 compatible (but it *is*). Cheers, -- JMA ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: bug in the syscons fonts ?
Maxime Henrion wrote: I've noticed a weird thing in the fonts of syscons that i think may be a bug. I am a french user, so i have these lines in my rc.conf to have FreeBSD correctly displaying my accentued characters : keymap="fr.iso.acc" font8x8="cp850-8x8" font8x14="cp850-8x14" font8x16="cp850-8x16" scrnmap="iso-8859-1_to_cp437" The problem is that when i type a "à" (an "a" with a backquote for thoses who cant see it correctly), i get a "D" on the screen ! This only occurs while i'm on a text console, not under X. Have i done something wrong ? Thanks for help ! Try this configuration: keymap="fr.iso.acc" font8x8="iso-8x8" font8x14="iso-8x14" font8x16="iso-8x16" (delete the "scrnmap" line). -- JMA ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Xircom PCMCIA card support
Will Mitayai Keeso Rowe wrote: Will FreeBSD be supporting the Xircom PCMCIA cards anytime in the near future? I've got a Xircom Cardbus 100 / 56K Modem combo PC card in my Dell Inspiron 5000, and i'd much rather run FreeBSD on it than Linux... FreeBSD supports the Xircom PCMCIA cards (xe(4) driver), but there is no support for any Cardbus devices yet. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: i810 Kernel module for XFree86 3.3.6.
Carl Makin wrote: Has anybody played around with porting the agpgart.o Linux kernel module to FreeBSD 3.4? Unfortunately I'm not up to the port myself however I'll help with testing it if anyone else is doing it! We had to reject five i810e-based PCs because they wasn't capable of running FreeBSD + XFree86 3.3.6. (Of course, I warned about that, but someone chose the cheaper model "with 133 MHz bus" -- when it runs at 100 MHz with a PIII 500!). Personally, I decided to boycott the i810 chipset. I am absolutely opposed to chipsets including graphics and audio controllers. And IMHO now Intel Corp. attacks the makers of graphics and audio cards, imposing [even] more restrictions on our freedom of choice in the PC market. Rats. -- JMA --- José Mª Alcaide | mailto:[EMAIL PROTECTED] Universidad del País Vasco | mailto:[EMAIL PROTECTED] Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 --- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Core dumps: FreeBSD 3.3-stable and bash 2.03.0(1) + ulimit -c 0
Trond Endrestol wrote: I'm using FreeBSD 3.3-stable, GNU bash 2.03.0(1), and I have a ``ulimit -c 0'' line in my .bashrc file. When I ran FreeBSD 2.2.8-RELEASE some while ago, ``ulimit -c 0'' caused no core files to be created when the software crashed. Under both FreeBSD 3.3-RELEASE and FreeBSD 3.3-stable, core files are created, but have zero length, despite ``ulimit -c 0''. What has gone wrong? Is it bash or is it FreeBSD? See PR kern/14540. It has been fixed in -CURRENT. -- JMA --- José Mª Alcaide | mailto:[EMAIL PROTECTED] Universidad del País Vasco | mailto:[EMAIL PROTECTED] Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 --- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
