On Tue, 12 Sep 2017 14:46:12 -0230
"Jonathan Anderson" wrote:
> On 12 Sep 2017, at 14:38, Julian Elischer wrote:
>
> > “〓是一个〓〓多字符文件名〓度的文件目的是命名一个文件用中文或者日文或者〓文字符并且要求字符〓度超〓八十五个字符然后拷〓〓文件到我〓的共享文件〓看看是否能〓拷〓〓文件到我.txt”
> > (I have no idea what that says but apparently it's a real filename
> > from a win
On 13/9/17 1:16 am, Jonathan Anderson wrote:
On 12 Sep 2017, at 14:38, Julian Elischer wrote:
“这是一个测试多字符文件名长度的文件目的是命名一个文件用中文或者日文或者韩文字符并且要求字符长度超过八十五个字符然后拷贝该文件到我们的共享文件夹看看是否能够拷贝该文件到我.txt”
(I have no idea what that says but apparently it's a real filename
from a windows machine that blew up when
On Tue, Sep 12, 2017 at 2:23 PM, Rainer Duffner wrote:
> And there’s also this bug:
>
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215067
>
> "g_dev_taste: make_dev_p() failed on importing pool with snapshots with long
> names“
>
>
>
> But maybe that has nothing to do with it.
Hi Rainer,
On Tue, Sep 12, 2017 at 2:11 PM, Ben RUBSON wrote:
> Hi Conrad,
>
> This patch makes me think about another related bug #184340 :
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184340
> It is about PATH_MAX which in some cases can be too small.
>
> Not sure if it's the case / and how to do it
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
>> so
> Am 12.09.2017 um 23:11 schrieb Ben RUBSON :
>
> 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 c
On 12 Sep 2017, at 14:38, Julian Elischer wrote:
“这是一个测试多字符文件名长度的文件目的是命名一个文件用中文或者日文或者韩文字符并且要求字符长度超过八十五个字符然后拷贝该文件到我们的共享文件夹看看是否能够拷贝该文件到我.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.)
Google Translate says, am
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
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
On 9/9/17 1:28 am, Conrad Meyer wrote:
On Fri, Sep 8, 2017 at 10:15 AM, Julian Elischer wrote:
Has anyone using freeBSD ever increased NAME_MAX (filename maximum length)
and have any experience with it?
We ($JOB) would recompile the entire system so intra-system compatibility
would probably be
On Fri, Sep 8, 2017 at 10:21 AM, David Wolfskill wrote:
> On Sat, Sep 09, 2017 at 01:15:31AM +0800, Julian Elischer wrote:
>> Has anyone using freeBSD ever increased NAME_MAX (filename maximum
>> length) and have any experience with it?
>>
>> We ($JOB) would recompile the entire system so intra-sy
On Fri, Sep 8, 2017 at 10:15 AM, Julian Elischer wrote:
> Has anyone using freeBSD ever increased NAME_MAX (filename maximum length)
> and have any experience with it?
>
> We ($JOB) would recompile the entire system so intra-system compatibility
> would probably be ok, and we have our own filesyst
On Sat, Sep 09, 2017 at 01:15:31AM +0800, Julian Elischer wrote:
> Has anyone using freeBSD ever increased NAME_MAX (filename maximum
> length) and have any experience with it?
>
> We ($JOB) would recompile the entire system so intra-system
> compatibility would probably be ok, and we have our o
13 matches
Mail list logo
