Re: My project wish-list for the next 12 months

2004-12-01 Thread Miguel Mendez
On Thu, 02 Dec 2004 10:44:32 +0530
"Kamal R. Prasad" <[EMAIL PROTECTED]> wrote:

[Please don't top-post]

> I find X windows to be a bit too compute intensive. Maybe something
> like apple's interface would be a good alternative [for those who
> don't need X-windows' powerful graphic features].

What makes you think so? X was originally desgined for systems with
little memory and processing power, certainly a lot less than today's
AMD and Intel space heaters. There are some features that do indeed
require more CPU, like antialiasing. That's the price to pay for eye
candy. Things like the composite and damage extensions do wonders to
help in those areas and make things like true transparency and alpha
blending possible. So, in time, X won't be that different from Aqua in
its use of hardware.

The lack of speed in some apps can be blamed mostly on the toolkits.
GTK+ 1.2 was a speed demon, GTK+ 2.x is a lot slower. There are some
people working on a fast Pango code path that could make english text
rendering fast again.

X gives you network transparency out of the box. I used an old SGI Indy
as an X term to connect to my FreeBSD box for years, and it worked like
a charm over a 10Mbit connection.

Replacing X means writing something that's API compatible, or writing an
X server on top of your new display system, so that you don't have to
throw the thousands of X apps into the trashcan.

About some of the other comments in the thread. IMHO using bsdinstaller
as a base could be beneficial for both groups and save duplicated work.
I'm sure they'll be glad to get internacionalization patches.

I agree that a journaled filesystem is really needed if you want to
manage multi TiB partitions. As rock solid and tested softupdates is,
fsck is not an acceptable solution in this case. Some people were
working on a port of XFS, has any progress been made? I tried contacting
them some time ago, but never got an answer. Sounds like a very
interesting, though.

Cheers,
-- 
Miguel Mendez <[EMAIL PROTECTED]> | lea gfx_lib(pc),a1
http://www.energyhq.es.eu.org| moveq   #0,d0
PGP Key: 0xDC8514F1  | move.l  4.w,a6
Note: All HTML mail goes to /dev/null| jsr -552(a6)



pgpciGqFVPARp.pgp
Description: PGP signature


Re: My project wish-list for the next 12 months

2004-12-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]>
John Hay <[EMAIL PROTECTED]> writes:
: > > 1.  Keyboard multiplexer.
: > 
: > I actually fail to stop thinking about a complete syscons and pcvt
: > replacement. You know, the one and only console implementation that
: > makes all others obsolete. Big plans, little time, yada yada yada...
: 
: It would be nice if one would still be able to use the keyboards
: separately too, even if you have to recompile the kernel for that.
: One nice usage would be on HP's quad kiosk machine. It is a single
: processor box with 4 x screen, keyboard and mouse, and then 4 people
: can use it.

I think that making it just another driver that knows about the
keyboard mux would make this possible in the short term...

Hmmm, maybe it is time for me to STFU and hack together what I'm
thinking :-)

Warner

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread John Hay
> > 
> > 1.  Keyboard multiplexer.
> 
> I actually fail to stop thinking about a complete syscons and pcvt
> replacement. You know, the one and only console implementation that
> makes all others obsolete. Big plans, little time, yada yada yada...

It would be nice if one would still be able to use the keyboards
separately too, even if you have to recompile the kernel for that.
One nice usage would be on HP's quad kiosk machine. It is a single
processor box with 4 x screen, keyboard and mouse, and then 4 people
can use it.

John
-- 
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Kamal R. Prasad
I find X windows to be a bit too compute intensive. Maybe something like 
apple's interface would be a good alternative [for those who don't need 
X-windows' powerful graphic features].

regards
-kamal
Scott Long wrote:
Jason C. Wells wrote:
--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long 
<[EMAIL PROTECTED]> wrote:

5.  Clustered FS support.  SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful.  RedHat recently bought Sistina and re-opened the GFS source
code, so exploring this would be very interesting.

This sounds very close to OpenAFS.  I don't know what distinguishes a 
SAN from other types of NAS.  OpenAFS does everything you mentioned 
in the above paragraph.  OpenAFS _almost_ works on FreeBSD right now.

Later,
Jason C. Wells

Well, AFS requires an intelligent node in front of each disk.  True SAN
clustering means that you have a web of disks directly connected to the
SAN (iSCSI, FibreChannel, etc), and two or more servers on the SAN that
see those disks as a single filesystem (actually a bit more complicated
than this, but you get the point).  If one server goes down, no access
to data is lost since the disks can be reached from any other server on
the SAN that is participating in the clustered FS.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]>
Scott Long <[EMAIL PROTECTED]> writes:
: 1.  Keyboard multiplexer.  We are running into problems with making
: ps/2 and USB/bluetooth keyboards work together and work with KVMs.
: Having a virtual keyboard device that multiplexes the various real
: keyboard devices and handles hotplug can solve this mess pretty
: effectively.  I know that there has been a lot of talk about this on
: mailing lists recently but I don't know how much progress is being made
: so I'm listing it here.

