| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Some systems have /bin/sh pointing to dash, which is even more stressful
for users when running in an emergency. Better first try bash. Also try
dash too in case /bin/sh is hosed.
|
|
|
|
| |
This helps debugging boot issues.
|
| |
|
|
|
|
|
| |
emergency means we want to get a shell as quickly as possible, so we do
not want any daemon at all.
|
|
|
|
| |
It has not been the kernel file name any more for a long time already.
|
| |
|
|
|
|
|
|
| |
Some systems have /bin/sh pointing to dash, which is even more stressful
for users when running in an emergency. Better first try bash. Also try
dash too in case /bin/sh is hosed.
|
|
|
|
| |
So that people can install just dash.
|
|
|
|
| |
for va_start etc.
|
|
|
|
| |
Message-ID: <Za3wnF34kVU0r1TS@jupiter.tail36e24.ts.net>
|
|
|
|
|
|
|
|
| |
* doc/hurd.texi (Special Files): added a reference to the zero store.
* doc/hurd.texi (Translators): added a sentence about /dev/random.
* doc/hurd.texi (Invoking 'mount'): added a short explanation.
* doc/hurd.texi (Trivfs Callbacks): added @code{FSTYPE_MISC}.
Message-ID: <20230921164822.9227-5-jbranso@dismail.de>
|
|
|
|
|
| |
* doc/hurd.texi (FAT FS): new section.
Message-ID: <20230921164822.9227-4-jbranso@dismail.de>
|
|
|
|
|
| |
* doc/hurd.texi (ISO-9960): I added in a short explanation.
Message-ID: <20230921164822.9227-3-jbranso@dismail.de>
|
|
|
|
|
| |
* doc/hurd.texi (Linux Extended 2 FS): added a short description.
Message-ID: <20230921164822.9227-2-jbranso@dismail.de>
|
|
|
|
|
|
|
| |
* doc/hurd.texi (Repairing Filesystems): described fixing filesystem
corruption.
* doc/hurd.texi (Shutdown): added the hurd specific halt-hurd command.
Message-ID: <20230921164822.9227-1-jbranso@dismail.de>
|
|
|
|
| |
Message-ID: <ZZBGYmkYNwpoamBm@jupiter.tail36e24.ts.net>
|
|
|
|
| |
Message-ID: <20231229212105.858759-11-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-10-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-9-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-8-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-7-flaviocruz@gmail.com>
|
|
|
|
|
| |
This makes GCC happy.
Message-ID: <20231229212105.858759-6-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-4-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-3-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-2-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229212105.858759-1-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229161211.312389-3-flaviocruz@gmail.com>
|
|
|
|
| |
Message-ID: <20231229161211.312389-2-flaviocruz@gmail.com>
|
|
|
|
|
|
| |
fix -Werror=enum-int-mismatch warnings
Message-ID: <20231229161211.312389-1-flaviocruz@gmail.com>
|
|
|
|
|
|
|
| |
-Werror=enum-int-mismatch warnings
MiG expects those to return kern_return_t.
Message-ID: <ZXqbbXpVqQAwd2qv@jupiter.tail36e24.ts.net>
|
| |
|
|
|
|
| |
This reverts commit 33c30b4ff76ca22bdedce4aa41d05736a546d86b.
|
|
|
|
| |
Message-ID: <20231124213041.952886-3-flaviocruz@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The translator received a null `netif_list` during initialization, this
caused a few bugs.
When started without parameters, the translator didn't add any new
interface to `netif_list`, and that broke any subsequent fsysopts over
the translator, as the stack was being initialized again instead of
being reconfigured.
DHCP was broken because the translator is usually installed without
parameters, which are supposed to be added by the DHCP client through
fsysopts.
The absence of an allocated `netif_list` also prevented configuring a
loopback interface.
After these changes, starting the translator always allocates one
interface and configures it as loopback.
Message-ID: <20231202101401.11542-2-jlledom@mailfence.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quiescence support in port-deref-deferred.c assumes that all threads will
sooner or later go through a quiescent state (because it finished processing
a message). But that is not true: proc doesn't set a thread timeout, and
thus some threads can stay indefinitely stuck in receiving messages. And
thus the deferred dereferencing used by ports_destroy_right never gets
achieved. This accumulation can be seen by running:
while true ; do echo $(echo -n $(echo a)) > /dev/null ; done
while running vminfo 4 | wc -l in parallel.
Making threads get out of mach_msg at least periodically allows
unstucking quiescence generations.
|
|
|
|
|
| |
flip_generations needs to make sure it is not throwing away a list of
objects to be released.
|
| |
|
|
|
|
|
|
| |
works on x86_64.
Message-ID: <ZVlHm2xuVaS8SItY@jupiter.tail36e24.ts.net>
|
| |
|
|
|
|
|
| |
INTR_INTERFACE needs to be always called for glibc to redirect mach_msg
into _hurd_intr_rpc_mach_msg.
|
|
|
|
|
|
| |
We don't really have plans to have anything else than "AT386" there, and
other OSes do not include it, so it brings us more harm than good to
include it.
|
| |
|
|
|
|
|
|
| |
On MACH_SEND_TIMED_OUT we defer sending the message to just-created
thread, we allocate a copy of the message to that end. We need to free
that once the message is indeed sent.
|
|
|
|
| |
This was added by 7487dda5f
|
| |
|
|
|
|
|
| |
It was never set, and re-connecting a socket to another address would
try to deref the port, thus crashing.
|
|
|
|
|
| |
When e.g. looking up a socket with O_DIRECTORY, we should return ENOTDIR
rather than EACCESS.
|
|
|
|
|
|
| |
This reverts commit 8b5b59c704e9edbb0784697ada1df9112fc3e18b.
This actually breaks various posix behaviors.
|
|
|
|
|
| |
When e.g. looking up a socket with O_DIRECTORY, we should return ENOTDIR
rather than EACCESS.
|