unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: jfs, jfsutils?
Date: Thu, 12 Dec 2019 00:57:54 +0100	[thread overview]
Message-ID: <87y2viifel.fsf@nckx> (raw)
In-Reply-To: <882e8091-aaa7-0705-306d-d4bf2824e050@gmail.com>

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

Michael,

Michael Zucchi 写道:
> I just built a new computer and thought i'd give guix a go

That's great to hear!  Welcome.

> but after
> finally getting everything working to the install stage ... I 
> hit a
> personal showstopper - no jfs support whatsoever.  It's mostly 
> an
> afterthought on every other distribution but this was a 
> surprise.
>
> Any reason for this or is it just that nobody thought of it?

s/thought/uses/

Nobody's going to add support for a file system they don't use, 
and nobody boots Guix from JFS.

…yet. :-)

> Anyway, I just ended up installing slackware-current and have 
> then
> installed guix atop that, to grab a few packages and to get more
> familiar with it.  I would probably have had to do that anyway 
> as it
> was probably too much to learn at once but I currently have a 
> lot of
> spare time to fill, so tried guix first.

Spare time sucks, consider contributing JFS support to Guix 
instead.

Assuming it's a pretty conventional Linux file system:

- Guix's Linux-Libre kernel already builds the module 
  (CONFIG_JFS_FS=m)
- it just needs to be added to the initramfs when booting from JFS
- jfsutils needs to be packaged for Guix and a static fsck added 
  to the initramfs
- some code must be added to (gnu build file-systems) to read JFS 
  labels & UUIDs: Guix does not use C tools to do this like other 
  distributions.

If you're completely new to Guix that might sound daunting, but 
it's honestly not that hard and you should get plenty of help on 
the mailing list and/or on IRC.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2019-12-11 23:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 22:31 jfs, jfsutils? Michael Zucchi
2019-12-11 22:38 ` Josh
2019-12-11 23:49   ` Michael Zucchi
2019-12-11 23:57 ` Tobias Geerinckx-Rice [this message]
2019-12-12  1:41   ` Tobias Geerinckx-Rice
2019-12-12  3:18     ` Michael Zucchi
2019-12-13 14:31       ` Joshua Branson
2019-12-13 16:07       ` Tobias Geerinckx-Rice
2019-12-13 16:23         ` Tobias Geerinckx-Rice
2019-12-14  1:15         ` Michael Zucchi
2019-12-30 23:38   ` Michael Zucchi
2019-12-31  0:42     ` Josh Marshall
2019-12-31  6:26       ` Michael Zucchi
2020-01-05 19:04         ` Gábor Boskovits
2020-01-06  7:20           ` Michael Zucchi
2019-12-13 14:33 ` Packing bcachefs " Joshua Branson
2019-12-13 15:32   ` Packaging bcachefs Tobias Geerinckx-Rice

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=87y2viifel.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).