unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Leo Famulari <leo@famulari.name>
Cc: 46482@debbugs.gnu.org
Subject: bug#46482: [core-updates] u-boot source cannot be downloaded
Date: Sun, 14 Feb 2021 04:57:50 +0100	[thread overview]
Message-ID: <20210214035750.GA4673@LionPure> (raw)
In-Reply-To: <YCgkjWU++McEBcsK@jasmine.lan>

Hi Leo et al,

On +2021-02-13 14:12:13 -0500, Leo Famulari wrote:
> On Sat, Feb 13, 2021 at 07:34:09PM +0100, Bengt Richter wrote:
> > I would prefer something that fits in with mes-philosopy.
> > ftp seems old and simple, so I would vote for push-back
> > to fix the ftp client involved.
> 
> FTP is more complicated than HTTP in that it requires the use of
> multiple connections. Additionally, it's often blocked on corporate
> networks, whereas HTTP/S is never going to be blocked (HTTPS anyways).
> 
> Based on experience in Guix, we have never had bug reports from users
> who could not access sources over HTTP/S, but there have been several
> reports of problems using FTP. The HTTP/S ports 80 and 443 are basically
> the only ports you can depend on being open on a network that is
> connected to the internet.
> 
> The creator of curl compares them here:
> 
> https://daniel.haxx.se/docs/ftp-vs-http.html

Thanks, that was interesting.

He says (re download speed)
    "Ultimately the net outcome of course differs depending on
     specific details, but I would say that for single-shot static files,
     you won't be able to measure a difference."

So in that case, what's minimal, and how vulnerable is it?

Is there a minimal quic without google upstream?

or X.25 -- dating myself ;-P

and what about TFTP/PXE ??

What would the mes-people suggest
for minimalist functionality, and minimal trust scope,
and maximal monopoly-independence, I wonder?

[meta-question] How does one gracefully go off-topic onto a tangential
discussion? I thought my original comment re expired gpg key might
have helped in some way, but my comment wanting to get the ftp fixed
intead of (or in addition to) being bypassed provoked the explanation
of how I was deluded (ok, no worries :), but I might want to
say something about separate connections isolating meta-data and data
as being a "feature" that I expect to see more of, but that would be
another step along the tangent ... or osculating circle? NNTR :-D 

-- 
Regards,
Bengt Richter




  reply	other threads:[~2021-02-14  3:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13  2:37 bug#46482: [core-updates] u-boot source cannot be downloaded Danny Milosavljevic
2021-02-13  3:19 ` Leo Famulari
2021-02-13 18:34 ` Bengt Richter
2021-02-13 19:12   ` Leo Famulari
2021-02-14  3:57     ` Bengt Richter [this message]
2021-02-19 15:26 ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20210214035750.GA4673@LionPure \
    --to=bokr@bokr.com \
    --cc=46482@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).