The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)
Date: Tue, 5 Nov 2024 10:52:04 -0800	[thread overview]
Message-ID: <CAP6exYJpP1L_qCFDyAageSdQ+6vb9=MtbsTBkSwfGK=4tSHC_w@mail.gmail.com> (raw)
In-Reply-To: <20241105175531.D180918C084@mercury.lcs.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

I keep wondering if this assertion of code difference or lack thereof can
be tested. Are not all these sources available? Which bits are missing?

On Tue, Nov 5, 2024 at 9:55 AM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > From: Warner Losh
>
>     >> On Mon, Nov 4, 2024 at 8:14PM Larry McVoy wrote:
>
>     >> The bmap implementations I saw were bit for bit identical, same
> code,
>     >> same variables, same style, same indentation. I'm 100% sure they
> were
>     >> not independent.
>
>     > They are different in 4.3BSD. They are different in 4.2BSD (but less
>     > different). The underlying filesystems are different on disk, so they
>     > routines have to be different.
>
> That last sentence points out something important that people need to
> remember
> in this discussion: in between 4.1 and 4.2 (technically, in 4.1B), BSD
> switched to the BSD Fast File System, so I very much doubt that the
> low-level
> (i.e. logical file block to disk block) file system code in anything after
> 4.1A looks much like the AT+T low-level file system code. (I have no idea
> how
> the BSD code compares to the Linux file system code, but that's between the
> Linux people, and Berkeley.)
>
>         Noel
>

[-- Attachment #2: Type: text/html, Size: 1671 bytes --]

  reply	other threads:[~2024-11-05 18:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 17:55 Noel Chiappa
2024-11-05 18:52 ` ron minnich [this message]
2024-11-05 19:01   ` Warner Losh
     [not found]     ` <CAEoi9W66zUf8RvzEYQG7qNXN-BX6gyDejXCrHw3rk46UM_-XPg@mail.gmail.com>
2024-11-08 20:27       ` Warner Losh
     [not found]         ` <61F8BCE5-44C5-49D2-BEFE-B8717E3DDEA8@kdbarto.org>
     [not found]           ` <CANCZdfrJExbrJqp3MgE0Tp9-a=PYTeFpkULk8NnPfBTeoyLW-g@mail.gmail.com>
2024-11-08 23:18             ` [TUHS] Fwd: " Warner Losh
2024-11-09  0:40               ` [TUHS] " rob
2024-11-05 18:58 ` Warner Losh
2024-11-05 20:25   ` [TUHS] Copyrights and copying.. [was SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)] Christian Hopps
2024-11-05 20:35     ` [TUHS] " Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2024-11-04  1:17 [TUHS] RIP Darl McBride former CEO of SCO Will Senn
2024-11-04  2:31 ` [TUHS] " Greg 'groggy' Lehey
2024-11-04  3:34   ` Wesley Parish
2024-11-04 17:35     ` Marc Rochkind
2024-11-04 22:50       ` [TUHS] SCO's "evidence" (was: RIP Darl McBride former CEO of SCO) Greg 'groggy' Lehey
2024-11-05  0:05         ` [TUHS] " Marc Rochkind
2024-11-05  0:39           ` Warner Losh
2024-11-05  1:09             ` Larry McVoy
2024-11-05  1:32               ` ron minnich
2024-11-05  1:39                 ` Warner Losh
2024-11-05  3:14                 ` Larry McVoy
2024-11-05  5:00                   ` Warner Losh
2024-11-05  1:35               ` Warner Losh
2024-11-05  1:54                 ` Larry McVoy
2024-11-05  2:13                   ` Warner Losh
2024-11-05  3:14                     ` Marc Rochkind
2024-11-07 20:41                       ` ron minnich
2024-11-07 20:59                         ` Marc Rochkind
2024-11-08  0:03                           ` Theodore Ts'o
2024-11-08  0:35                             ` Warner Losh
2024-11-09 18:29                           ` G. Branden Robinson
2024-11-09 20:30                             ` Theodore Ts'o
2024-11-09 22:23                               ` G. Branden Robinson
2024-11-10  4:27                                 ` Theodore Ts'o
2024-11-12  1:55                       ` Kevin Bowling
2024-11-12  2:34                         ` Kevin Bowling
2024-11-12 18:12                           ` Marc Rochkind

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP6exYJpP1L_qCFDyAageSdQ+6vb9=MtbsTBkSwfGK=4tSHC_w@mail.gmail.com' \
    --to=rminnich@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).