In article <199903170258.saa01...@implode.root.com>,
David Greenman wrote:
>A much better solution would be for someone to spend the time to
> implement the needed VM frobbing of modifying, at BSDI binary exec-time,
> the ps_strings address constant in the binary's crt0 that is causing the
>
David Greenman writes:
>If the remaining userland issues are dealt with, then perhaps. It is
> currently necessary to rebuild certain utilities after changing this,
> however, so making it a simple kernel compile time option isn't sufficient.
Are these crash-and-burn-class problems, or is it
On 17-Mar-99 Mikhail Teterin wrote:
> => > The bug is on the web site, not in the kernel.
> I'd consider the web-site a "spec" and the kernel -- "implementation".
> By this logic, the kernel needs fixing...
I think its a little too rapidly evolving for that, especially -current.
> =Probably.
>"Daniel O'Connor" writes:
>> On 17-Mar-99 Dag-Erling Smorgrav wrote:
>> > The bug is on the web site, not in the kernel. David Greenman
>> > committed a patch to better support large memory configurations.
>> > Unfortunately, it seems this was not possible to achieve without
>> > breaking BSD
=> > The bug is on the web site, not in the kernel.
I'd consider the web-site a "spec" and the kernel -- "implementation".
By this logic, the kernel needs fixing...
=> > David Greenman committed a patch to better support large memory
=> > configurations. Unfortunately, it seems this was not po
"Daniel O'Connor" writes:
> On 17-Mar-99 Dag-Erling Smorgrav wrote:
> > The bug is on the web site, not in the kernel. David Greenman
> > committed a patch to better support large memory configurations.
> > Unfortunately, it seems this was not possible to achieve without
> > breaking BSDI comp
On 17-Mar-99 Dag-Erling Smorgrav wrote:
> > that bladeenc does not run, the problem is that a BSDI executable
> > does not run. Which breaks a promise from
> The bug is on the web site, not in the kernel. David Greenman
> committed a patch to better support large memory configurations.
> Unfort
Mikhail Teterin writes:
> Does not seem a better solution to me at all. The problem is not
> that bladeenc does not run, the problem is that a BSDI executable
> does not run. Which breaks a promise from
> http://www.freebsd.org/features.html
The bug is on the web site, not in the kernel. Da
Dirk Froemberg once stated:
=As a better solution I'll ask the original author for a native FreeBSD
=version.
Does not seem a better solution to me at all. The problem is not
that bladeenc does not run, the problem is that a BSDI executable
does not run. Which breaks a promise from
http:/
>
> It seems to work fine except it core dumps on exit for some reason.
>
Marcel fixed that one a while back; update your system. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.
On 15-Mar-99 Dirk Froemberg wrote:
> > So one should either fix the kernel or BROKEN=YES the bladeenc Port or use
> > the
> > linux executable (if it works at all)
>
> As a workaround I'll mark bladeenc as BROKEN for FreeBSD-current.
> As a better solution I'll ask the original author for a
Hi Michael!
On Mon, Mar 15, 1999 at 05:25:38PM +0100, Michael Reifenberger wrote:
> just for the record (as it is allready documented )
> the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc)
> an MPEG3 encoder. Former kernels did.
Yes, this was discussed on freebsd-commi
Hi,
just for the record (as it is allready documented )
the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc)
an MPEG3 encoder. Former kernels did.
So one should either fix the kernel or BROKEN=YES the bladeenc Port or use the
linux executable (if it works at all)
Bye!
--
13 matches
Mail list logo
