Re: SPARC Issues Open for Conjecture
On 06/10/2016 08:31 PM, alexmcwhirter@triadic.us wrote:
> Something that might be worth doing it having the install check loaded modules on initialization, then compare that to the loaded modules before finalizing. If
> any new modules have shown up they should be added to /etc/initramfs-tools/modules before generating initrd. This way any modules the user had to manually load
> during install time will at least carry over to the actual installation.
This sounds like a rather crude hack. I do not think the DI team would any of such patches.
> Of course udev is the better option, but think of this as a type of fail safe in case udev doesn't work.
If udev doesn't work, you will have way more serious issues anyway. There isn't really a normal
scenario where udev doesn't work. If it doesn't work, you won't be able to do anything anyway.
As I have mentioned before, modules not being loaded automatically is an issue with the
modules itself.
> Great, i've been looking for information about this. Are there any guides out there for cloning the entire source tree and building a repo from scratch? I have
> seen some references to buildd which appears to be an internal tool to do just this more or less, but with not a lot of documentation that i can find.
You want to build 11,000 packages from source? Why? There isn't anything to gain from, really.
Also, buildd is not an internal tool, it's part of the sbuild package and you can just install
it yourself. You just need a wanna-build server to interact with.
> ZFS actually works great on most sparc boxes, but i don't know where debian stands on it with the CDDL debate. That's an issue for another time i suppose.
> Regardless the installer in fact doesn't have the ZFS modules included (probably because they fail to build on SPARC without some minor patching). The
> partitioner attempts to load them, but they are missing so it just keep chugging along without them, which is fine for now.
Debian ships with zfslinux now, although the module itself is source-only. We use DKMS for installation.
> Will do, i have a feeling that we should avoid patching the installer and just make sure the CD has everything in place to work with it if possible.
Debian Installer has lots of architecture-specific code and that code sometimes needs some
patching, there is nothing wrong with that.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: