Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 5:33 PM Johannes Lundberg wrote: > > > On 5/22/19 4:22 PM, Alan Somers wrote: > > On Wed, May 22, 2019 at 5:18 PM Johannes Lundberg > > wrote: > >> > >> On 5/22/19 4:12 PM, Johannes Lundberg wrote: > >>> On 5/22/19 3:02 PM, Conrad Meyer wrote: > On Wed, May 22, 2019

Re: Weirdness when writing to pseudofs file

On 5/22/19 4:22 PM, Alan Somers wrote: > On Wed, May 22, 2019 at 5:18 PM Johannes Lundberg wrote: >> >> On 5/22/19 4:12 PM, Johannes Lundberg wrote: >>> On 5/22/19 3:02 PM, Conrad Meyer wrote: On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg wrote: >> It seems, a single '>'

Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 5:18 PM Johannes Lundberg wrote: > > > On 5/22/19 4:12 PM, Johannes Lundberg wrote: > > On 5/22/19 3:02 PM, Conrad Meyer wrote: > >> On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg > >> wrote: > It seems, a single '>' will cause it to try to create the file (even

Re: Weirdness when writing to pseudofs file

On 5/22/19 4:12 PM, Johannes Lundberg wrote: > On 5/22/19 3:02 PM, Conrad Meyer wrote: >> On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg >> wrote: It seems, a single '>' will cause it to try to create the file (even though it already exists) and that fails (kern_openat). >>>

Re: Weirdness when writing to pseudofs file

On 5/22/19 3:02 PM, Conrad Meyer wrote: > On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg wrote: >>> It seems, a single '>' will cause it to try to create the file (even >>> though it already exists) and that fails (kern_openat). >>> >> I would guess because of >> >>

Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg wrote: > > It seems, a single '>' will cause it to try to create the file (even > > though it already exists) and that fails (kern_openat). > > > I would guess because of > >

Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 12:03:00PM -0600, Alan Somers wrote: > On Wed, May 22, 2019 at 11:59 AM Johannes Lundberg > wrote: > > > > > > On 5/22/19 10:51 AM, Konstantin Belousov wrote: > > > On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: > > >> Hi > > >> > > >> I'm fiddling

Re: Weirdness when writing to pseudofs file

On 5/22/19 1:53 PM, Johannes Lundberg wrote: > On 5/22/19 11:03 AM, Alan Somers wrote: >> On Wed, May 22, 2019 at 11:59 AM Johannes Lundberg >> wrote: >>> On 5/22/19 10:51 AM, Konstantin Belousov wrote: On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: > Hi >

Re: Weirdness when writing to pseudofs file

On 5/22/19 11:03 AM, Alan Somers wrote: > On Wed, May 22, 2019 at 11:59 AM Johannes Lundberg > wrote: >> >> On 5/22/19 10:51 AM, Konstantin Belousov wrote: >>> On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: Hi I'm fiddling with lindebugfs, which is based on

Re: Core: Yes please, Code of Conduct committee: No Thanks.

> http://phk.freebsd.dk/sagas/israel/ Usual anti-semitic rant, nothing special. Arrogant, ignorant, hateful, bad grammar. I've seen too much of this stuff in the UK lately. The only thing missing is "some of my best friends are jews". In some EU countries anti-semitic speech is a crime, e.g. UK

Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 11:59 AM Johannes Lundberg wrote: > > > On 5/22/19 10:51 AM, Konstantin Belousov wrote: > > On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: > >> Hi > >> > >> I'm fiddling with lindebugfs, which is based on pseudofs. When writing > >> to a file, > >> > >>

Re: Weirdness when writing to pseudofs file

On 5/22/19 10:51 AM, Konstantin Belousov wrote: > On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: >> Hi >> >> I'm fiddling with lindebugfs, which is based on pseudofs. When writing >> to a file, >> >> this works: # echo  1 >> /path/to/file >> >> but this does not: # echo 1 >

Re: Weirdness when writing to pseudofs file

On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote: > Hi > > I'm fiddling with lindebugfs, which is based on pseudofs. When writing > to a file, > > this works: # echo  1 >> /path/to/file > > but this does not: # echo 1 > /path/to/file > > "Operation not supported." is returned

Weirdness when writing to pseudofs file

Hi I'm fiddling with lindebugfs, which is based on pseudofs. When writing to a file, this works: # echo  1 >> /path/to/file but this does not: # echo 1 > /path/to/file "Operation not supported." is returned before the pseudofs code is even entered. Is this expected behavior? (if so, why?)

Re: impossible to installkernel without a compiler?

On 22/05/2019 16:37, Warner Losh wrote: > Try setting _NO_INCLUDE_COMPILERMK=t in your environment and then doing the > make > install. This works a bit worse than my original hack: sh: ld: not found make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning: Unable to determine

Re: impossible to installkernel without a compiler?

Try setting _NO_INCLUDE_COMPILERMK=t in your environment and then doing the make install. Warner On Wed, May 22, 2019 at 2:09 AM Andriy Gapon wrote: > > Trying to update a small system with a kernel built for it on a bigger > machine I > get this: > > sh: cc: not found > make:

impossible to installkernel without a compiler?

Trying to update a small system with a kernel built for it on a bigger machine I get this: sh: cc: not found make: "/usr/devel/svn/head/share/mk/bsd.compiler.mk" line 176: Unable to determine compiler type for CC=cc. Consider setting COMPILER_TYPE. Sources and objects are mounted over NFS,