There aready are multiplexers in the kernel.  The problem is that we
need a many to one mux that is the OR of all the ones installed.  We
can current set WHICH keyboard is connected to the mux, but can't say
'ALL OF THEM' at all.  I believe that Brooks Davis has said he's
working on this.

Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Scott Long
Foxfair Hu wrote:
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
All,
[]
1.  Keyboard multiplexer.  We are running into problems with making
ps/2 and USB/bluetooth keyboards work together and work with KVMs.
Having a virtual keyboard device that multiplexes the various real
keyboard devices and handles hotplug can solve this mess pretty
effectively.  I know that there has been a lot of talk about this on
mailing lists recently but I don't know how much progress is being made
so I'm listing it here.

   How about reuse NetBSD's wscons ? I've kept an eye on it and thought
it should be a good start for FreeBSD.
foxfair
If it provides keyboard mux'ing like we need, then please go and
give it a shot.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Peter Kieser
Scott Long wrote:
2.  New installer.  I know some people still consider this a joke, but
the reality is that sysinstall is no longer state of the art.  It's
fairly good at the simple task that it does, but it's becoming harder
and harder to fix bugs and extend functionality in it.  It's also
fairly unfriendly to those of us who haven't been using it since 1995.
The DFly folks have some very interesting work in this area
(www.bsdinstaller.com) and it would be very good to see if we can
collaborate with them on it.

Please, don't change /stand/sysinstall *too* much, there is really 
nothing wrong with the interface of it, and it's what makes FreeBSD so 
"quick" to install. At the very least, make sure you do NOT go for an 
XFree86 installation, and keep to the "KISS" approach. Visually wise, 
theres nothing wrong with the current installer.. and its one of the 
things I "promote" about FreeBSD -- the ease to install. It's small, its 
fast.. and it works, however in error situations it does mess up badly.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Foxfair Hu
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
> All,
> 
[]
> 
> 1.  Keyboard multiplexer.  We are running into problems with making
> ps/2 and USB/bluetooth keyboards work together and work with KVMs.
> Having a virtual keyboard device that multiplexes the various real
> keyboard devices and handles hotplug can solve this mess pretty
> effectively.  I know that there has been a lot of talk about this on
> mailing lists recently but I don't know how much progress is being made
> so I'm listing it here.

   How about reuse NetBSD's wscons ? I've kept an eye on it and thought
it should be a good start for FreeBSD.


foxfair



pgphRpubvLcFv.pgp
Description: PGP signature


Re: My project wish-list for the next 12 months

2004-12-01 Thread Scott Long
Marcel Moolenaar wrote:
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
1.  Keyboard multiplexer.

I actually fail to stop thinking about a complete syscons and pcvt
replacement. You know, the one and only console implementation that
makes all others obsolete. Big plans, little time, yada yada yada...

2.  New installer.

