On 08/16/06 20:37 Pyun YongHyeon said the following:
If the media is set to 'none' you couldn't send anything from re(4) as
recent changes checks whether the link is present(Receiver should work).
ifconfig re0 media 10baset or 100baset always returns error, so there
doesn't seem to be
On Thu, Aug 17, 2006 at 02:05:48PM +0800, Dinesh Nair wrote:
On 08/16/06 20:37 Pyun YongHyeon said the following:
If the media is set to 'none' you couldn't send anything from re(4) as
recent changes checks whether the link is present(Receiver should work).
ifconfig re0 media
On Wed, 2006-Aug-16 15:54:25 -0700, Micah wrote:
I think you could fake it as follows:
struct dirent {
__uint32_t d_fileno;/* file number of entry */
__uint16_t d_reclen;/* length of this record */
__uint8_t d_type; /* file type, see
I've seen this several times now, but this time I got a dump.
Basically, the system comes up after unclean shutdown, throws a bunch of
filesystems into the background fsck list, and begins 60 seconds later.
After some amount of time, the system will lock up, presumably hung
waiting on
Dinesh Nair [EMAIL PROTECTED] writes:
i never got re(4) working, and the patch i'm currently using forces
the use of rl(4) instead of using re(4). using rl(4) still shows
media as none, but it works the way it should with packets going in
and out. i've yet to try dag-erling's suggestion of
On Thu, Aug 17, 2006 at 07:08:31AM -0500, Eric Anderson wrote:
I've seen this several times now, but this time I got a dump.
Basically, the system comes up after unclean shutdown, throws a bunch of
filesystems into the background fsck list, and begins 60 seconds later.
After some amount
On 08/17/06 07:25, Kostik Belousov wrote:
On Thu, Aug 17, 2006 at 07:08:31AM -0500, Eric Anderson wrote:
I've seen this several times now, but this time I got a dump.
Basically, the system comes up after unclean shutdown, throws a bunch of
filesystems into the background fsck list, and begins
Is it possible that we can add some loadable module into the kernel to
get a pid of a daemon-process and then somehow trace routing socket
messages coming in / going out from the kernel to that particular
daemon ?
The thing why I am in need of this is that there are two daemons ,
one daemon is
get a pid of a daemon-process and then somehow trace routing
socket messages coming in / going out from the kernel to that
particular daemon ?
`ktrace -p DAEMON-PID` might be what you want.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
On 08/17/06 07:30, Eric Anderson wrote:
On 08/17/06 07:25, Kostik Belousov wrote:
On Thu, Aug 17, 2006 at 07:08:31AM -0500, Eric Anderson wrote:
I've seen this several times now, but this time I got a dump.
Basically, the system comes up after unclean shutdown, throws a bunch of
filesystems
On Thu, Aug 17, 2006 at 09:53:28AM -0500, Eric Anderson wrote:
On 08/17/06 07:30, Eric Anderson wrote:
On 08/17/06 07:25, Kostik Belousov wrote:
On Thu, Aug 17, 2006 at 07:08:31AM -0500, Eric Anderson wrote:
I've seen this several times now, but this time I got a dump.
Basically, the system
On 08/17/06 10:04, Kostik Belousov wrote:
On Thu, Aug 17, 2006 at 09:53:28AM -0500, Eric Anderson wrote:
On 08/17/06 07:30, Eric Anderson wrote:
On 08/17/06 07:25, Kostik Belousov wrote:
On Thu, Aug 17, 2006 at 07:08:31AM -0500, Eric Anderson wrote:
I've seen this several times now, but this
On Thu, 17 Aug 2006, Shriek wrote:
Is it possible that we can add some loadable module into the kernel to get a
pid of a daemon-process and then somehow trace routing socket messages
coming in / going out from the kernel to that particular daemon ? The thing
why I am in need of this is that
Hi all,
I'm sort of curious as to how many people might be interested in this. I'm
aware that there are still other companies who also have embedded products
/ appliances based on FreeBSD 4, and I suppose that's probably the only
interest for such a patch. It's available at:
14 matches
Mail list logo
