From a126aa28d5adefc78a124bbe4af17b69ccc7c805 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Wed, 9 Aug 2023 19:49:42 +0200 Subject: Add link to pre-built 64bit image Drop outdated irc comments --- open_issues/64-bit_port.mdwn | 61 +++----------------------------------------- 1 file changed, 4 insertions(+), 57 deletions(-) (limited to 'open_issues/64-bit_port.mdwn') diff --git a/open_issues/64-bit_port.mdwn b/open_issues/64-bit_port.mdwn index 55138b1a..ab386388 100644 --- a/open_issues/64-bit_port.mdwn +++ b/open_issues/64-bit_port.mdwn @@ -30,13 +30,16 @@ Make sure to have `debootstrap >= 1.0.128+nmu2+hurd.1` sudo mkdir chroot-hurd-amd64/etc/apt/trusted.gpg.d sudo ln -s /usr/share/keyrings/debian-keyring.gpg chroot-hurd-amd64/etc/apt/trusted.gpg.d/ +Or use the pre-built image from https://people.debian.org/~sthibault/hurd-i386/initrd-amd64.img.gz + Then boot it, it will drop you into a shell. You need to make / writable: fsysopts / --writable -and then run the second stage of the deboostrap: +and then run the second stage of the deboostrap (and clear debs): /debootstrap/debootstrap --second-stage + apt clean set a root password: @@ -53,59 +56,3 @@ In principle crosshurd should be working, one however needs to add this source: deb http://people.debian.org/~sthibault/tmp/hurd-amd64 unstable into /etc/crosshurd/sources.list/gnu - -# IRC, freenode, #hurd, 2011-10-16 - - it'd be really good to have a 64bit kernel, no need to care about - addressing space :) - yes a 64 bits kernel would be nice - i guess it wouldn't be too hard to have a special mach kernel for - 64 bits processors, but 32 bits userland only - well, it means tinkering with mig - -[[mig_portable_rpc_declarations]]. - - -# IRC, freenode, #hurd, 2012-10-03 - - youpi: just so you know in case you try the master-x86_64 with - grub - youpi: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689509 - ok, thx - the squeeze version is fine but i had to patch the wheezy/sid one - I actually hadn't hoped to boot into 64bit directly from grub - youpi: there is code in viengoos that could be reused - i've been thinking about it for a time now - ok - the two easiest ways are 1/ the viengoos one (a -m32 object file - converted with objcopy as an embedded loader) - and 2/ establishing an identity mapping using 4x1 GB large pages - and switching to long mode, then jumping to c code to complete the - initialization - i think i'll go the second way with x15, so you'll have the two :) - - -## IRC, freenode, #hurd, 2013-07-02 - -In context of [[mondriaan_memory_protection]]. - - BTW, it's not like I have an infinite amount of time for this, - but having 64-bit support would be valuable for me, so I might contribute - that back if it's not a too monumental task - I saw some discussions about 32bit apps on top of 64bit mach, but - I'd like a full 64bit system - any clues? - I suppose the compiler support is all there already - is MIG (and mach) the only piece missing? - the problem is the interfaces themselves - type widths - as passed between userspace and kernel - - -## IRC, OFTC, #debian-hurd, 2013-10-05 - - and what about 64 bit support, almost done? - kernel part is done - MIG 32/64 trnaslation missing - -[[mig_portable_rpc_declarations]]. -- cgit v1.2.3