Re: struct file at VFS level (round 1.5)

2016-05-02 Thread Emmanuel Dreyfus
Christoph Badura wrote: > Mandatory file locking simply is a SMOP for the kernel to add a flag to a > vnode that indicates whether mandatory locking is in effect and adding the > necessary checks and interaction with file systems to open(2), read(2), > write(2) etc. at the syscall level. VOP_ADV

Re: Scripting DDB in Forth?

2016-05-02 Thread Valery Ushakov
On Mon, May 02, 2016 at 15:43:35 +, Taylor R Campbell wrote: >Date: Mon, 2 May 2016 04:59:32 +0300 >From: Valery Ushakov > >I've accidentally wrote a Forth for sh3 (long story). I thought it >might be interesting to put it into the kernel so that it can be >hooked into D

Re: Scripting DDB in Forth?

2016-05-02 Thread Michael
Hello, On Mon, 2 May 2016 15:00:15 +0300 Valery Ushakov wrote: > > > I've accidentally wrote a Forth for sh3 (long story). > > > > What kind of accident makes you write something relatively non-trivial > > without meaning to? > > I guess the perceived "otherness" of Forth prevents people reali

Re: Scripting DDB in Forth?

2016-05-02 Thread Paul_Koning
> On May 2, 2016, at 11:45 AM, Eduardo Horvath wrote: > > On Mon, 2 May 2016, Valery Ushakov wrote: > >> ... >> Or we can port real OF perhaps? OpenBIOS is GPLv2, but since it will >> not be part of the kernel, that's not an issue. Also, Sun did release >> OpenBOOT under BSD'ish license, if y

Re: Scripting DDB in Forth?

2016-05-02 Thread Martin Husemann
On Mon, May 02, 2016 at 04:06:35PM +, Taylor R Campbell wrote: > fdt / flattened device tree, as used on tegra and perhaps other ARM > and MIPS systems? Where would Forth come into play here? Martin

Re: Scripting DDB in Forth?

2016-05-02 Thread Taylor R Campbell
Date: Mon, 2 May 2016 15:00:15 +0300 From: Valery Ushakov On Mon, May 02, 2016 at 00:59:06 -0400, Michael wrote: > I'm afraid my first thought was OF_interpret() on machines that have > OF-like device trees but no OF. I'm not sure I understand. OF_interpret() by itself is not

Re: Scripting DDB in Forth?

2016-05-02 Thread Eduardo Horvath
On Mon, 2 May 2016, Valery Ushakov wrote: > On Mon, May 02, 2016 at 00:59:06 -0400, Michael wrote: > > > On Mon, 2 May 2016 04:59:32 +0300 > > Valery Ushakov wrote: > > > I thought it might be interesting to put it into the kernel so that > > > it can be hooked into DDB. > > > > I'm afraid my

Re: Scripting DDB in Forth?

2016-05-02 Thread Taylor R Campbell
Date: Mon, 2 May 2016 04:59:32 +0300 From: Valery Ushakov I've accidentally wrote a Forth for sh3 (long story). I thought it might be interesting to put it into the kernel so that it can be hooked into DDB. Neat! If there's interest I can push what I have to bitbucket (I use

Re: struct file at VFS level (round 1.5)

2016-05-02 Thread Christoph Badura
On Mon, May 02, 2016 at 07:15:12AM +, Emmanuel Dreyfus wrote: > NetBSD filesystems implement advisory locks, where the only place the > filesystem actually check locks as VOP_ADVLOCK. Any other operation > performed on a file region locked by someone else succeeds: the locks > are only advisor

Re: Scripting DDB in Forth?

2016-05-02 Thread Valery Ushakov
On Mon, May 02, 2016 at 00:59:06 -0400, Michael wrote: > On Mon, 2 May 2016 04:59:32 +0300 > Valery Ushakov wrote: > > > I've accidentally wrote a Forth for sh3 (long story). > > What kind of accident makes you write something relatively non-trivial > without meaning to? I guess the perceived

struct file at VFS level (round 1.5)

2016-05-02 Thread Emmanuel Dreyfus
Hello I try to summarize the thing so far. NetBSD filesystems implement advisory locks, where the only place the filesystem actually check locks as VOP_ADVLOCK. Any other operation performed on a file region locked by someone else succeeds: the locks are only advisory, and it is the application