Hello again,
Apr 24, 2025, 19:05 by yelni...@tutamail.com:
> Hello Samuel,
>
> I haven't had much time to look into this in depth yet but I have adapted my
> initial example s.t. it doesn't need an external program for the main socket
> (please excuse my terrible C code and the formatting).
>
>
"lspci -nn" shows the ids and names.
Then you can search the PCI device id in the rump ahci source.
Damien
Sent from Proton Mail Android
Original Message
On 29/4/25 7:21 pm, Zhaoming Luo wrote:
> On Tue, Apr 29, 2025 at 09:51:25AM +0200, Samuel Thibault wrote:
> >
> > Wh
Hello Samuel,
I haven't had much time to look into this in depth yet but I have adapted my
initial example s.t. it doesn't need an external program for the main socket
(please excuse my terrible C code and the formatting).
The socket is first created nonblocking and once the first connection com
;
> It's indeed more challenging than I thought. I supposed I can see the
> linked rump library using ldd, but it seems it's not the correct way:
> ```
> demo@debian:~/hurd$ ldd build/rumpplay/rumpplay
> libirqhelp.so.0.3 => /lib/i386-gnu/libirqhelp.so.0.3 (0x0
Hello,
This was originally https://issues.guix.gnu.org/77610.
Guix recently switched to systemd-style socket activation
(https://www.freedesktop.org/software/systemd/man/latest/daemon.html#Socket-Based%20Activation)
for their daemon.
When I tried this on a Guix Hurd VM the first connection to
Dear Samuel,
Thank you for your feedback.
I am in the process of polishing the GCC configuration files and I will send
them a patch for the riscv64-gnu backend shortly. It is indeed a trivial change
with no more than 100 lines.
For the Mach, I'm planning on getting a simple kprintf working an
Hi all,
I’ve been working on getting GNU Mach to compile on riscv64, and I wanted to
share an early update and ask if there’s interest in upstreaming a stub port.
So far I’ve created a set of stub implementation files for riscv64, mostly
copied and stripped down from the existing i386 directory
You probably want to disable it entirely so it doesn't need to execute a branch
condition every time it reads the timer, ie with #ifdef.
This code path would be critical for timing.
Damien
Sent from Proton Mail Android
Original Message
On 23/3/25 9:13 pm, Zhaoming Luo wrote:
/*
> > > > + * Initialize the HPET
> > > > + */
> > > > + hpet_init();
> > > > }
> > > >
> > > > /* Conserve power on processor CPU. */
> > >
> > > You should also cope with the cas
Hi,
On Fri, Mar 14, 2025 at 12:44:02PM +, jbra...@dismail.de wrote:
> Apoligies for the click baity title...
That's the kinda mail that might've better been sent privately,
methinks.
Michael
droid
Original Message
On 4/2/25 11:01 am, Almudena Garcia wrote:
> This is awesome!! How can I test rumpusbdisk?
>
> El lun, 3 feb 2025 a las 21:32, Samuel Thibault ()
> escribió:
>
>> Hello,
>>
>> Damien Zammit via Bug reports for the GNU Hurd, le
Samuel Thibault wrote:
> > when I run 'sync' it hangs. I can interrupt the 'sync' command via
> > Ctrl-C and restart it, but it then still hangs. I ended up rebooted
> > anyway, and after reboot an 'fsck' was required. This 'fsck' found
> > between 17000 and 17 empty directories (depending on h
Samuel Thibault wrote:
> > In the default (NAT) configuration of a VirtualBox VM, in all VMs
> > so far I could "ssh 10.0.2.2" to log into the VM host. With these
> > new Hurd VMs, this is not the case
>
> Uh? What symptom do you actually get?
The ssh comm
Samuel Thibault wrote:
> it really looks like
> something in bash/libtinfo is inventing escape sequences.
Indeed: with 'dash' instead of 'bash' there is no issue.
> If you export TERM=dumb, that disappears, so it's really related to
> terminal sequences. Even TERM=vt100 produces it,
I see. And
Hi,
For quite a while I've been using Hurd from 2022 [1] for testing
various GNU packages, and it's been quite stable.
This week, Samuel invited me to try newer Hurd versions [2].
So, I tried
- Hurd/i386 from June 2023 [3]
- Hurd/x86_64 from November 2024 [4].
In all cases, I do th
The usb stack also uses SCSI emulation for usb mass storage.
---
rumpdisk/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rumpdisk/Makefile b/rumpdisk/Makefile
index e7f53511..cbe93845 100644
--- a/rumpdisk/Makefile
+++ b/rumpdisk/Makefile
@@ -17,7 +17,7 @@
RUMPLIB
Hi,
I would like to suggest the following upgrade of rump to be on par with
my "develop" branch[1]. The patches would need to be fetched from my
branch directly because there is a very large changeset in the NetBSD
upstream update commit.
The main thing is upgrading rump from 9.99.x to 10.99.x
On 12/29/24 8:56 AM, Samuel Thibault wrote:
> Damien Zammit via Bug reports for the GNU Hurd, le sam. 28 déc. 2024 06:39:04
> +, a ecrit:
>> + setenv ("RUMP_MEMLIMIT", "16m", 1);
> Did you test this a lot?
>
> We'd probably want to disable rump-
Proxied memory was not rounded up to page size, causing
error with vm_map'ing the underlying memory.
WARNING: Assumes pci memory resources are at least page aligned.
If not, this will expose part of next resource to userspace.
---
pci-arbiter/netfs_impl.c | 8 +++-
1 file changed, 7 inserti
Return positive error code when return value indicates error.
---
acpi/acpi-ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/acpi/acpi-ops.c b/acpi/acpi-ops.c
index 47f7e3d2..16d96e71 100644
--- a/acpi/acpi-ops.c
+++ b/acpi/acpi-ops.c
@@ -84,7 +84,7 @@ S_acpi_get_pci_irq
---
rumpdisk/main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/rumpdisk/main.c b/rumpdisk/main.c
index ca166274..ca9deea1 100644
--- a/rumpdisk/main.c
+++ b/rumpdisk/main.c
@@ -123,6 +123,8 @@ main (int argc, char **argv)
setenv ("RUMP_NCPU", "1", 1);
setenv ("RUMP_VERBOSE", "1"
---
rumpdisk/block-rump.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/rumpdisk/block-rump.c b/rumpdisk/block-rump.c
index cd7af494..8a3a404a 100644
--- a/rumpdisk/block-rump.c
+++ b/rumpdisk/block-rump.c
@@ -373,6 +373,7 @@ rumpdisk_device_write (void *d, mach_port_t reply_port,
Proxied memory was not rounded up to page size, causing
error with vm_map'ing the underlying memory.
WARNING: Could be security risk if assumption is incorrect:
Assumes start of all pci memory resources are at least page aligned.
---
pci-arbiter/netfs_impl.c | 11 ++-
1 file changed, 10
This internal function acpi_get_irq_number() returns negative for
error, otherwise returns valid IRQ.
---
acpi/acpi-ops.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/acpi/acpi-ops.c b/acpi/acpi-ops.c
index 1aaec10c..16d96e71 100644
--- a/acpi/acpi-ops.c
+++ b/acpi
Because we support up to 64 irqs with 2 IOAPICs.
---
i386/i386/irq.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/i386/i386/irq.c b/i386/i386/irq.c
index 3c2f1748..91318f67 100644
--- a/i386/i386/irq.c
+++ b/i386/i386/irq.c
@@ -65,7 +65,9 @@ __enable_irq (irq_t irq_nr)
This mostly fixes the numbering of IRQs when requested.
This now works on an old AMD board with broken _CRS.
It requests the possible irqs from _PRS and generates
a valid _SRS request to set the one from the end of the list.
v2: It also no longer errors on a valid _CRS.
---
debian/patches/acpi-i
This mostly fixes the numbering of IRQs when requested.
This now works on an old AMD board with broken _CRS.
It requests the possible irqs from _PRS and generates
a valid _SRS request to set the one from the end of the list.
Note that acpi translator can only be used with gnumach that
has been com
This ensures the resources are correct when matching.
Resources are always all ones in the function field
as they apply to all functions of a device.
---
debian/patches/acpi-init-files.diff | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/debian/patches/acpi-init-files
This allows rumpdisk to probe correctly on machines
with broken LNKx._CRS methods by selecting a valid
irq from _PRS possible resources and calling the _SRS method
to set the irq. Somehow this fix is not working on some intel machines,
but makes rump_init() get further than before during probe.
Hi,
I addressed the comments in v3. This is v4.
I was unable to locate documentation for correct STARTUP IPI mode,
but I tested this series on both AMD fam15h and qemu and it boots.
Damien
Now that things are in place, we switch to parallel init.
The key to this change is that the INIT/STARTUP sequence
is done in one step, and all cpus wake up at the same time.
Synchronisation is done via waiting for individual flags stored
in separate memory locations.
---
i386/i386/apic.h| 4
Add workaround for broken systems that advertise 8 bit APIC ids
but only match IPIs on 4 bits of the APIC id.
---
i386/i386/apic.c | 28 +++-
i386/i386/apic.h | 15 ++-
i386/i386/cpu_number.h| 3 +++
i386/i386/cpuboot.S
Fixes ESR==0x8 error on AMD fam15h. Fixed timings.
Cannot locate documentation on correct mode for STARTUP IPI,
but this patch works on AMD hw and qemu.
---
i386/i386/smp.c | 62 +++--
1 file changed, 40 insertions(+), 22 deletions(-)
diff --git a/i386
On 12/22/24 11:35 AM, Samuel Thibault wrote:
> This is quite verbose. Could you check that the attached patch on top of
> it still works?
>
> Samuel
Your patch works and is much more readable.
Thanks, Damien
This allocates a constant space for percpu gdts
and copies the first entry to the nth entry on each cpu,
then patches its own copy of the gdt so it can function
independently.
---
i386/i386/cpuboot.S | 63 ++---
1 file changed, 53 insertions(+), 10 deletions
Add workaround for broken systems that advertise 8 bit APIC ids
but only match IPIs on 4 bits of the APIC id.
---
i386/i386/apic.c | 28 +++-
i386/i386/apic.h | 15 ++-
i386/i386/cpu_number.h| 3 +++
i386/i386/cpuboot.S
Hi,
The first two patches are exactly v2, but I have added two more
that make SMP functional on my AMD fam15h processor.
Thanks,
Damien
Fixes ESR==0x8 error on AMD fam15h. Fixed timings.
---
i386/i386/smp.c | 62 +++--
1 file changed, 40 insertions(+), 22 deletions(-)
diff --git a/i386/i386/smp.c b/i386/i386/smp.c
index befa0510..e3e4cc82 100644
--- a/i386/i386/smp.c
+++ b/i386/i386/smp
Now that things are in place, we switch to parallel init.
The key to this change is that the INIT/STARTUP sequence
is done in one step, and all cpus wake up at the same time.
Synchronisation is done to complete each cpu setup individually.
---
i386/i386/mp_desc.c | 51 +++--
h
not matching the width of the APIC id. Does anyone know how this works?
Thanks,
Damien
On 12/17/24 11:05 PM, Damien Zammit via Bug reports for the GNU Hurd wrote:
> Now that things are in place, we switch to parallel init.
> The key to this change is that the INIT/STARTUP sequence
> is do
Previously, we were ignoring cpus that were not enabled
but online-capable.
---
i386/i386at/acpi_parse_apic.c | 2 +-
i386/i386at/acpi_parse_apic.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/i386/i386at/acpi_parse_apic.c b/i386/i386at/acpi_parse_apic.c
index 24470426..ae
Now that things are in place, we switch to parallel init.
The key to this change is that the INIT/STARTUP sequence
is done in one step, and all cpus wake up at the same time.
Synchronisation is done to complete each cpu setup individually.
---
i386/i386/mp_desc.c | 51 +++--
This allocates a constant space for percpu gdts
and copies the first entry to the nth entry on each cpu,
then patches its own copy of the gdt so it can function
independently.
---
i386/i386/cpuboot.S | 63 ++---
1 file changed, 53 insertions(+), 10 deletions
Hi,
These two patches complete smp parallel init by preserving early gs access,
and makes the cpus all wake concurrently. Care has been taken so memory
is not trampled on by other cpus during startup.
Thanks,
Damien
This is basically a no-op but ensures we are doing smp
bringup correctly.
---
i386/i386/mp_desc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/i386/i386/mp_desc.c b/i386/i386/mp_desc.c
index 7595eb1e..295fccc7 100644
--- a/i386/i386/mp_desc.c
+++ b/i386/i386/mp_desc.c
@@
If this is not done, the spl code is called by kmsg_putchar
on APs during printing of bringup debug, causing the only
unnecessary early access of GS.
---
i386/i386/mp_desc.c | 3 ++-
i386/i386at/model_dep.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/i386/i386/mp_de
Now that things are in place, we switch to parallel init.
The key to this change is that the INIT/STARTUP sequence
is done in one step, and all cpus wake up at the same time.
Synchronisation is done to complete each cpu setup individually.
---
i386/i386/mp_desc.c | 51 +++--
Since the gdt for apboot is located at a shared location
in memory, we cannot patch the gdt values per cpu during
parallel smp init, or havoc entails.
---
i386/i386/cpuboot.S | 75 +
i386/i386/mp_desc.c | 6 ++--
2 files changed, 11 insertions(+), 70 de
The number is actually a mask bit per cpu.
---
i386/i386/apic.c | 2 +-
i386/i386/apic.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/i386/i386/apic.c b/i386/i386/apic.c
index 7ec8c49b..e0941c6a 100644
--- a/i386/i386/apic.c
+++ b/i386/i386/apic.c
@@ -337,7 +337,7 @@ lapi
Hi,
I figured out what was broken in my previous attempt at this:
The APs were calling splhigh() in the debug printing code,
which caused an unnecessary GS segment access.
This should now support all x86 cpus with any core counts.
Every 8 processors are grouped into the same IPI group,
so on oc
The condition was intended for non-BSP processors to
disable timer, but apic_id != 0 means it could affect BSP
if its apic id is non-zero. Fixes this bug.
---
i386/i386/apic.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/i386/i386/apic.c b/i386/i386/apic.c
index 41b335
Since modern x86 cpus only support 4 bits of destination field
in ICR, we could only address up to 16 processors, assuming
their physical APIC ID was < 0x10. Some processors eg AMD fam15h
have physical apic ids starting at 0x10 but only support 4 bits.
So these lapics are unaddressable using physi
Since we just set up the gs segment, we can use
CPU_NUMBER instead of CPU_NUMBER_NO_STACK.
---
i386/i386/cpuboot.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/i386/i386/cpuboot.S b/i386/i386/cpuboot.S
index 9ac86845..09855864 100644
--- a/i386/i386/cpuboot.S
+++ b/i386/i386
Prepare for smp parallel init where we want to call these
two functions on different cpus at different times.
---
i386/i386/mp_desc.c | 1 +
i386/i386at/model_dep.c | 1 +
i386/intel/pmap.c | 2 --
3 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/i386/i386/mp_desc.c b/i386
Hi,
This patchset consists of 6 patches that have been tested **not** to break
both smp and non-smp systems, but get us closer to having smp working fully.
The rationale for going with parallel init for smp is that APICs are not
individually addressible for more than 8 cpus (in logical mode) or
To make selectors work reliably, we need to
write zero to it before writing its final value.
---
i386/i386/cpuboot.S | 2 ++
1 file changed, 2 insertions(+)
diff --git a/i386/i386/cpuboot.S b/i386/i386/cpuboot.S
index 09855864..f549a2bc 100644
--- a/i386/i386/cpuboot.S
+++ b/i386/i386/cpuboot.S
@
The current segmentation already adds -KERNELBASE.
But only when accessing the memory.
Don't forget to reload gdt.
---
i386/i386/cpuboot.S | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/i386/i386/cpuboot.S b/i386/i386/cpuboot.S
index 7e6c4770..9ac86845 100644
--- a
Non-master processors cannot have cpu_number() == 0.
The synchronisation fails hard if the cpu number is wrong.
Alert the condition if this is the case.
(On AMD fam15h, this assert currently fails, but I haven't
been able to boot it with smp yet either).
---
i386/i386/mp_desc.c | 3 +++
1 file c
Fallthrough was incorrectly using fxsave() instead of
xsave() or xsaveopt().
TESTED: on AMD fam15h: no longer throws "No coprocessor" exception.
---
i386/i386/fpu.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/i386/i386/fpu.c b/i386/i386/fpu.c
index 3d146
Fallthrough was incorrectly using fxsave() instead of
xsave() or xsaveopt().
TESTED: on AMD fam15h: no longer throws "No coprocessor" exception.
---
i386/i386/fpu.c | 4
1 file changed, 4 insertions(+)
diff --git a/i386/i386/fpu.c b/i386/i386/fpu.c
index 3d146f71..203de993 100644
--- a/i386
parallelism on Hurd in a controlled way.
---
debian/hurd.install.in | 1 +
debian/rules | 2 +-
sutils/Makefile| 2 +-
sutils/smp.c | 80 ++
4 files changed, 83 insertions(+), 2 deletions(-)
create mode 100644 sutils/smp.c
parallelism on Hurd in a controlled way.
---
debian/hurd.install.in | 1 +
debian/rules | 2 +-
sutils/Makefile| 2 +-
sutils/smp.c | 71 ++
4 files changed, 74 insertions(+), 2 deletions(-)
create mode 100644 sutils/smp.c
---
acpi/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/acpi/Makefile b/acpi/Makefile
index ceccb351e..6e91e980f 100644
--- a/acpi/Makefile
+++ b/acpi/Makefile
@@ -27,7 +27,7 @@ SRCS = main.c netfs_impl.c acpi.c \
MIGSRCS=
OBJS = $(patsub
When an irq handler dies, we are decrementing the n_unacked count
and calling __enable_irq() the right number of times, but we need
to decrement the total interrupt count by the number that were lost
and also clear that number.
This fixes a hang when a shared irq handler quits and leaves some
unac
this problem in a future. > > If you'd
like you could help us debug this minor issue. I would like to help :). > > I
think it's $hurd-src/hurd/shutdown.c I didn't find $hurd-src/hurd/shutdown.c,
but instead I found $hurd-src/shutdown/shutdown.c; is this shutdown server
Hi,
This addresses the bug that shutdown does not work correctly since ACPI server
was introduced:
Firstly, the acpi server needs to not exit when notified of shutdown, so that
it can serve the S_acpi_sleep() RPC to halt the machine.
Second, a workaround for netfs not running on libmachdev path;
Since libmachdev cannot currently serve netfs as well as trivfs on a
path, we need to allow connecting to the bootstrapped acpi server
to shut down the machine.
---
shutdown/shutdown.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/shutdown/shutdown.c b
The acpi server needs to survive after the shutdown notification,
so it can serve S_acpi_sleep() RPC to actually shut down the machine.
Therefore we need to keep the server alive and not respond to the
trivfs goaway request.
---
acpi/main.c| 4 ++--
libmachdev/machdev.h | 1
Hi,
On 11/5/24 6:16 PM, Yuqian Yang wrote:
> In conclusion, there is no way to do things like using a pointer to pass
> data pointed by it in Mach. I can understand this is rooted in Mach
> design. This does create problems of mimicking API in Linux to reuse a
> lot of high-level things. At least
o we solve the ordering
problem of
the *_length parameter?
My attempt at coding this is currently here [1] and [2].
Damien
[1] https://git.zammit.org/hurd-sv.git/commit/?h=drm-server
[2] https://git.zammit.org/hurd-sv.git/commit/?h=drm-server-ioctl
Flavio Cruz writes:
> This fixes an incompatible-pointer-types error on GCC14.
Applied. We do test on GCC14 but alas not on the Hurd, nice catch!
/Simon
signature.asc
Description: PGP signature
Hi,
On Fri, Dec 29, 2023 at 02:51:31PM +0100, Luca Dariz wrote:
> > > +$ gdb gnuamch
> >
> > Typo ;)
>
> What would be a better command? This is actually how I start gdb from the
> build directory,
You probably start gnumach though, and not gnuamch?
Michael
Hello,
NIIBE Yutaka, le jeu. 25 mai 2023 09:21:43 +0900, a ecrit:
> I wonder if it works for GNU Hurd system:
>
> diff --git a/configure.ac b/configure.ac
> index d0fa6f2..ca7731c 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -590,7 +590,7 @@ if test x"$g
I have committed this patch here:
https://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=afe3168ee9f15783c71653bee0ec97536daaf217
Btw, please add NEWS entries next time. I added the following,
corrections welcome:
https://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=976de5463bedcd8060c7
Hi. I have commited this now:
https://git.savannah.gnu.org/cgit/inetutils.git/commit/?id=0b35abbd7a5d074c7e245a49585b2de036d4dec7
/Simon
signature.asc
Description: PGP signature
Samuel Thibault writes:
> Hello,
>
> Simon Josefsson, le mer. 28 sept. 2022 13:46:52 +0200, a ecrit:
>> have you signed copyright assignment papers for InetUtils,
>
> I didn't know there was copyright assignment for InetUtils :/
>
> I now have sent the form to the clerk, but really, such process
Both your patches looks good to me -- however, have you signed copyright
assignment papers for InetUtils, or how are these contributed?
Generally I'm not sure how useful it is to require copyright assignment
for smaller InetUtils contributions -- the majority of the code is not
copyright by FSF any
I think it is cleaner like this:
root@kibar:~/procps-3.3.16# diff -u ../orig/procps-3.3.16/pgrep.c pgrep.c
--- ../orig/procps-3.3.16/pgrep.c 2020-02-06 06:04:02.0 -0500
+++ pgrep.c 2021-02-02 12:24:49.0 -0500
@@ -494,10 +494,15 @@
pid_t saved_pid = 0;
I am going on a slightly different approach.
I did:
#apt-get build-dep vte2.91
#apt-get source vte2.91
vte2.91, come with an example called app...
modified src/app/meson.build to add: -g -O0 to cflags
meson _build
ninja -C _build
gdb _build/src/app/vte-2.91
break 1394
p m
Paul Dufresne writes:
> I was investigating a bit, under Ubuntu, but I suspect this is quite similar
> in Debian... will verify a bit more tomorrow.
>
Looks like you're on the right track! Keep going!
> paul@jacko:/etc/menu$ dpkg -L twm
>
> paul@jacko:/etc/X11/twm$ cat /usr/bin/xfce4-terminal
;
> Samuel
Indeed, after a reinstallation of the same previous cdrom.iso file I get:
paul@debian:~$ showtrans /dev/urandom
/hurd/symlink random
I don't know why.
I have xterm (and lxterm) working in Xorg now, but I did not figure out why...
yet.
First, trying to do a program with fdwalk, I have come to the conclusion fdwalk
does not exist in Debian sid.
My program:
paul@debian:~$ cat fdwalk.c
#include
#include
#include
struct rlimit rl;
I love Samuel's positivity. He's probably one of the most positive people I
know.
I read recently that 80% of your success is mental
and only 20% is technical skill. For example Gregor Mendel failed his
teachers'
exams three times, but he still spent 10 years cross breeding 21,000 plants to
.. at least that what the installer made me think):
Last login: Tue Jan 26 12:22:38 2021 from 10.0.2.2
paul@debian:~$ cat /etc/apt/sources.list
#
# deb cdrom:[Debian GNU/Hurd sid _Sid_ - Unofficial hurd-i386 NETINST
20210126-12:41]/ sid main
# deb cdrom:[Debian GNU/Hurd sid _Sid_ - Unofficia
of known
hosts.
paul@localhost's password:
GNU debian 0.9 GNU-Mach 1.8+git20201129-486/Hurd-0.9 i686-AT386
The programs included with the Debian GNU/Hurd system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/c
Le dim., 24 janv. 2021 08:21:07 -0500 Samuel Thibault
écrit
> Paul Dufresne, le dim. 24 janv. 2021 07:18:35 -0500, a ecrit:
> >> I now realized that I was confused by the existence of both:
> >>
> >> [1]https://cdimage.debian.org/cdimage/ports/c
n libjson-c3 (>= 0.10) however libjson-c3 is not installed
rsyslog depends on liblogging-stdlog0 (>= 1.0.2) however the package is not
installed
rsyslog depends on liblognorm2 (>=1.1.2) however the package is not installed
That was with
https://d-i.debian.org/daily-images/hurd-i386/daily/netbo
I vote we give Samuel commit access! His genius deserves to be
recognized. All in favor, say aye!
--
Joshua Branson
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, a
Forget about this, it was working with settrans b/c this command replaces the ol
d translator. I was testing the old code when using fsysopts... :(
Anyway, here's the patch to fix that bug.
From: Joan Lledó
A misuse of strtol() caused wrong parameters to be interpreted as '0'
* pci-arbiter/options.c:
* New function parse_number() to handle wrong input
* Call parse_number() from all places where strtol was being called
---
pci-arbiter/options.c | 58
Hello,
I'm blocked trying to solve a bug I found in the option parsing of the
arbiter, at:
http://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/pci-arbiter/options.c#n135
strtol() returns 0 if it wasn't able to convert the input, for instance,
-d jj will set h->curset->domain t
From: Joan Lledó
Shortcut for -d, -b, -s and -f
Usage: --device [:]:.
E.G. --device 00:05.0 is shortcut for -d 0 -b 0 -s 5 -f 0
* pci-arbiter/options.c: Implement --slot option
* pci-arbiter/options.h: Add --slot to options list
---
pci-arbiter/options.c | 57 +++
From: Joan Lledó
Rename some CLI options in order to add the new -D --device arg.
Replace -s by -c for subclasses.
Replace -D by -d for domains.
Domains are optional from now on, default to 0.
Replace -d by -s for devices.
The formerly called "devices" are now called "slots", and
Hi,
El 15/2/20 a les 15:02, Samuel Thibault ha escrit:
> Why a capital b? It's be more coherent to have -d -b -s -f all
> small-caps.
>
Because of this notice in --help:
"More than one permission scope may be specified. Uppercase options
create a new permission scope if the current one already
From: Joan Lledó
Shortcut for -d, -B, -s and -f
Usage: --device [:]:.
E.G. --device 00:05.0 is shortcut for -d 0 -B 0 -s 5 -f 0
* pci-arbiter/options.c: Implement --slot option
* pci-arbiter/options.h: Add --slot to options list
---
pci-arbiter/options.c | 60 +++
From: Joan Lledó
Rename some CLI options in order to add the new -d --device arg.
Replace -s by -c for subclasses.
Replace -D by -d for domains.
Domains are optional from now on, default to 0.
Replace -b by -B for buses.
Bus now creates a new permission scope if the current one
Hello Hurd,
I made some changes in the options parser to add a new --device option, as a
shortcut for current -D -b -d -f options.
I also renamed some options in order to free -D and --device to use it for this
purpose. From now on, the formerly called "devices" are now called &q
Hello Hurd,
I'm glad to say that our patches for both picutils and libpciaccess are
now upstream.
El 10/11/19 a les 2:44, Samuel Thibault ha escrit:
> Joan Lledó, le sam. 09 nov. 2019 17:36:19 +0100, a ecrit:
>> I was also wondering if after your changes, libpciaccess would sup
Hi,
El 1/12/19 a les 1:10, Damien Zammit ha escrit:
> libpciaccess 0.16-1+hurd.1 is still broken on rumpdisk. Somehow the 2
> applied patches
> don't allow probing of AHCI to occur in rump_init().
> I've packaged rump libs into a debian package following Robert Millan
Hello Hurd,
I updated the pciutils patch I wrote in 2017. The new version is attached.
This is the same patch with minor changes:
- Makefile updated to be applied on newer sources.
- hurd_detect(): Use stat() instead of lstat() to work with symbolic links.
- enum_devices(): Call closedir() on
1 - 100 of 147 matches
Mail list logo