oader; or
written
in userconf(4) interactive session.
userconf(4), M.I., is the correct place to add these. And the majority
of the work has already been done to allow such extensions (see
https://github.com/tlaronde/BeSiDe for the code).
--
Thierry Laronde
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
On Mon, Dec 11, 2023 at 01:00:38PM +, Robert Swindells wrote:
>
> tlaro...@kergis.com wrote:
> > In Mesa code implementations for futex_wake() and futex_wait() are
> > provided for Linux, Windows, FreeBSD and OpenBSD.
> >
> > There is a __futex(2) syscall in NetBSD, used only for now, if I'm
In Mesa code implementations for futex_wake() and futex_wait() are
provided for Linux, Windows, FreeBSD and OpenBSD.
There is a __futex(2) syscall in NetBSD, used only for now, if I'm not
mistaken, to implement Linux compat.
Is it OK to use for NetBSD "native" code since it is not "advertised"
On Thu, Dec 07, 2023 at 03:36:41PM +0100, Reinoud Zandijk wrote:
> Hi,
>
> On Wed, Dec 06, 2023 at 09:52:54AM +0100, Reinoud Zandijk wrote:
> > On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> > > On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > > > my old
When initializing drmkms, the kernel prints bogus things like:
[ 4.193896] Zone kernel: Available graphics memory: 9007199254113272 KiB
[ 4.193896] Zone dma32: Available graphics memory: 2097152 KiB
The reason is to be found in
sys/external/bsd/drm2/include/linux/mm.h
which fills a
ing another path.
Or, instead of trying artificial intelligence, trying natural one.
[1] This is the userconf(4) I have modified:
https://github.com/tlaronde/netbsd-src/tree/tsjl
--
Thierry Laronde
http://www.kergis.com/
http://kertex.kergis.com/
Ke
Code is at:
https://github.com/tlaronde/netbsd-src/tree/tsjl
in 3 commits:
- config(1): it accepts now also context neutral "userconf"
directives. These add the double quoted string given as
argument to the userconf_kconf[] array. This array is
i
With some delay, I'm finishing modification of cons/userconf/config
(having implemented more in userconf than initially projected):
* aliases hence local malloc/free;
* executable aliases (macros without parameters but multiple
lines possible meaning that one can
For at least userconf, are added means to define a char mapping for
the console during startup (the userconf char to char mapping command
will be "kmap", key 'k'; and a series of instructions, assembled by
config(1), will be proceeded during userconf_init() before
userconf_bootinfo(), allowing one
FWIW, various things I have modified can be seen here:
https://github.com/tlaronde/netbsd-src/tree/tsjl
The userconf version present at the moment on the published branch, was
my first attempt (patterns introduced by slashes---working but not
solving the problem about drmkms).
There are other
On Sun, Nov 05, 2023 at 11:17:02AM +, RVP wrote:
>
> Oh, I like the idea (I've always wanted a mechanism to list drivers
> etc. using patterns); it's just the syntax that sticks in the craw.
> Too many meta-chars. there.
>
> OTOH, `cmd -p xyz* *abc' doesn't need much thought. And, aliases
>
On Sun, Nov 05, 2023 at 01:53:31PM +0200, Staffan Thomén wrote:
> One thing I'd like to point out is that I often find I don't have the
> right keyboard layout or am restricted in some way in from typing in the
> bootloader (glitchy serial connection or really fast repeating keyboard
> or
On Sat, Nov 04, 2023 at 11:59:00AM +0100, Martin Husemann wrote:
> On Sat, Nov 04, 2023 at 11:25:01AM +0100, tlaro...@kergis.com wrote:
> > I think that my second proposal is the simplest, allowing not breaking
> > existing and introducing extensions without much typing.
>
> This whole thing
On Sat, Nov 04, 2023 at 09:30:53AM +, RVP wrote:
> On Sat, 4 Nov 2023, tlaro...@kergis.com wrote:
>
> > > > No...: this is a break of existing. Trailing `*' selects STARred devices
> > > > (I'm not the inventor of this). So `*' can not be used as a joker ;-)
> > > >
> > >
> > > You can
On Sat, Nov 04, 2023 at 08:31:09AM +, RVP wrote:
> On Sat, 4 Nov 2023, tlaro...@kergis.com wrote:
>
> > > 1) Allowing shell-like patterns (not hard to implement):
> > >
> > > uc> disable drm* # all starting with `drm'
> >
> > No...: this is a break of existing. Trailing `*' selects STARred
On Sat, Nov 04, 2023 at 08:20:43AM +, Michael van Elst wrote:
> tlaro...@kergis.com writes:
>
> >disable {drmkms} # NEW: disable devices belonging to group "drmkms"
>
> Almost noone would need to turn off all drmkms drivers. What you may
> want to control is that a GPU isn't used as a
On Sat, Nov 04, 2023 at 07:41:19AM +, RVP wrote:
> On Sat, 4 Nov 2023, tlaro...@kergis.com wrote:
>
> > - 1) No change to the general form of current syntax;
> >
> > - 2) Selection can be as presently: by number (index in cfdata), by
> > name (driver name), but also (NEW) by pattern: a
Revised proposition:
- 1) No change to the general form of current syntax;
- 2) Selection can be as presently: by number (index in cfdata), by
name (driver name), but also (NEW) by pattern: a pattern is
between slashes, it is a fix substring, that can be optionnally
anchored at the beginning
On Fri, Nov 03, 2023 at 09:41:14AM +0100, Martin Husemann wrote:
> On Thu, Nov 02, 2023 at 05:32:20PM +0100, tlaro...@kergis.com wrote:
> > On Thu, Nov 02, 2023 at 05:05:53PM +0100, Martin Husemann wrote:
> [..]
> > > Something like:
> > >
> > > uc> drm off
> > >
> > > and then have the drm
On Thu, Nov 02, 2023 at 04:12:43PM +, Robert Swindells wrote:
>
> tlaro...@kergis.com wrote:
> > As stated in a message before, disabling, via userconf(4), all the
> > drmkms drivers can not rely on a pattern matching since, for historical
> > reasons (several versions of DRM), the namespace
On Thu, Nov 02, 2023 at 05:05:53PM +0100, Martin Husemann wrote:
> I would prefer to have a special new command that does all the magic
> internaly, and don't waste code and complexity on pattern matching
> and generalizations.
>
> Something like:
>
> uc> drm off
>
> and then have the drm
On Thu, Nov 02, 2023 at 06:59:50PM +0300, Valery Ushakov wrote:
> On Thu, Nov 02, 2023 at 16:29:42 +0100, tlaro...@kergis.com wrote:
>
> > You will find attached the man page in order to be able to comment
> > about the proposed new syntax---supplementary syntax: it does not
> > replace the
As stated in a message before, disabling, via userconf(4), all the
drmkms drivers can not rely on a pattern matching since, for historical
reasons (several versions of DRM), the namespace of the drivers is not
"ruled".
So I want to add a "group" member to the cfdata structure, with
modifications
[Note: no need to Cc me anymore. Culprit (me...) being found; and
problem solved.]
I have added the translated man pages in xsrc/local/man/man[37] and a
UPDATING file at the root of xsrc.
Can be pulled from:
https://github.com/tlaronde/xsrc
commit b24a2c96577617a6297efde04ce5628985291eb4 (HEAD
On Thu, Oct 19, 2023 at 10:41:53AM -0400, Mouse wrote:
> >>> [...DV_DRMKMS...userconf...]
> >> [...devices in multiple classes...maybe use a separate namespace,
> >> used by only config(1) and userconf?...]
> > This is precisely why I ask for comment ;-)
>
> :-)
>
> > I have two requirements:
>
On Thu, Oct 19, 2023 at 09:10:36AM -0400, Mouse wrote:
> > I propose to add a DV_DRMKMS class to sys/device.h:enum_devclass; to
> > augment cfdata with a devclass member [...]
>
> > Comments?
>
> This is not intended as criticism; I am just trying to examine all
> sides of this question.
>
>
[Please do CC me on reply since I _am_ subscribed to the list but don't
get the messages...]
Note: code can be seen on https://github.com/tlaronde/src .
I have implemented "patterns" in sys/kern/subr_userconf.c, in order to
allow to manipulate (change, disable, enable, find, list
moved long ago (now superseded by
> > viadrmums, provided in drm2/ ---drmkms--- part).
> >
> > Patch can be retrieved from https://github.com/tlaronde/src
>
> Thanks, I took the opportunity to update the whole man page. Didn't
> realize until now that our drm(4) man page was
On Wed, Oct 18, 2023 at 10:35:26AM +, Taylor R Campbell wrote:
>
> > There is no man page for drmkms (the kernel part), but there are man
> > pages in the X sources, in the rst format
> > (external/mit/libdrm/dist/man/drm-kms.7.rst) with a bunch of related
> > resources that provide a view of
On Tue, Oct 17, 2023 at 02:33:43PM +0100, Robert Swindells wrote:
>
> tlaro...@kergis.com wrote:
> > So to clarify: I'm proposing to convert the rst doc pages to man
> > pages (with for example the utility I cite), and to add the man pages,
> > in man format, to the sources (in order for the
and the Linux
kernel implementation is still changing frequently and heavily (the
drm2/ sources are already significantly behind the Linux sources with
not trivial changes; it's, for me, a lost race...).
On Tue, Oct 17, 2023 at 02:39:58PM +0200, tlaronde wrote:
> I have modified drm.4 to st
I have modified drm.4 to state that the drivers are obsolete and
to suppress a mention of viadrm that was removed long ago (now superseded by
viadrmums, provided in drm2/ ---drmkms--- part).
Patch can be retrieved from https://github.com/tlaronde/src
There is no man page for drmkms (the kernel
d for long
> enough they are probably named in existing boot.cfg files, so changing
> them might is likely to break people's bootloaders.
>
> Not hard to imagine creating a new way to tag drivers that can be
> referenced by userconf so that renaming isn't necessary.
>
If the driv
ll continue with
documentation / comments and end with future directions (for me).
Note: I have finally taken again an Internet optical fiber connection
(after infelicities with a previous provider), so I have been able to
pull and push on a fork that is here:
https://github.com/tlaronde/s
ll continue with
documentation / comments and end with future directions (for me).
Note: I have finally taken again an Internet optical fiber connection
(after infelicities with a previous provider), so I have been able to
pull and push on a fork that is here:
https://github.com/tlaronde/s
FWIW---and this is probably already known by must---I found that:
"The RISC-V reader: an open architecture atlas", by David Patterson
and Andrew Waterman, Strawberry Canyon LLC, ISBN 9780999249116
to be a great help to "put things together"---I mean it is a short book
(a hundred of pages
Le Sun, May 07, 2023 at 06:14:35PM +0200, Martin Husemann a écrit :
> On Sun, May 07, 2023 at 04:56:33PM +0200, tlaro...@polynum.com wrote:
> > I'm a bit reluctant to put all the platform lists in copy, since this
> > is typically generic: it deals with the monitor capacities, updating
> > the
Le Sun, May 07, 2023 at 09:40:56AM -0400, Thor Lancelot Simon a écrit :
> On Sat, May 06, 2023 at 12:12:54PM +0200, tlaro...@polynum.com wrote:
> >
> > How to submit patches without wasting time? (mine included)
>
> It might be that you get quicker response on one of the mailing lists
> for
Since there are some infelicities in the handling of the resolution of
the framebuffer (10.0_BETA doesn't behave as 9.3), I have started to
review the code, starting from the end: the monitor.
The monitor being the reference, I have replaced the modelines, derived
from XFree86, with the
Le Sat, May 06, 2023 at 02:13:58PM +0200, Martin Husemann a écrit :
> On Sat, May 06, 2023 at 12:12:54PM +0200, tlaro...@polynum.com wrote:
> > Hello,
> >
> > On Mon, 27 Feb 2023 12:33:32 +0100, I sent to this list a collection of
> > patches for sys/dev/videomode/, starting by updating the DMT
Hello,
On Mon, 27 Feb 2023 12:33:32 +0100, I sent to this list a collection of
patches for sys/dev/videomode/, starting by updating the DMT to the
latest, and planning to review further the code (sending patches
when I have achieved a complete step in the course, because I'm having
a hard time
Since there are some infelicities in the handling of the resolution of
the framebuffer (10.0_BETA doesn't behave as 9.3), I have started to
review the code, starting from the end: the monitor.
The monitor being the reference, I have replaced the modelines, derived
from XFree86, with the
Le Tue, Feb 21, 2023 at 10:00:10AM -0400, Jared McNeill a écrit :
> Yeah sorry you can?t just not exit boot services and boot the OS. UEFI code
> has certain expectations around the execution environment (MMU on, 1:1 PA to
> VA for example) that starting the kernel is going to interfere with.
Since the choice of the resolution (with 10.0 BETA) is not optimal, I
have started to review sys/dev/videomode in order to fix the
preferences.
The first step was to update the timings.
Since, with whatever choice for the resolution, a monitor will not do
what it is not able to do, I replaced
Le Sun, Jan 29, 2023 at 05:23:00PM +, Taylor R Campbell a écrit :
> > Date: Sun, 29 Jan 2023 16:44:08 +0100
> > From: tlaro...@polynum.com
> >
> > I will look (silently) to dev/pci/radeonfb.c to understand better the
> > logics and try to find if there is a way to obtain a better console
> >
Le Sun, Jan 29, 2023 at 03:59:45PM +0100, tlaro...@polynum.com a écrit :
> Le Sun, Jan 29, 2023 at 02:54:39PM +0100, tlaro...@polynum.com a écrit :
> > Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaro...@polynum.com a écrit :
> > >
> > > Context: I'm testing NetBSD 10.0 BETA on an isolated node
Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaro...@polynum.com a écrit :
>
> Context: I'm testing NetBSD 10.0 BETA on an isolated node (not
> production). Only kernel and modules (not userland); and kernel is not
> GENERIC but a special config one matching the previous 9.2 config
> running on the
Le Sun, Jan 29, 2023 at 02:54:39PM +0100, tlaro...@polynum.com a écrit :
> Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaro...@polynum.com a écrit :
> >
> > Context: I'm testing NetBSD 10.0 BETA on an isolated node (not
> > production). Only kernel and modules (not userland); and kernel is not
> >
Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaro...@polynum.com a écrit :
> [Please feel free to redirect me to another list if this is not the
> correct one for kernel beta testing]
>
> Context: I'm testing NetBSD 10.0 BETA on an isolated node (not
> production). Only kernel and modules (not
Le Mon, Jan 23, 2023 at 05:17:29AM +0700, Robert Elz a écrit :
> Date:Sun, 22 Jan 2023 20:27:24 +0100
> From:tlaro...@polynum.com
> Message-ID:
>
>
> | +Zone kernel: Available graphics memory: 9007199254079374 KiB
>
> I see something like that too, but while it
017, 2018, 2019, 2020, 2021, 2022, 2023
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 10.0_BETA (CONFIG) #0: Sun Jan 22 11:01:04 CET 2023
tlaronde@cauchy.polynum.loca
Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaro...@polynum.com a écrit :
> [...]
>
> The main difference is about the framebuffer: previous kernel version
> picked the correct mode. NetBSD 10.0 does not and use "entry level"
> mode 640x480x67, resulting streched fat big characters; message:
>
>
[Please feel free to redirect me to another list if this is not the
correct one for kernel beta testing]
Context: I'm testing NetBSD 10.0 BETA on an isolated node (not
production). Only kernel and modules (not userland); and kernel is not
GENERIC but a special config one matching the previous 9.2
Hello,
I have experienced a USB failure with an excessive amount of file cache,
while the mounted filesystems shouldn't have this lot of blocks in
cache: this was likely due to a rsync(1) failure on an USB connected
disk. The USB was detached ("file system full") while rsync(1) was
operating but
I don't know if this is for tech-kern or tech-userlevel (perhaps the
two).
I just read today, on the devel UEFI edk2 devel list, from patches for
ext4, a comment on the problem of the encoding of dir entries.
The problem is that, generally in fs, no encoding is specified: dir
entries are just a
I'm about to start to commit modifications to the UEFI edk2 sources in
order to allow to build and test it under NetBSD.
Why is it related to the kernel? Because UEFI is not limited to one
arch (so it's not linked to some port); because the edk can be
compiled and used on a not UEFI hardware in
Le Mon, Sep 12, 2022 at 09:17:52PM +0200, Edgar Fuß a écrit :
> I'm trying to run NetBSD on a Dell PowerEdge R6515, and the kernel is being
> loaded (PXE or USB) but then the machine hangs hard.
>
> What's the way to debug a kernel that hangs so early that you can't printf
> or drop into ddb? I
FWIW, I have put there notes about the installation, booting and dual
booting of NetBSD on an OVH baremetal server:
https://notes.kergis.com/netbsd_on_OVH_baremetal.html
The part that could be of interest to kernel developers is at the end:
what I found handy or could be handy in trying to get
Le Sun, Aug 21, 2022 at 03:25:36PM +, Emmanuel Dreyfus a écrit :
> On Sun, Aug 21, 2022 at 02:16:58PM +0200, tlaro...@polynum.com wrote:
> > Addition (asked by Taylor R Campbell): a current GENERIC boots only
> > with i915drmkms disabled.
> >
> > With the framebuffer stuff enabled, it does
Addition (asked by Taylor R Campbell): a current GENERIC boots only
with i915drmkms disabled.
With the framebuffer stuff enabled, it does not boot, and does not even
panic and reboot. It freezes somewhere. The same as the 9.x series.
Le Sat, Aug 20, 2022 at 09:03:52PM +0200, tlaro...@polynum.com
A final point:
Context: I rent a baremetal server (OVH) that has an Intel Xeon
quadcore, IvyBridge, with 16Gb of RAM, 3 2TB disks, an Intel PRO 1000
ethernet card (but the bandwith is limited to 100Mib). It is an entry
level offer, that I wanted only for an IPv4 address (there is an IPv6
address
Le Thu, Aug 18, 2022 at 04:33:04PM +0200, tlaro...@polynum.com a écrit :
> Context: I rent a baremetal server and try to install NetBSD on it. I
> finally installed a Linux (Debian) and installed NetBSD as a dual boot.
> But NetBSD doesn't come up (in case there was a
> network misconfiguration, I
Hello,
Le Fri, Aug 19, 2022 at 02:36:33PM +0100, David Brownlee a écrit :
> Tangentially...
>
> If it's an issue picking up the root filesystem, you could boot an
> INSTALL type kernel with a built in ramdisk with dhcpcd and sshd
> enabled, and see if you can ssh into the box (I think someone
Context: I rent a baremetal server and try to install NetBSD on it. I
finally installed a Linux (Debian) and installed NetBSD as a dual boot.
But NetBSD doesn't come up (in case there was a
network misconfiguration, I verified that no log, no dmesg was written)
and neither does it crashes and
Le Mon, Mar 21, 2022 at 08:54:43AM -0400, Mouse a écrit :
> >> I've been making very-spare-time progress on building my own
> >> compiler on and off for some years now; perhaps I'll eventually get
> >> somewhere. [...]
> > Have you looked at pcc? http://pcc.ludd.ltu.se/ and in our source
> >
On Sat, Jun 26, 2021 at 06:49:17AM +0200, Martin Husemann wrote:
> Also any reason to use 9.1 instead of 9.2 or 9.2_STABLE?
> (Not that I think it would make a difference for azalia)
Practical reason: I start to update the node I'm doing my main
programing/developing work on and I then, after
On Fri, Jun 25, 2021 at 09:32:40PM +, RVP wrote:
> On Fri, 25 Jun 2021, RVP wrote:
>
> >On Fri, 25 Jun 2021, tlaro...@polynum.com wrote:
> >
> >>But if azalia is not supported anymore because it crashes the
> >>kernel, shouldn't it be removed and not simply be commented out?
> >>
> >
> >I
Hello,
On Fri, Jun 25, 2021 at 08:47:30PM +, RVP wrote:
> On Fri, 25 Jun 2021, tlaro...@polynum.com wrote:
>
> >The new kernel panics at boot time with azalia (it is not crucial since
> >it is a server and I have no use with it but I have added the support
> >since it's here and 7.1.1 has no
Hello,
I was trying to update a server, running a NetBSD 7.1.1 (amd64) to
NetBSD 9.1.
The new kernel panics at boot time with azalia (it is not crucial since
it is a server and I have no use with it but I have added the support
since it's here and 7.1.1 has no problem with it).
It's a
On Fri, Apr 30, 2021 at 06:51:10AM -0500, Jonathan A. Kollasch wrote:
> On Fri, Apr 30, 2021 at 12:56:04PM +0200, tlaro...@polynum.com wrote:
> > There is excellent support, thanks to Reinoud Zandijk, in NetBSD for
> > UDF. And this is cross-system (I use it to share---not distribute: it's
> > not
On Thu, Apr 29, 2021 at 10:06:05PM +0200, Vincent DEFERT wrote:
>
> On 29/04/2021 20:34, Christos Zoulas wrote:
> >Some ext4 features were implemented as part of GSoC 2016 (extents,
> >htrees).
> >I am sure that there are other unimplemented features. What are you looking
> >for?
> >
> >christos
On Fri, Feb 19, 2021 at 01:43:07AM +, David Holland wrote:
> [...]
>
> (9) We need a model for what happens to the unwritten data. Throwing
> it away is clearly wrong (some may recall a furor a couple years ago
> when it was discovered that Linux did this) but retrying and likely
> failing on
Hello,
On Fri, Nov 13, 2020 at 08:42:03AM +0100, Martin Husemann wrote:
> On Fri, Nov 13, 2020 at 07:35:24AM +0100, tlaro...@polynum.com wrote:
> > I tried to recompile a kernel, with 8.2 and with 9.1 and both
> > crash, 9.1 with:
> >
> > unable to execute instruction 0x18 (SMEP)
> >
> > (from
rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 8.0 (CONFIG) #0: Thu Apr 16 18:47:07 CEST 2020
tlaronde@cauchy.polynum.local:/usr/obj/polynum.NODECONF-cauchy.polynum.local_netbsd-8.0-amd64_netbsd-amd64
Hello,
On Sun, Apr 19, 2020 at 08:17:06PM +0200, tlaro...@polynum.com wrote:
> Hello,
>
> On Sun, Apr 19, 2020 at 05:10:37PM +, m...@netbsd.org wrote:
> > On Sun, Apr 19, 2020 at 05:29:40PM +0200, tlaro...@polynum.com wrote:
> > > Hello,
> > >
> > > Mainly in order to be able to test wine,
Hello,
On Sun, Apr 19, 2020 at 05:10:37PM +, m...@netbsd.org wrote:
> On Sun, Apr 19, 2020 at 05:29:40PM +0200, tlaro...@polynum.com wrote:
> > Hello,
> >
> > Mainly in order to be able to test wine, I'm compiling a NetBSD kernel
> > from netbsd-9-0-RELEASE sources on an amd64 (Intel
Hello,
Mainly in order to be able to test wine, I'm compiling a NetBSD kernel
from netbsd-9-0-RELEASE sources on an amd64 (Intel bicore).
My config has very minimal changes from NetBSD 8.* config, the only important
modification being USER_LDT (and I'm not putting option SVS).
When it crashes,
On Mon, Feb 24, 2020 at 05:35:22PM -0500, Mouse wrote:
> > Unless I remember wrong, older C standards explicitly say that the
> > integer 0 can be converted to a pointer, and that will be the NULL
> > pointer, and a NULL pointer cast as an integer shall give the value
> > 0.
>
> The only one I
On Mon, Sep 30, 2019 at 02:23:02PM +0200, Piotr Meyer wrote:
> On Mon, Sep 30, 2019 at 11:01:51AM +0200, tlaro...@polynum.com wrote:
> > On Mon, Sep 30, 2019 at 10:32:40AM +0200, Martin Husemann wrote:
> > > I guess noone would object a metafont2wsfont converter tool.
> > > Look at the true type
On Mon, Sep 30, 2019 at 10:32:40AM +0200, Martin Husemann wrote:
> I guess noone would object a metafont2wsfont converter tool.
> Look at the true type tool Michael mentioned in xsrc/local and do something
> similar for metafont.
I have already planed to re-start with the Hershey fonts, for
On Fri, Sep 27, 2019 at 08:30:40AM +0200, Martin Husemann wrote:
> On Thu, Sep 26, 2019 at 09:40:22PM +0200, tlaro...@polynum.com wrote:
> > If the vulnerabilities can only be exploited by running Linux binaries,
> > IMHO, the point is moot: the ones that don't run Linux binaries are not
> >
On Thu, Sep 26, 2019 at 10:17:51AM +0200, Maxime Villard wrote:
> I recently made a big set of changes to fix many bugs and vulnerabilities in
> compat_linux and compat_linux32, the majority of which have a security impact
> bigger than the Intel CPU bugs we hear about so much. These compat layers
Hello Reinoud,
On Thu, Jun 20, 2019 at 03:12:12PM +0200, Reinoud Zandijk wrote:
> Hi Thierry,
>
> On Fri, Jun 14, 2019 at 12:19:11PM +0200, tlaro...@polynum.com wrote:
> > So I'd like to see the good work made by Reinoud Zandijk put a step
> > further with a robust fsck_udf(8) for using indeed
Hello,
Context: I have a NetBSD fileserver serving files to mainly various
MS/Windows nodes and some NetBSD ones. The fileserver is making also
various backups among which, in order to plan for disaster, one backup
is made on USB removable disks that have to be directly readable by
Windows
Hello,
On Sat, Oct 13, 2018 at 08:31:43AM +0100, Iain Hibbert wrote:
> On Thu, 11 Oct 2018, Emmanuel Dreyfus wrote:
>
> > Hello
> >
> > On both netbsd-8 and -current, I have a problem with USB devices that
> > get stuck in a non-functionning state even after a reboot.
> >
> > This happens
keeping persistently the name, so I guess in the GPT? Is there such
a thing?)
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
. This could give
a supplementary indication about the level the problem is. (Can one
instruct NetBSD to use only one CPU without an ad-hoc kernel?)
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key
On Thu, Jul 02, 2015 at 11:07:19AM +0200, tlaronde wrote:
On an NetBSD 6.1.5/amd64, when I connect a second USB connected disk to
the machine, NetBSD freezes. Unable to connect remotely; hard reboot
required.
Indeed, the system doesn't freeze but crashes (some long time without
response
.
But has something be made concerning USB and umass on post-6.1.x
kernels that could give a clue about what the problem is/was?
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7
that is mainly supposed to be administrated
from remote...
TIA,
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
the whole system (and I have nothing in the messages
after rebooting, indicating whatever...)
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95
the
performance of a filesystem driver depend on the way the device is
connected?) Problem with librefuse ?
Any clue would be welcomed.
TIA,
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7
. I may be wrong, but my error is
neither caused by wanting to be sync with fashion nor by wanting
systematically to be out of fashion: I simply ignore fashion.)
I gather that I will not convince you; but you can surely conclude that
you will never convince me ;)
--
Thierry Laronde tlaronde
. So MetaPost can also be
used to generate PS figures with roff text formatted.
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
http://www.arts-po.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
:
http://www.kergis.com/en/kertex.html
It is not orphaned but stalled for the moment due to ETIME.
Best,
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
uhidev1: Logitech Logitech USB Keyboard, rev 1.10/23.00, addr 3, iclass 3/0
uhidev1: 2 report ids
uhid0 at uhidev1 reportid 1: input=2, output=0, feature=0
uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
uhub2: device problem, disabling port 4
--
Thierry Laronde tlaronde +AT+ polynum
, and fails.
any other message before this ?
No. Only that it fails to read the very first sector when I finally
manage to kill the reading process (takes minutes).
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF
, or if
there is a driver for this on a *BSD flavor that could be ported to
NetBSD?
TIA
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
://www.linuxfoundation.org/collaborate/workgroups/networking/alx
Does NetBSD participate to this also?
--
Thierry Laronde tlaronde +AT+ polynum +dot+ com
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
1 - 100 of 104 matches
Mail list logo
