Taylor R Campbell wrote:
> A quicker way to address most of it is to just define your own malloc:
>
> $ cat null.o
> #include
> void *malloc(size_t n) { return NULL; }
> void *realloc(void *p, size_t n) { return NULL; }
> void *calloc(size_t n, size_t sz) { return NULL; }
> void free(void *p) {}
Hi Brook,
Brook Milligan wrote:
> Installboot can install U-Boot boot blocks directly into a
> system image. Normally, the U-Boot files are searched for in
> /usr/pkg/share/u-boot, under the expectation that most people will
> build them with pkgsrc. However, it is also possible to set an
>
Lots of interesting discussion! Thanks all.
Broadly I think I can summarise to the following options:
1. The existing critical_filesystems_zfs rc.conf variable, which
mixes ZFS configuration in both rc.conf and with ZFS itself.
2. Add ZFS "critical" properties for filesystems and mount
Brad Spencer wrote:
> Simon Burge writes:
>
> > I'm using ZFS as my root filesystem, with the EFI boot loader reading
> > the kernel from the ZFS root filesystem. This is based on the the
> > FreeBSD libsa ZFS code. https://github.com/snarkophilus/src/tree/zfsboot
&
Paul Goyette wrote:
> On Tue, 15 Mar 2022, Simon Burge wrote:
>
> > Do we have any valid need to have non-critical local filesystems?
>
> Well, I have a dedicated filesystem for builds, separate from my
> OS. The /build happens to be my nvme SSD.
>
> Build
[ Moving this from source-changes-d to tech-userlevel and combining
a couple of messages with one rambling reply. ]
Greg Troxel wrote:
> Simon Burge writes:
>
> > I'm running with a complete ZFS-only setup with no legacy mounts. This
> > is my basic ZFS layout (leavin
Kamil Rytarowski wrote:
> On 14.07.2020 06:28, Martin Husemann wrote:
> > On Tue, Jul 14, 2020 at 02:49:00AM +0200, Joerg Sonnenberger wrote:
> >> Replacing malloc is just as invalid from a strict standard compliance
> >> perspective, so *shrug*
> >
> > Why is that?
> >
> > We have e.g.
Kamil Rytarowski wrote:
> I find this program useful, however it should be refreshed or rewritten
> for modern times. Its switches and usage is not compatible with modern
> grep(1) and the implementation is pretty simplistic.
>
> If someone would be interested to pick this project it would be
Kamil Rytarowski wrote:
> I can see the following solutions to suppress leaks:
>
> 1. use standard free(3)
> 2. use standard interfaces from LLVM/GCC sanitizers; potentially
> wrapping the interfaces in our headers
> 3. add libc functions to suppress leaks
4. fix the santisers and not
John Nemeth wrote:
> Numerous people have stated that they use telnet on a local
> network on older systems where ssh is too slow. For this purpose,
> it is pretty obvious that a telnetd would be needed.
I use rlogin/rlogind on my pc532. Never thought to use telnetd! I do
use the telnet
Greg Troxel wrote:
> a...@100acres.us writes:
>
> > The seq command behaves a little differently than I expect. I needed a
> > comma
> > separated list of integers, but seq gave me this:
> >
> > $seq -s , 1 3
> > 1,2,3,$
> >
> > Notice the extra comma and no trailing return. The comma is
Manuel Bouyer wrote:
> On Thu, Dec 13, 2018 at 10:50:30PM +, co...@sdf.org wrote:
> > Hi,
> >
> > telnet:
> > [ ... ]
> > Let's pull it out as a package, the alternative being breaking
> > functionality for the four remaining users.
>
> Actually, lots of mananged network equipements (or
m...@netbsd.org wrote:
> On Tue, Sep 25, 2018 at 04:32:03PM +1000, Simon Burge wrote:
> > Should you be allowed to call dirname(3) on the results of a previous
> > dirname(3) call?
>
> This is about minidlna, right?
Yes, minidlna.
> if it works, please feel fre
Edgar =?iso-8859-1?B?RnXf?= wrote:
> > or are we restricted by some standard from having dirname(3)
> > be able to be called on the results of a previous dirname(3) call
> Not exactly restricted from, but
> This is not strictly a bug; it is explicitly allowed by
> IEEE Std
Hi folks,
Should you be allowed to call dirname(3) on the results of a previous
dirname(3) call?
On NetBSD 8:
thoreau 49994> cat dirtest.c
#include
#include
#include
#include
int
main(void)
{
char *p =
Paul Goyette wrote:
> In my case, I have a shell alias for
>
> alias diff "diff -u"
>
> 'cuz most of the time I want a -u output. But once in a blue moon (or
> perhaps
> once in a blue+super moon) I want a -y (side-by-side) output; it's a real
> pain
> to have to bypass the alias by
Thor Lancelot Simon wrote:
> It appears tac was written by some unknown person, then rewritten
> by the late Jay Lepreau of the University of Utah in 1985 and sent
> to CSRG for inclusion on the "contrib" tape of 4.3BSD, but may or
> may not have shipped with 4.3 -- I can't find the "contrib"
Paul Goyette wrote:
> I often find myself (no pun intended!) wanting to determine which files
> were accessed before/since a particular timestamp. There currently
> exist the -{a,c}{newer,min,time} primitives, but none of these allow me
> to say "since today at 5 AM".
>
> I'd like to suggest
18 matches
Mail list logo
