unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Shivam Madlani <shivammadlani5@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: pukkamustard <pukkamustard@posteo.net>,
	Attila Lendvai <attila@lendvai.name>,
	 Christopher Baines <mail@cbaines.net>,
	guix-devel@gnu.org
Subject: Re: Hello GUIX
Date: Fri, 7 Apr 2023 15:24:23 +0530	[thread overview]
Message-ID: <CAAa6HdeLJ_RJ3jw6yTNGHe3OaPUNWaDq+X-q1UKbs9LcMNiPzg@mail.gmail.com> (raw)
In-Reply-To: <87zg7lx0n4.fsf@riseup.net>

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

> The NNCP utility might be worth taking a look at.  There is a way to set
> it up alongside udev to automatically transfer files from connected USB
> storage.

I did a bit of research at the NNCP util and yes, this can be used for
automatic file transfers.
We can create a new udev rule that would trigger nncp when a USB device is
connected. The directories where the files need to be transferred can be
done by creating a config file for NNCP and setting the 'nncpdir' variable
as the desired path. Further customization can be done by altering the nncp
config and udev rules.

I also took a look at the rsync utility which is more widely used but does
not provide features like encryption and compression. Although, it does
have a feature that transfers only the changes within the file instead of
the whole file (better transfer speeds).

Personally, I think nncp is a better choice here as it provides more
features and the tradeoff for using rsync is not that much.

Regards,
Shivam

On Thu, 6 Apr 2023 at 06:55, Csepp <raingloom@riseup.net> wrote:

>
> Shivam Madlani <shivammadlani5@gmail.com> writes:
>
> > Thanks a lot for the feedback!!
> >
> >>  Reading from a disk maybe should happen automagically if it can be
> >>  detected (and is enabled in some configuration). This might also
> >>  require some integration with udisks. The complexity of this should
> >>  not be underestimated.
> >
> > We can set it up in such a way that on running `guix install {xyz}` it
> will first check for mounted drives in /media
> > directory and install {xyz} if it's present in the drive.
> >
> >> Writing packages to a USB stick seems to be closer to a `guix
> >>  publish` or `guix deploy`. Maybe you can read up on those commands
> >>  and think of a nice way to publish or deploy a set of packages to a
> >>  USB stick. This is also relevant for publishing to other p2p
> >>  networks (IPFS, GNUnet, etc.).
> >
> > Perhaps, We can introduce a new utility? (maybe something like `guix
> sneak`). This will scan for external drives
> > and on detecting a drive it will encode and store the nars into it.
> > The size of the drive can cause an issue here in case the content to be
> encoded is very large. In this case an
> > appropriate error message will be displayed. Although this is rare as
> flash drives/hard drives have a lot of storage
> > capacity these days but it's still a thing to consider.
> >
> > Another way would be to use `guix publish` itself to do all of this. We
> can introduce a flag `--sneak` which instead
> > of spawning an HTTP server, encodes and stored into the drive. But i
> don't think we should modify an already
> > existing utility for this. I would like to hear your thoughts on this.
>
> The NNCP utility might be worth taking a look at.  There is a way to set
> it up alongside udev to automatically transfer files from connected USB
> storage.
>

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

      reply	other threads:[~2023-04-07  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 18:27 Hello GUIX Shivam Madlani
2023-03-29  9:55 ` pukkamustard
2023-03-31  9:16   ` Shivam Madlani
2023-04-06  1:23     ` Csepp
2023-04-07  9:54       ` Shivam Madlani [this message]

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=CAAa6HdeLJ_RJ3jw6yTNGHe3OaPUNWaDq+X-q1UKbs9LcMNiPzg@mail.gmail.com \
    --to=shivammadlani5@gmail.com \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    --cc=pukkamustard@posteo.net \
    --cc=raingloom@riseup.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.
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).