On Thu, Feb 28, 2008 at 02:34:01PM +, Pete French wrote:
> yesterday I had my first experience of an if_re interface simply stopping
> responding. I ma running 7.0-RELEASE on the machine, but with
> the lates files taken from here:
>
> http://people.freebsd.org/~yongari/re/7.0R/if_re
On Mon, 25 Feb 2008 18:18:26 +0100
Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:
> After the last update, I saw that there had been a lot of fixes for re
> (4) in the source, so I didn't bother with this patch.The machine is
> still up, but I haven't tried any heavy network traffic yet.
Note to se
I tried to install 7.0 on a computer with an ABIT AV8 motherboard. This board
has an integrated NIC and the installer didn't find it.
This same machine works just fine with 6.2.
Any suggestions would be appreciated.
Thanks to all.
___
freebsd-stable@
I think that your patch solved the problem with my 8.0-current.
Thank you..
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> > Marko Lerota wrote:
> > > In http://www.freebsd.org/releases/7.0R/announce.html says
> > >
> > > Updating Existing Systems
> > >
> > > > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> > > > a major version upgrade, so no matter which method you use to update
> >
> Marko Lerota wrote:
> > In http://www.freebsd.org/releases/7.0R/announce.html says
> >
> > Updating Existing Systems
> >
> > > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> > > a major version upgrade, so no matter which method you use to update
> > > an older syste
Bakul Shah wrote:
As I've tried to explain, the difficulty is when you start recompiling
parts of them, e.g. a shared library used by other ports.
Understood.
Hmm... If prior to any recompile such a shared lib was copied
to a compat dir (based on the most recent shared lib *it*
depends on), p
Teemu Korhonen wrote:
Jung-uk Kim wrote:
On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
Did anyone find a solution to the "jerky mouse" -problem? It still
exists in 7.0-RELEASE.
I have pretty much exact same symptoms as in this post:
http://lists.freebsd.org/pipermail/fre
On Fri, 29 Feb 2008 01:57:32 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote:
> Bakul Shah wrote:
> > On Fri, 29 Feb 2008 00:54:55 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >> portupgrade -faP requests to reinstall everything from precompiled
> >> packages. It will only fall back to compil
Marko Lerota wrote:
> In http://www.freebsd.org/releases/7.0R/announce.html says
>
> Updating Existing Systems
>
> > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> > a major version upgrade, so no matter which method you use to update
> > an older system you should rein
Bakul Shah wrote:
On Fri, 29 Feb 2008 00:54:55 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote:
portupgrade -faP requests to reinstall everything from precompiled
packages. It will only fall back to compiling them locally if the
package is unavailable (e.g. for legal reasons).
Second, the rea
On Fri, 29 Feb 2008 00:54:55 +0100 Kris Kennaway <[EMAIL PROTECTED]> wrote:
> portupgrade -faP requests to reinstall everything from precompiled
> packages. It will only fall back to compiling them locally if the
> package is unavailable (e.g. for legal reasons).
>
> Second, the reason for thi
Edwin Groothuis wrote:
On Fri, Feb 29, 2008 at 01:03:31AM +0100, Kris Kennaway wrote:
Edwin Groothuis wrote:
On Fri, Feb 29, 2008 at 12:08:22AM +0100, Marko Lerota wrote:
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
An upgrade of any existing system t
On Fri, Feb 29, 2008 at 01:03:31AM +0100, Kris Kennaway wrote:
> Edwin Groothuis wrote:
> >On Fri, Feb 29, 2008 at 12:08:22AM +0100, Marko Lerota wrote:
> >>In http://www.freebsd.org/releases/7.0R/announce.html says
> >>
> >>Updating Existing Systems
> >>
> >>>An upgrade of any existing system to
Edwin Groothuis wrote:
On Fri, Feb 29, 2008 at 12:08:22AM +0100, Marko Lerota wrote:
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
a major version upgrade, so no matter which method yo
Nothing to stop you using packages if you so wish.
- Original Message -
From: "Marko Lerota" <[EMAIL PROTECTED]>
# portupgrade -faP
etc...
Why!!! Do you know how much time I have to spend with my PC to reinstall
all of this programs from ports? Only openoffice takes one day! And where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marko Lerota wrote:
> In http://www.freebsd.org/releases/7.0R/announce.html says
>
> Updating Existing Systems
>
>> An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
>> a major version upgrade, so no matter which method you use t
Marko Lerota wrote:
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
a major version upgrade, so no matter which method you use to update
an older system you should reinstall any ports yo
On Fri, Feb 29, 2008 at 12:08:22AM +0100, Marko Lerota wrote:
> In http://www.freebsd.org/releases/7.0R/announce.html says
>
> Updating Existing Systems
>
> > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> > a major version upgrade, so no matter which method you use to u
On Feb 28, 2008, at 3:08 PM, Marko Lerota wrote:
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
a major version upgrade, so no matter which method you use to update
an older system you sho
-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-
> [EMAIL PROTECTED]"
>
> __ NOD32 2910 (20080228) Information __
>
> This message was checked by NOD32 antivi
In http://www.freebsd.org/releases/7.0R/announce.html says
Updating Existing Systems
> An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes
> a major version upgrade, so no matter which method you use to update
> an older system you should reinstall any ports you have installed
Hello,
I've updated to the recent RELENG_7 as of 2008/02/28
to try the new kld-add feature in kgdb, among other things
(yes, i do debug kernel modules).
However, now I get an error message;
also I'm unable to use the add-kld command.
For example:
# kgdb -q /boot/kernel/kernel /dev/mem
[GDB will
On Thu, Feb 28, 2008 at 02:47:28PM +, Chris wrote:
> Did they push ahead with release because waiting for the mia dev?
There's a lot of things that go into deciding when to release. The
release cycle this time was not supposed to be as long as it was.
We kept finding showstoppers and needing
David E. Thiel wrote:
On Thu, Feb 28, 2008 at 08:30:17PM +0200, Teemu Korhonen wrote:
Did anyone find a solution to the "jerky mouse" -problem? It still exists
in 7.0-RELEASE.
I experienced some relief from this by switching my single-CPU system
to use hyperthreading, and using an SMP
Jung-uk Kim wrote:
On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
Did anyone find a solution to the "jerky mouse" -problem? It still
exists in 7.0-RELEASE.
I have pretty much exact same symptoms as in this post:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-Janu
On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
> Did anyone find a solution to the "jerky mouse" -problem? It still
> exists in 7.0-RELEASE.
>
> I have pretty much exact same symptoms as in this post:
>
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039599.html
Can y
Jase Thew wrote:
Jase Thew wrote:
John Baldwin wrote:
On Saturday 23 February 2008 03:32:41 pm Dominic Fandrey wrote:
Oliver Herold wrote:
Hi
the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long
time, but after some period it stopped working. This patch from Uwe
Grohnwaldt:
On Thursday 28 February 2008 02:48 pm, Kris Kennaway wrote:
> Jung-uk Kim wrote:
> > On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
> >> Did anyone find a solution to the "jerky mouse" -problem? It
> >> still exists in 7.0-RELEASE.
> >>
> >> I have pretty much exact same symptoms as i
Terrific job!
Thanks for anyone contributed to this fine release :)
On Feb 27, 2008, at 5:32 PM, Ken Smith wrote:
Just in case some interested parties are not subscribed to the
freebsd-announce mailing list... FreeBSD 7.0-RELEASE has been
formally
released. If you would like to see the rel
Jase Thew wrote:
John Baldwin wrote:
On Saturday 23 February 2008 03:32:41 pm Dominic Fandrey wrote:
Oliver Herold wrote:
Hi
the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long
time, but after some period it stopped working. This patch from Uwe
Grohnwaldt:
http://www.freebs
John Baldwin wrote:
On Saturday 23 February 2008 03:32:41 pm Dominic Fandrey wrote:
Oliver Herold wrote:
Hi
the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long
time, but after some period it stopped working. This patch from Uwe
Grohnwaldt:
http://www.freebsd.org/cgi/query-pr
Jung-uk Kim wrote:
On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
Did anyone find a solution to the "jerky mouse" -problem? It still
exists in 7.0-RELEASE.
I have pretty much exact same symptoms as in this post:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/0395
On Thursday 28 February 2008 01:30 pm, Teemu Korhonen wrote:
> Did anyone find a solution to the "jerky mouse" -problem? It still
> exists in 7.0-RELEASE.
>
> I have pretty much exact same symptoms as in this post:
>
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039599.html
No.
Teemu Korhonen wrote:
Did anyone find a solution to the "jerky mouse" -problem? It still
exists in 7.0-RELEASE.
I have pretty much exact same symptoms as in this post:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039599.html
Part of the problem here is that these "symptoms"
On Thu, Feb 28, 2008 at 08:30:17PM +0200, Teemu Korhonen wrote:
> Did anyone find a solution to the "jerky mouse" -problem? It still exists
> in 7.0-RELEASE.
I experienced some relief from this by switching my single-CPU system
to use hyperthreading, and using an SMP kernel. On dual-core machines
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada wrote:
> > You're not getting responses back from __any__ of those NTP servers. If
> > you have a firewall *in front* of your BSD box (meaning a separate box,
> > not ipfw/ipfilter/pf on the same BSD box!), then this is likely the
> > c
Did anyone find a solution to the "jerky mouse" -problem? It still
exists in 7.0-RELEASE.
I have pretty much exact same symptoms as in this post:
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039599.html
___
freebsd-stable@freebsd.org
Thank you all for answers.
I guess i'll use stable (R_7) in home and release (R_7_0 for now) on servers
Have a good rebuilding night! :>
Stefan Lambrev wrote ..
> Greetings,
>
> Georgi Iovchev wrote:
> >Congrats :))
> >
> >I have been waiting it :>>
> >
> >p.s. yesteday csuped sour
[Please wrap your posts before 80 columns
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada wrote:
>> You're not getting responses back from __any__ of those NTP servers. If
>> you have a firewall *in front* of your BSD box (meaning a separate box,
>> not ipfw/ipfilter/pf on the same
Clifton Royston wrote:
On Thu, Feb 28, 2008 at 02:39:35PM +, Chris wrote:
On 28/02/2008, Krassimir Slavchev <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Chadwick wrote:
On Wed, Feb 27, 2008 at 11:15:30PM -0800, Doug Hardie wrote:
I have just installed 7.
On Thu, Feb 28, 2008 at 02:39:35PM +, Chris wrote:
> On 28/02/2008, Krassimir Slavchev <[EMAIL PROTECTED]> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > Jeremy Chadwick wrote:
> > > On Wed, Feb 27, 2008 at 11:15:30PM -0800, Doug Hardie wrote:
> > >> I have just installed 7.0
On Feb 28, 2008, at 9:39 AM, Chris wrote:
Ahh thats useful, on the occasions I have remotely installed freebsd
over linux I have always failed due to incorrectly guessing the hd id
and as such a wrong fstab, if I know it will always be ad0 and ad1 and
so on it makes this much easier.
I much p
>
> If you replace the disk and you still continue to see DMA errors, then
> my vote would be that you're experiencing the same thing others (and
> myself, on one occasion) are. I've done my best to bring this issue to
> the attention of proper people in recent days, and that's all I can say
> on
On 28/02/2008, Krassimir Slavchev <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeremy Chadwick wrote:
> > On Wed, Feb 27, 2008 at 11:15:30PM -0800, Doug Hardie wrote:
> >> I have just installed 7.0 on some new hardware. Have never tried earlier
> >> versions. T
yesterday I had my first experience of an if_re interface simply stopping
responding. I ma running 7.0-RELEASE on the machine, but with
the lates files taken from here:
http://people.freebsd.org/~yongari/re/7.0R/if_re.c
http://people.freebsd.org/~yongari/re/7.0R/if_rlreg.h
Luckily
On Thu, Feb 28, 2008 at 09:02:20PM +0700, Pongthep Kulkrisada wrote:
> > You're not getting responses back from __any__ of those NTP servers. If
> > you have a firewall *in front* of your BSD box (meaning a separate box,
> > not ipfw/ipfilter/pf on the same BSD box!), then this is likely the
> > c
> You're not getting responses back from __any__ of those NTP servers. If
> you have a firewall *in front* of your BSD box (meaning a separate box,
> not ipfw/ipfilter/pf on the same BSD box!), then this is likely the
> cause of the problem.
The question is that two weeks ago, with same machine, s
Greetings,
Georgi Iovchev wrote:
Congrats :))
I have been waiting it :>>
p.s. yesteday csuped sources and rebuilded world,
but my tag in supfile was RELENG_7 not 7_0
RELENG_7 will show 7.0-STABLE.
If you want release use RELENG_7_0.
I guess there is not big difference between
On Thu, Feb 28, 2008 at 02:32:11PM +0200, Georgi Iovchev wrote:
>p.s. yesteday csuped sources and rebuilded world,
>but my tag in supfile was RELENG_7 not 7_0
>and now in dmesg i am stil getting FreeBSD 7 PRERELEASE
>is this a problem, and should i csup again and rebuild world again
> Congrats :))
>
> I have been waiting it :>>
>
> p.s. yesteday csuped sources and rebuilded world,
>
> but my tag in supfile was RELENG_7 not 7_0
>
> and now in dmesg i am stil getting FreeBSD 7 PRERELEASE
>
> is this a problem, and should i csup again and rebuild world again?
>
>
Georgi Iovchev wrote:
Congrats :))
I have been waiting it :>>
p.s. yesteday csuped sources and rebuilded world,
but my tag in supfile was RELENG_7 not 7_0
and now in dmesg i am stil getting FreeBSD 7 PRERELEASE
is this a problem, and should i csup again and rebuild world ag
Congrats :))
I have been waiting it :>>
p.s. yesteday csuped sources and rebuilded world,
but my tag in supfile was RELENG_7 not 7_0
and now in dmesg i am stil getting FreeBSD 7 PRERELEASE
is this a problem, and should i csup again and rebuild world again?
Georgi Iovchev
David Marec wrote:
Le Thursday 28 February 2008 12:32:28 David Marec, vous avez écrit :
I am trying to use the freebsd-update script for the first time.
sh -x freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
freebsd update requires a known state to upgrade from, i.e. so it c
On Thu, 2008-02-28 at 11:44 +, Gavin Atkinson wrote:
> On Thu, 2008-02-28 at 12:01 +0100, Huub Schuurmans wrote:
> >
> >
> > > I have a problem running the Atheros AR5414 wireless mini-pci-card
> > > (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a
> > > Soekris 452
Le Thursday 28 February 2008 12:32:28 David Marec, vous avez écrit :
> I am trying to use the freebsd-update script for the first time.
sh -x freebsd-update.sh -f freebsd-update.conf -r 7.0-RELEASE upgrade
--
+ fetch -q http://update1.FreeBSD.org/6.3-STABLE/i386/pub.ssl
+ true
+ [ -r pub.ssl ]
Le Wednesday 27 February 2008 23:32:55 Ken Smith, vous avez écrit :
> http://www.freebsd.org/releases/7.0R/announce.html
>
> On behalf of the FreeBSD Project thanks for your interest in FreeBSD.
> We hope you enjoy the new release.
I am trying to use the freebsd-update script for the first time
On Thu, 2008-02-28 at 12:01 +0100, Huub Schuurmans wrote:
>
>
> > I have a problem running the Atheros AR5414 wireless mini-pci-card
> > (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a
> > Soekris 4521.
>
> Problem with the ath driver appears to have been solved after
Thank you all and Congrats! :)
Regards,
-Abdullah Ibn Hamad Al-Marri
Arab Portal
http://www.WeArab.Net/
- Original Message
> From: Ken Smith <[EMAIL PROTECTED]>
> To: freebsd-stable ; [EMAIL PROTECTED]
> Sent: Thursday, February 28, 2008 1:32:55 AM
> Subject: FreeBSD 7.0-RELEASE Availa
> I have a problem running the Atheros AR5414 wireless mini-pci-card
> (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a
> Soekris 4521.
Problem with the ath driver appears to have been solved after I
installed a custom kernel replacing the GENERIC kernel.
Huub
__
On Thu, Feb 28, 2008 at 01:19:43AM -0800, Jeremy Chadwick wrote:
> On Thu, Feb 28, 2008 at 09:24:43AM +0100, Thomas Krause wrote:
> > Dear list,
> >
> > as described in http://www.freebsd.org/releases/6.3R/announce.html
> > I tried a binary upgrade to 6.3R. But the command
> >
> > # sh freebsd-upd
>>
>> failed with
>>
>> 102520253025402550256025702580259026002610262026302640...
>> done.
>> Applying patches... done.
>> Fetching 1587 files... failed.
>
> Is this reproducable or is this fetch problem an one time issue?
Yes, it is. I put a "se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Chadwick wrote:
> On Wed, Feb 27, 2008 at 11:15:30PM -0800, Doug Hardie wrote:
>> I have just installed 7.0 on some new hardware. Have never tried earlier
>> versions. There are a couple of unexpected items that I do not understand.
>>
>> 2.
Nope, I'm on the latest official one (1.9 with .47 for the SI3112). I guess
it's hopeless then...
"Andrey V. Elsukov" <[EMAIL PROTECTED]> escribió: Jisakiel wrote:
> Is there any way to make this card work on FreeBSD 7, or anything
> else that I could try?
Did you find any new BIOS versions fo
On Thu, Feb 28, 2008 at 09:24:43AM +0100, Thomas Krause wrote:
> Dear list,
>
> as described in http://www.freebsd.org/releases/6.3R/announce.html
> I tried a binary upgrade to 6.3R. But the command
>
> # sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade
>
> failed with
>
> 10
On Thu, Feb 28, 2008 at 09:24:43AM +0100, Thomas Krause wrote:
> Dear list,
>
> as described in http://www.freebsd.org/releases/6.3R/announce.html
> I tried a binary upgrade to 6.3R. But the command
>
> # sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade
>
> failed with
>
> 10
Dear list,
as described in http://www.freebsd.org/releases/6.3R/announce.html
I tried a binary upgrade to 6.3R. But the command
# sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade
failed with
102520253025402550256025702580259026002610..
On Wed, Feb 27, 2008 at 08:04:10PM +0100, Patrick M. Hausen wrote:
> Hello,
>
> On Wed, Feb 27, 2008 at 09:18:31AM -0800, Jeremy Chadwick wrote:
>
> > I think you're looking for all the WITHOUT knobs in src.conf(5).
>
> I'm running RELENG_6_3 on production machines unlikely to change
> any time
68 matches
Mail list logo
