From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] notes on fossil, ANTS, and 9front/Bell labs controversies
Date: Sat, 11 Jan 2020 15:56:55 +0000 [thread overview]
Message-ID: <DD90EDD5-E1B0-480C-AB8E-E5150461032C@quintile.net> (raw)
In-Reply-To: <CA+cCjXo4BcTUsR2BXRW_N_=f77sVe-R+GBb1uZKE=N5zPrpMxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
using tlssrv is an option, as is import, but what was saying it fossil’s native 9p server does not support tls, which it doesn't - i dont believe anyone has added it.
the issue is 9boot would need tls to be able download the kernel from a file server and it doesn’t have it. this is the labs boot procedure of course.
9front booting uses a full kernel to bootstrap (correct me if i am wrong) so tls is not a problem there.
anyway, fossil does not have tls and i would like to have. such a change would mean changes to the labs distro boot proceedure
-Steve
> On 11 Jan 2020, at 10:42 am, Rodrigo G. López <rodrigosloop@gmail.com> wrote:
>
>
> i'm sorry, what? lack of TLS?
>
> go read 9front's tlssrv(8). it's been there for a while already.
>
>
> -rodri
>
>> On Sat, Jan 11, 2020, 11:32 AM Steve Simon <steve@quintile.net> wrote:
>>
>> fyi i have been running a fossil/venti pair since 2004 and it has been solid.
>>
>> what is too big - honest question.
>>
>> i thought the biggest issues are:
>>
>> performance - the elegance and generality sacrifice some performance, though this is not a problem for me.
>>
>> lack of a tls fs interface - there is (imho) no excuse for a lack of tls these days.
>>
>> no way for a user in (say) the ventidump group to request an immediate dump - handy for checkpointing a code release, though justing copying the release to a new dir is ok.
>>
>> no way to push a vac score into the /archive hierarchy - nice for migrating in other backups.
>>
>> all these are fixable and on my todo list but none have happened.
>>
>> > On 10 Jan 2020, at 9:37 pm, hiro <23hiro@gmail.com> wrote:
>> >
>> >
>> >>
>> >> The major fly in the ointment is the outdated sha1 hash function used by venti
>> >
>> > major? fly? there's no problem with how sha1 is used by venti right now.
>> >
>> > a more substantial complaint would be that the venti/fossil system is
>> > way too big.
>>
>> ------------------------------------------
>> 9fans: 9fans
>> Permalink: https://9fans.topicbox.com/groups/9fans/Ta5071137bc09d294-M7a56202f84a795cc3e7d9a1e
>> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
> 9fans / 9fans / see discussions + participants + delivery options Permalink
[-- Attachment #2: Type: text/html, Size: 4071 bytes --]
next prev parent reply other threads:[~2020-01-11 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:29 mycroftiv
2020-01-10 21:36 ` [9fans] " hiro
2020-01-11 10:31 ` Steve Simon
2020-01-11 10:41 ` Rodrigo G. López
2020-01-11 15:56 ` Steve Simon [this message]
2020-01-11 19:32 ` Rodrigo G. López
2020-01-13 9:33 ` Richard Miller
2020-01-11 4:36 ` Lucio De Re
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=DD90EDD5-E1B0-480C-AB8E-E5150461032C@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).