Date: Sat, 25 Mar 2000 15:52:09 -0500 From: Sam Samalin <ssamalin@ionet.net> To: hackers@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #792 Message-ID: <38DD26F8.C05B017E@ionet.net> References: <bulk.65125.20000325124337@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
unsubscribe freebsd-hackers freebsd-hackers-digest wrote: > freebsd-hackers-digest Saturday, March 25 2000 Volume 04 : Number 792 > > In this issue: > Re: shell issue > Re: top sorting error > zsh compdef collection for FreeBSD > Missing keyboard symbols > Re: top sorting error > 3.x -> 4.x kernel config converter > Re: zsh compdef collection for FreeBSD > Re: Missing keyboard symbols > Re: Missing keyboard symbols > Re: zsh compdef collection for FreeBSD > Re: Missing keyboard symbols > Re: WaveLAN PCI Adapter > Re: Possible bug in 3.4 > Re: 3.x -> 4.x kernel config converter > Dreamweaver 2 > Comments above kmem_malloc() (vm/vm_kern.c) > Re: Dreamweaver 2 > Re: Unicode on FreeBSD > Re: Unicode on FreeBSD > Request for review (HW checksum patches) > Shim Code #error needed > > ---------------------------------------------------------------------- > > Date: Fri, 24 Mar 2000 12:19:32 -0800 > From: Alfred Perlstein <bright@wintelcom.net> > Subject: Re: shell issue > > * Dungeonkeeper <zethix@sofiaonline.com> [000324 10:03] wrote: > > > > > > Hi there, > > > > First of all: I want to apologise for my poor english. > > > > Today me and a few friends of mine discussed the shells' (well, shell is > > actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion > > routines, mainly because of a problem discovered by one of my friends. I'm not > > sure if this is something new... So, let me explain what he found. It seems > > that the shell wants to allocate enough memory to hold the entire command line > > when expanding all of the arguments and we can force it to allocate hudge > > ammount of memory with a tricky command like this: > > > > carnivoro# /bin/csh -c `cat /dev/urandom` > > > > (I use tcsh here (the carnivoro# prompt), but the same thing happens when > > testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough > > memory to hold what it > > reads from /dev/urandom, because it must be passed as a command line argument > > to /bin/csh ( actually, any command will be ok ). So, the shell eats more and > > more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to > > take some action (like killing some processes... started by other users? > > system services? or... in my case... crash :). My friend said that he sent a > > mail to bugtraq describing this problem. Those who are interested can read it. > > > > I believe that the shells have a maximum command lenght, so... I'm trying now > > to make the shell use the same command lenght when expanding such commands. I > > think this is the best way to avoid this problem. Any ideas? > > Yes, that's a good idea, I'd file a problem report with send-pr and > it will probably be addressed. > > thanks, > - -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 20:04:21 +0000 > From: David Malone <dwmalone@maths.tcd.ie> > Subject: Re: top sorting error > > On Fri, Mar 24, 2000 at 01:00:54PM -0500, Luke Hollins wrote: > > > I don't know if this is specific to FreeBSD but I just noticed it when i > > picked o time in top: > > > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > > 79364 root 2 0 2696K 1636K select 8:23 0.00% 0.00% apache > > 235 mysql 2 0 13372K 6384K poll 361:14 0.15% 0.15% mysqld > > It seems to be an overflow problem - top was reilying on things > fitting into a int, which were 64 bits long. It looks like someone > ran into the problem before for the %cpu field, and fixed it in a > different way. This patch below should fix it regardless of the > type of the variable. > > It's for a file in /usr/src/usr.bin/top. > > David. > > - --- machine.c.orig Fri Mar 24 19:57:36 2000 > +++ machine.c Fri Mar 24 19:58:17 2000 > @@ -737,26 +737,26 @@ > 4 /* stop */ > }; > > +#define CMP(a,b) ( (a) == (b) ? 0 : (a) < (b) ? -1 : 1 ) > > #define ORDERKEY_PCTCPU \ > - - if (lresult = (long) PP(p2, p_pctcpu) - (long) PP(p1, p_pctcpu), \ > - - (result = lresult > 0 ? 1 : lresult < 0 ? -1 : 0) == 0) > + if ((result = CMP(PP(p2, p_pctcpu),PP(p1, p_pctcpu))) == 0) > > #define ORDERKEY_CPTICKS \ > - - if ((result = PP(p2, p_runtime) - PP(p1, p_runtime)) == 0) > + if ((result = CMP(PP(p2, p_runtime),PP(p1, p_runtime))) == 0) > > #define ORDERKEY_STATE \ > - - if ((result = sorted_state[(unsigned char) PP(p2, p_stat)] - \ > - - sorted_state[(unsigned char) PP(p1, p_stat)]) == 0) > + if ((result = CMP(sorted_state[(unsigned char) PP(p2, p_stat)], \ > + sorted_state[(unsigned char) PP(p1, p_stat)])) == 0) > > #define ORDERKEY_PRIO \ > - - if ((result = PP(p2, p_priority) - PP(p1, p_priority)) == 0) > + if ((result = CMP(PP(p2, p_priority),PP(p1, p_priority))) == 0) > > #define ORDERKEY_RSSIZE \ > - - if ((result = VP(p2, vm_rssize) - VP(p1, vm_rssize)) == 0) > + if ((result = CMP(VP(p2, vm_rssize),VP(p1, vm_rssize))) == 0) > > #define ORDERKEY_MEM \ > - - if ( (result = PROCSIZE(p2) - PROCSIZE(p1)) == 0 ) > + if ((result = CMP(PROCSIZE(p2),PROCSIZE(p1))) == 0 ) > > /* compare_cpu - the comparison function for sorting by cpu percentage */ > > @@ -774,7 +774,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -816,7 +815,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -845,7 +843,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -874,7 +871,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > @@ -903,7 +899,6 @@ > register struct kinfo_proc *p1; > register struct kinfo_proc *p2; > register int result; > - - register pctcpu lresult; > > /* remove one level of indirection */ > p1 = *(struct kinfo_proc **) pp1; > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 07:58:50 +0900 > From: "Akinori -Aki- MUSHA" <knu@idaemons.org> > Subject: zsh compdef collection for FreeBSD > > Hi, FreeBSD hackers! > > I suppose FreeBSD users who use zsh (the Z shell) must have been > customizing it so well and got some neat definitions for FreeBSD (or > *BSD rather) environment. > > Now I have a suggestion. > > Why not we collect those useful compdef's to send to the zsh > development team? You know, the latest zsh 3.1.6-dev-19 includes > Debian specific functions in `Completion/Debian', then why not we have > ours? I'm afraid that zsh will only have Linux/Solaris oriented > configurations if we don't feed anything to the zsh team. > > It might take so long, but we always have a port. :) > > Anyway, I open mine at the following site. > > http://people.freebsd.org/~knu/etc/zsh/functions/ > > The stock contents: > - cvsup > - kldload / kldunload > - pkg_add / pkg_delete / pkg_info > - mount / umount (very poor for the present) > > Then, who's next? :) Any input is welcome! > > - -- > / > /__ __ > / ) ) ) ) / > Akinori -Aki- MUSHA aka / (_ / ( (__( <knu@idaemons.org> > > "If you choose not to decide you still have made a choice." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:36:09 NZST > From: "Crash Override" <mofo_junkhead@hotmail.com> > Subject: Missing keyboard symbols > > Hello, > I'm an NT admin that has been using FreeBSD at work for 5 years now. > But since we changed many of the servers in our company to FreeBSD I have > had a rather serious error while doing administrative work. The consolemode > programs (Why don't they all just have a GUI? argh :-) ask me to press some > Annykey to continue installation. > But I can't find this function key anywhere on my keyboard! Most of these > now-BSD boxes still have Windows keyboards, so I assume that this is the > problem..., but it seems braindamaged to me that FreeBSD wouldn't function > just because of such a trivial thing. > So far (since I don't want to risk messing our business servers up!) I have > been forced to press Reset, and some of the users have been complaining > recently, so I really need to sort this out. > Are there ms-keyboard patches that provide Annykey compatibility, > and if not, will FreeBSD support this properly in the future? > > Sincerely, > Arne R. Muhsson. > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 23:56:32 +0000 > From: David Malone <dwmalone@maths.tcd.ie> > Subject: Re: top sorting error > > On Fri, Mar 24, 2000 at 08:04:21PM +0000, David Malone wrote: > > > It seems to be an overflow problem - top was reilying on things > > fitting into a int, which were 64 bits long. It looks like someone > > ran into the problem before for the %cpu field, and fixed it in a > > different way. This patch below should fix it regardless of the > > type of the variable. > > I notice this was fixed in version 1.28 by bde, though he only changed > the check on the 64 bit field. The commit message says: > > Fixed sorting on time. On i386's, time differences of more than 2147 > seconds caused overflow. Use a type-safe but slightly slower comparison. > Comparisons for other fields are still fragile. > > Maybe this could be MFC'ed into RELENG_3? My patch would make all the > comparisons in the robust, but slightly slower way. > > David. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 02:49:00 +0200 > From: Neil Blakey-Milner <nbm@mithrandr.moria.org> > Subject: 3.x -> 4.x kernel config converter > > Hi, > > I wrote a quick hackish perl script to hopefully automatically > convert 3.4 kernel configurations to 4.0 configurations. I can > pipe RELENG_3 LINT through it and get a 4.0 config'able configuration, > but I'm not sure if it's likely to produce booting kernels. > > Anyway, I thought some people might be interested in this - if it > works well enough, it might even be useful to put in the tools > directory, or integrate it into any 'update' target that may appear. > > It's at http://people.FreeBSD.org/~nbm/three-to-four-conf.pl > > Neil > - -- > Neil Blakey-Milner > nbm@rucus.ru.ac.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 16:52:35 -0800 (PST) > From: Doug Barton <Doug@gorean.org> > Subject: Re: zsh compdef collection for FreeBSD > > On Sat, 25 Mar 2000, Akinori -Aki- MUSHA wrote: > > > Hi, FreeBSD hackers! > > > > I suppose FreeBSD users who use zsh (the Z shell) must have been > > customizing it so well and got some neat definitions for FreeBSD (or > > *BSD rather) environment. > > > > Now I have a suggestion. > > > > Why not we collect those useful compdef's to send to the zsh > > development team? > > I use the following in my .bashrc. I'm operating on the assumption > that zsh has aliases of some sort, otherwise feel free to ignore this > entire post. :) > > (Beware linewrap) > > case $MACHTYPE in > *[Ff]ree[Bb][Ss][Dd]*) > alias mergemaster='mergemaster -w ${COLUMNS}' > alias kern='make depend && make && make install' > alias cleanobj='rm -f -r /usr/obj/* || chflags -R noschg /usr/obj/* && > rm -r /usr/obj/*' > alias myps='/bin/ps -axo > user,pid,ppid,%cpu,%mem,vsz,rss,state,start,time,command' > ;; > esac > > Enjoy, > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 16:57:15 -0800 (PST) > From: Doug Barton <Doug@gorean.org> > Subject: Re: Missing keyboard symbols > > On Sat, 25 Mar 2000, Crash Override wrote: > > > Hello, > > I'm an NT admin that has been using FreeBSD at work for 5 years now. > > But since we changed many of the servers in our company to FreeBSD I have > > had a rather serious error while doing administrative work. The consolemode > > programs (Why don't they all just have a GUI? argh :-) ask me to press some > > Annykey to continue installation. > > Errr... If this is a joke, you should have sent it to -chat. If > this is a serious question you should send them to > freebsd-questions@freebsd.org in the future. > > If you are seriously asking about the "Any" key, think about it for a > second. The message doesn't say, "Push THE Any key ..." It says push any > key. If that's too complicated, just press the space bar. > > Good luck, > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 17:03:44 -0800 (PST) > From: Matthew Dillon <dillon@apollo.backplane.com> > Subject: Re: Missing keyboard symbols > > : Errr... If this is a joke, you should have sent it to -chat. If > :this is a serious question you should send them to > :freebsd-questions@freebsd.org in the future. > : > : If you are seriously asking about the "Any" key, think about it for a > :second. The message doesn't say, "Push THE Any key ..." It says push any > :key. If that's too complicated, just press the space bar. > : > :Good luck, > : > :Doug > > The space bar? The SPACE BAR? Oh my god, I've been hitting the > wrong key for *YEARS*!!! > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 03:03:42 +0200 > From: Neil Blakey-Milner <nbm@mithrandr.moria.org> > Subject: Re: zsh compdef collection for FreeBSD > > On Fri 2000-03-24 (16:52), Doug Barton wrote: > > I use the following in my .bashrc. I'm operating on the assumption > > that zsh has aliases of some sort, otherwise feel free to ignore this > > entire post. :) > > My ~/.tcsh/os-FreeBSD (which get auto-called by my .tcshrc) has: > > /---- > setenv PR_FORM ~/.send-pr > # bsd make allows knowing the targets like so: > uncomplete make > complete make 'p@*@`if -e Makefile make -dg1 -q | grep "^[^.#][-_a-z. \t]*:" | awk '"'"'{print $1}'"'"'`@' > > # if I have a local copy of the cvs tree, add aliases to easy moving > # into it > alias ncvs 'if ( "\!*" == "" ) then \ > pushd $NCVS/`pwd | cut -f 3- -d/`; \ > else \ > pushd $NCVS/\!*; \ > endif' > complete ncvs "p%*%D:$NCVS/%" > alias uncvs 'popd' > > complete pkg_delete 'p%*%D:/var/db/pkg/% %' > complete pkg_info 'p%*%D:/var/db/pkg/% %' > > # indt alias compares given code to code given by indent(1) > alias indt 'cat \!\!:1 | indent -st | diff \!\!:1 - | $PAGER' > > # show the rlog of a file through favourite pager > alias rl 'rlog \!:1 | $PAGER' > /--- > > That basically sets up 'make' completion: > > (nbm@mithrandr) /usr/src> make > afterdistribute everything move-aout-libs > all hierarchy obj > aout-to-elf includes objlink > aout-to-elf-build install regress > aout-to-elf-install installkernel rerelease > ... > > It also completes pkg_delete and pkg_info: > > (nbm@mithrandr) /usr/home/nbm> pkg_delete c > cdd-1.0/ checkpassword-0.81/ cvsup-mirror-1.0/ > cdrecord-1.8a33/ cvsup-bin-16.1/ cvsupd-bin-16.1/ > > ncvs pops me into the cvs tree of the directory I'm in: > > (nbm@mithrandr) /usr/src/contrib/cvs> ncvs > (nbm@mithrandr) /home/ncvs/src/contrib/cvs> > > uncvs pushes me back. ncvs could be made much more intelligent, of > course. > > Anyway, enough of that. Time for me to finally learn zsh. > > Neil > - -- > Neil Blakey-Milner > nbm@rucus.ru.ac.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 17:13:40 -0800 (PST) > From: Doug Barton <Doug@gorean.org> > Subject: Re: Missing keyboard symbols > > On Fri, 24 Mar 2000, Matthew Dillon wrote: > > > : Errr... If this is a joke, you should have sent it to -chat. If > > :this is a serious question you should send them to > > :freebsd-questions@freebsd.org in the future. > > : > > : If you are seriously asking about the "Any" key, think about it for a > > :second. The message doesn't say, "Push THE Any key ..." It says push any > > :key. If that's too complicated, just press the space bar. > > : > > :Good luck, > > : > > :Doug > > > > The space bar? The SPACE BAR? Oh my god, I've been hitting the > > wrong key for *YEARS*!!! > > Heh... You know, I started to type out something to the effect of, > "... space bar. FreeBSD has been mapping the Space Bar to the Any key > combination since about 1992 to get around the restrictions of modern PC > keyboards." But I thought there was an outside chance that this was a > serious question, and I didn't want to run the risk that the poor doofus > would repeat that statement in front of someone with a clue... > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 18:51:25 -0700 > From: Warner Losh <imp@village.org> > Subject: Re: WaveLAN PCI Adapter > > In message <20000324142448.A22279@WN.NET.UA> romik@WN.com.UA writes: > : We bought WaveLAN PCI Adapter PCMCIA Controller (SCM Microsystems GMBH PCIC2CPR10 based on PCI1225PDV chip) and have trouble with installing it in FreeBSD 3.4 Does > : FreeBSD support this device if yes were we can read about this problem ? > > Not really in 3.4. I have some patches knocking around my tree that I > need to clean up. I got them from isawaki-san and other Japanese > laptop users and haven't had the chance to look into them in detail. > You may have to use 4.0 instead. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 20:40:01 -0800 (PST) > From: Jamie Bowden <ragnar@sysabend.org> > Subject: Re: Possible bug in 3.4 > > On Fri, 24 Mar 2000, Wes Peters wrote: > > :The 1510 is a notoriously weak little piece of compu-trash. Put the > :internal tape drive on your 2940 and be happy. > > While I can appreciate your disdain for the card in question, I'd still > like to know if anyone has any ideas on why FreeBSD won't boot when I plug > the tape drive in. It's an Archive Python 25588-xxx according to NT and > 98, in case anyone cares. > > After I upgrade in the near future, I should have enough PCI slots to dump > the 1510 and plug in the Symbios Logic card I have. The goal is to get > the hard drives on one bus, and the misc. peripherals on another. > > Jamie Bowden > > - -- > > "Of course, that's sort of like asking how other than Marketing, > Microsoft is different from any other software company..." > Kenneth G. Cavness > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Fri, 24 Mar 2000 21:29:31 -0800 > From: Doug Barton <Doug@gorean.org> > Subject: Re: 3.x -> 4.x kernel config converter > > Neil Blakey-Milner wrote: > > > > Hi, > > > > I wrote a quick hackish perl script to hopefully automatically > > convert 3.4 kernel configurations to 4.0 configurations. > > I don't want to cast cold water on your plans here, but we try to > encourage users to start with a GENERIC kernel, and work their way from > there. The problem with converting is that there will likely be > something missing from their old kernel file that should be in the new > one. > > Doug > - -- > "So, the cows were part of a dream that dreamed itself into > existence? Is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 22:13:31 +1100 > From: "VR Dredge" <vrdredge@stringline.com.au> > Subject: Dreamweaver 2 > > Hi, my name is Robert. > I came across your address while trying to find a crack for Dreamweaver > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > asking if you have or know where I can it. Also are there any programs for > generating cracks, passwords and so on > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:46:23 -0500 (EST) > From: Bosko Milekic <bmilekic@dsuper.net> > Subject: Comments above kmem_malloc() (vm/vm_kern.c) > > Is the following comment above kmem_malloc()'s definition in: > /sys/vm/vm_kern.c > ... still valid? (I hope and suspect not): > > " * Note that this still only works in a uni-processor environment and > * when called at splhigh(). " > > The only places, as far as I've seen, that call kmem_malloc are the > kernel's malloc() and the mbuf allocation routines. Niether of these > seems to do it at splhigh(), either. > > - --Bosko Milekic <bmilekic@dsuper.net> > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 11:34:31 -0600 > From: Chris Costello <chris@calldei.com> > Subject: Re: Dreamweaver 2 > > On Saturday, March 25, 2000, VR Dredge wrote: > > Hi, my name is Robert. > > I came across your address while trying to find a crack for Dreamweaver > > 2.I've got to admit I'm pretty green at this sort of thing, so I guess I'm > > asking if you have or know where I can it. Also are there any programs for > > generating cracks, passwords and so on > > Where did you get this address as a place to get cracks for > Windows software? This mailing list is for general FreeBSD > technical discussion. > > - -- > |Chris Costello <chris@calldei.com> > |All the simple programs have been written, and all the good names taken. > `------------------------------------------------------------------------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: 25 Mar 2000 18:34:19 +0100 > From: naddy@mips.rhein-neckar.de (Christian Weisgerber) > Subject: Re: Unicode on FreeBSD > > MikeM <mike_bsdlists@yahoo.com> wrote: > > > Has anyone thought of Unicode support on FreeBSD? > > It has crossed my mind... > > > I think that it is inevitable that eventually FreeBSD > > will *need* to support unicode if it wants to continue > > as a viable operating system in the future. > > Probably. The demand for Unicode support is currently rather limited, > but I expect it to pick up somewhat once it is pervasive under > Linux and applications programmers come to expect its availability. > > > This means that it probably will need to be modified from the > > ground up. > > Not at all. > > > Is there any way of implementing partial support, > > working in stages, untill it is fully supported? > > Just that. > > I suggest you read these documents: > > "UTF-8 and Unicode FAQ" by Markus Kuhn > http://www.cl.cam.ac.uk/~mgk25/unicode.html > > "The Unicode HOWTO" by Bruno Haible > ftp://ftp.ilog.fr/pub/Users/haible/utf8/Unicode-HOWTO.html > > "Unicode Fonts and Tools for X11" by Markus Kuhn > http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html > > These are written for Linux but they are largely applicable to BSD > in general and FreeBSD in particular, too. > > The practical relevance of Unicode has taken a huge leap forward > when Thomas Dickey made xterm became capable of displaying UTF-8 > encoded Unicode character streams and Markus Kuhn coordinated the > creation of some suitable fonts. This work has been merged into > XFree86 4.0. For those of us still relying on an older release or > actually requiring an even newer version of xterm, I have made > ports available: > > http://home.pages.de/~naddy/unix/freebsd/xterm.shar > http://home.pages.de/~naddy/unix/freebsd/ucs-fixed.shar > > (Earlier versions of) these have been submitted in PRs #15545 and > #15840, but for some reason they have never been committed. > > - -- > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 10:50:36 -0800 > From: Julian Elischer <julian@elischer.org> > Subject: Re: Unicode on FreeBSD > > Christian Weisgerber wrote: > > > > > > (Earlier versions of) these have been submitted in PRs #15545 and > > #15840, but for some reason they have never been committed. > > > > don't give up. > It's not immediatly who is responsible for this, but > it's something that is generally considered > an important future subject for freebsd development. > But you just need to figure out who is the right 'sponsor'. > > > -- > > Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de > > - -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > - ---> X_.---._/ presently in: Perth > v > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 13:35:53 -0600 > From: Jonathan Lemon <jlemon@flugsvamp.com> > Subject: Request for review (HW checksum patches) > > I have a set of patches which allows offloading checksums to > NICs which support it (right now, only the Alteon based cards). > The patch is at <http://www.freebsd.org/~jlemon/csum.patch>. > > Note that the alpha bits are currently untested. > - -- > Jonathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > Date: Sat, 25 Mar 2000 13:43:12 -0700 > From: Warner Losh <imp@village.org> > Subject: Shim Code #error needed > > I've been burned about 6 times now by the shim device support becoming > optional. Oh well, that's current. > > However, I was thinking that it would be nice if there was something > simple to grep for to see what drivers still needed to be converted. > What would people think of my adding the following to the shim using > devices: > > cvs diff: Diffing . > Index: amd.c > =================================================================== > RCS file: /home/imp/FreeBSD/CVS/src/sys/pci/amd.c,v > retrieving revision 1.3 > diff -u -r1.3 amd.c > - --- amd.c 2000/01/14 03:39:30 1.3 > +++ amd.c 2000/03/25 18:07:31 > @@ -50,6 +50,10 @@ > /* #define AMD_DEBUG0 */ > /* #define AMD_DEBUG_SCSI_PHASE */ > > +#ifndef COMPAT_OLDPCI > +#error "The amd device requires the old pci compatibility shims" > +#endif > + > #include <sys/param.h> > > #include <sys/systm.h> > > At least this way you get a decent error message when it fails to > work. > > Comments? > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > ------------------------------ > > End of freebsd-hackers-digest V4 #792 > ************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38DD26F8.C05B017E>