As there was no objections, I am going to commit changes to cam_get_device()
that remove the following features:
- ignoring 'r' and 'n' at the start of device name
- ignoring whitespace at end of device name
- parsing and ignoring slice and partition names in a device name
cam(3) manual page is
Hello,
On Thu, Oct 07, 2010 at 12:35:01PM +, Peter Much wrote:
> Any clues, ideas, pointers, hints, ressources,... are greatly
> welcomed!!
Maybe you don't really want to hear this, but...
ISDN is a dying technology. Any time soon you won't get ISDN termination
by your telecom provider anym
On Thu, Oct 07, 2010 at 09:28:22PM +0300, Andriy Gapon wrote:
> on 07/10/2010 20:31 John Hay said the following:
> > Oct 7 17:11:49 thumper1 kernel: mvsch23: EMPTY CRPB 30 (->0) 0 4000
>
> Can you rule out hardware (or driver-level) problems?
> E.g. by dd-ing to/from disk directly.
> Doing that i
Recently rs has adopted a habit of damaging data in long lines
of input. This can easily be tested:
# jot -s\ -b 01234567 1000 | rs 0 1 | grep -vxF 01234567
012345
67
012
34567
012345
67
012
34567
012345
67
012
34567
The jot command prints the string 01234567 a thousand times in
a single row.
T
> Ok. But how stable (production ready) the FreeBSD-8-STABLE is? What is your
> opinion?
I am running 8-STABLE from 27th September on all our ptoduction
machines (from webservers to database servers to the company mail
server) and it is fine. I am going to update again over the next
few days, as
On Fri, Oct 08, 2010 at 01:24:04AM +0300, Andriy Gapon wrote:
> on 08/10/2010 00:35 Matthew Seaman said the following:
> > On 07/10/2010 21:28:30, Andriy Gapon wrote:
> >> on 07/10/2010 13:45 Matthew Seaman said the following:
> >>> However, according to my understanding, if you want to boot from a
This is straying a bit, but I think it is important:
the only good measure of when a technology is too old, is when people
(who use FreeBSD in this case) stop using it.
On Fri, 08 Oct 2010 11:12:32 +0200
Oliver Brandmueller wrote:
> Maybe you don't really want to hear this, but...
>
> ISDN is a
On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
Another thing about VoIP calls: have they solved the "emergency call
needs a location" problem? Here (again: in Norway) they are still
working out how to solve this: if you call emergency services (police,
fire department, etc.) from yout VoIP number;
I noticed this is occurring on the siis driver. Silicon Image has, in my
observations, had issues when any kind of port multiplication is occurring
(either by the card itself or by hardware port multiplier that you
purchase). I have timeouts on my drives for my Silicon Image based
controller card
Apologies for late response, wanted to check the code again.
On 10/07/2010 10:03 AM, Alan Cox wrote:
> Alan Cox wrote:
> At a high-level, I agree with much of what you say. In particular, if
> pmap_enter() is applied to a virtual address that is already mapped by a large
> page, the reported pan
Kurt Alstrup wrote:
Apologies for late response, wanted to check the code again.
On 10/07/2010 10:03 AM, Alan Cox wrote:
Alan Cox wrote:
At a high-level, I agree with much of what you say. In particular, if
pmap_enter() is applied to a virtual address that is already mapped by a large
page
On Friday 08 October 2010 12:22:40 pm Dimitry Andric wrote:
> On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
> > Another thing about VoIP calls: have they solved the "emergency call
> > needs a location" problem? Here (again: in Norway) they are still
> > working out how to solve this: if you call e
Does anybody know how to correct the audio driver problem of the
opensolaris guest?
The internet advice to run
pfexec update_drv -a -i '"pci8086,2415"' audio810
is better than nothing, but the audio quality is absolutely miserable.
It is clearly not the required audio driver.
Therefore the flashpl
On Fri, Oct 8, 2010 at 1:00 PM, Harald Weis wrote:
> Does anybody know how to correct the audio driver problem of the
> opensolaris guest?
> The internet advice to run
> pfexec update_drv -a -i '"pci8086,2415"' audio810
>
> is better than nothing, but the audio quality is absolutely miserable.
>
,--- You/Harald (Fri, 8 Oct 2010 20:00:46 +0200) *
| My hope to find an interim solution for the flashplayer nightmare
| (while waiting for gnash) can be measured by the amount of hours
| I've spent to get flash - easily and long-term-wise - playing on FreeBSD,
| Ubuntu, PCBSD...
|
| I guess
Steven Friedrich writes:
> On Friday 08 October 2010 12:22:40 pm Dimitry Andric wrote:
>> On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
>> > Another thing about VoIP calls: have they solved the "emergency call
>> > needs a location" problem? Here (again: in Norway) they are still
>> > working out
On 8 October 2010 18:12, Torfinn Ingolfsen
wrote:
[...]
> I don't know how it works in other countries, but here (in Norway) it
> works like this: yes - ISDN technology is dying.
> However, like all other technologies that major telcos have invested a
> lot in, its death is very slow. Extremely sl
On Sunday, October 03, 2010 2:49:27 am Daniel O'Connor wrote:
>
> On 14/09/2010, at 16:49, Daniel O'Connor wrote:
> >> So, you either have to disable one of them or upgrade to a more recent
> >> version.
> >> The version you need is r206183. The latest stable/8 would do, obviously.
> >
> > I'll
On 10/8/2010 2:12 AM, Oliver Brandmueller wrote:
ISDN is a dying technology.
That sort of isn't relevant to the questions of:
1) Are there developers willing to support it, and
2) Are there users that want to use it.
If both of those are true, then we need to do support it.
Doug (tools, not
Or have they been superceded by voip stacks that abstract away the isdn
layer? I would contend, at least in the US, ISDN is alive and well. Your
basic smb softpbx installation is going to be talking to a digium card that
is connected to a Basic/Primary Rate ISDN (B/PRI) or T-line.
If the OP is u
On 10/8/2010 12:37 PM, Peter C. Lai wrote:
If the OP is using I4B to do voice data processing, perhaps he would
be better served migrating to either freeswitch and/or asterisk ports?
That's a policy decision. We don't do policy decisions, we do
technology. I'll say it again, "Tools, not policy
I noticed this is occurring on the siis driver. Silicon Image has, in my
observations, had issues when any kind of port multiplication is occurring
(either by the card itself or by hardware port multiplier that you
purchase). I have timeouts on my drives for my Silicon Image based
controller card
On Fri, Oct 08, 2010 at 04:35:41PM -0400, Adam Stylinski wrote:
> I noticed this is occurring on the siis driver. Silicon Image has, in my
> observations, had issues when any kind of port multiplication is occurring
> (either by the card itself or by hardware port multiplier that you
> purchase).
On Fri, 08 Oct 2010 18:22:40 +0200
Dimitry Andric wrote:
> On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
> > Another thing about VoIP calls: have they solved the "emergency call
> > needs a location" problem? Here (again: in Norway) they are still
> > working out how to solve this: if you call em
24 matches
Mail list logo
