>I don't know why this thread got out of hand. But, as the OP I really
>had just two points. One was that, like myself, there may have been
>many others using tmpfs (due to the upbeat announcement of its
>inclusion).

This is OpenBSD.  Things change.

> And that two, there was no indication of its removal in
>the "following -current" faq, as I (apparently incorrectly) thought it
>might be importaunt if your system doesn't either successfully reboot
>or successfully mount all of your file systems after installing a new
>kernel, especially hampering those upgrading remotely.

Whoa.  You haven't read the first paragraph of current.html, let me
include it here:

    Active OpenBSD development is known as the -current branch. These
    sources are frequently compiled into releases known as
    snapshots. Active development sometimes pushes aggressive changes, and
    complications can arise when building the latest code from a previous
    point in time. Some of the shortcuts for getting over these hurdles
    are explained on this page. In general, it's far better to use the
    OpenBSD upgrade procedure with a newer snapshot, as developers will
    have gone through the trouble for you already.

That purpose of the page is to help people "make build" through the
most disruptive changes.

You seem to believe it is for a different purpose -- to alert about removal
of subsystems which are not critical for building through snapshots.

We already have significant problems curating change reports --
basically folding the CommitLog down to plus.html files, and finally
creating a 60.html for for an upcoming release.  Go look at the state
of the 60.html file.  This is simply not something volunteers can
consistantly do well.

It should tell you that you missed the commits in the log!

There is noone in our group who has a role to provide reports in the
form you are asking for.

Perhaps it should be done.  Perhaps by you?  No?

What should I do, whip developers until they create such a page, which
they themselves don't need?

Expectation management is a bitch.  Did you track down why tmpfs was
disabled?

You can enable it on your own system.  At least for a while.  If
the quality is improved by someone stepping up, it will remain.  If
the quality is not improved in a timely fashion, this disabled code
will rot further, and then need to be removed.

Reply via email to