of ports-mgmt/pkg
make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory
Error: Unknown stuck queue bug detected. Please submit the entire build
output to poudriere developers.
/mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building
/mnt/system/DATEN
long
Hit CTRL+t at any time to see build progress and stats
[01] Starting build of ports-mgmt/pkg
make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory
Does ports-mgmt/pkg exist in the ports tree you are using?
Error: Unknown stuck queue bug detected. Please submit
progress and stats
[01] Starting build of ports-mgmt/pkg
make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory
Does ports-mgmt/pkg exist in the ports tree you are using?
Error: Unknown stuck queue bug detected. Please submit the entire
build output to poudriere
long
Hit CTRL+t at any time to see build progress and stats
[01] Starting build of ports-mgmt/pkg
make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory
Does ports-mgmt/pkg exist in the ports tree you are using?
Error: Unknown stuck queue bug detected. Please submit
queue bug detected. Please submit the entire
build output to poudriere developers.
/mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building
/mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool
/mnt/system/DATEN/poudriere
--- 10.219.5.193 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.032/0.032/0.032/0.000 ms
%arp 10.219.5.193
10.219.5.193 (10.219.5.193) -- no entry
Is it bug or feature?
Thanks
Radek
FreeBSD 9.0-RELEASE, i386
Xiphos is giving me a strange warning[0], and I'm not quite sure what to
make of it. The forums don't address this specifically that I could
find, and nothing via a web search seemed to be relevant to my issue.
Not quite sure what the issue is, either, to be honest. I
On Mon, 05 Nov 2012 18:54:43 -0600, Joseph a Nagy Jr wrote:
FreeBSD 9.0-RELEASE, i386
Xiphos is giving me a strange warning[0], and I'm not quite sure what to
make of it.
Currently C is set as the default language setting (locale)
for that specific program. It cannot handle it and probably
On 11/05/12 19:19, Polytropon wrote:
On Mon, 05 Nov 2012 18:54:43 -0600, Joseph a Nagy Jr wrote:
FreeBSD 9.0-RELEASE, i386
Xiphos is giving me a strange warning[0], and I'm not quite sure what to
make of it.
Currently C is set as the default language setting (locale)
for that specific
On Mon, 05 Nov 2012 19:25:54 -0600, Joseph a Nagy Jr wrote:
On 11/05/12 19:19, Polytropon wrote:
On Mon, 05 Nov 2012 18:54:43 -0600, Joseph a Nagy Jr wrote:
FreeBSD 9.0-RELEASE, i386
Xiphos is giving me a strange warning[0], and I'm not quite sure what to
make of it.
Currently C is
snip
Thanks for the help and quick lessons! Very useful information to know!
--
Yours in Christ,
Joseph A Nagy Jr
Whoever loves instruction loves knowledge, But he who hates correction
is stupid. -- Proverbs 12:1
Emails are not formal business letters, whatever businesses may want.
Original
Hello
I cannot get the lagg driver to work properly at 9.0
the Cisco switch is well configured to support LACP no problem
on that side it supports another Linux server with two aggregated
eth ports that works well.
here is the config of the FreeBSD 9.0-P3 server
ifconfig_bce0=up
On 2012-10-23 06:02, Frank Bonnet wrote:
Hello
I cannot get the lagg driver to work properly at 9.0
the Cisco switch is well configured to support LACP no problem
on that side it supports another Linux server with two aggregated
eth ports that works well.
here is the config of the FreeBSD
Hello
I have a problem with a server running FreeBSD 9.0-P3
It seems the lagg driver does not works well
here is the contents of the /etc/rc.conf file
the problem is, only the first interface (bce0) is working
in the lagg0 interface , the two others are not active
ifconfig_bce0=up
Where could be a problem? Is it bug or I am wrong but I dont see any mistake
Thank you
Radek
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions
Hi again,
I take example line from manual:
zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home
modify it to:
zfs set sharenfs='rw=@pokus.starnet.cz,root=0' storage/pokus
Where could be a problem? Is it bug or I am wrong but I dont see any
mistake
I found solution
Bug report for /usr/bin/calendar
SUMMARY: calendar does not match Thu+1 or Mon+1 in some months.
With one exception, it looks like calendar file dates such as Thu+1
and Mon+1 are failing to match in two cases: (1) the 7th of Jan-Nov,
and (2) December.
DETAILS/EXAMPLES:
FreeBSD crystal 9.0
Hi,
Please report bugs with send-pr
(cos bug reports to mail list get lost)
See
man send-pr
If you can attach a patch to fix it, so much the better
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like
Given this script:
#!/bin/sh
foo=
while read line
do
foo=$foo -e
done
echo $foo
Say I respond 3 times, I'd expect to see:
-e -e -e
Instead, I get:
-e -e
Linux appears to do the right thing here, so this seems like it
is a bug ... or am I missing something
it
is a bug ... or am I missing something?
echo takes a -e flag, so it eats the first one. Bash does the same thing,
so any Linux that uses bash as /bin/sh will also. You must be testing on a
Linux that uses something else as /bin/sh. Better to use the printf command
if you are worried about
, so this seems like it
is a bug ... or am I missing something?
echo takes a -e flag, so it eats the first one. Bash does the same thing,
so any Linux that uses bash as /bin/sh will also. You must be testing on a
Linux that uses something else as /bin/sh. Better to use the printf command
if you
On Tue, 05 Jun 2012 10:40:45 -0500
Tim Daneliuk tun...@tundraware.com wrote:
Given this script:
#!/bin/sh
foo=
while read line
do
foo=$foo -e
done
echo $foo
Say I respond 3 times, I'd expect to see:
-e -e -e
Instead, I get:
-e -e
The last line echo $foo is what is
From: Tim Daneliuk tun...@tundraware.com
Given this script:
#!/bin/sh
foo=
while read line
do
foo=$foo -e
done
echo $foo
Say I respond 3 times, I'd expect to see:
-e -e -e
Instead, I get:
-e -e
Linux appears to do the right thing here, so this seems like it
is a bug
Hello first of all. This is my first post here.. a test..
i stream on line as i read todays post. So about xorg file cause i make 6
months with nvidia 9200fx let talk first for the card. second there is no
xorg need it so u can back up and delete it, and test you X with xrandr -q
man xrandr and
with and without hal and when Xorg is started with
startx or startxfce4. xorg.conf is unmodified from a 'Xorg -configure'. The
monitor driver select is radeon. The radeonhd driver crashes.
The system is not down, as I can ssh into it,the only real bug is that the
consoles are not available. I think
.log or xdm.log.
I get the same symptoms with and without hal and when Xorg is started
with startx or startxfce4. xorg.conf is unmodified from a 'Xorg
-configure'. The monitor driver select is radeon. The radeonhd driver
crashes.
The system is not down, as I can ssh into it,the only real bug
is not down, as I can ssh into it,the only real bug is that the
consoles are not available. I think this is a bug handling the monitor rather
than
the keyboard because of the 'no signal' indication and the ctrl-alt keys work, I
just can not see whats on the console.
Is additional logging available? Anybody
Hi guys ... just for the record.
I've fixed the issue simply moving the cable of the backup interface to
another switch as suggested by the network guys of the DC. Which is even
preferable under the network redundancy perspective.
Now works perfectly and the failover NIC0-NIC1 and (NIC1-NIC0) is
Sorry top posting from phone.
Show your switch's port configurations.
We're using VLAN tagging over lagg failover interfaces at work and I have
already tried the tests you described, to much better results.
We're also running 8.2 so the only thing that seems to differ between us is the
Hi Dweimer and Damien,
thanks for replying.
The server is connected to a switch of the datacentre. The configuration
of this switch is unknown to me and I obviously have no access to it but
I truly believe that such an enterprise environment has management
capabilities.
Anyway, in which way the
You're not looking for FEC or ethechannel or 802.3ad at all.
What you're looking for, in the case of a *failover* configuration, is a
spanning-tree portfast feature so that your port doesn't transition
through the different spantree states before forwarding traffic.
Kindly obtain the
I've requested the configuration. I'll post that as soon as I have it.
Thank you very much for your time.
On Fri, 2012-03-16 at 12:10 +0100, Damien Fleuriot wrote:
You're not looking for FEC or ethechannel or 802.3ad at all.
What you're looking for, in the case of a *failover* configuration,
That's the STP configuration on my two switch ports:
spanning-tree portfast
spanning-tree bpduguard enable
On Fri, 2012-03-16 at 12:10 +0100, Damien Fleuriot wrote:
You're not looking for FEC or ethechannel or 802.3ad at all.
What you're looking for, in the case of a *failover*
I confirm you should see fast transition for your VLANs to forwarding state.
Are your ports in access or trunk mode ?
If they're trunked, portfast alone won't do it, you need spanning-tree
portfast trunk.
Additionally, are you using link aggregation on the cisco swi ?
(channel-group)
On
I actually don't know Damien. I'll have to have a chat with the network
guy in the DC as I'm not managing the switch neither I have access to
it, plus I'm not really a Cisco guy so I'll forward those questions to
him.
Moreover I'm getting a bit lost with this.
If the ports are in trunk mode would
Hi there,
a while after setting up my new server (with 8 jails in it) I've decided
(after postponing several times) to properly check the functionality of
the lagg and the result was very disappointing.
The test I've done is very simple.
I've started copying a file from one site to another of my
On 15.03.2012 14:06, Snoop wrote:
Hi there,
a while after setting up my new server (with 8 jails in it) I've
decided
(after postponing several times) to properly check the functionality
of
the lagg and the result was very disappointing.
The test I've done is very simple.
I've started copying
At 13:48 26/01/2012, you wrote:
There seems to be an old BUG,
http://osdir.com/ml/freebsd-bugs/2006-04/msg00309.html
that has recently been noted on the Postfix forums.
Was this bug ever actually addressed? In other words, is this an
actual bug or is it working as intended? If it is a bug
There seems to be an old BUG,
http://osdir.com/ml/freebsd-bugs/2006-04/msg00309.html
that has recently been noted on the Postfix forums.
Was this bug ever actually addressed? In other words, is this an
actual bug or is it working as intended? If it is a bug, and since
it is apparently nearly 5
On Thu, Jan 26, 2012 at 07:48:18AM -0500, Jerry wrote:
There seems to be an old BUG,
http://osdir.com/ml/freebsd-bugs/2006-04/msg00309.html
that has recently been noted on the Postfix forums.
403 Forbidden
Was this bug ever actually addressed? In other words, is this an
actual bug
whether it's a bug or incorrect configuration
on my part. The lang/lua port throws a linker error, claiming to need -fPIC,
which is odd because the port Makefile seems to have logic to add that in,
but somehow the logic seems not to have any effect, at least in my case.
Making the port Makefile put
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with
FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect
configuration on my part. The lang/lua port throws a linker error,
claiming to need -fPIC, which is odd because the port Makefile
On Mon, Jan 23, 2012 at 04:22:30PM -0700, Lee Thomas wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with
FreeBSD 9.0-STABLE, and I'm not sure whether it's a bug or incorrect
configuration on my part. The lang/lua port throws a linker error
On Tue, Jan 24, 2012 at 12:22 AM, Lee Thomas lthomas_li...@lthomas.net wrote:
Hello fellow FreeBSD users,
I ran across an odd issue compiling lua from ports on amd64 with FreeBSD
9.0-STABLE, and I'm not sure whether it's a bug or incorrect configuration
on my part. The lang/lua port throws
HI, Tri.
scp -pr * name@host:/home/dir
does not copy files which have ':' sign in their names
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-questions@freebsd.org mailing list
| grep snmp
root snmpd 233763 /var 588894 -rw-r--r-- 132 w
root snmpd 233768 /var 588872 -rw-r- 728 r
# df -h
/dev/ad0s1d6.7G1.2G 5G19%/var
It seems that that is the BUG of snmpd
# snmpd -v
NET-SNMP version: 5.5
Web
Hi all,
Not sure if this is a bug, but I'm using 8.1-RELEASE-p4 with VIMAGE enabled and
am experiencing something odd.
I set sysctl security.jail.mount_allowed=1 and then fire up a jail, all is good
(jail has value of 1).
I then set sysctl security.jail.enforce_statfs=1 and then restart
Behavior:
tobago# kldload snd_driver
driver bug: Unable to set devclass (devname: (null))
ppc0: parallel port not found.
driver bug: Unable to set devclass (devname: (null))
ppc0: parallel port not found.
ppc0: parallel port not found.
driver bug: Unable to set devclass
On Mon Mar 21 11, Laszlo Nagy wrote:
Hi All,
I have a Python program that goes up to 100% CPU. Just like this (top):
you might want to re-post this message to freebsd-hackers@. in my experience
freebsd-questions@ is suited for user-related questions and not that much
for developers who
Hi All,
I have a Python program that goes up to 100% CPU. Just like this (top):
PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU
COMMAND
80212 user1 2 440 70520K 16212K select 1 0:30 100.00%
/usr/local/bin/python process_updates_ss_od.py -l 10
I
If my bug report is marked [regression] what does that mean?
Am I a troglodyte or a Luddite or something?
--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266
___
freebsd-questions@freebsd.org mailing list
On Sun, 6 Mar 2011, Lars Eighner wrote:
If my bug report is marked [regression] what does that mean?
Am I a troglodyte or a Luddite or something?
Regression is something that used to work but doesn't any more.
___
freebsd-questions@freebsd.org
On Sun 06 Mar 2011 at 10:58:57 PST Warren Block wrote:
On Sun, 6 Mar 2011, Lars Eighner wrote:
If my bug report is marked [regression] what does that mean?
Am I a troglodyte or a Luddite or something?
Regression is something that used to work but doesn't any more.
Like me. I'm retired
I'm posting this in questions because 1) I'm not sure if it's really a defect,
and 2) I'm not sure what other list might be more appropriate.
I've been experimenting with modifications to the i386 platform in STABLE-8 to
support 64-bit time_t values. After changing sys/i386/include/_types.h so
HI, Freebsd-questions.
http://www.freebsd.org/ru/releases/
on this page is wrong information about releases.
Old release is 6.0 and last is 8.1 on march 2006!! year.
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
/Oru4iDF4uPl7ejp?= wrote:
HI, Freebsd-questions.
http://www.freebsd.org/ru/releases/
on this page is wrong information about releases.
Old release is 6.0 and last is 8.1 on march 2006!! year.
Please file a change request:
man send-pr
send-pr
Which both:
- lodgess in bug
Hi, Freebsd-questions.
Nov 18 20:27:54 meta-up kernel:
Nov 18 20:29:11 meta-up kernel: 110ip11f0w: ipfw: 102 102D enyD enTyCP
T1C9P 192.168.2.173:4425 192.168.168.155:445 out via re0
Nov 18 20:32:30 meta-up kernel: 110 iefw: 102 Deny UDP 192.168.2.90:54625
192.168.1.33:59306 out via re0
Nov 18
rree00
This particular bug of overlapping output from multiple-core machines
has been around for years. I don't think it's going to get fixed
anytime soon.
--
Jonathan Chen j...@chen.org.nz
___
freebsd-questions@freebsd.org mailing list
http
Hi, Freebsd-questions.
net.isr.swi_count: -1692211928
as I think count can not be negative. in this case it is.
Is this a bug or negative value means some special?
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd
On Sat Nov 13 10, ??? ??? wrote:
Hi, Freebsd-questions.
net.isr.swi_count: -1692211928
as I think count can not be negative. in this case it is.
Is this a bug or negative value means some special?
what is the output of 'uname -a'? looks like a 32 bit integer is being used
please take a look to my other mail (getgrent related) - there
seems another bug ...
Do you have another one-liner that will reproduce it? A simple
/usr/bin/getent group doesn't return dupes for me. Oddly enough, the
*grent code doesn't use an internal counter, so the bug you found
On 07/16/10 18:13, Dan Nelson wrote:
Hi Dan,
In the last episode (Jul 16), Jens Rehsack said:
On 07/16/10 15:07, Dan Nelson wrote:
In the last episode (Jul 16), Jens Rehsack said:
Could you please take a look to my other mail (getgrent related) - there
seems another bug ...
Do you have
related) - there
seems another bug ...
Do you have another one-liner that will reproduce it? A simple
/usr/bin/getent group doesn't return dupes for me. Oddly enough, the
*grent code doesn't use an internal counter, so the bug you found in
endpwent doesn't exist in endgrent (afaik
to the beginning.
Ah. I missed the endpwent calls.
Was difficult for me to format the single liner ;)
To me it definitely looks like a bug in FreeBSD's getpw*() family of
functions.
As tested using sysutils/lsof, in the following program in FreeBSD, the
descriptor corresponding to '/etc/pwd.db
Jens Rehsack writes:
2010/7/16 Dan Nelson dnel...@allantgroup.com:
[...]
Try the following patch:
Thanks, I'll try it when I'm on my FreeBSD box.
Can I do this without a full world rebuild? (I do not develop in FBSD
actively).
Otherwise I recommend (the test case was in OP) that someone
On 07/16/10 08:36, Ashish SHUKLA wrote:
Jens Rehsack writes:
2010/7/16 Dan Nelsondnel...@allantgroup.com:
[...]
Try the following patch:
Thanks, I'll try it when I'm on my FreeBSD box.
Great \o/
[...]
I had to develop a workaround for all other boxes anyway.
As a workaround you
Jens Rehsack writes:
[...]
I cached the entires - I rate setpwent as to dangerous.
dangerous ? why ?
You can take a look at
http://cpansearch.perl.org/src/REHSACK/DBD-Sys-0.01_01/lib/DBD/Sys/Plugin/Unix/Users.pm
Jens
--
Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9
On 07/16/10 09:12, Ashish SHUKLA wrote:
Jens Rehsack writes:
[...]
I cached the entires - I rate setpwent as to dangerous.
dangerous ? why ?
Because it modifies something - and I might not know the source.
getpwent(3) delivers entries from yp, too (or LDAP) etc. - and
when I call
Jens Rehsack writes:
On 07/16/10 09:12, Ashish SHUKLA wrote:
Jens Rehsack writes:
[...]
I cached the entires - I rate setpwent as to dangerous.
dangerous ? why ?
Because it modifies something - and I might not know the source.
getpwent(3) delivers entries from yp, too (or LDAP) etc.
On 07/16/10 09:59, Ashish SHUKLA wrote:
Jens Rehsack writes:
On 07/16/10 09:12, Ashish SHUKLA wrote:
Jens Rehsack writes:
[...]
I cached the entires - I rate setpwent as to dangerous.
dangerous ? why ?
Because it modifies something - and I might not know the source.
getpwent(3)
Jens Rehsack writes:
[...]
You're absolutely right - I never took a deeper look, because I always
was only interested to read the (user|group) data and expected setpwent
to modify such an entry.
Its UNIX :P
A quick look into Stevens Advanced Programming in the UNIX environment
could had
mentioned) should rewind the position in passwd database to the
beginning.
Ah. I missed the endpwent calls.
Was difficult for me to format the single liner ;)
To me it definitely looks like a bug in FreeBSD's getpw*() family of
functions.
As tested using sysutils/lsof, in the following
and NetBSD's libc (as
OP mentioned) should rewind the position in passwd database to the
beginning.
Ah. I missed the endpwent calls.
Was difficult for me to format the single liner ;)
To me it definitely looks like a bug in FreeBSD's getpw*() family of
functions.
As tested using sysutils/lsof
In the last episode (Jul 16), Jens Rehsack said:
On 07/16/10 15:07, Dan Nelson wrote:
In the last episode (Jul 16), Jens Rehsack said:
Could you please take a look to my other mail (getgrent related) - there
seems another bug ...
Do you have another one-liner that will reproduce
On 07/16/10 18:13, Dan Nelson wrote:
In the last episode (Jul 16), Jens Rehsack said:
On 07/16/10 15:07, Dan Nelson wrote:
In the last episode (Jul 16), Jens Rehsack said:
Could you please take a look to my other mail (getgrent related) - there
seems another bug ...
Do you have another one
Hi all,
I detected an issue with getpwent on my FreeBSD test box:
perl -MData::Dumper -e 'my @e = getpwent(); print Dumper(\...@e);
endpwent(); @e = getpwent(); print Dumper(\...@e); endpwent(); @e =
getpwent(); print Dumper(\...@e); endpwent();'
$VAR1 = [
'root',
'',
In the last episode (Jul 15), Jens Rehsack said:
Hi all,
I detected an issue with getpwent on my FreeBSD test box:
perl -MData::Dumper -e 'my @e = getpwent(); print Dumper(\...@e); endpwent();
@e = getpwent(); print Dumper(\...@e); endpwent(); @e = getpwent(); print
Dumper(\...@e);
is also invoking 'endpwent()' after every 'getpwent()' invocation
which according to GNU/Linux's glibc and NetBSD's libc (as OP mentioned)
should rewind the position in passwd database to the beginning.
To me it definitely looks like a bug in FreeBSD's getpw*() family of
functions.
As tested using
calls.
To me it definitely looks like a bug in FreeBSD's getpw*() family of
functions.
As tested using sysutils/lsof, in the following program in FreeBSD, the
descriptor corresponding to '/etc/pwd.db' is closed on endpwent(3) but
position in database is never rewinded as shown in the output
% mixer vol +4
Setting the mixer vol from 90:90 to 94:94.
% mixer vol -4
Setting the mixer vol from 94:94 to 90:90.
% mixer 95
Setting the mixer vol from 90:90 to 95:95.
% mixer 90
Setting the mixer vol from 95:95 to 90:90.
% mixer +5
Setting the mixer vol from 90:90 to 5:5.
% mixer -5
usage:
Egorka# uname -a
FreeBSD Egorka.noc.kstu-kai.ru 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Thu Apr 15
16:40:38 MSD 2010
Egorka# cd /usr/ports/ports-mgmt/portupgrade
Egorka# make clean
Makefile, line 60: Could not find
/usr/ports/misc/ldconfig_compat/bsd.ldconfig.mk
make: fatal errors encountered --
We use iostat to collect statistics of hard drive activity. We've been seeing
some values for the transaction wait column that look suspicious. This is easy
to reproduce by just running iostat repeatedly over a short period of time, as
I show below. Notice the third from last column. From what
for this?
# for ((i=1; i =100; i++)); do iostat -dxI ad8|tail +3; sleep 5; done
ad8 10291.0 569044.0 151986.0 10164944.0 4294967295 47.7 93
ad8 10304.0 570070.0 152012.0 10185395.0 4294967295 47.6 93
ad8 10312.0 571047.0 152028.0 10204575.0 85 47.5 93
This looks like a bug in iostat
This looks like a bug in iostat. 4294967295 == 2 * 32 - -1
It seems that some call returns (unsigned long)-1, e.g. to indicate a failing
system/library call but iostat still prints the result:
Which _precise_ version of FreeBSD are you using?
Well, that's a good question. The particular
Dear all,
Found this in full-disclosure mailing list.
-- Forwarded message --
From: Kingcope kco...@googlemail.com
Date: Fri, Mar 5, 2010 at 11:19 PM
Subject: [Full-disclosure] FreeBSD and OpenBSD ftpd bug (not exploitable?)
To: full-disclos...@lists.grok.org.uk, bugt
Hello,
I found the solution about why this bug occurs.
http://www.freebsd.org/cgi/query-pr.cgi?pr=125239cat=
I would like to contribute my knowledge to FreeBSD website but do not
know where to start.
Can you let me know what's the next step if I want to submit a solution?
Thank,
--
Jeff Mo
On Wed, Feb 17, 2010 at 6:20 PM, Jeff Mo mo0...@gmail.com wrote:
Hello,
I found the solution about why this bug occurs.
http://www.freebsd.org/cgi/query-pr.cgi?pr=125239cat=
Make use of Submit Followup link.
I would like to contribute my knowledge to FreeBSD website but do not
know where
'
Then load ndisgen module.
Then single step it with `s' it should panic after few steps.
At least this is issue I'm experiencing on amd64, it fails in
DriverEntry().
with the same virtual address as in kern/132672.
I fixed bug that caused panic on amd64 in DriverEntry().
Code is available
Здравствуйте, Ihor.
Вы писали 4 января 2010 г., 20:44:18:
IP Коньков Евгений wrote:
Здравствуйте, Freebsd-questions.
kes# setfib 1 get_last.pl
setfib: get_last.pl: No such file or directory
kes# pwd
/usr/home/kes/
Для продолжения нажмите любую клавишу...
kes# setfib -1
Matthew Seaman wrote:
I'll add your patches and post an updated shar later on.
Done.
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Здравствуйте, Freebsd-questions.
kes# setfib 1 get_last.pl
setfib: get_last.pl: No such file or directory
kes# pwd
/usr/home/kes/
Для продолжения нажмите любую клавишу...
kes# setfib -1 /usr/home/kes/get_last.pl
run is OK!
setfib must use current directory to run programm
or at least must supply
On Mon, Jan 04, 2010 at 08:29:53PM +0200, Коньков Евгений wrote:
Здравствуйте, Freebsd-questions.
kes# setfib 1 get_last.pl
setfib: get_last.pl: No such file or directory
kes# pwd
/usr/home/kes/
Для продолжения нажмите любую клавишу...
kes# setfib -1 /usr/home/kes/get_last.pl
run is OK!
Коньков Евгений wrote:
Здравствуйте, Freebsd-questions.
kes# setfib 1 get_last.pl
setfib: get_last.pl: No such file or directory
kes# pwd
/usr/home/kes/
Для продолжения нажмите любую клавишу...
kes# setfib -1 /usr/home/kes/get_last.pl
run is OK!
setfib must use current directory to
Jeffrey Goldberg wrote:
Alternatively, if someone were sufficiently motived they could put
together an SA utilities port that installs a number of maintenance
scripts which a user can enable.
This sounds like a very good idea to me. As far as I can see, there's only
one script required,
There is an apparent bug in 'spamassassin' regarding 2010 e-mails. The
full story is available here:
http://spamassassin.apache.org/.
There is also a discussion of it on SlashDot:
http://it.slashdot.org/story/10/01/02/0027207/SpamAssassin-2010-Bug
--
Jerry
ges...@yahoo.com
On Sun, 3 Jan 2010 06:19:55 -0500
Jerry ges...@yahoo.com wrote:
There is an apparent bug in 'spamassassin' regarding 2010 e-mails. The
full story is available here:
http://spamassassin.apache.org/.
There is also a discussion of it on SlashDot:
http://it.slashdot.org/story/10/01/02
Matthew Seaman wrote:
Jeffrey Goldberg wrote:
Alternatively, if someone were sufficiently motived they could put
together an SA utilities port that installs a number of maintenance
scripts which a user can enable.
This sounds like a very good idea to me. As far as I can see, there's only
On Jan 3, 2010, at 2:10 PM, Matthew Seaman wrote:
There's a .shar of the new port at:
http://www.infracaninophile.co.uk/sa-utils.shar
Comments, critique are welcome. Unless there are any killer bugs, I'll
send-pr(1) in a week or so.
Thanks for doing that. It looks great to me. I just
On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
Comments, critique are welcome. Unless there are any killer bugs,
I'll send-pr(1) in a week or so.
You have:
: ${daily_sa_compile=YES}
sa-compile is installed by the SA port, but it requires
On Sun, 03 Jan 2010 20:10:19 +
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
Comments, critique are welcome. Unless there are any killer bugs,
I'll send-pr(1) in a week or so.
You have:
: ${daily_sa_compile=YES}
sa-compile is installed by the SA port, but it requires
1 - 100 of 611 matches
Mail list logo
