On Sat, May 06, 2006 at 12:10:46AM -0400, Miles Lubin wrote:
> I know this is rather late in the release process, but given that this
> issue will affect many people, I think it should be considered fixing
> this driver for 6.1.
The release is imminent. The last Ts are being crossed and Is dott
On Fri, 5 May 2006, Bjoern A. Zeeb wrote:
On Fri, 5 May 2006, Wilko Bulte wrote:
I had a similar event last night, on a P4 on an Asus P4P800. The current
driver is much less prone to this lockup problem than it used to be. In my
case it does not have to be in a high-load situation, it appear
On Fri, 5 May 2006 10:01:09 +0930
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> On Friday 05 May 2006 07:41, Rostislav Krasny wrote:
> > write the same file to the same floppy I didn't run umount and it crashed
> > again. Following are footsteps of the first crash, founded in the
> > /var/log/mes
Last night I updated on of my machines from 6.0-RELEASE to 6.1-RC. As
far as I understand, I followed the instructions correctly - in particular:
boot -s
# fsck -p
# mount -u /
# mount -a
# adjkerntz -i
# cd /usr/src
# mergemaster -p
# make installworld
I found that installworld stops, because
On Saturday 06 May 2006 09:33, Rostislav Krasny wrote:
> > Can you get a back trace? ie enable crash dumps and do it again, or
> > transcribe, or photograph the screen as it panics if you are local.
>
> Unfortunately I cannot reproduce it now. Doesn't the old log help?
> There is one "Fatal trap 12
On Saturday 06 May 2006 00:34, David Coder wrote:
> thx for the suggestions, guys. with
>
> device uftdi
> device uplcom
You can just kldload these BTW.
Saves time when testing :)
> in the kernel config the adapter shows up as
>
> ugen0: ArkMicroChips USB-UART Controller, rev 1
[I've seen some comments here about people struggling w/ mga_hal, so I
thought I'd share this.]
I wanted to use features of the Matrox mga x11 driver (dual headed
digital video) that required the hal, but I wasn't able to get the
mga_hal port to work with Xorg 6.9.
I cobbled up an underhanded h
Mike Jakubik wrote:
arrive at the sacrifice of stability. I think FreeBSD should only be
released when known major bugs are worked out. A known broken release to
me and most new users is useless, lets not release simply for the sake
of numbering.
For me, and many other quiet users, FreeBSD *I
On Fri, May 05, 2006 at 08:26:54PM +, Bjoern A. Zeeb wrote..
> On Fri, 5 May 2006, Wilko Bulte wrote:
>
> >On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote..
> >>My motherboard has a built-in ethernet port that is handled by the sk
> >>driver. I'm running FreeBSD 6.1-RC on amd64. Wh
On Fri, 5 May 2006, Wilko Bulte wrote:
On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote..
My motherboard has a built-in ethernet port that is handled by the sk
driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is
under high load, it often kills any current connection
> From: Nik Clayton <[EMAIL PROTECTED]>
>
> I've got an IBM T42 laptop that's currently running 5.4, and it's working
> nicely at the moment. ACPI works well enough that suspend to RAM works
> ('zzz'), the audio works, USB devices are recognised, and the battery life's
> reasonable (with est en
My vote goes to PureFtpd..
It`s ideal server..
On 5/4/06, N.J. Thomas <[EMAIL PROTECTED]> wrote:
* Noah <[EMAIL PROTECTED]> [2006-05-04 05:48:40 -0800]:
> What are people using for their ftpd these days? I am looking for
> something easy to initiailize, configure, and is very secure.
Anothe
On Fri, 5 May 2006, Paul Allen wrote:
One detail of this has to do with version numbering. The FreeBSD version
number says a lot more about the userland than it does about the kernel per
se.
If we were to version the kernel arch, I think it would look more like this:
'94 1.1.5.1 (Last N
Guys,
I appreciate the attempts at rational explaination from camp A, and
I appreciate the flood of emotional outpouring from camp B. However:
Mike Jakubik, David Kirchner, and others: You are making a mountain out
of a molehill and exploiting the unprecendented openness of the release
engineer
Mark Linimon wrote:
Make Jakubik wrote:
FreeBSD users now demand stability and performance, as opposed to an
influx of new bells and whistles just before the release [...] I fully
understand that this is a volunteer project [...]
I'm sorry, but the former statement proves the latter f
On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote..
> My motherboard has a built-in ethernet port that is handled by the sk
> driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is
> under high load, it often kills any current connections and leaves the
> message "sk0: w
Mike Tancsa wrote:
At 02:27 PM 05/05/2006, Mike Jakubik wrote:
This quota/nve problem sure stirred things up, i guess im partly to
blame, but anyway i think that it all boils down to is this; FreeBSD
users now demand stability and performance, as opposed to an influx
of new bells and
I think
Make Jakubik wrote:
> FreeBSD users now demand stability and performance, as opposed to an
> influx of new bells and whistles just before the release [...] I fully
> understand that this is a volunteer project [...]
I'm sorry, but the former statement proves the latter false.
Let's try to do our
Scott Long wrote:
Please contact me privately with a list of issues on the 6.1 TODO list
that are presently affecting you, and I will personally resolve them for
you.
Scott, thanks for the very generous gesture, but i cant ask you
something like this. The problems that are affecting me are qu
At 02:27 PM 05/05/2006, Mike Jakubik wrote:
This quota/nve problem sure stirred things up, i guess im partly to
blame, but anyway i think that it all boils down to is this; FreeBSD
users now demand stability and performance, as opposed to an influx
of new bells and
I think you *are* forgettin
One detail of this has to do with version numbering.
The FreeBSD version number says a lot more about the
userland than it does about the kernel per se.
If we were to version the kernel arch, I think it would
look more like this:
'94 1.1.5.1 (Last Net/2) Version 0
Nov '94 2.0
Mike Jakubik wrote:
This quota/nve problem sure stirred things up, i guess im partly to
blame, but anyway i think that it all boils down to is this; FreeBSD
users now demand stability and performance, as opposed to an influx of
new bells and whistles just before the release. FreeBSD already has
On Fri, 5 May 2006, Mike Jakubik wrote:
This quota/nve problem sure stirred things up, i guess im partly to blame,
but anyway i think that it all boils down to is this; FreeBSD users now
demand stability and performance, as opposed to an influx of new bells and
whistles just before the releas
This quota/nve problem sure stirred things up, i guess im partly to
blame, but anyway i think that it all boils down to is this; FreeBSD
users now demand stability and performance, as opposed to an influx of
new bells and whistles just before the release. FreeBSD already has many
great features
Hello,
I recently replaced a DVD Automated Burner unit with a newer model. The
older model used firewire for the drive interface and dvd+rw-tools
worked fine.
The new model uses USB 2.0 ports (1 for each drive.) Unfortunately, it
seems that dvd+rw-tools no longer seems to work. Running
dvd+rw-
On 5/5/06, Pawel Jakub Dawidek <[EMAIL PROTECTED]> wrote:
It isn't good to release a software with known, documented bugs, but its
better than shipping an untested software with god-one-knows unknown
bugs.
There's another reasonable option: the known buggy code could be
disabled by default, and
Hi -
I have an install base of machines running MIT Krb5 (which have their
own com_err implementation), and I have always used NO_KERBEROS=true so
that the integrated Heimdal stuff wouldn't be built during a buildworld.
However libcom_err does, and that causes issues when trying to link in
progra
> >Is anyone aware of any regressions in laptop functionality going from 5.4
> >to
> >6.x?
If you're worried, just burn a FreeSBIE first.
Paul
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
My motherboard has a built-in ethernet port that is handled by the sk
driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is
under high load, it often kills any current connections and leaves the
message "sk0: watchdog timeout" in dmesg. I've seen previous posts on this
issue, bu
Hi,
> On Fri, 5 May 2006 09:46:22 +0200
> Jan Gyselinck <[EMAIL PROTECTED]> said:
> Which application did you use? The application which doesn't use
> getaddrinfo(3) has this issue, and it cannot be fixed without
> re-writing the application to use getaddrinfo(3).
Jan> konqueror, which
On May 5, 2006, at 11:04 AM, David Coder wrote:
thx for the suggestions, guys. with
device uftdi
device uplcom
you should really only need one of these.
in the kernel config the adapter shows up as
ugen0: ArkMicroChips USB-UART Controller, rev 1.10/0.01, addr 2
thx for the suggestions, guys. with
device uftdi
device uplcom
in the kernel config the adapter shows up as
ugen0: ArkMicroChips USB-UART Controller, rev 1.10/0.01, addr 2
no specific com port shows up, however, so i must need something else.
David Coder
Network Eng
On Thu, May 04, 2006 at 04:59:33PM -0700, David Kirchner wrote:
> Here's how to reproduce the snapshot deadlock I'm seeing, with 6.1-RC2
> cvsup'd as of 5 or 6 hours ago:
>
> 1) dd if=/dev/zero of=/usr/bigfile bs=1024 seek=209715200 count=0
> 2) mdconfig -a -t vnode -f /usr/bigfile
> 3) bsdlabel -
On Thu, May 04, 2006 at 01:54:58AM -0400, Mike Jakubik wrote:
+> Kris Kennaway wrote:
+> >On Thu, May 04, 2006 at 12:41:57AM -0400, Mike Jakubik wrote:
+> >>Then why utilize a known non-functional technology?
+> >>
+> >
+> >Because again, the benefits have been judged by the decision-makers
+>
On Fri, May 05, 2006 at 08:38:20AM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> > On Mon, 1 May 2006 20:46:40 +0200
> > Jan Gyselinck <[EMAIL PROTECTED]> said:
>
> Jan> What I find strange though, is the fact it's now applying the searchlist
> Jan> to get an answer on the query. Other tha
Hi,
I have just upgraded some of our product build machines to 6.1RC2 and I
am having a few problems getting a custom install.cfg to work with the
way sysinstall now selects/installs kernels. I am trying to select a
custom distribution set using something like the following:
dists=base kerne
36 matches
Mail list logo
