Hi,
since yesterday i am proud operator of a Debian GNU/Hurd installed via
http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/netinst.iso
in a kvm image file on Debian GNU/Linux 6.0.2 amd64.
Building my projects GNU xorriso or libisofs from source tarball
failed with missing
Hi,
harish badrinath wrote on debian-hurd@lists.debian.org:
I have posted a bug
report,http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639517
Niv Sardi wrote to 639...@bugs.debian.org:
http://wiki.debian.org/ReleaseGoals/LAFileRemoval
IIRC, It's a release goal.
I do wonder, how my
Hi,
Samuel Thibault wrote:
libisofs not building was becoming more and more a problem, so I patched
the libacl.la file by hand (yes, a bad thing).
A change in the Debian package configurations of libisofs and libisoburn
for hurd-i386 would avoid unnecessary problems.
Currently the support for
Hi,
does errno -303 announce bigger trouble ?
Probably yes: the query/reply IPC ping-pong got disturbed somehow.
Here is a minimal C example:
#include unistd.h
#include stdio.h
#include errno.h
int main()
{
int ret;
Hi,
i guess it is not intentional that on a freshly installed Debian GNU/Hurd
$ su
Password:
# apt-get install libacl1-dev
fails with
...
Get:2 http://jk.fr.eu.org/debian/hurd-installer/mirror/ sid/main libacl1-dev
hurd-i386 2.2.47-3 [78.1 kB]
Fetched 119 kB in 0s (373 kB/s)
Hi,
Svante Signell wrote:
Debian has fixed this already.
Samuel Thibault wrote
In Debian Linux, yes. But we still have the issue on Debian Hurd. There
is no reason why we shouldn't be able to get the same behavior.
I would like to understand how this miracle works on my amd64
installation
Hi,
Thomas do you need mount.h?
Not yet.
But i am having trouble with udev (or udisks ?) on amd64 which interfere
with burn runs. So it might become necessary to care about umounting
before burning. Quite a nightmare. I would have the choice between forking
shell commands or using system
Hi,
Ritesh Raj Sarraf wrote:
A quick search for scsi related items on Hurd shows nothing interesting
Samuel Thibault wrote:
You can look on the bug-hurd mailing list, Interface for SCSI
transactions, Thomas Schmitt proposed to work on a generic interface, I
don't know its status.
Well
Hi,
i found
https://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/build/util/x86-image
which indeed produces a file grub_embed.
But it uses a blob as first part of that file:
cat "/usr/lib/grub/$platform/boot.img" "$workdir/core.img" >
"$outdir/boot/grub/grub_embed"
I have one on
Hi,
i wrote:
> > https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64
-netinst.iso
> > With OVMF, GRUB2 is in charge and works fine.
Samuel Thibault wrote:
> That's probably sheer luck.
> [ Part 2, Image/PNG 545 KB. ]
Wow. That's really unusable.
The appearance of
Hi,
i wrote:
> > I would need to know how the MBR and the subsequent data blocks
> > are produced.
Samuel Thibault wrote:
> The build log is available on
> https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/daily/debian-cd.log
This mentions grub_embed two times when xorriso gets
Hi,
my assembler reading skills are obviously insufficient. It turns out that
the bytes in the MBR partition table range are not significant for booting
the ISO from qemu -hda.
I boldly zeroed them in a copy of the GNU/Hurd ISO and it still boots.
(To make sure that it does not boot by El Torito
Hi,
Samuel Thibault wrote:
> I rather guess the double-buffering support in grub.
But where would that be controllable ?
grub-mkimage --help has no options for that. Google does not find me
any clue about grub.cfg statements which would promise to do it.
Have a nice day :)
Thomas
Hi,
Samuel Thibault wrote:
> Files on
> https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/daily/
> are now updated accordingly
Oh yes. Now it looks much better and should be digestible for partition
editors.
Hi,
Graham Cunnington wrote:
> my computer does not even
> see the DVD-1 in the DVD drive, although it sees all Linux bootable isos and
> the Haiku iso when a disk is put in the hard drive.
Most GNU/Linux Installation- or Live-ISOs are prepared for booting
via BIOS and EFI firmware. The Debian
Hi,
the DVD images 1 to 3 in
http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/debian-hurd-2017/
are listed with sizes 1.6G, 1.7G, and 1.7G respectively. At least DVD-1
really has only 1,680,308,224 bytes (and is not truncated or rolled over).
Is the small size intentional ?
A normal DVD
Hi,
i wrote:
> > i see a quite insane MBR partition table:
Samuel Thibault wrote:
> That's not surprising by nowadays' """ISO""" image standard: they are
> both valid as CD image, usb stick image, etc.
Sure. But normally the MBR has a valid partition table.
Not only the ISOLINUX MBR of Debian
Hi,
in
http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/debian-hurd-2017/debian-hurd-2017-i386-NETINST-1.iso
i see a quite insane MBR partition table:
$ /sbin/fdisk -lu debian-hurd-2017-i386-NETINST-1.iso
...
Disklabel type: dos
...
Device Boot
Hi,
Samuel Thibault wrote:
> Mmm, actually I had tested with the amd64 debian iso image , not the
> i386. The i386
http://cdimage.debian.org/cdimage/release/10.2.0/i386/iso-cd/debian-10.2.0-i386-netinst.iso
> has the same issue,
Aren't amd64 and i386 GNU/Linux systems ?
Those have ISOLINUX
Hi,
Samuel Thibault wrote:
> kvm -cdrom debian-sid-hurd-i386-NETINST-1.iso -bios OVMF.fd
> doesn't manage to boot it. Perhaps that's a kvm issue, or perhaps that's
> a grub-ia32 issue (since I can't boot a linux-i386 image either)
Indeed, this gives a "UEFI Interactive Shell" prompt and no
Hi,
Samuel Thibault wrote:
> Indeed, a 32bit version of OVMF is needed. I could grab one,
This explains why i could not repeat my success with qemu-system-i386.
(Now i wonder what i did to fall victim to that illusion.)
> grub boots fine. gnumach however doesn't.
Good luck with the rest of
21 matches
Mail list logo
