Reasonable Browser Support in Debian hurd
After Seamonkey was removed from Debian some time ago, i wonder if maybe one of the developers of debian hurd have some Information about if and when we can expect Firefox support in debian hurd. Thank you for your efforts.
Re: Debian GNU/Hurd 2017 released!
Thank you developers for your constant hard work on Debian Hurd!
iso_not_recognised
Hello team Over the last 2 years. 3 times I have tried to install Debian-Hurd and failed because I make an installation DVD and then 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. So the Debian-Hurd DVD has been made to be non-bootable for reasons that I cannot even imagine: the installation disc is in fact a dead disc. The problem that I experience will be very common (at least 50%, I guess) as I multi-boot using Grub and in 95% of cases find installing different operating systems easy enough but as you do not even mention this initial installation problem on your web site installation instruction, then I suppose the people who fail to install Debian-Hurd because the installation disc is not recognised just give up and install an alternative instead, and do not submit bug-reports, as such a submission is very complicated and often too baffling to actually do. Have you any idea on what the iso recognition problem is and how to overcome it? I would love to give a non-systemd Debian system a try, as over the years, Debian has been until recently my favourite Linux operating system. Yours sincerely Graham Cunnington
Re: Reasonable Browser Support in Debian hurd
matthias...@web.de, on lun. 19 juin 2017 17:35:14 +0200, wrote: > After Seamonkey was removed from Debian some time ago, i wonder if maybe one > of > the developers of debian hurd have some Information about if and when we can > expect Firefox support in debian hurd. There's a version on debian-ports: $ apt-cache policy firefox firefox: Installé : (aucun) Candidat : 45.0.2-1+hurd.1 Table de version : 45.0.2-1+hurd.1 500 500 http://ftp.ports.debian.org/debian-ports unreleased/main hurd-i386 Packages Samuel
Still Failing: g-i-installation_debian_sid_daily_hurd_lxde/372
See https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/372/ and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/372//console and https://jenkins.debian.net/job/g-i-installation_debian_sid_daily_hurd_lxde/372//artifact/results/ if there are any.
Why are the 2017 DVD ISOs so small ?
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 has a capacity of 4482.625 MiB = 4.378 GiB. So most of the data would fit onto a single medium. Other Debian DVD-1 ISOs are a bit smaller than 4 GiB to fit on a "4 GB" USB stick. See for example https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/ Have a nice day :) Thomas
Re: Why are the 2017 DVD ISOs so small ?
Thomas Schmitt, on lun. 19 juin 2017 20:43:48 +0200, wrote: > 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 ? Yes, our isofs still uses a mere memory mapping of the whole image, so it doesn't support big sizes. Samuel
Re: iso_not_recognised
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 GNU/Hurd ISOs DVD-1 and NETINST only offer starting points for BIOS, not for EFI. (I am not sure whether Hurd would run on hardware from modern EFI times.) The image wget http://ftp.ports.debian.org/debian-ports-cd/hurd-i386/debian-hurd-2017/debian-hurd-2017-i386-DVD-1.iso works for me on qemu virtual machines with SeaBIOS from virtual DVD or virtual hard disk (or USB stick). haiku-r1alpha4.iso is exotic. It boots by an emulated 2.8 MB floppy in the El Torito boot image. (GRUB and ISOLINUX boot by no-emulation boot images, which are x86 programs.) > Have you any idea on what the iso recognition problem is and how to overcome > it? You will have to tell more about your computer. Especially its processor (e.g. 32 bit Intel Pentium) and the boot firmware (e.g. Phoenix-Award BIOS vX.YZ). Then you will have to give the exact URL of the ISO which does not work for you. Have a nice day :) Thomas
Re: iso_not_recognised
Hello, Justwalking, on lun. 19 juin 2017 16:36:27 +0100, wrote: > Over the last 2 years. 3 times I have tried to install Debian-Hurd and > failed because I make an installation DVD and then my computer does not even > see the DVD-1 in the DVD drive, How is the DVD drive connected? SATA? I'm not sure the AHCI driver was fixed for various kinds of DVD drives, that probably still needs fixing. You can as well just try to copy the pre-installed disk image over your disk, or just copy the "/" partition. > I suppose the people who fail to install Debian-Hurd because the > installation disc is not recognised just give up and install an > alternative instead, Or install on a VM, like most people do when trying a fancy OS that probably doesn't have drivers for everything in the world :) Samuel
Re: Debian GNU/Hurd 2017 released!
Hello, Thomas Schmitt, on dim. 18 juin 2017 11:07:36 +0200, wrote: > > 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: That's not surprising by nowadays' """ISO""" image standard: they are both valid as CD image, usb stick image, etc. > One should ask the provider of grub_embed whether it is intentional to > have a MBR signature in bytes 510 and 511 and to have the cleartext word > "Floppy" in the range where the MBR is supposed to expose its partition > table. Ask grub people then :) > although the menu switches by every press of an arrow key from dark purple > with horizontal and vertical roll-over to grey cyan with correct geometry. Again, a grub issue :) Samuel
Re: Enable PIE by default in GCC?
Hello, Pino Toscano, on dim. 18 juin 2017 21:33:53 +0200, wrote: > as $subj asks, should we ask for GCC with PIE enabled by default, like > is done in the majority of the other archs (i.e. [1])? Ideally, yes. In practice, it works but gdb is lost with PIE executables, so that has to be fixed first. Samuel
Re: Debian GNU/Hurd 2017 released!
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 x86 ISOs but also the MBR of grub-mkrescue. My program xorriso writes those partition tables if it is told to do so. But in the case of the grub_embed MBR there seems to be code where the partition tables is supposed to be. So it would not be a good idea to simply add option --protective-msdos-label to the xorriso -as mkisofs run. > > One should ask the provider of grub_embed > Ask grub people then :) I would need to know how the MBR and the subsequent data blocks are produced. (And for what device an MBR with garbled partition table would be deemed suitable, if that is known.) The code in the MBR of grub-mkrescue obviously hops onto the program in the El Torito boot image. So it can be small enough to leave bytes 446 ff. unused. I refer to grub-mkrescue because it is the official upstream proposal to prepare the GRUB2 entrails and the xorrisofs options for a GRUB2 bootable ISO. > > although the menu switches by every press of an arrow key from dark purple > > with horizontal and vertical roll-over to grey cyan with correct geometry. > Again, a grub issue :) Do you see the same effects in your tests ? If not, with what virtual firmware do you test ? (And why is your /boot/grub/grub_eltorito not needy of xorrisofs option --grub2-boot-info ?) Have a nice day :) Thomas
Re: Debian GNU/Hurd 2017 released!
Thomas Schmitt, on mar. 20 juin 2017 00:05:01 +0200, wrote: > > Ask grub people then :) > > I would need to know how the MBR and the subsequent data blocks > are produced. The build log is available on https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/daily/debian-cd.log xorriso is version 1.3.2 > > > although the menu switches by every press of an arrow key from dark purple > > > with horizontal and vertical roll-over to grey cyan with correct geometry. > > > Again, a grub issue :) > > Do you see the same effects in your tests ? Yes. And also with linux/kfreebsd images. > (And why is your /boot/grub/grub_eltorito not needy of xorrisofs > option --grub2-boot-info ?) I haven't looked into all these so I don't know, I'm just using what happens to be there in the Debian scripts. Samuel
Unintentional spam report
Good morning. Please, don't consider the spam report come some minutes ago from the page: https://lists.debian.org/debian-hurd/2017/06/msg00017.html; I unintentionally clicked the mouse on the "report as spam" button cause of a sleep blow. I appreciate the great job of all You. Thanks for Your attention. Mark B.
root password is not empty on new hurd image
Hi, I looked at this page https://people.debian.org/~sthibault/hurd-i386/README and it says the root password is empty. So why is it I enter root as the user and hit enter at password prompt it says "Invalid password?" -- Eric
Re: root password is not empty on new hurd image
Nevermind false alarm. On 06/19/2017 10:30 PM, Eric Noble wrote: Hi, I looked at this page https://people.debian.org/~sthibault/hurd-i386/README and it says the root password is empty. So why is it I enter root as the user and hit enter at password prompt it says "Invalid password?" -- Eric
Re: Enable PIE by default in GCC?
On 19 Jun 2017, at 22:13, Samuel Thibault wrote: > Pino Toscano, on dim. 18 juin 2017 21:33:53 +0200, wrote: >> as $subj asks, should we ask for GCC with PIE enabled by default, like >> is done in the majority of the other archs (i.e. [1])? > > Ideally, yes. In practice, it works but gdb is lost with PIE > executables, so that has to be fixed first. I see you suffer from RAS syndrome :) In all seriousness though, is there anywhere explaining what the issue with GDB is? I see [1] but that is from a while ago and talking about PIEs themselves not working. It's not completely out of the question that I will look into it (though no promises, I have a lot of things I want to get done...). Regards, James [1] https://www.gnu.org/software/hurd/open_issues/gcc/pie.html
Re: Debian GNU/Hurd 2017 released!
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 its name and when xorriso reports to have used it. But i see no hint how this files gets created. It would be interesting to know which documentation and which GRUB modules lead to that binary. I googled for "grub_embed". The best match was your changelog entry from 2014: Add usb key boot support for kfreebsd & hurd images. This needs another grub image, grub_embed, which has to be very small. Add x86-image script, similar to efi-image script, with factorized grub-cpmodules part, to build minimal grub images with iso9660 and biosdisk support, and put GRUB modules on the ISO image. I was unable to find kFreeBSD ISOs which have an MBR. Would that "x86-image script" explain more ? (https://sources.debian.net/src/debian-cd/unstable/ throws "Internal Server Error", so i cannot currently explore debian-cd myself.) > xorriso is version 1.3.2 It's fully sufficient, although quite old. > > > > with horizontal and vertical roll-over > > Do you see the same effects in your tests ? > Yes. And also with linux/kfreebsd images. Not with amd64 (can't get i386 to boot with -bios OVMF.fd on my amd64 machine). https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso With SeaBIOS, ISOLINUX is in charge and works fine. With OVMF, GRUB2 is in charge and works fine. The kFreeBSD mini ISOs i have indeed show the same display problem as the newest Hurd NETINST. But debian-7.9.0-kfreebsd-amd64-netinst.iso is OK with SeaBIOS. It has GRUB 1.99 (which is a GRUB2 before its first official release). So currently it looks like the problem is with GRUB 2.02 on (Sea)BIOS. I will ponder how to reproduce it with grub-mkrescue. Have a nice day :) Thomas
