From owner-freebsd-arch@freebsd.org Wed Sep 13 10:10:33 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27391E18315 for ; Wed, 13 Sep 2017 10:10:33 +0000 (UTC) (envelope-from repeatable_compression@yahoo.com) Received: from sonic317-36.consmr.mail.ne1.yahoo.com (sonic317-36.consmr.mail.ne1.yahoo.com [66.163.184.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA94A80990 for ; Wed, 13 Sep 2017 10:10:32 +0000 (UTC) (envelope-from repeatable_compression@yahoo.com) X-YMail-OSG: fa7upfoVM1nl8iWzSx0nDQob3jj8WG8SevkqzxdBk6jIvhdNCbhblOqsDKOwJ09 X9uSlEO.TbTJm7wCUrnA4p1uiuMgzVWjC4TEJgi7VbSpM5zGvu3qMH16IiZmN0K5rdyNwnB5wbiT ccbt5NX_SbqobznCgMKa3eJVAEatF6dCVBw.dAw7fzRab99AJ8Fn.Edv7lvxZZrBX8Toxb14FxPt n2J6PhOecWsWr3.8d5ppGDRgUjDcDGHu.6.idI650m2mIesZ74tdeNdSD0pf7uJuzYwZf6wBeR9w aB6jebeG2U4ef5IyIYn2QJRhCcorpWdyjh1TS_loPfp8t9xALStF5nk2E90Kzlp0P.7g8Yq9HwCl 42W9oFG2Fh4csNfq2sc68dOaZV7PdIJjTlXBsJATKJKN7ZvJsJW.XLnpA6rN.J2sPE5vlva_C8yV hiPEFhhOvIEHGDGyvS2Px8AJHfezsaBtyO1gd5alYyoZFhachZ.GYZ1pIkYSNq_c4E6CO6c0wXNi kSemkQu52TUSGWKCbOSdrMZ_jUwa5gbIP Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.ne1.yahoo.com with HTTP; Wed, 13 Sep 2017 10:10:25 +0000 Received: from [127.0.0.1] by smtp219.mail.ne1.yahoo.com with NNFMP; 13 Sep 2017 10:10:23 -0000 X-Yahoo-Newman-Id: 280334.33333.bm@smtp219.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: fa7upfoVM1nl8iWzSx0nDQob3jj8WG8SevkqzxdBk6jIvhd NCbhblOqsDKOwJ09X9uSlEO.TbTJm7wCUrnA4p1uiuMgzVWjC4TEJgi7VbSp M5zGvu3qMH16IiZmN0K5rdyNwnB5wbiTccbt5NX_SbqobznCgMKa3eJVAEat F6dCVBw.dAw7fzRab99AJ8Fn.Edv7lvxZZrBX8Toxb14FxPtn2J6PhOecWsW r3.8d5ppGDRgUjDcDGHu.6.idI650m2mIesZ74tdeNdSD0pf7uJuzYwZf6wB eR9waB6jebeG2U4ef5IyIYn2QJRhCcorpWdyjh1TS_loPfp8t9xALStF5nk2 E90Kzlp0P.7g8Yq9HwCl42W9oFG2Fh4csNfq2sc68dOaZV7PdIJjTlXBsJAT KJKN7ZvJsJW.XLnpA6rN.J2sPE5vlva_C8yVhiPEFhhOvIEHGDGyvS2Px8AJ HfezsaBtyO1gd5alYyoZFhachZ.GYZ1pIkYSNq_c4E6CO6c0wXNikSemkQu5 2TUSGWKCbOSdrMZ_jUwa5gbIP X-Yahoo-SMTP: KDkTLsqswBBCmUTAOzBaZ_hLyVQzFsoqgrhYGNK2rJDiXlA- Subject: Re: Fwd: Re: extending the maximum filename length (pointer to patch)[request for input] To: freebsd-arch@freebsd.org References: <3e85f646-1787-98dd-30e2-1dae78fa9962@freebsd.org> From: Jules Gilbert Message-ID: <71c41b0d-f2a5-b556-cae8-f19e930604d0@yahoo.com> Date: Wed, 13 Sep 2017 06:10:21 -0400 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <3e85f646-1787-98dd-30e2-1dae78fa9962@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2017 10:10:33 -0000 First, I'm just an old guy, I don't maintain any systems (maybe a couple of laptop's,) but no one holds me responsible if their work stations fail. However very suddenly I have a contribution... Do not worry about windoz or compatibility with windoz. I assure you, billygates and his gang never stayed up late worrying about how they could keep the 'BSD boys happy. Truth, the historical record is that Microsoft made changes in their OS in order to break the programs of alternative ISD'ers. One example, Wordstar, Micropro was selling a version for MS-DOS and when MS brought out their own editor/word-processor, suddenly MS-DOS was changed in a way that, too bad, the Micropro product wouldn't work on MS systems. Indeed, Micropro failed and eventually MS faced DOJ sanctions for such behavior. So folks, just design and build the best you can. Recently I got my wife a laptop running W10. She's not a computer person, in fact she hasn't used a computer for about fifteen years. Now she can. So I discovered how it is, running W10. (Bloated, and little more than a vehicle for delivering advertisements to the user.) If you want to support windoz, one last question, do you remember when billy went around the country giving speeches telling people how wrong it was to use open source programs? I don't post here often. So now I'm going to break the rules go off-topic. First, friend up with the guys from OpenBSD. Yes they can be, well not jerks, just not overly social. They have a lot to contribute. Second, this business of giving chips the appearance of multiple cores is nice if that's all you need/want. But I think the world is looking for an OS that goes way beyond, say, a mere hypercube. What is needed are operating system architectures that can make use of many millions of internet connected machines. And the people behind FreeBSD are the right people to put something like this together. On 09/12/2017 08:55 PM, Julian Elischer wrote: > is this a topic for arch? > > > Julian > > > > -------- Forwarded Message -------- > > > On 12/9/17 2:17 pm, Conrad Meyer wrote: >> On Sat, Sep 9, 2017 at 9:09 AM, Julian Elischer >> wrote: >>> maybe we could get it into -current. >>> It'd be silly to have to have people re-inventing hte wheel all the >>> time. >>> How about you put those changes into the reviews.freebsd.org and we >>> can get >>> some general consensus on them. >>> We'll have to do similar for the Asian customers and anyone who uses >>> UTF-8. >>> So it >>> would be silly to have to develop it all again (but subtly different of >>> course). >>> >>> The key issue is how many system calls and other APIs would be broken, >>> and how many would be broken in a non backwards compatible way? >>> >>> We would need it in a stable/10 and 11 branch but if the patch is >>> isolated >>> enough we could carry it forward until we get to 12. >>> >>> One has to allow people to do whatever they are used to with Windows. >>> And in this case the issue is serving files over samba to windows >>> machines. >> Hey Julian, >> >> I've thrown the patch up at https://reviews.freebsd.org/D12330 . I >> haven't actually tested it on FreeBSD, but it does compile. We also >> have some patches against contrib/pjdfstest to fix those tests against >> long file names, but I think we can hold off on those changes until >> we've nailed down what the architectural change will be (if any). > > thanks! > > that looks a lot like a proof -of concept patch we derived a while > back but never really tested. > The issue for us is that using UTF-8 the filenames become too short > for common usage in China and Japan. > Apparently they routinely nae files with the contents of a small novella. > > e.g. > > “这是一个测试多字符文件名长度的文件目的是命名一个文件用中文或者日文或者韩文字符并且要求字符长度超过八十五个字符然后拷贝该文件到我们的共享文件夹看看是否能够拷贝该文件到我.txt” > > (I have no idea what that says but apparently it's a real filename > from a windows machine that blew up when written via samba.) > > Does anyone else have any thoughts about whether FreeBSD 12 might grow > longer path/filename support? > (I'm told Linux uses 1K and 4096 for filenames and path length.) > > Julian > >> >> It's quite possible this accidentally breaks even more APIs than >> expected and we should do some fine tuning to reduce the damage. Our >> $WORK product mostly doesn't care about ABI, so we may not have >> noticed some ABI breakage. >> >> If anyone else is interested, please subscribe or add yourself as a >> reviewer on the phabricator revision. >> >> Best, >> Conrad >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" .