Pedro Giffuni writes:
> Now, just some food for thought, but if you are unsure your patch
> applies cleanly, why would you choose to use the -s (silent) option?
Because by default patch(1) is overly verbose. At first, I'm only
interested if a patch applies cleanly, then what files fail to apply.
Hi,
The following log messages are displayed on a box where I am testing
stable/9. It occurs only when trying to shutdown the box:
| Waiting (max 60 seconds) for system process `vnlru' to stop...done
| Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
| Waiting (max 60
TB --- 2013-07-27 00:52:38 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-27 00:52:38 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hi Jan;
El 26/07/2013 8:01 p. m., Jan Beich escribió:
bsdpatch doesn't list files of the failed hunks with -C and -s option.
This may be less convenient if you edit a patch directly rather than
regen it after polluting the tree.
$ patch -CEfsp0 -i /path/to/varsym.diff
1 out of 1 hunks failed
1
bsdpatch doesn't list files of the failed hunks with -C and -s option.
This may be less convenient if you edit a patch directly rather than
regen it after polluting the tree.
$ patch -CEfsp0 -i /path/to/varsym.diff
1 out of 1 hunks failed
1 out of 2 hunks failed
2 out of 2 hunks failed
1 out of 5
Hello;
After an exp-run it was found that only two ports presented regressions
with the new BSD-licensed patch derived from Open/DragonFly BSD.
The issue was related to some patch level detection the previous
GNU patch has and the new patch lacks. Otherwise both versions
are basically equivalent
on 26/07/2013 17:39 Andriy Gapon said the following:
> Please note that nothing changes with respect to matching simple paths like
> /dev/something.
I must add: and thus rules in etc/defaults/devfs.rules should not be affected
except for their unintended side-effects.
--
Andriy Gapon
___
hi,
in an attempt to simplify the locking in netmap,
i would like to code the poll handler along these lines
netmap_poll() {
...
/* PART1 */
revents = 0;
/* see if any of the rings has data */
for (i = first_ring; i < last_ring; i++) {
na->
I have just committed a significant change to devfs path matching logic
http://svnweb.freebsd.org/changeset/base/253677
Jaakko Heinonen (jh@) has full credit for the code while I have full
responsibility for any consequences of the commit.
Before this change the logic of matching the devfs paths
Hi!
At $WORK, we use 802.1X to authenticate computers on the network.
Authenticated computers receive a lease in the 192.168.X.X/24 network.
Unauthenticated ones receive a lease in the 172.16.X.X/24 network.
Today, I upgraded one computer running 10-CURRENT to latest HEAD and it
seems that the in
Hello
Some time ago, after update system on several servers I'm notice strange memory
behavior
For example
Mem: 1245M Active, 937M Inact, 4093M Wired, 13M Cache, 1670M Free
ARC: 495M Total, 50M MFU, 192M MRU, 17M Anon, 29M Header, 208M Other
For zfs configures is
vm.kmem_size="3G"
vfs.zfs
Hi,
As of now expand_number(3) does not properly check too large data.
It currently handles errors only for prefixed values.
(an argument is intentionally signed to be closer to the real buggish world,
e.g. as it's currently done in truncate(1). This should not compile, though
see bsd.sys.mk@1697
12 matches
Mail list logo
