On 24/11/2022 5:41 am, Flavio Cruz wrote:
On Wed, Nov 23, 2022 at 11:51:36AM +0100, Samuel Thibault wrote:
Flavio Cruz, le mer. 23 nov. 2022 00:10:10 -0500, a ecrit:
Latest GCC will pick up gnu17 by default but gnu11 will be better
supported with older compilers.
Mmm, but why explicitly reque
On 13/12/2022 12:46 am, Sergey Bugaev wrote:
@@ -90,6 +95,21 @@ __file_name_lookup_at (int fd, int at_flags,
}
}
+ if ((orig_flags & __O_TMPFILE) == __O_TMPFILE)
+{
+ /* What we have looked up is not the file iteself, but actually
s/iteself/itself.\/
+ th
On 14/05/2023 7:01 am, jbranso wrote:
May 13, 2023 1:46 PM, "Sergey Bugaev" wrote:
On Sat, May 13, 2023 at 7:38 PM jbranso wrote:
+Hurd developers are adding 64-bit support, and they plan to drop the
+32-bit support, once the 64-bit support is deemed stable.
Is this really the plan? :(
Has
On 23/05/2023 5:23 am, Joshua Branson wrote:
Sergey Bugaev writes:
Hi,
On Mon, May 22, 2023 at 6:49 PM jbra...@dismail.de wrote:
+upgrade to the bleeding edge Debian GNU/Hurd:
+
+ $ wget
http://ftp.de.debian.org/debian/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2023
On 19/12/2015 6:53 a.m., Samuel Thibault wrote:
> David Renz, on Fri 18 Dec 2015 18:49:11 +0100, wrote:
>> if it really wouldn't be supported by Debian Hurd, then the installation
>> process couldn't even reach that stage, isn't it?
>
> Yes it would: loading the kernel and initrd is done by grub t
On 07/07/17 03:19, Samuel Thibault wrote:
Hello,
Nice progress :)
Joan Lledó, on dim. 02 juil. 2017 10:29:33 +0200, wrote:
the stack offers the option of
using DAD[2] to check if the address is already in use. This isn't
likely to happen, since the interface identifier is based on the link
add
r, are there any alternatives available on Hurd?
Amos Jeffries
On 20/02/18 11:03, Samuel Thibault wrote:
> Samuel Thibault, on lun. 19 févr. 2018 19:04:57 +0100, wrote:
>> See the branches there, they already exist.
>>
>>> and ask you to commit upstream upstream?
>>
>> If it was a matter of committing, that'd be done already... See what I
>> wrote on 18 Jan 20
On 01/03/18 14:23, Samuel Thibault wrote:
> Joseph Myers, on jeu. 01 mars 2018 01:17:18 +, wrote:
>> Missing spaces before '(' in the calls to atomic_increment,
>
> etc.
>
> Can people _please_ help me with all these? (not only on that patch, but
> on the whole set of patches which we *DO* n
This patch updates the copyright blurbs in libpthread repository to
match upstream glibc requested format.
Specific changes are:
* use -2018 for copyright dates
* replace obsolete FSF address with current gnu.org URL reference from
glibc.
Joseph also asked in the other thread for "Contri
On 02/03/18 03:45, Samuel Thibault wrote:
> Amos Jeffries, on ven. 02 mars 2018 03:37:17 +1300, wrote:
>> Joseph also asked in the other thread for "Contributed by" lines not to
>> be added in new files. There are a few in this code, but the files
>> creation are
On 08/06/18 04:58, Joshua Branson wrote:
>
> I would actually recommend that you just run the Hurd in qemu. Most, if
> not all, of the main Hurd developers just run the Hurd inside qemu.
>
> Also a cool idea! I believe I read somewhere that it possible to have
> the Hurd running in qemu, but ma
On 09/06/18 04:53, Joshua Branson wrote:
> Amos Jeffries writes:
>
>> On 08/06/18 04:58, Joshua Branson wrote:
>>>
>>> I would actually recommend that you just run the Hurd in qemu. Most, if
>>> not all, of the main Hurd developers just run the Hurd in
On 15/06/18 10:31, Almudena Garcia wrote:
> Yes, I concluded the same a few hours ago. I tried to edit
> kern/cpu_number.h, to add a new definition with many cores, at this form
>
> int master_cpu; /* 'master' processor - keeps time */
>
> #if (NCPUS == 1)
> /* cpu number is a
On 21/07/18 09:37, Ranvijay Kumar Vijay wrote:
> Dear All,
>
> I've created a HURD Bazaar fork,
Er, are you aware that "Bazaar" is already taken by a VCS system? it is
going to be very confusing to have something called a "Bazaar fork" when
it is actually a git fork, not managed by Bazaar.
> be
On 16/12/18 6:17 am, Almudena Garcia wrote:
> Can you add a new FAQ about 64 bit support?
> Or, if exists, modify It to add this link
> https://www.gnu.org/software/hurd/open_issues/64-bit_port.html
>
The rebootstrap link on that page is outdated and now a 404.
The job name should be "rebootstrap
On 17/12/18 10:56 am, Joshua Branson wrote:
> Amos Jeffries writes:
>
>> On 16/12/18 6:17 am, Almudena Garcia wrote:
>>> Can you add a new FAQ about 64 bit support?
>>> Or, if exists, modify It to add this link
>>> https://www.gnu.org/software/hurd/ope
On 12/08/20 12:17 am, Almudena Garcia wrote:
>> You can use b (break) within a git rebase session to stop at some point.
>> That way you can stop before the big change, commit part of it, and use
>> git rebase --continue, and let git discover that part of the big change
>> is already there and drop
On 11/08/20 11:57 pm, Samuel Thibault wrote:
> Almudena Garcia, le mar. 11 août 2020 13:45:19 +0200, a ecrit:
>>> P.S. You might be interested in using the program git send-email.
>>> Apparently it makes it really easy to send in a patches series. It's
>>> actually what GNU Guix contributing guid
With my hat on as an IETF HTTPbis WG member. Here are some editorial
nits in regards to HTTP protocol things being mentioned ...
On 10/09/20 2:29 am, Joshua Branson wrote:
> I copied most of the text from the Hurd extras repos.
> ---
> hurd/translator/httpfs.mdwn | 68 +
The HEAD request used to fetch metadata about a file via HTTP
contains a trailing 0x20 character which will cause modern HTTP/1.1
servers to reject the request.
===
RCS file: /sources/hurdextras/httpfs/http.c,v
retrieving revision 1.3
On 10/09/20 5:16 am, Samuel Thibault wrote:
> Amos Jeffries, le jeu. 10 sept. 2020 04:16:54 +1200, a ecrit:
>> The HEAD request used to fetch metadata about a file via HTTP
>> contains a trailing 0x20 character which will cause modern HTTP/1.1
>> servers to reject the r
Sorry, not quite. :(
On 10/09/20 11:49 am, Joshua Branson wrote:
> +
> +# settrans -a tmp/ /hurd/httpfs
> https://www.gnu.org/software/hurd/index.html
> +
"https://"; is not supported sadly. Just "http://"; scheme.
Amos
Yay! :-)
Armchair review comments inline..
On 9/07/23 22:05, Damien Zammit wrote:
This is not quite right for library/std, but applies clean to a 2021 tree
of rust on hash 25ea6be13e3 and allows up to the following stage1 build
until libstd breaks on hurd, (with the other patch for rust-libc).
On 17/10/24 19:06, jbra...@dismail.de wrote:
diff --git a/open_issues/resource_management_problems.mdwn
b/open_issues/resource_management_problems.mdwn
index daf97954..51025d34 100644
--- a/open_issues/resource_management_problems.mdwn
+++ b/open_issues/resource_management_problems.mdwn
+Thes
On 17/10/24 12:30, jbranso wrote:
diff --git a/hurd/translator/streamio.mdwn b/hurd/translator/streamio.mdwn
new file mode 100644
index ..9f1de6ec
--- /dev/null
+++ b/hurd/translator/streamio.mdwn
@@ -0,0 +1,23 @@
+[[!meta copyright="Copyright © 2024 Free Software Foundation,
+Inc."]]
+
+
On 17/10/24 12:30, jbranso wrote:
+
+[[!tag stable_URL]]
+
+`devnode` is the Hurd devnode translator.
I would guess that means it provides access to system devices under the
path "/dev" ?
Cheers
Amos
On 4/07/25 03:40, Milos Nikic wrote:
Hi all,
I’m working on a user-space metadata journaling layer for libdiskfs and
have run into a boot-time issue I hope to get guidance on.
The goal is to capture metadata changes very early in the boot process —
ideally even before fsck — and flush them t
28 matches
Mail list logo