It may actually be interesting to see if we can make an expert
system for this. When I think about implementing an installer (alas
I've been doing that), I'm not so much interested in how things are
packaged, or how it looks but rather what needs to be done, when and
how all these actions relate and interact with each other. This is
especially tricky when actions are triggered by the current
configuration of the machine onto which one tries to install. Knowing
all the possible activities and their dependencies should help
establish a control flow through the installation process in such a
way that users get asked only those questions that are relevent and
also when it matters. One puts a UI on top of this to get a nice
looking installer. At least, that's how I look at it...
Yeah, I've had many similar thoughts.  The hard part of a new installer,
or any complex UI application, is the framework that ties events and
actions together.  The easy part is writing the modules on top of that
that do the discrete actions.  While I see quite a few rough edges in
the upper layers of the DF installer, it seems like quite a bit of work
is going into the framework, and that's why I'm actually so interested
in it.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Marcel Moolenaar
On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote:
> 
> 1.  Keyboard multiplexer.

I actually fail to stop thinking about a complete syscons and pcvt
replacement. You know, the one and only console implementation that
makes all others obsolete. Big plans, little time, yada yada yada...

> 2.  New installer.

It may actually be interesting to see if we can make an expert
system for this. When I think about implementing an installer (alas
I've been doing that), I'm not so much interested in how things are
packaged, or how it looks but rather what needs to be done, when and
how all these actions relate and interact with each other. This is
especially tricky when actions are triggered by the current
configuration of the machine onto which one tries to install. Knowing
all the possible activities and their dependencies should help
establish a control flow through the installation process in such a
way that users get asked only those questions that are relevent and
also when it matters. One puts a UI on top of this to get a nice
looking installer. At least, that's how I look at it...

-- 
 Marcel Moolenaar USPA: A-39004  [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Dan Nelson
In the last episode (Dec 01), Jason C. Wells said:
> --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long 
> <[EMAIL PROTECTED]> wrote:
> 
> >5.  Clustered FS support.  SANs are all the rage these days, and
> >clustered filesystems that allow data to be distributed across many
> >storage enpoints and accessed concurrently through the SAN are very
> >powerful.  RedHat recently bought Sistina and re-opened the GFS source
> >code, so exploring this would be very interesting.
> 
> This sounds very close to OpenAFS.  I don't know what distinguishes a
> SAN from other types of NAS.  OpenAFS does everything you mentioned
> in the above paragraph.  OpenAFS _almost_ works on FreeBSD right now.

OpenAFS is a network-centric system that replicates data across its
nodes, I think, and each node has a cache.  A clustered filesystem uses
a single block of shared storage (usually on a fibre-channel SAN, but
you can also use shared scsi on a 2-machine cluster) that all servers
access directly.  The magic is getting the locking right to make sure
the servers don't stomp on each other's data.  Extremely useful for
server farms that need to share large files, or even lots of small
files (webservers for example).

-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Scott Long
Jason C. Wells wrote:
--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long 
<[EMAIL PROTECTED]> wrote:

5.  Clustered FS support.  SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful.  RedHat recently bought Sistina and re-opened the GFS source
code, so exploring this would be very interesting.

This sounds very close to OpenAFS.  I don't know what distinguishes a 
SAN from other types of NAS.  OpenAFS does everything you mentioned in 
the above paragraph.  OpenAFS _almost_ works on FreeBSD right now.

Later,
Jason C. Wells
Well, AFS requires an intelligent node in front of each disk.  True SAN
clustering means that you have a web of disks directly connected to the
SAN (iSCSI, FibreChannel, etc), and two or more servers on the SAN that
see those disks as a single filesystem (actually a bit more complicated
than this, but you get the point).  If one server goes down, no access
to data is lost since the disks can be reached from any other server on
the SAN that is participating in the clustered FS.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Kris Kennaway
On Wed, Dec 01, 2004 at 03:29:10PM -0800, Jason C. Wells wrote:
> --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long 
> <[EMAIL PROTECTED]> wrote:
> 
> >5.  Clustered FS support.  SANs are all the rage these days, and
> >clustered filesystems that allow data to be distributed across many
> >storage enpoints and accessed concurrently through the SAN are very
> >powerful.  RedHat recently bought Sistina and re-opened the GFS source
> >code, so exploring this would be very interesting.
> 
> This sounds very close to OpenAFS.  I don't know what distinguishes a SAN 
> from other types of NAS.  OpenAFS does everything you mentioned in the 
> above paragraph.  OpenAFS _almost_ works on FreeBSD right now.

I'd be very interested to try using this for package builds, btw.
Currently I have to rsync a lot of data to the remote build clients,
which takes a very long time.

Kris


pgpfdwcYMSTUZ.pgp
Description: PGP signature


Re: My project wish-list for the next 12 months

2004-12-01 Thread Scott Long
Kris Kennaway wrote:
On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote:

Another issue I had with the dfly installer was one point I believe needs
to be central to any next-gen installer. Internationalisation.

Careful not to pile on so many wishes that achieving anything becomes
impossible.  Our current installer doesn't do this, so it's not a hard
requirement that a better installer should.
Kris
Internationalization is actually quite important, and is not easy to
bolt on after the fact but is fairly easy to program to once the core is
in place.  The fact that sysinstall doesn't have it makes it no less
important.  Now this isn't a reason to reject the DFly work, but it
could certainly be a good area for someone to contribute.
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Kris Kennaway
On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote:

> Another issue I had with the dfly installer was one point I believe needs
> to be central to any next-gen installer. Internationalisation.

Careful not to pile on so many wishes that achieving anything becomes
impossible.  Our current installer doesn't do this, so it's not a hard
requirement that a better installer should.

Kris


pgp53kTmYZYNU.pgp
Description: PGP signature


Re: My project wish-list for the next 12 months

2004-12-01 Thread Ryan Sommers

Scott Long said:
> 2.  New installer.  I know some people still consider this a joke, but
> the reality is that sysinstall is no longer state of the art.  It's
> fairly good at the simple task that it does, but it's becoming harder
> and harder to fix bugs and extend functionality in it.  It's also
> fairly unfriendly to those of us who haven't been using it since 1995.
> The DFly folks have some very interesting work in this area
> (www.bsdinstaller.com) and it would be very good to see if we can
> collaborate with them on it.

I've spent a good deal of time taking notes and diagrams of what I wanted
from a new installer. However, time constraints have kept me from actually
putting any of it to code yet.

I've looked at the DFly installed quite a bit and I like what it offers,
however, I have a few complaints with it. Quite honestly I wasn't
impressed with the code.

Another issue I had with the dfly installer was one point I believe needs
to be central to any next-gen installer. Internationalisation. My idea of
an installer front-end would use a dynamically loadable language library.
All resources of the front-end (ie strings, images, etc) would be packaged
into a seperate language-pack. These language-packs can then be grouped
together into a language library. A few basic packs would be distributed
with the default library but other libraries could easily be substituted
to make localized distribution sets with little trouble.

The benefit of this is that instead of translating the code you would only
need to translate the language-(pack|library). I think this would greatly
simplify translation and make a seperation between language and the
front-end code.

This is where my complaint with Dfly comes in, upon reading the source,
there are string constants everywhere. Perhaps I am missing something, but
this means that in order to supply localization support much work would
need to be done to find some scheme that doesn't mean translating the
source.

I have quite a bit of notes on seperation and even down to specific
methods and sub-libraries necessary for the back-end. Perhaps if I have
some time soon I'll put it into a PDF somewhere.

Has anyone else put much thought into this?

-- 
Ryan Sommers
[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My project wish-list for the next 12 months

2004-12-01 Thread Andre Oppermann
Scott Long wrote:
All,
I know that I said last month that we were going to stop promising
specific features for the next major release.  However, I'd like to
throw out a list of things that would be really nice to have in the
future, whether its 6.0 or 7.0 or whatever.  Most of these tasks are
not trivial, but I hope that talking about them will encourage some
interest.  These are in no particular priority order.  I'd also be
thrilled if someone wanted to dress this list up in docbook and add
it to the webpage.  While this is just my personal list, I'd welcome
other additions to it (in the sense of significant projects, not just
individual PRs or bug fixes that one might be interested in).
1.  Keyboard multiplexer.  We are running into problems with making
ps/2 and USB/bluetooth keyboards work together and work with KVMs.
Having a virtual keyboard device that multiplexes the various real
keyboard devices and handles hotplug can solve this mess pretty
effectively.  I know that there has been a lot of talk about this on
mailing lists recently but I don't know how much progress is being made
so I'm listing it here.
2.  New installer.  I know some people still consider this a joke, but
the reality is that sysinstall is no longer state of the art.  It's
fairly good at the simple task that it does, but it's becoming harder
and harder to fix bugs and extend functionality in it.  It's also
fairly unfriendly to those of us who haven't been using it since 1995.
The DFly folks have some very interesting work in this area
(www.bsdinstaller.com) and it would be very good to see if we can
collaborate with them on it.
3.  Native PCI Express support.  I keep on hoping to take care of this,
but I never seem to have the time to get past designing it.  This task
includes 3 parts that are mostly independent.  The first is support for
the extended PCI config space and memio access method, the second is
MSI, and the third is link QOS management.  If anyone is interested
here, please let me know.
4.  Journaled filesystem.  While we can debate the merits of speed and
data integrety of journalling vs. softupdates, the simple fact remains
that softupdates still requires a fsck run on recovery, and the
multi-terabyte filesystems that are possible these days make fsck a very
long and unpleasant experience, even with bg-fsck.  There was work at
some point at RPI to add journaling to UFS, but there hasn't been much
status on that in a long time.  There have also been proposals and
works-in-progress to port JFS, ReiserFS, and XFS.  Some of these efforts
are still alive, but they need to be seen through to completion.  But at
the risk of opening a can of worms here, I'll say that it's also
important to explore non-GPL alternatives.
5.  Clustered FS support.  SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful.  RedHat recently bought Sistina and re-opened the GFS source
code, so exploring this would be very interesting.
6.  Overhaul CAM, add iSCSI.  CAM is very parallel-SCSI centric right
now.  I have some work-in-progress in Perforce to address this, but it's
pretty minimal.  The parallel SCSI knowledge needs to be separated out
and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and
maybe even ATA transports.  There is a Lucent implementation of iSCSI
for FreeBSD 4.x that could be a useful reference, though it's a
monolithic stack that doesn't really address the shortcomings of CAM.
Having iSCSI infrastructure that supported both hardware and software
implementations would be ideal.
Seeing all this storage related stuff is very interesting because I just
stumbled across a company making a new digital Cinematography system that
has 8Mpix and they say that using this in a day's worth shooting they end
up with up to 6.63TB of raw digigal footage.  In the end this is 398TB for
an average feature movie.  The camera delivers the images over
quad-infiniband to the recording system at 400MB/s.  Pretty impressive.
 http://www.dalsa.com/dc/workflow/storage.asp
--
Andre
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


My project wish-list for the next 12 months

2004-12-01 Thread Scott Long
All,
I know that I said last month that we were going to stop promising
specific features for the next major release.  However, I'd like to
throw out a list of things that would be really nice to have in the
future, whether its 6.0 or 7.0 or whatever.  Most of these tasks are
not trivial, but I hope that talking about them will encourage some
interest.  These are in no particular priority order.  I'd also be
thrilled if someone wanted to dress this list up in docbook and add
it to the webpage.  While this is just my personal list, I'd welcome
other additions to it (in the sense of significant projects, not just
individual PRs or bug fixes that one might be interested in).
1.  Keyboard multiplexer.  We are running into problems with making
ps/2 and USB/bluetooth keyboards work together and work with KVMs.
Having a virtual keyboard device that multiplexes the various real
keyboard devices and handles hotplug can solve this mess pretty
effectively.  I know that there has been a lot of talk about this on
mailing lists recently but I don't know how much progress is being made
so I'm listing it here.
2.  New installer.  I know some people still consider this a joke, but
the reality is that sysinstall is no longer state of the art.  It's
fairly good at the simple task that it does, but it's becoming harder
and harder to fix bugs and extend functionality in it.  It's also
fairly unfriendly to those of us who haven't been using it since 1995.
The DFly folks have some very interesting work in this area
(www.bsdinstaller.com) and it would be very good to see if we can
collaborate with them on it.
3.  Native PCI Express support.  I keep on hoping to take care of this,
but I never seem to have the time to get past designing it.  This task
includes 3 parts that are mostly independent.  The first is support for
the extended PCI config space and memio access method, the second is
MSI, and the third is link QOS management.  If anyone is interested
here, please let me know.
4.  Journaled filesystem.  While we can debate the merits of speed and
data integrety of journalling vs. softupdates, the simple fact remains
that softupdates still requires a fsck run on recovery, and the
multi-terabyte filesystems that are possible these days make fsck a very
long and unpleasant experience, even with bg-fsck.  There was work at
some point at RPI to add journaling to UFS, but there hasn't been much
status on that in a long time.  There have also been proposals and
works-in-progress to port JFS, ReiserFS, and XFS.  Some of these efforts
are still alive, but they need to be seen through to completion.  But at
the risk of opening a can of worms here, I'll say that it's also
important to explore non-GPL alternatives.
5.  Clustered FS support.  SANs are all the rage these days, and
clustered filesystems that allow data to be distributed across many
storage enpoints and accessed concurrently through the SAN are very
powerful.  RedHat recently bought Sistina and re-opened the GFS source
code, so exploring this would be very interesting.
6.  Overhaul CAM, add iSCSI.  CAM is very parallel-SCSI centric right
now.  I have some work-in-progress in Perforce to address this, but it's
pretty minimal.  The parallel SCSI knowledge needs to be separated out
and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and
maybe even ATA transports.  There is a Lucent implementation of iSCSI
for FreeBSD 4.x that could be a useful reference, though it's a
monolithic stack that doesn't really address the shortcomings of CAM.
Having iSCSI infrastructure that supported both hardware and software
implementations would be ideal.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


5.3 release snd_ich strange behaviour

2004-12-01 Thread Zajcev Evgeny

I've installed 5.3-RELEASE recently and pretty happy with it.  But
i've noticed some strange behaviour.

I've added

   snd_ich_load="YES"

to my /boot/loader.conf to enable sound in boot time.  Reboot machine
and everything was working ok.  But then i noticed that cooler on my
notebook starts more often then without snd_ich.  Running top shows
that machine is about 15-20% in interrupts.  Unloading snd_ich makes
top showing interrups about 0-1%.  Then i loaded snd_ich by hand
(kldload snd_ich) and the problem dissapeared, top shows 0-1% and
cooler starts as without snd_ich.  I commented this string in
/boot/loader.conf and rebooted the machine.  Then load snd_ich by
hand.  Everything is ok!  I assumed that it was some strange thing and
uncommented string in loader.conf and rebooted.  The situation with
15-20% inturrupts repeeted!  However kldunload & kldload resolves it.

So the only suitable solution for me was to load snd_ich using rc.d

Thanks!

PS: I have iRU intro 1214 notebook with acpi enabled.

-- 
lg
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My freebsd dream

2004-12-01 Thread braulio
Hi.

As a latinamerican a dream of an elegant desktop FreeBSD too.  I studied
computer sciences and I can install FreeBSD for desktop use easily, but
"regular" people can't.  They also can't see what I see beautiful. I hope
that biculturalism
(http://www.joelonsoftware.com/articles/Biculturalism.html) will merge
into one beautiful way.

I know that in this life anything comes for free.  I also know that free
software comes from freedom and does not mean software for free.  Every
project needs funding.  Therefore I hope that someday "someone" will find
interest and give funding to a Desktop FreeBSD project that
latin-americans and the caribbeans could use.

I like very much your work.

Best regards,

Braulio Solano Rojas

> Hello Sirs,
>First thank you all for making such an
> beautiful, robust and elegant OS. I have a dreamto
> make worlds best free bsd based desktop system in the
> world .but why do I want that (freebsd does great
> on servers ...and why do we need this ?) ..Bcos
> billions of people who desktop system have no real
> choice ...they are stuck with M$ and further confused
> by hundreds of linux variants..they need a
> INTUITIVE, EASY to USE ,FRIENDLY
> which is also easy to manage centrally in a cooperate
> environments has binary compatibilities , SECURE and
> Virus free . I think freebsd provides this ..after
> all MAc OS X is based on it i also went to drawin
> + gnu drawin site ...failed to find anything
> interesting (and confusing license)
>
> I think we should have a elegant graphical install
> graphical install ->> can we boot from bootable CD
> (lik e knoppix) and then run a install program (which
> maybe web(from the bootable cd)/perl-gtk script based
> GUI software for easy installthis will allow us to
> easily install the system with out low level
> installation
> Easy Management(scallable to thousands of system)->p2p
> based software distribution system like bittorent or
> jaxta to pull heavy software package then use port
> ystem to finally install
> Centrall Administration & policies -> Samba + Openldap
> + phpLDAPadmin + policies (???)
> Autonomic healing - ???
> Stateless BSD (like redhats stateless linux project)
>
> I know my dream is worth while .one day people
> will use freeBsd variant as thier desktop ...which
> will never crash nor complain
>
> I have a dream .it called MyBSD (most easy to use
> , friendly freeBSD based desktop in the world and
> administrator’s delight  )
>
> Pl give your feedback/ suggestions / hate mails
>
> regards,
> BSD Romeo
> gp
>
>
>
>
> __
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> http://promotions.yahoo.com/new_mail
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: My freebsd dream

2004-12-01 Thread Chris McDermott
I have a dream that one day this [OS] will rise up and live out the
true meaning of its creed: "We hold these truths to be self-evident:
that all [code is] created equal." I have a dream that one day on the
red[mond] hills of [Washington] the [derived works] of former
[research projects] and the [derived works] of former [corporations]
will be able to [link] together [in] a table of [compatibility]. I
have a dream that one day even the [company of Microsoft], a desert
[company], sweltering with the heat of injustice and oppression, will
be transformed into an oasis of freedom and justice. I have a dream
that my four [computers] will one day [run] in a nation where they
will not be judged by the color of their [GUI] but by the content of
their [code base]. I have a dream today.

I have a dream that one day the state of [IP], whose [lawyer's] lips
are presently dripping with the words of interposition and
nullification, will be transformed into a situation where little
[freebsd boxes] and [linux boxes] will be able to [share code] with
little [windows boxes] and [solaris boxes] and [run] together as
[clients] and [servers]. I have a dream today. I have a dream that one
day every [interface] shall be [defined], every [bug] and [error]
shall be [documented], the [compiler warnings] will be made
[understandable], and the [stack pages] will be made [no-exec], and
the glory of the [Code] shall be revealed, and all [users] shall see
it together. This is our hope. This is the faith with which I return
to the [buildworld]. With this faith we will be able to hew out of the
mountain of despair a stone of hope. With this faith we will be able
to transform the jangling discords of [operating systems] into a
beautiful [cluster] of [beowulf]. With this faith we will be able to
work together, to [code] together, to [debug] together, to [core dump]
together, to stand up for [standards] together, knowing that we will
be [compatible] one day.

...

Sorry for OT/flamebait , I had to share this. ;)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


MYSQL connection problem (SOLVED) - Thanks to all that replied

2004-12-01 Thread mario . lobo
Thanks to everyone that replied and tried.

My best regards to you all !!

-- 
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


My freebsd dream

2004-12-01 Thread freeBsd Romeo
Hello Sirs,
   First thank you all for making such an
beautiful, robust and elegant OS. I have a dreamto
make worlds best free bsd based desktop system in the
world .but why do I want that (freebsd does great
on servers ...and why do we need this ?) ..Bcos
billions of people who desktop system have no real
choice ...they are stuck with M$ and further confused
by hundreds of linux variants..they need a
INTUITIVE, EASY to USE ,FRIENDLY
which is also easy to manage centrally in a cooperate
environments has binary compatibilities , SECURE and
Virus free . I think freebsd provides this ..after
all MAc OS X is based on it i also went to drawin
+ gnu drawin site ...failed to find anything
interesting (and confusing license)

I think we should have a elegant graphical install
graphical install ->> can we boot from bootable CD
(lik e knoppix) and then run a install program (which
maybe web(from the bootable cd)/perl-gtk script based
GUI software for easy installthis will allow us to
easily install the system with out low level
installation
Easy Management(scallable to thousands of system)->p2p
based software distribution system like bittorent or
jaxta to pull heavy software package then use port
ystem to finally install  
Centrall Administration & policies -> Samba + Openldap
+ phpLDAPadmin + policies (???)
Autonomic healing - ???
Stateless BSD (like redhats stateless linux project) 

I know my dream is worth while .one day people
will use freeBsd variant as thier desktop ...which
will never crash nor complain

I have a dream .it called MyBSD (most easy to use
, friendly freeBSD based desktop in the world and
administrator’s delight  )

Pl give your feedback/ suggestions / hate mails 

regards,
BSD Romeo 
gp




__ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: isp driver not 64 bit?

2004-12-01 Thread Matt Emmerton

- Original Message - 
From: "Dan Nelson" <[EMAIL PROTECTED]>
To: "David Gilbert" <[EMAIL PROTECTED]>
Cc: "Matt Emmerton" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, November 30, 2004 12:56 AM
Subject: Re: isp driver not 64 bit?


> In the last episode (Nov 29), David Gilbert said:
> > Well... cam_calc_geometry seems to get called quite a bit.  Almost
> > everytime you touch the disk, in fact.  fsck'ing a partition calls
> > it, for instance.

Does this not seem excessive to anyone?  Call me naive, but shouldn't the
only time we need to obtain the geometry is at initial probe time?

> > Console access is personally expensive (much driving, for instance),
> > but from memory the debugging I put in cam_calc_geometry() would
> > print before the correct output from dadone().  Your description
> > reminds me of this --- but it's no less vexing that the output from
> > dadone() has the correct sector and volume size and the ccg in
> > cam_calc_geometry() has bogus data.
> >
> > I don't know if it's significant, but the correct numbers were:
> >
> > 279353684 sectors of 512 bytes
> >
> > The ccg structure comes up with:
> >
> > 3737169375 sectors of 3737169374 bytes
> >
> > Not entirely sensible.  Interesting that they're close values.
> > However, with different things on the stack, the values changed.
>
> Even more interesting is their hex values:
>
> DEC0ADDF and DEC0ADDE, aka 0xDEADC0DE.  Something's reading memory
> after the kernel freed it.

Which makes me wonder if one of our 'extra' cam_calc_geometry() calls is
being executed from a place where it shouldn't be.

--
Matt Emmerton

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: USB OHCI problems...

2004-12-01 Thread Hans Petter Selasky
On Tue, Nov 30, 2004 at 06:16:03PM +0100, Hans Petter Selasky wrote:
> Hi,
> 
> http://home.c2i.net/hselasky/isdn4bsd/privat/usb/Makefile
> http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.diff.bz2
> http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.tar.bz2
> 

I fixed a small bug in the code that prevented isoc. from working. You might 
want to re-download the files. 

Yours
-HPS

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Oracle 9/10g under FreeBSD

2004-12-01 Thread Ceri Davies
On Wed, Dec 01, 2004 at 08:19:02AM +0100, Christoph Kukulies wrote:
> Anyone having one of the Oracle linux dists running under FreeBSD?

I have 9i running.  It turned out to be easier doing it that way than
finding a Linux dist that would work.  I followed the instructions at
http://ezine.daemonnews.org/200402/oracle.html, which actually worked.

Ceri
-- 
Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former.-- Einstein (attrib.)


pgpxh04Qhs3pp.pgp
Description: PGP signature


MYSQL connection problem (SOLVED) - Thanks to all that replied

2004-12-01 Thread mario . lobo
Thanks to everyone that replied and tried.

My best regards to you all !!

-- 
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MYSQL connection problem (SOLVED)

2004-12-01 Thread mario . lobo
YSS !!! IT WORKED !!

Thanks a million Daniel.

What exactly does with-liwrap do?

-- 
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br


On 1 Dec 2004 at 12:54, Daniel Bye wrote:

> 
> I had similar problems recently.  Edit the port's Makefile, removing the
> line:
> 
> --with-libwrap \
> 
> and rebuild the port.
> 
> This worked for me - but there is probably a better way to deal with it.
> 
> Dan
> 
> -- 
> Daniel Bye
> 
> PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
> PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F
>  _
>   ASCII ribbon campaign ( )
>  - against HTML, vCards and  X
> - proprietary attachments in e-mail / \
> 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MYSQL connection problem

2004-12-01 Thread mario . lobo
YSS !!! IT WORKED !!

Thanks a million Daniel.

What exactly does with-liwrap do?

-- 
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br


On 1 Dec 2004 at 12:54, Daniel Bye wrote:

> 
> I had similar problems recently.  Edit the port's Makefile, removing the
> line:
> 
> --with-libwrap \
> 
> and rebuild the port.
> 
> This worked for me - but there is probably a better way to deal with it.
> 
> Dan
> 
> -- 
> Daniel Bye
> 
> PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
> PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F
>  _
>   ASCII ribbon campaign ( )
>  - against HTML, vCards and  X
> - proprietary attachments in e-mail / \
> 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: USB OHCI problems...

2004-12-01 Thread Barry Bouwsma
[drop me from any replies, and I'll catch up from the archives, thanx]


On Wed, 1 Dec 2004 10:48:42 +1030, "Daniel O'Connor" wrote:

> > In addition, I've connected a uaudio sound device, which
> > works to play audio for between 10 and 13 minutes, before
> > bombing out with an error in ohci_device_isoc_enter(),

> On a side note..
> How are you testing it?

``waveplay -S 48000 -f /dev/dsp[0-2]'' (when part of a pipeline
that cuts off the WAV header info), or via a wrapper that invokes
`ogg123' with the appropriate /dev/dsp? audio device.  Into a
pair of headphones.

I haven't done a serious comprehensive test to try recording or
anything; that comes later.


> Last time I tried my USB audio device I got pretty reliable panics trying to
> get KDE to use it :(

Which FreeBSD and what sort of device?  My FreeBSD-4.x is using as
much USB code from -current as possible, which might make some
difference.  The uaudio device I have is one that I inquired about
some months back in either the -multimedia or -hardware list -- I
need to dig out that post, and make a followup to it with potentially
useful info sometime later today.

There are, um, ``interesting'' things I've observed, which I'll
mention in my followup to whichever list, that I need to verify
are independent of UHCI/OHCI controller, and also whether afflict
NetBSD as well.  NetBSD also gives me more access to the device.
FreeBSD finds it as uaudio and uhid, and (my module source) plays
back at a fixed volume level (apparently samplerate too).

The (usual) worst I experience is the `isoc TD' message followed
by a `pcmX:play: timeout, channel dead' type of message, after
which the device no longer works.  While I've had panics from
other causes, I don't think any of mine could be pinned on the
uaudio/uhid device -- but I haven't done much in the way of
connect/disconnecting and stuff.


thanks
barry bouwsma

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Oracle 9/10g under FreeBSD

2004-12-01 Thread Christoph Kukulies
Anyone having one of the Oracle linux dists running under FreeBSD?
--
Chris Christoph P. U. Kukulies kuku_at_kukulies.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Soundcard tweaking: `mixer' v. `sysctl' ?

2004-12-01 Thread Barry Bouwsma
[drop me from replies and I'll catch up from the archives RSN]


I seek guidance in my hideous hacking.

I have multiple sound cards based on the CMI8738 chip with spdif
input in one machine, for which I was using hacked kernel modules
to select either optical or coaxial spdif input from both cards.

The cmpci driver under NetBSD has far more functionality, allowing
one to use mixerctl/audioctl to access much more than FreeBSD's
mixer or sysctl can give me.  Now that I'm wanting to record from
different sources on the two cards, as well as having been spoilt
by what NetBSD is able to offer in monitoring and whatnot, I'm
wanting to hack comparable functionality into my FreeBSD kernel
modules.

My first ugly hack makes use of two added mixer inputs to allow
me to select one of the two spdif inputs independently of the
other card, with `mixer', whee.  After I had had no luck with my
wish to use a sysctl to select recording source like the NetBSD
mixerctl program.

First question, am I missing anything that gives sysctl-like
control over sound devices, under my FreeBSD4?


Secondly, after another attempt to whup the sysctl into
submission, I had success.  Yow.  So I was able to duplicate
my `mixer' input source selection hack as a `sysctl' input
source selection hack, as well as introduce a handful of
other sysctl knobs to be used to tweak things important to
me, leaving the door open for others.

So, should I give up on `mixer' in favour of `sysctl' to
select recording source (the spdif inputs are exclusive),
or is it still reasonable/preferable to use `mixer =rec dig1'
as my earlier hacks allow (haven't tried to make those
disappear from the mixer itself, as the level cannot
be adjusted) ?


In addition, for something like enabling spdif monitor to the
analog outputs (which NetBSD's mixerctl spdif.monitor allows
me to do), should this be done with a sysctl, as my later
hack does, or by something else?  There's already one sysctl
for this sound driver to enable spdif playback output, so I
would imagine this is the way to go.


Apologies for my stupidity.  And I'll submit (ugly) patches,
when I'm happy with my hacks.  If desired.


thanks
barry bouwsma

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


MYSQL connection problem (added info)

2004-12-01 Thread mario . lobo
Adding the tcpdump output after changing mysqld to port 5004 (just a try :(( ) 
and issuing:

[~]>mysql --port=5004 --host=127.0.0.1 --user=xxx database -p


[~]>tcpdump -vv -i lo0 port 5004
tcpdump: listening on lo0, link-type NULL (BSD loopback), capture size 96 bytes

08:57:04.755597 IP (tos 0x0, ttl  64, id 5384, offset 0, flags [DF], length: 
64) localhost.58972 >
localhost.5004: S [tcp sum ok] 1832068379:1832068379(0) win 65535 

08:57:04.755654 IP (tos 0x0, ttl  64, id 5385, offset 0, flags [DF], length: 
64) localhost.5004 >
localhost.58972: S [tcp sum ok] 87927240:87927240(0) ack 1832068380 win 65535 


08:57:04.755685 IP (tos 0x0, ttl  64, id 5386, offset 0, flags [DF], length: 
52) localhost.58972 >
localhost.5004: . [tcp sum ok] 1:1(0) ack 1 win 35840 

08:57:04.756399 IP (tos 0x0, ttl  64, id 5387, offset 0, flags [DF], length: 
52) localhost.5004 >
localhost.58972: F [tcp sum ok] 1:1(0) ack 1 win 35840 

08:57:04.760855 IP (tos 0x8, ttl  64, id 5388, offset 0, flags [DF], length: 
52) localhost.58972 >
localhost.5004: . [tcp sum ok] 1:1(0) ack 2 win 35840 

08:57:04.761035 IP (tos 0x8, ttl  64, id 5389, offset 0, flags [DF], length: 
52) localhost.58972 >
localhost.5004: F [tcp sum ok] 1:1(0) ack 2 win 35840 

08:57:04.761067 IP (tos 0x0, ttl  64, id 5390, offset 0, flags [DF], length: 
52) localhost.5004 >
localhost.58972: . [tcp sum ok] 2:2(0) ack 2 win 35839 

7 packets captured
7 packets received by filter
0 packets dropped by kernel


I hope this helps,

--
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br



-- First post /*

===

I have two machines:

1) Free 4.10 / mysql (5.0.0) listening on port 5006

2) Free 5.3 Release / mysql (5.0.0) listening on port 5007

On both, no firewalls, blocks or anything of that sort. Both machines have the 
same configuration.
Both mysql were compiled from the ports with the same options. The only 
difference between the two
machines is the Free version and port mysql is listening on.

Here are the outputs of the following commands on machine 1):

>telnet localhost 5006
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
9
5.0.0-alpha}l'zRjBG,!js%Zxl6f"p3
(after a few seconds...)
Connection closed by foreign host.

-

>mysql -u root -P 5006 -h 127.0.0.1 -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 8 to server version: 5.0.0-alpha

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

**
Now, here are the outputs of the same commands on machine 2):

]>telnet localhost 5007
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host. (no wait for this line to show!)

>mysql -u root -P 5007 -h 127.0.0.1 -p
Enter password:
ERROR 2013 (HY000): Lost connection to MySQL server during query
(no wait for the above line to show either!)

**

I can only connect on machine 2) if I use a mysql.sock file. Any attempt to 
connect via TCP/IP
doesn´t work !! command line client, java connectors (all possible versions) 
none work.

I´ve been into every single link google returned to me on the ERROR 2013 above 
for 2 days now and
none of them had any info to get this working. Believe me, I tried every hint 
of suggestion there
was.

I really hope someone here has any clues to what is going on.

I´ve posted this to hackers but no clues so far.

thanks,

--
   //|  //||
  // | // ||
-//--//---|| ARIO LOBO
//  //||
-
[EMAIL PROTECTED]
http://www.ipad.com.br

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MYSQL connection problem (correction re-post)

2004-12-01 Thread Mike Silbersack
On Tue, 30 Nov 2004 [EMAIL PROTECTED] wrote:
Hi Arun;
hrmm.
Can you try switching the port to another port number? Perhaps a lower port
number?
See if you can get it to connect in that way?
Makes no difference
Try doing a "tcpdump -n -i lo0" and see what traffic occurs when you make 
the connection attempt.  It should only be a few lines, so posting to this 
thread will be fine.

Mike "Silby" Silbersack
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MYSQL connection problem (correction re-post)

2004-12-01 Thread Andre Oppermann
[EMAIL PROTECTED] wrote:
Hi Arun;
hrmm.
Can you try switching the port to another port number? Perhaps a lower port 
number?
See if you can get it to connect in that way?
Makes no difference
In your log file, does it print messages about having successfully started 
up?
Yes, it does. Like I said, if I use mysql.sock I connect fine. The problem 
is in TCP connections.
Do you have ipfw or any other packet filter on your machine?
None whatsoever, of any kind.
Do this and try again:
 sysctl net.inet.ip.portrange.randomized=0
--
Andre
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


sysctl machdep.hlt_logical_cpus affects kernel HZ?

2004-12-01 Thread Steven Hartland
One of my colleagues has just noticed that setting:
sysctl machdep.hlt_logical_cpus=1
appears to double the kernel frequency as reported by
systat on 5.2.1-RELEASE-p11.
Is this correct? What are the implications? How can this
be corrected?
   Steve

This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please 
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"