Re: Very large kernel
> I noticed that the kernel directory was very large compaired to 6.1. Is > this for debugging and can I safely remove the symbols files I want to > save some space? Yes, you can do this safely. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Jamie Bowden schrieb: On 9/9/06, Mark Andrews <[EMAIL PROTECTED]> wrote: > Yeah, -STABLE is what you should run if you want stable code, right? No. STABLE means STABLE API. If you want stable code you run releases. Between releases stable can become unstable. Think of stable as permanent BETA code. Changes have passed the first level of testing in current which is permanent ALPHA code. No, this is what it means now. [...] Why do you say "No" if you mean "Yes, but in former times ..."? Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
hackmiester (Hunter Fuller) schrieb: On 12 September 2006, at 02:06, Björn König wrote: Karl Denninger schrieb: This is not cool folks. I think you misunderstood what -STABLE means. (Or maybe I do?) -STABLE is still a development branch without guarantee of a stable and working operating system. Hahahahaha... That's ironic... That wasn't meant to be ironic. Years of experience and observations of development lead to this conclusion. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Vivek Khera schrieb: On Sep 12, 2006, at 6:23 PM, hackmiester (Hunter Fuller) wrote: -STABLE is still a development branch without guarantee of a stable and working operating system. Hahahahaha... That's ironic... No, just misinterpretation of which attribute of the system to which the word "stable" applies. Do you really think I misinterpreted the meaning of -STABLE? *I* think most people misinterprete -STABLE because the first thing that comes to mind is runtime stability. The same issue exists in the GNU/Debian Linux world: Debian stable doesn't mean that the system run always rock-solid and works perfectly, but rather the state of software is stable, i.e. maintainers ensure 100% compatibility between updates. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Karl Denninger schrieb: This is not cool folks. I think you misunderstood what -STABLE means. (Or maybe I do?) -STABLE is still a development branch without guarantee of a stable and working operating system. -STABLE guarantees that interfaces remain stable. If you want reliability then jump from release to release. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unmounting a filesystem safely that doesn't exist anymore
Peter Jeremy schrieb: On Sat, 2006-Jun-10 19:40:41 +0200, Bjrn Knig wrote: I did a mistake: I unplugged my digital camera accidentally before I unmounted the filesystem. *doh* This happens very often, because I'm very scatterbrained. =) Your best solution may be to use mtools (ports/emulators/mtools) rather than mounting the filesystem. changed ad hoc. I just want to know if somebody knows a workaround or small trick that prevents the other filesystems from being unclean on next boot-up. The only way to do this is to have all the other filesystems mounted read-only. The "filesystem clean" flag is part of the superblock and is cleared when a filesystem is mounted. It will be set only if the filesystem is cleanly unmounted. Thank you very much for these information. They help me a lot. Björn P.S. I get the feeling questions@ would had been a better place for my question. ;-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unmounting a filesystem safely that doesn't exist anymore
Hello, I did a mistake: I unplugged my digital camera accidentally before I unmounted the filesystem. *doh* This happens very often, because I'm very scatterbrained. =) The kernel will panic and all filesystems remain unclean in any case now. I know that this is a well know issue and in past discussions you stated that this behaviour is intended and won't be changed ad hoc. I just want to know if somebody knows a workaround or small trick that prevents the other filesystems from being unclean on next boot-up. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 RELEASE compiling problems:
Kaiwai Gardiner schrieb: Hi, I am experiencing problems compiling FreeBSD 6.1 RELEASE; the following link has the relevant information: http://www.freebsd.org/cgi/query-pr.cgi?pr=97240 The file does exist in the src/contrib/gcc directory, but it seems that the compiler/installer isn't picking it up. Thank you for any help, This is not a problem that occur with 6.1-RELEASE only. There are a lot of mails in the FreeBSD mailing list archive concerning this. I suggest to delete /usr/obj and remove compiler settings and flags from /etc/make.conf. buildworld is not supported with "-Os -march=pentiumpro". Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't compile without COMPAT_43 on i386
Mike Jakubik schrieb: I can compile an amd64 kernel just fine without the option COMPAT_43, but not i386. Why is this? /usr/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:36:2: #error "Unable to compile Linux-emulator due to missing COMPAT_43 option!" mkdep: compile failed I don't want or need the Linux-emulator. The corresponding module will be built nevertheless. If you want to build only a selection of modules then you have to specify MODULES_OVERRIDE, e.g. makeoptions MODULES_OVERRIDE="acpi" in your kernel configuration file. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
Dmitry Morozovsky schrieb: BK> cat /tftpdroot/boot/loader.conf none Then loader.conf of your NFS root. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
Dmitry Morozovsky schrieb:
Colleagues,
${SUBJ} says almost all. PXEboot leads to
Can't work out which disk we are booting from.
error.
Ungzipping /boot/mfsroot.gz helps
Hello Dmitry,
I can't report any problems regarding this with 6.0-RELEASE. Can you
show me
find /tftproot -type f
and
cat /tftpdroot/boot/loader.conf
please?
Did you compiled pxeboot without gzip support accidentally?
Regards
Björn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: loader_color="YES"
Nikolas Britton schrieb: On 2/28/06, Pete Slagle <[EMAIL PROTECTED]> wrote: loader_logo does not appear in /boot/defaults/loader.conf, at least not in 6.0-RELEASE-p4. Is that an oversight? Their are lots of undocumented feature in FreeBSD. loader_color="YES" AFAIK It was never document in 5.x, I found it by accident Nevertheless it has been removed before 6.0-RELEASE. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel build failure
Robert Uzzi schrieb: Can someone shed some light on the following error? rm -f .depend GPATH GRTAGS GSYMS GTAGS CC=cc make -f ../../../dev/aic7xxx/aicasm/Makefile MAKESRCPATH=../../../dev/aic7xxx/aicasm Warning: Object directory not changed from original /usr/src/sys/i386/compile/CUSTOM-SMP cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I../../../dev/aic7xxx/aicasm -c aicasm_gram.c ../../../dev/aic7xxx/aicasm/aicasm_gram.y:1933: error: conflicting types for 'yyerror' aicasm_gram.c:3133: error: previous implicit declaration of 'yyerror' was here *** Error code 1 Stop in /usr/src/sys/i386/compile/CUSTOM-SMP. *** Error code 1 Stop in /usr/src/sys/i386/compile/CUSTOM-SMP. Tried rm -R /usr/obj? Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linksys WPC54g v4, NDIS, & Kernel Panics
Bill Paul schrieb: People, I'm getting tired of always having to ask for this basic information. The more I have to ask, the more annoyed I get, and the less inclined I am to help anyone. The shit you don't think is important? It's important. So spill it already. Take it easy. Just refer to http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-questions/x114.html next time. ;-) Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Source upgrade for 6-STABLE gets: "ERROR: Source upgrades from versions prior to 5.3 not supported."
David Wolfskill schrieb:
This caught me a bit by surprise. This was on my laptop:
localhost(6.0-S)[2] uname -a
FreeBSD localhost 6.0-STABLE FreeBSD 6.0-STABLE #56: Wed Jan 18 07:47:29 PST 200
6 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386
localhost(6.0-S)[3]
As you see, I had done this recently, and the process isn't exactly
unfamiliar to me.
So I started the "make buildworld" and got:
localhost(6.0-S)[1] _bw^M
root
/dev/ad0s3a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s3e on /usr (ufs, local, soft-updates)
/dev/ad0s3f on /var (ufs, local, soft-updates)
/dev/ad0s3g on /common (ufs, local, soft-updates)
/dev/ad0s3h on /bkp (ufs, local, soft-updates)
procfs on /proc (procfs, local)
/dev/md0 on /tmp (ufs, local, soft-updates)
FreeBSD localhost 6.0-STABLE FreeBSD 6.0-STABLE #56: Wed Jan 18 07:47:29 PST 200
6 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386
Thu Jan 19 08:00:52 PST 2006
--
Building an up-to-date make(1)
--
make: don't know how to make /usr/include/sys/cdefs.h. Stop
--
Rebuilding the temporary build tree
--
rm -rf /usr/obj/usr/src/tmp
mkdir -p /usr/obj/usr/src/tmp/legacy/usr/bin
...
ln -sf /usr/src/sys /usr/obj/usr/src/tmp
--
stage 1.1: legacy release compatibility shims
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp INSTALL="sh /usr/src/tools/i
nstall.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legac
y/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin W
ORLDTMP=/usr/obj/usr/src/tmp MAKEFLAGS="-m /usr/src/tools/build/mk -j 6 -m /us
r/src/share/mk" /usr/obj/usr/src/make.i386/make -f Makefile.inc1 DESTDIR= BOOT
STRAPPING=0 -DNO_HTML -DNO_INFO -DNO_LINT -DNO_MAN -DNO_NLS -DNO_PIC -DNO_PROF
ILE -DNO_SHARED -DNO_CPU_CFLAGS -DNO_WARNS legacy
ERROR: Source upgrades from versions prior to 5.3 not supported.
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
localhost(6.0-S)[2] uname -a^M
FreeBSD localhost 6.0-STABLE FreeBSD 6.0-STABLE #56: Wed Jan 18 07:47:29 PST 200
6 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386
localhost(6.0-S)[3] exit
I realize that "0" is likely to be considered "< 503000" (ref
/usr/sr/cMakefile.inc1, line 765 of rev. 1.499.2.7).
Is BOOTSTRAPPING really "0"? Add the line
@echo ${BOOTSTRAPPING}
below this line to make sure in case you didn't already.
Show also the output of
grep 'define.*FreeBSD' /usr/include/osreldate.h
Björn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pw groupdel misbehavior?
Hello, Right now I submitted a problem report with a suggestion for a patch concerning this. It has the internal identification `bin/90114'. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 stable and Apache 2.0
Quirino Santilli wrote: ...and is this directive valid both for the ports and the package system? It works only for ports. This behaviour is documented in the introducing comments of /usr/ports/Mk/bsd.port.mk Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 stable and Apache 2.0
Hello Quirino, add the line APACHE_PORT=www/apache13-modssl or APACHE_PORT=www/apache20 or whatever you like to /etc/make.conf and every port that depends on Apache will require the specified port. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: who has experience about updating freebsd from 4.11 to 5.x
Hello, Read also http://www.freebsd.org/releases/5.4R/migration-guide.html Best Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-RELEASE (amd64) on LSILogic 1030 / mpt controller.
Krzysztof Kowalik wrote: And 6.0-BETA2 works fine. Did someone forget to merge some fixes for mpt from RELENG_5 to RELENG_5_4? [...] It might be a candidate for an errata notice. Those fixes won't go without saying into a previously released branch. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VIA vt6202 controller not recognised by FreeBSD 5.4-Release (ehci)
Mark Sergeant wrote: Output from pciconf -lv [EMAIL PROTECTED]:7:2 class=0x0c0320 card=0x12340925 chip=0x31041106 rev=0x51 hdr=0x00 vendor= 'VIA Technologies Inc' device= 'VT6202 USB 2.0 Enhanced Host Controller' class= serial bus subclass= USB The same card has it's usb 1.0 component recognised as a VIA VT82xx UHCI USB 1.1 Controller, it also has the ehci part recognised by ubuntu. Any ideas ? Build a custom kernel with "options ehci". It's disabled by default as you can see in /usr/src/sys/i386/conf/GENERIC. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.11 to RELENG_6
Randy Bush wrote: any peculiarities/clues for upgrading an antique from 4.11 to RELENG_6 beyond the "To upgrade in-place from 5.x-stable to current" in UPDATING? I guess not. From the release notes of 6.0-BETA2: "Source upgrades to FreeBSD 6.0-CURRENT are only supported from FreeBSD 5.3-RELEASE or later. Users of older systems wanting to upgrade 6.0-CURRENT will need to update to FreeBSD 5.3 or newer first, then to FreeBSD 6.0-CURRENT." Björn -- Björn König ([EMAIL PROTECTED]) student at the Technische Universität Berlin http://bkoenig.alpha-tierchen.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 vs amd64 - benchmark results
Martin wrote: But I'm impressed by the RELENG_6 results. I think I'm going to upgrade my system instantly. Yes, the results are slightly better, even the support of amd64 appears to be much better, but I would be careful; it's easy to overrate benchmark results. There is a lot that you can do wrong if you create benchmarks and I would not guarantee for the correctness of my own results. Nevertheless I think 6.0 will be a great release with increased performance. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386 vs amd64 - benchmark results
You might want to have a look at my private benchmarks too: http://www.alpha-tierchen.de/dateien/etc/benchmark.html Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xf86enableIO error 28Feb 2005 Snapshots for FreeBSD available
-«:terror:»- wrote: How could I fix this error? Thanks Start here http://www.google.com/search?q=xf86enableIO+FreeBSD Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Fatal trap 12" while debugging a 4.11 kernel with remote gdb
Hello, I'm trying to debug a FreeBSD 4.11 kernel that has been compiled with makeoptions DEBUG=-g options DDB The remote machine is running FreeBSD 5.4 and I'm using devel/gdb6. I have no problems as long as I escape to the debugger after the kernel was loaded, but I like to trace something during the initialisation. I type 'boot -d', 'gdb' and 's' on the 4.11 machine and the following commands on the 5.4 machine: (kgdb) s Reply contains invalid hex digit 84 (kgdb) s Warning: Cannot insert breakpoint -1. Error accessing memory address 0xc02f09a8: Input/output error. At the same time of the second 'step' this happens with the 4.11 kernel: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xf0010502 fault code = supervisor read, page not present intruction pointer = 0x8:0xc02ed6b6 stack pointer = 0x10:0xc045de3c frame pointer = 0x10:0xc045de48 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam Does anyone has a hint for me to prevent this? Thanks in advance Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: recent RELENG_5 error
Tell the kind of your machine and the content of your make.conf, i.e. CFLAGS if there are any and so on. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Extended msdos partition
Jan Sebosik wrote: > I`ve klkload-ed msdosfs module, tried disklabel on /dev/ad0s2 > (which damaged my partition table), but it still something > about that it cannot mount partition (yeh, mount point e.g. > /mnt/c exists :-\ ). Is freebsd so different against Linux, or NetBSD? What is the error message? What did you type into the console? Did you use the -t option? Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
Scott Long schrieb: Are you talking about the AHCI standard, or something else? Can you provide a reference, please? I meant in particular ADMA from http://www.t13.org/project/d1510r1-Host-Adapter.pdf See also http://www.pacificdigital.com/talon/whitepaper.pdf I'm not sure if I mix something up right now. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
Holtor schrieb: Does the latest 5.x-STABLE support the Pacific Digital Talon ZL4-150 SATA RAID Card (U-30245)? After checking the hardware release notes I'm not sure. Any ideas? There is no hint that there is a FreeBSD driver implementing the public ATA host adapter standard. Therefore I think that this controller won't work. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Save the Demon!
David Magda wrote: It's "daemon", not "demon". :) It's a question whether you are British or American or understand it as a proper name. ;-) Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
Chris schrieb: there is also a bug which prevents compiling of ezbounce and psybnc, I wonder how much testing went into the new gcc compiler or was it just bundled into the release, considering this is the reccommended release for production server's now this is a bad oversight, I think the gcc should be changed in the next patch level back to 3.3.6. I compiled psybnc already a few times with FreeBSD 5.3 successfully. If there is a problem then please tell it. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: correct value for LANG variable
Michael Nottebrock schrieb: Use tr [:lower:] [:upper:] instead. I was wondering about a third-party script which always worked for years with Solaris. I just didn't realized that this issue concerns a difference between SysV and BSD. I tried to set another LANG string and it worked, but now I see that it will work this way with an arbitrary string, because it's invalid. ;-) Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: correct value for LANG variable
Tim Robbins wrote: For better or worse, this is not the correct way to perform case conversion in non-ASCII locales on FreeBSD 5 and later. See the COMPATIBILITY section of the tr(1) manpage for more information. Thanks a lot for this hint. I will pay more attention to this section. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
correct value for LANG variable
I am a bit confused. Neither de_DE.ISO-8859-1 nor de_DE.ISO8859-1 work properly in all cases. > setenv LANG de_DE.ISO8859-1 > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF ÚWXYÝ] > setenv LANG de_DE.ISO-8859-1 > echo abcdef uvwxyz | tr '[a-z]' '[A-Z]' ABCDEF UVWXYZ > perl perl: warning: Setting locale failed. [lot of indignation about locale settings] I am suspicious that de_DE.UTF-8 would work correct with most software. Is it the only solution to don't use localization currently at all or should it be my ambition to fix this? What should be the correct value? I would prefer the notation "ISO-8859-1", but even the almighty perl does not. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [5.3-STABLE] netstat doesn't show tcp sockets
It works fine for me. My world and kernel were compiled with "CPUTYPE?=p3" and "CFLAGS= -O -pipe". FreeBSD 5.3-STABLE #0: Sat Dec 11 18:24:44 CET 2004 Björn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: standard-supfile = stable-supfile with 5.3 ?
Rob wrote: both have *default release=cvs tag=RELENG_5 although the first one claims to download CURRENT. And, eh, why is the filename "standard-supfile" and why not the more obvious "current-supfile" ? It only claims, but it doesn't bring you -CURRENT. That's the reason why it should not be renamed. The standard-supfile contains the standard tag of your release to keep it up to date. Maybe someone will change this sentence to 'This file contains all of the "CVSup collections" that make up the FreeBSD-stable source tree.' soon. Björn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
