The Alpha install CD lacks JFS tools, i.e. mkfs and fsck. This is true for the one dated 6/8/2013 and the one before that.
I just checked and jfsutils was never marked stable for alpha[1]. That explains why it isn't enabled on the alpha CD specs[2]. If you want to change this, you'll have to ask the alpha team to test it and mark it stable. [1] - http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-fs/jfsutils/jfsutils-1.1.15.ebuild?revision=1.8&view=markup [2] - http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=blob_plain;f=releases/weekly/specs/alpha/installcd-stage1.spec;hb=refs/heads/master
jfsutils have been marked stable: 14 Jun 2013; Tobias Klausmann <klausman@gentoo.org> jfsutils-1.1.15.ebuild: Make jfsutils-1.1.15 stable on alpha (bug 473238)
Added to the installcd spec, will close this when a new installcd is built.
There was a new CD released in January. I think this is fixed?
(In reply to Matt Turner from comment #4) > There was a new CD released in January. I think this is fixed? I think they fixed it autumn 2014, which led to Bug 524060 because that CD wouldn't boot. I don't think isomarkboot has been fixed, since that bug is still open, but a workaround seems to have been used. However, jfs gives portage severe problems on my alpha. Only some packages can be emerged successfully. The first one to fail is gentoo-sources... I don't why this happens. It's not swap space this time. I gave up and built a separate new ext3 partition. I don't expect the jfs/portage problem will ever be fixed, since I am the only person trying to use the gentoo+alpha+jfs combination. I did build an amd64 gentoo setup using jfs in the mean time, so it's a gentoo alpha problem with that filesystem. I think this bug can be closed. I will do it.
