|
|
 Up |
|
|
  |
Author: patrick keshishianpatrick keshishian
Date: May 8, 2008 23:49
Not to come off as "pushy" but wanted to make sure these patches
didn't fall through the cracks, assuming they were rejected for
some reason.
Cheers,
On Sun, Apr 06, 2008 at 06:32:39PM -0700, patrick keshishian wrote:
> On Sun, Apr 06, 2008 at 09:39:20AM -0400, Todd C. Miller wrote:
|
| Show full article (2.75Kb) |
|
| |
no comments
|
|
|
Author: Kenneth R WesterbackKenneth R Westerback
Date: May 8, 2008 17:12
It has been discovered that some network drivers are not correctly
sending the routing messages (RTM_IFINFO) expected when link status
changes. These messages are used by dhclient to react properly to
such link status changes, even more so in upcoming diffs.
The diff below, which you are free to test, 'fixes' bge(4).
It would be helpful to discover which drivers are currently
misbehaving, if any other than bge do. Testing your network
card/driver is easy and fun!
As root or via sudo run
route -n monitor
and unplug and plug in your cable. You should see something like:
$ sudo route -n monitor
Password:
got message of size 144 on Fri May 9 09:06:03 2008
RTM_IFINFO: iface status change: len 144, if# 2, link: no carrier,
flags:
got message of size 144 on Fri May 9 09:06:05 2008
RTM_IFINFO: iface status change: len 144, if# 2, link: active,
flags:
|
| Show full article (2.26Kb) |
|
| |
no comments
|
|
|
|
|
|
Author: Antoine JacoutotAntoine Jacoutot
Date: May 8, 2008 12:49
Hi.
This diff adds a non-interactive mode to sysmerge.
It may be handy when updating several boxen (or one even) as it will
save differing files so you can diff/merge them later yourself after
further inspection.
Also yesno was only used once so nuke it.
Man page bits enhancements from jmc@.
Comments?
===> http://www.bsdfrog.org/tmp/sysmerge.diff
Index: sysmerge.8
===================================================================
RCS file: /cvs/src/usr.sbin/sysmerge/sysmerge.8,v
retrieving revision 1.3
diff -u -r1.3 sysmerge.8
--- sysmerge.8 30...
|
| Show full article (4.06Kb) |
|
no comments
|
|
|
Author: Hannah SchroeterHannah Schroeter
Date: May 8, 2008 12:11
Hello, Dasn!
I was advised that my earlier response might feel offensive to some,
perhaps you too. If so, I apologize for it. I didn't meen to offend, but
to be humorous, but probably I failed.
On Thu, May 08, 2008 at 02:45:17PM +0200, Hannah Schroeter wrote:
>On Thu, May 08, 2008 at 07:24:19AM +0800, Dasn wrote:
>>On 05/05/08 16:00 +0200, Hannah Schroeter wrote:
>>> After reading the kernel sources about this, I think the definition in
>>> is probably in error and it should be
>>> #define TIOCSIG _IOW('t', 95, int)
>>> ^^^^ ^^^
>>> Strangely, the xterm sources don't reference TIOCSIG, so I don't know
>>> how xterm implements the send SIGfoo menu functions instead.
>>>>But I cannot find any clues about it in pty(4).
>>>>The code:
>>>> int sig = SIGTERM;
>>>> ioctl(pty_master, TIOCSIG, &sig) ;
|
| Show full article (3.04Kb) |
|
no comments
|
|
|
|
|
|
Author: Hannah SchroeterHannah Schroeter
Date: May 8, 2008 12:11
Hi!
On Thu, May 08, 2008 at 07:24:19AM +0800, Dasn wrote:
>On 05/05/08 16:00 +0200, Hannah Schroeter wrote:
>> After reading the kernel sources about this, I think the definition in
>> is probably in error and it should be
>> #define TIOCSIG _IOW('t', 95, int)
>> ^^^^ ^^^
>> Strangely, the xterm sources don't reference TIOCSIG, so I don't know
>> how xterm implements the send SIGfoo menu functions instead.
>>>But I cannot find any clues about it in pty(4).
>>>The code:
>>> int sig = SIGTERM;
>>> ioctl(pty_master, TIOCSIG, &sig) ;
>> That usage should be ok, and perhaps would work if you patched
>> appropriately (recompile kernel, reboot, recompile your
>> app).
>Thank you, guys. After applying the patch,
That patch (cleaned up, of course) has been committed to the tree
(-current) in-between, as I've seen.
|
| Show full article (2.30Kb) |
|
no comments
|
|
|
|
|
