4 msg'kernel: rtfree: 0xc3c4bd98 has 2 refs' on rece...
8 msghard-lock with CPU spinning
3 msgZFS with USB 'SCSI'
3 msgfdc0 doesn't attach on my current machine
7 msgBest way to build a 'new' AMD64 current
9 msgLOR in iwi with new 802.11 work
2 msgpanic in drm_ioctl
5 msgRe: smb related problem
9 msgDisappearing userland output with -current
4 msgBIND 9.4.1 performance on FreeBSD 6.2 vs. 7.0
4 msgi386/i386/busdma_machdep.c 1.88 breaks isp
7 msgath device appears broken
8 msgKTR and SCTP

old bugs
\ Volodymyr Kostyrko (13 Jun 2007)
. \ Dave Grochowski (14 Jun 2007)

6 msgZFS tuning tips?
1 msg(Delayed) HEADS UP: AUDIT in GENERIC
13 msgHEADS UP: IPX over IP support removed
4 msgRFC: diff(1) update
2 msgCall for testers, amd64 only, new scheduler.
4 msgHPS stack and ural
Subject:old bugs
Group:Freebsd-current
From:Volodymyr Kostyrko
Date:13 Jun 2007


 
Recently bumped once again into "misc/58117: installworld /tmp/
problem". Would it be better to solve it at "once and for all" basis?

This is a good choice for securing servers to make /tmp noexec. But when
you did that - you'll have to face this bug again. Yes, it can be solved
by specifying TMPDIR. But:
- UPDATING says nothing about that;
- nor documentation do;
- the message is kindda cryptic and it takes time to understand whats
going on.

Why not document the issue or prevent it by using custom catalog?

--
Sphinx of black quartz judge my vow!

_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"


© 2004-2008 readlist.com