I don’t see the point of implementing /dev/full. The python regress test is the
only time I’ve personally run into this. And I think the issue was that
python’s test suite made wrong assumptions about what devices exist on a
particular system. Therefore the fix needed to be on the python side.
On Sun, 15 Jan 2023, Crystal Kolipe wrote:
> Hi Daniel,
>
> On Sun, Jan 15, 2023 at 05:54:39PM -0500, Daniel Dickman wrote:
> > Hi Crystal,
> >
> > I tried your patch but it seems to tickle something on my lenovo laptop.
> >
> > I see this me
Hi Crystal,
I tried your patch but it seems to tickle something on my lenovo laptop.
I see this message:
entry point at 0x1001000
and then nothing further seems to show up.
In case helpful, dmesg from this laptop is shown below.
OpenBSD 7.2-current (GENERIC.MP) #0: Sun Ja
I have a laptop with these Transmeta devices:
pchb0 at pci0 dev 0 function 0 vendor "Transmeta", unknown product 0x0060 rev
0x00
ppb0 at pci0 dev 1 function 0 vendor "Transmeta", unknown product 0x0061 rev
0x00
NetBSD describes device 0061 as the integrated North Bridge, but I think
this is in
> On Sep 29, 2022, at 8:24 PM, Joerg Sonnenberger wrote:
>
> On Thu, Sep 29, 2022 at 08:39:16PM +1000, Jonathan Gray wrote:
>> wc counts items in files. Finding the longest item indeed sounds
>> like a task better suited to awk.
Doesn’t gnu wc show that tabs have length 8 rather than length
On Sat, Aug 27, 2022 at 7:15 AM Jonathan Gray wrote:
>
> On Fri, Aug 26, 2022 at 10:21:32PM -0500, Scott Cheloha wrote:
> > I noticed that on non-LAPIC systems we program channel 0 in periodic
> > mode with an initial count of 11932 to effect a 100hz clock interrupt.
> > And then we also use that
On Sun, 21 Aug 2022, Jonathan Gray wrote:
> On Sun, Aug 21, 2022 at 02:16:10AM -0400, Daniel Dickman wrote:
> > On Sun, 21 Aug 2022, Jonathan Gray wrote:
> >
> > > removed from amd64 in locore.S 1.71 in 2015
> > > the cpuid_level == -1 path can go in a later
On Sun, 21 Aug 2022, Jonathan Gray wrote:
> removed from amd64 in locore.S 1.71 in 2015
> the cpuid_level == -1 path can go in a later step
Can we also remove
375:extern const struct cpu_nocpuid_nameclass i386_nocpuid_cpus[];
from
include/cpu.h
?
locore.s rev 1.113 from 2007 removed support for 80386 processors from
copyin and copyout. However, the note about 386 CPUs in the comment for
copyout was missed. Patch below updates the comment to match the code.
While here s/destination/source/ for the description of copyin. Taken from
NetBSD
I've committed the updates for the German airports but left the
metropolitan area airports alone.
Thanks!
On Sat, Aug 20, 2022 at 9:50 PM Jonathan Gray wrote:
> why not just
>
> product TRANSMETA SDRAM 0x0396 SDRAM
> product TRANSMETA BIOS 0x0397 BIOS
That works too.
We have some generic PCI devices names:
product TRANSMETA MEM1 0x0396 Mem1
product TRANSMETA MEM2 0x0397 Mem2
Likely because these devices both appear as class=5 and subclass=0 (which
indicates a RAM device):
# pcidump -v
...
0:0:1: Transmeta Mem1
0x: Vendor ID: 1
The below diff removes detection code for the Cyrix 486DLC and Cyrix 6x86
CPUs from OpenBSD/i386.
The Cyrix 486DLC is a 486-class CPU which we no longer support.
The 6x86, also known as the M1, does not support CPUID by default. But it
can be made to support this instruction if bit 7 in CCR4 is
> On Jul 29, 2022, at 2:18 AM, Tomasz Rola wrote:
>
> On Thu, Jul 28, 2022 at 08:06:28PM -0400, Daniel Dickman wrote:
>>> On Thu, Jul 28, 2022 at 3:37 AM Jeroen Massar wrote:
>>>
> [...]
>>>
>>> I personally would not touch the .h
On Mon, Jul 25, 2022 at 5:10 AM Thomas Wager wrote:
>
> Hi,
>
> some changes to /share/misc/airport to treat german umlauts more
> consistently, remove the "Flugplatz" (german for airport, which is kind
> of redundant as it is all airports in the list), remove NRW which does
> not exist as IATA co
On Thu, Jul 28, 2022 at 3:37 AM Jeroen Massar wrote:
>
>
>
> > On 28 Jul 2022, at 04:18, Daniel Dickman wrote:
> >
> > The diff below removes support for 386SX/DX processors. We already claim
> > we don't support anything older than a Pentium so
The diff below removes support for 386SX/DX processors. We already claim
we don't support anything older than a Pentium so there's no point to keep
this code.
The main code change is in locore0.S and is to stop checking if the CPU
we're on has the alignment check (PSL_AC) flag.
The rest of the
On Sun, Jul 24, 2022 at 2:55 AM Jonathan Gray wrote:
>
> On Sun, Jul 24, 2022 at 02:16:23AM -0400, Daniel Dickman wrote:
> >http://datasheets.chipdb.org/Rise/
> >
> >Quoting the data sheet from this link:
> >
> >“The CMPXCHG8B instruction is supp
On Jul 24, 2022, at 12:25 AM, Jonathan Gray wrote:On Sat, Jul 23, 2022 at 02:13:27PM -0400, Daniel Dickman wrote:The Rise mp6 was a short lived processor that was announced around 20+ years and didn't make it to market.I think we can delete the cpu identification for this cpu at this point
The Rise mp6 was a short lived processor that was announced around 20+
years and didn't make it to market.
I think we can delete the cpu identification for this cpu at this point.
ok?
Index: i386/machdep.c
===
RCS file: /cvs/src/sy
Over a decade ago there was some work in bsd.man.mk to build tbl pages
with mandoc. For example this commit from 2010:
revision 1.32
date: 2010/10/17 22:47:08; author: schwarze; state: Exp; lines: +8 -18;
Build tbl(1) pages with mandoc(1), not groff.
Xenocara build
> On Jul 5, 2022, at 1:51 AM, Otto Moerbeek wrote:
>
> On Mon, Jul 04, 2022 at 05:44:33PM -0400, Daniel Dickman wrote:
>
>>
>>
>>> On Sun, 3 Jul 2022, Daniel Dickman wrote:
>>>
>>> On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
&g
On Mon, Jul 4, 2022 at 8:09 PM Daniel Dickman wrote:
>
>
>
> > On Jul 4, 2022, at 8:07 PM, Ben Fuller wrote:
> >
> > On Mon, Jul 04, 2022 at 19:30:19 -0400, Daniel Dickman wrote:
> >>>> Maldive Islands:Male
> >>> A more common name is just
> On Jul 4, 2022, at 8:07 PM, Ben Fuller wrote:
>
> On Mon, Jul 04, 2022 at 19:30:19 -0400, Daniel Dickman wrote:
>>>> Maldive Islands:Male
>>> A more common name is just "{The }Maldives".
>>
>> I don't think so. See this article:
&
The patch below removes the (small) amount of code used to identify NexGen
CPUs. I'm doubtful that these CPUs would be supported anymore and we don't
do anything with the information once we identify a NexGen CPU.
The code does a division early in the i386 boot process (in locore0) and
checks t
On Mon, 4 Jul 2022, Ben Fuller wrote:
> On Mon, Jul 04, 2022 at 17:44:33 -0400, Daniel Dickman wrote:
> > I had some time on my hand and took a stab on this. A few notes:
>
> Ach, you beat me to sending a patch. I made almost exactly the same changes as
> you have. I&#
On Sun, 3 Jul 2022, Daniel Dickman wrote:
> On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
> >
> > I noticed Montenegro doesn't have an entry. Presumably this file hasn't
> > been updated since before 2006!
>
> These files could use a big overhaul
On Sat, Jul 2, 2022 at 9:26 PM Ben Fuller wrote:
>
> I noticed Montenegro doesn't have an entry. Presumably this file hasn't
> been updated since before 2006!
These files could use a big overhaul and are very dated.
In the below, make sure to keep the file sorted.
In the Europe file there are o
> On May 21, 2022, at 4:16 PM, Daniel Douglas Dyrseth
> wrote:
> Hi
> Is porting natively a microkernel like seL4, Minix's or rewriting one for
> OpenBSD an option and something the developers could implement? I see this as
> an excellent addition to the already most robust OS in the world
> On Jan 12, 2022, at 2:06 AM, Philip Guenther wrote:
>
>
>> On Tue, Jan 11, 2022 at 4:09 PM Daniel Dickman wrote:
>
>> On Mon, Jan 10, 2022 at 8:12 PM Leo Larnack wrote:
>> >
>> > i386
>> >
>>
>>
>>
>> with t
On Mon, Jan 10, 2022 at 8:12 PM Leo Larnack wrote:
>
> i386
>
with this diff I was able to install includes, rebuild ld.so and
ctfconv. I've not managed to build a release yet.
Unfortunately polyml still fails to build, but I it did get quite a
bit further. most of the build log shown below.
On Fri, 26 Feb 2021, YASUOKA Masahiko wrote:
> Hi,
>
> My vaio repeatedly crashed by "Data modified on freelist"(*1) or other
> memory corruptions. After my long time debug, I found the route cause
> is a handling of references of LocalX, like the following:
>
> If ((SMRW
John,
I'm now able to clone the repo from windows following this commit:
https://github.com/openbsd/src/commit/6e49571c59fe1f1e78405e5a57a1e8dc40029e00
Two caveats:
1) if you wanted to bisect the repo on windows or checkout any earlier
commit than the one above, it won't be possible to do from wi
On Sun, Dec 13, 2020 at 7:51 PM Jonathan Gray wrote:
>
> On Sun, Dec 13, 2020 at 03:44:54PM -0500, Daniel Dickman wrote:
> >
> >
> > On Sat, 12 Dec 2020, Jonathan Gray wrote:
> >
> > > games/battlestar/com1.c
> > > games/battlestar/com2.c
> >
On Sat, 12 Dec 2020, Jonathan Gray wrote:
> games/battlestar/com1.c
> games/battlestar/com2.c
> games/battlestar/com3.c
> games/battlestar/com4.c
> games/battlestar/com5.c
> games/battlestar/com6.c
> games/battlestar/com7.c
> usr.bin/mail/aux.c
Diff below syncs with netbsd commits from 2001 to
On Wed, Dec 9, 2020 at 4:50 AM Jonathan Gray wrote:
>
> On Tue, Dec 08, 2020 at 11:36:37PM -0700, jo...@armadilloaerospace.com wrote:
> > The game battlestar has source files names com1.c through com7.c, which
> > are illegal on windows due to ancient dos com port rules.
> >
> > I understand there
> [PATCH] Add IOMMU support for Intel VT-d and AMD Vi
>
> This hooks each pci device and overrides bus_dmamap_xxx to issue
> remap of DMA requests to virtual DMA space. It protects devices
> from issuing I/O requests to memory in the system that is outside
> the requested DMA space.
Hi Jordan, th
Looking to add a few Atheros devices to pcidevs. ok?
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1928
diff -u -p -u -r1.1928 pcidevs
--- pcidevs 30 Jun 2020 04:37:24 - 1.1928
+++ pcid
> On Jul 1, 2019, at 2:50 AM, Moritz Buhl wrote:
>
> Hi,
>
> while testing arm hardware on OpenBSD I noticed that some floating point
> operations cause failures of other tests.
> In fact the current libm is incorrect according to the ISO C Std Annex
> G. I found this out after porting some F
Add core 4g thermal id from one of my systems. ok?
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1866
diff -u -p -u -r1.1866 pcidevs
--- pcidevs 8 Nov 2018 06:54:13 - 1.1866
+++ pcide
sync the text in csh(1) with text from getrlimit(2) and remove mention of
sbrk.
ok?
Index: csh.1
===
RCS file: /cvs/src/bin/csh/csh.1,v
retrieving revision 1.79
diff -u -p -u -r1.79 csh.1
--- csh.1 12 Dec 2017 11:34:38 -
Below patch removes use of sbrk from mkhybrid.
sbrk is only used here when mkhybrid is run in verbose mode to print a
diagnostic (see src/mkisofs.c).
ok?
Index: src/config.h
===
RCS file: /cvs/src/gnu/usr.sbin/mkhybrid/src/config.
(dropping ports@)
> On Nov 5, 2018, at 9:22 AM, Marc Espie wrote:
>
>> On Mon, Nov 05, 2018 at 09:15:28AM -0500, Daniel Dickman wrote:
>> gcc uses them for precompiled headers (PCH) which is a local diff added
>> by kurt@ in 2009. its likely nothing in base u
> On Nov 5, 2018, at 8:47 AM, Marc Espie wrote:
>
>> On Mon, Nov 05, 2018 at 08:43:56AM -0500, Daniel Dickman wrote:
>>
>>
>>> On Nov 5, 2018, at 8:30 AM, Marc Espie wrote:
>>>
>>> Or we could just finally remove brk and sbrk from the l
> On Nov 5, 2018, at 8:30 AM, Marc Espie wrote:
>
> Or we could just finally remove brk and sbrk from the libc ?
>
>
you won’t get very far. they are still needed in base (gcc, clang, mkhybrid).
> On Aug 17, 2018, at 8:37 AM, Solene Rapenne wrote:
>
> The sad state is that less and less
> ports are running on them.
>
The last package count for 6.3 shows macppc had the most packages after amd64
and i386.
Can you share examples of ports you’re missing? I’d be interested to look at
On Fri, Aug 17, 2018 at 8:48 AM, Mark Cave-Ayland
wrote:
> On 17/08/18 13:34, Jonathan Gray wrote:
>
>> On Fri, Aug 17, 2018 at 12:15:10PM +0100, Mark Cave-Ayland wrote:
>>> Hi all,
>>>
>>> I was just wondering what is the current state of the openbsd/macppc
>>> port? As part of my recent work on
On Thu, Mar 10, 2016 at 8:14 AM, Jeremie Courreges-Anglas
wrote:
> Ingo Schwarze writes:
>
>> Hi,
>
> Hi Ingo,
>
>> two general remarks:
>>
>> 1) The head(1) utility is supposed to handle text files.
The posix description for tail seems clear. I suggest following the
same treatment for head.
>
On Wed, Mar 9, 2016 at 9:35 PM, Michael McConville wrote:
> Jeremie Courreges-Anglas wrote:
>> >> @@ -66,13 +66,18 @@ main(int argc, char *argv[])
>> >>argv++;
>> >>}
>> >>
>> >> - while ((ch = getopt(argc, argv, "n:")) != -1) {
>> >> + while ((ch = getopt(argc, argv, "c:n:")) !=
you're missing at least the removal of the flag in the standards section of the
man page.
I agree with deraadt though, this needs a check of ports.
> On Dec 8, 2015, at 12:06 AM, Michael McConville wrote:
>
> It's been 0.9 since the original import in 2003...
>
>
> Index: grep.1
> ==
On Thu, Oct 29, 2015 at 10:31 PM, Michael McConville wrote:
> This one confused me for a few minutes. See sys/uvm/uvm_user.c for the
> function definition.
>
> ok?
looks like it's been out of sync since r1.10 in 2002.
ok.
>
>
> Index: share/man/man9/uvm.9
> =
committed with a minor tweak Thanks!
>
> Do I miss something simpler?
>
> Index: bin/rm/rm.1
> ===
> RCS file: /var/cvs/src/bin/rm/rm.1,v
> retrieving revision 1.37
> diff -u -p -r1.37 rm.1
> --- bin/rm/rm.1 25 May 2014 19:07:36 -
On Fri, Sep 11, 2015 at 3:18 PM, Maxime Villard wrote:
>
> _19/ UNINITIALIZED VARIABLE: sys/arch/i386/i386/bios.c rev1.112
>
Fixed. Thanks.
On Thu, Jun 18, 2015 at 10:18 AM, Jason McIntyre wrote:
> On Thu, Jun 18, 2015 at 03:56:15PM +0200, Theo Buehler wrote:
>>
>> >From looking at the source code, I'm quite sure that the other BSD's
>> behavior is the same as the current behavior in OpenBSD.
>>
>> I agree that the formulations in the
> On Tue, Jan 20, 2015 at 11:14 AM, Jonathan Gray wrote:
> So it seems at some point after gcc 4.4 --std=c89 and --std=c99
> starting allowing anonymous unions/structs when this behaviour
> was otherwise only accepted with --std=gnu99, --std=c99 -fms-extensions
> or omitting a --std option entire
On Sat, Sep 20, 2014 at 3:07 PM, Maxime Villard wrote:
> Hi,
> I put here a bug among others:
>
> Index: ssh-ed25519.c
> ===
> RCS file: /cvs/src/usr.bin/ssh/ssh-ed25519.c,v
> retrieving revision 1.4
> diff -u -r1.4 ssh-ed25519.c
> --
On Tue, Oct 7, 2014 at 3:34 AM, Otto Moerbeek wrote:
> On Tue, Oct 07, 2014 at 03:10:44AM -0400, Daniel Dickman wrote:
>
>> Fritjof, have you let the gnu rcs project know about the segfault?
>> Maybe see how they choose to fix things and then follow their lead?
>
> That wi
>
> > >
> > > On Thu, Oct 02, 2014 at 12:54:13AM +0100, Nicholas Marriott wrote:
> > > > Matching GNU RCS seems preferable to me but I don't feel strongly about
> > > > it.
> > > >
> > > > I wouldn't mention this in the man
posix commands (like ls(1) for example) keep the last option when mutually
exclusive options are specified. does it make sense to keep rcs consistent with
that convention? also is a man page diff needed?
> On Oct 1, 2014, at 7:17 PM, Nicholas Marriott
> wrote:
>
> The existing behaviour isn'
according to the numpy developers asinhl on sparc64 might be buggy. I
haven't worked out a test case yet but just reporting in case anyone else
wants to take a look as well.
bug report:
https://github.com/numpy/numpy/issues/5026#issuecomment-54711361
r your feedback.
> -Adam
>
>> On July 10, 2014 10:05:45 PM CDT, Daniel Dickman wrote:
>> Patch below turns off the following ancient protocols built into lynx:
>> bibp, finger, gopher, and news.
>>
>> For some urls, lynx will invoke an external command. Turn o
>> For some urls, lynx will invoke an external command. Turn off telnet,
>> rlogin and tn3270 urls by defining them to false(1) as documented in the
>> lynx manual.
>
> Gopher and NNTP are actually still being used (the former a bit
> sparsely, but there are a few servers here and there). The rest
Patch below turns off the following ancient protocols built into lynx:
bibp, finger, gopher, and news.
For some urls, lynx will invoke an external command. Turn off telnet,
rlogin and tn3270 urls by defining them to false(1) as documented in the
lynx manual.
Finally, turn off the file editor w
On Tue, Jul 8, 2014 at 9:59 PM, Brian Callahan wrote:
> Hi everyone --
>
> port-modules.5 is missing an "If" to make a complete sentence.
> OK?
ok daniel@
>
> ~Brian
>
> Index: port-modules.5
> ===
> RCS file: /cvs/src/share/man/man
>>
>> confirming that this patch fixes the failing numpy regress test on i386.
>>
>> let me know if you want me to test a different diff.
>
> Here's a better diff, inspired by what FreeBSD has.
>
> ok?
>
>
ok with me. numpy works with this diff too.
On Tue, Jun 3, 2014 at 7:35 PM, enh wrote:
> GCC 4.9 complains:
>
> bionic/libc/upstream-openbsd/lib/libc/stdio/vfwprintf.c:328:16: error:
> variable 'uio' set but not used [-Werror=unused-but-set-variable]
> struct __suio uio; /* output information: summary */
> ^
>
> suggested
>
> Another bug. Intel chose an extended precision format with an
> explicit integer bit, and the code doesn't handle that. Assuming we
> don't support machines with extended precision format that have an
> implicit integer bit, the following diff (an adaptation of the code in
> glibc) should fix
>From the numpy test suite, I think I might have found a bug in
nextafterl(3). The "result_ld" variable below comes back as nan on
i386. But doing the same calculations with floats returns the expected
values.
A test on Linux also shows the expected results for both the float and
long double cases
On Mon, Jun 2, 2014 at 5:33 AM, Mark Kettenis wrote:
>> Date: Mon, 2 Jun 2014 10:17:53 +0200 (CEST)
>> From: Mark Kettenis
>>
>> > Date: Mon, 02 Jun 2014 09:34:20 +0200
>> > From: Benjamin Baier
>> >
>> > You might want to read up on floating point arithmetic. (rounding and
>> > representation)
far too big for the
existing calculation to be correct. I'm linking to the wikipedia
article for some background reading for you but there's a lot more
info on the web on this topic:
http://en.wikipedia.org/wiki/Unit_in_the_last_place
>
> On 06/02/14 05:13, Daniel Dickman wrote:
>>
I hit this problem while working with the numpy 1.8.1 regress suite
which has some tests that are currently failing.
Here is a reduced test case of the logaddexp2 python function which
ends up calling exp2. Is this a bug in the openbsd exp2
implementation?
---8<---
#include
#include
#include
The ACPI RSDP table has a checksum and an extended checksum. At the moment
if the ACPI rvision is zero, the checksum is checked and if the revision
is more recent only the extended checksum field is checked.
However the spec says that the checksum field "...must sum to zero." At
the moment this
I think I recently ran into a similar issue but I suspect the root cause might
be the same. I think the floorl function is wrong for numbers slightly larger
than -1 to numbers slightly below 0. In this range floorl returns -0 instead of
-1.
> On Feb 5, 2014, at 3:57 AM, David Coppa wrote:
>
>
Tell people the equivalent of the Command and Option keys for anyone
using a PC keyboard instead of a Mac keyboard...
Index: prep
===
RCS file: /home/cvs/src/distrib/notes/macppc/prep,v
retrieving revision 1.19
diff -u -p -u -r1.19
>> I'm trying to port compcert to openbsd. Here's a first patch to allow
>> jot to be compiled with compcert.
> Wouldn't it be better to check for __STDC_VERSION__ >= 199901L rather than a
> list of compilers? (I don't have a source tree close by which is why I don't
> have a patch.)
Supporting _
I'm trying to port compcert to openbsd. Here's a first patch to allow
jot to be compiled with compcert.
Before the patch is applied compcert fails because _Bool is predefined as
per C99:
# ccomp -fall -c /usr/src/usr.bin/jot/jot.c
/usr/include/stdbool.h:20: Error: illegal combination of type sp
minor patch for uvm(9) :-
- remove redundant sentence about misc functions
- note that pmap(9) is the MD portion of UVM.
- Convert reference to Chuck's dissertation to .Rs/.Re section
- uvm is no longer "new".
- Remove "(Missouri)". St. Louis should be enough to remove any confusion
between wust
It looks like copyright for sys/kern/sysv_ipc.c was assigned to NetBSD
in rev 1.13 in 1998:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/kern/sysv_ipc.c.diff?r1=1.12&r2=1.13&only_with_tag=MAIN&f=h
NetBSD then dropped clauses 3 & 4 in rev 1.21 in 2008:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/k
fix rcs ids.
Index: elf32_powerpc_merge.x
===
RCS file: /home/cvs/src/sys/arch/macppc/stand/boot.mac/elf32_powerpc_merge.x,v
retrieving revision 1.1
diff -u -r1.1 elf32_powerpc_merge.x
--- elf32_powerpc_merge.x 5 Dec 2006 20:30:
The lex Makefile says:
"To bootstrap lex, cp initscan.c to scan.c and run make."
On amd64-current this doesn't seem to build:
[/usr/src/usr.bin/lex] cp initscan.c scan.c
[/usr/src/usr.bin/lex] make
yacc -d parse.y
mv y.tab.c parse.c
mv y.tab.h parse.h
cc -O2 -pi
I guess the intent was to get a custom message at build time which would
be shown when phantasia starts up. But --
(1) That would make the build interactive.
(2) _PATH_PHANTDIR is not defined anywhere so this won't compile.
(3) As the ifdef macro says, this can be done from the Makefile if
n
Get rid of trigraphs. No effect with gcc since the default is to ignore
trigraphs, but does get rid of the warnings during build.
Index: /usr/src/usr.sbin/rbootd/rbootd.c
===
RCS file: /usr/cvs/src/usr.sbin/rbootd/rbootd.c,v
retriev
The files below change with every build because they include the `date`
they were generated (and etcsum changes because it references some of the
files that keep changing).
/etc/mail/localhost.cf
/etc/mail/sendmail.cf
/etc/mail/submit.cf
/usr/share/info/dir
/var/db/sysmerge/etcsum
The patch bel
> how did you end up without /usr/obj?
>
> $ tar tzf base48.tgz ./usr/obj
> ./usr/obj
> $
user error on my part. but:
(1) Let me turn this around. What's the objection to making the
change? is there something that would break? why not protect against
user error when possible to do so?
(2) xenocar
> Sorry, I don't think this makes sense. I always start with doing a
> make obj. It's way too easy to mess things things up if you forget to
> do that step, so running anything in my source tree without doing make
> obj first makes me very nervous.
>
> Does changing the order actually fix somethi
I think it might be better to create missing directories (especially
/usr/obj) before creating the symlinks. This is one less opportunity for
someone to mess up if /usr/obj is missing for some reason...
Index: release.8
===
RCS fil
On Thu, Jul 22, 2010 at 6:15 PM, Jason McIntyre wrote:
> On Thu, Jul 22, 2010 at 05:38:29PM -0400, Daniel Dickman wrote:
>>
>> I think the man page is bit confusing. Note that I sent jmc@ the patch
>> below for the man page to try to clear things up a bit there as well. The
Hi Ingo,
Thanks for taking a look.
> > exit 126 means "utility was found but could not be invoked".
> > exit 1-125 means some other error in env(1)
>
> Not quite; the -current manual says:
>
> 1-125 utility was invoked but failed in some way; see its manual page
> for more informati
exit 126 means "utility was found but could not be invoked".
exit 1-125 means some other error in env(1)
So change 2 places to return an exit code of 125 instead.
Index: env.c
===
RCS file: /usr/cvs/src/usr.bin/env/env.c,v
retrieving
The diff(1) man page (and posix) specify the following as exit values:
0 No differences were found.
1 Differences were found.
>1 An error occurred.
So I think the patch below is needed.
Index: xmalloc.c
=
> If you notice, the asm part does a "setc %b1". And in your
> case, that would simply nuke %ecx. The original code did not
> take into account the length returned, it ignored it as it
> was asking for the max, some biosen always return the max,
> and nothing should ever return more than what was
Int 0x15, AX=e820 doesn't return the length of the buffer in EDX. That's
actually returned in ECX. So I think the patch below is needed.
For reference see:
http://www.ctyme.com/intr/rb-1741.htm
Tested on amd64.
Index: amd64/stand/libsa/memprobe.c
===
The shell script to launch jbrickshooter depends on having the JRE
installed and fails if only the JDK is available.
# jbrickshooter
/usr/local/bin/jbrickshooter[2]: /usr/local/jre-1.7.0/bin/java: not found
The patch below fixes things to use javaPathHelper which is more robust
and will work if
On Fri, 12 Feb 2010, Stuart Henderson wrote:
> On 2010/02/11 23:44, Daniel Dickman wrote:
> > ftp(1) will reliably stall for me when doing uploads. I tracked the
> > problem down to the keep-alive option. Not sure how widespread this issue
> > is as I'd imagine it de
ftp(1) will reliably stall for me when doing uploads. I tracked the
problem down to the keep-alive option. Not sure how widespread this issue
is as I'd imagine it depends on what server is on the receiving end. But
here's a sample transcript which gets stuck every time and requires me to
kill t
On Thu, 28 Jan 2010, Otto Moerbeek wrote:
> On Thu, Jan 28, 2010 at 03:25:21AM -0500, Daniel Dickman wrote:
>
> > Note: the patch below is NOT recommended for 4.7 as this will change
> > the semantics of fts_open and will BREAK things like "gzip -" and
> > possi
Note: the patch below is NOT recommended for 4.7 as this will change
the semantics of fts_open and will BREAK things like "gzip -" and
possibly other stuff.
Calls to fts_open should probably be audited first...
On Thu, Jan 28, 2010 at 2:06 AM, Daniel Dickman wrote:
> As report
As reported on the git mailing list[1], find(1) should exit with non-zero
status when a non-existent path is given which I think is also the intent
of the find(1) code.
[1] http://marc.info/?l=git&m=126186443524638
For example:
# find /no-such-path
find: fts_open: No such file
The patch below allows the sequence of steps to build the base system to
be the same as the steps for building xenocara. essentially:
# make bootstrap
# make obj
# make
# make release
At least for me, it's nice to have to type (and remember) fewer
keystrokes. No patch for release(8) for now, si
> $ ftp -o- http://junkpile.org/sort-ispell.txt | sort -u -t/ +0f -1 +0
The -u seems unimportant. Using more modern syntax, the following seems to
have the same effect:
$ ftp http://junkpile.org/sort-ispell.txt && sort -t/ -k1,1 -k1 sort-ispell.txt
>
> The second one I've seen affects at least
1 - 100 of 105 matches
Mail list logo
