On Thu, Oct 4, 2018 at 7:31 PM, tech-lists wrote:
Hi,
Which is the better package for linux emulation on 12-alpha8 - c6 or
c7? Or something else?
Emulation is for boinc_client to take linux work
c7 is newer, of course it's better, c6 is very old stuff. But you can
also just extrac
Hi,
Which is the better package for linux emulation on 12-alpha8 - c6 or c7?
Or something else?
Emulation is for boinc_client to take linux work
thanks
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
On 0828T1207, Larry Rosenman wrote:
> On 2015-08-24 11:07, Edward Tomasz Napierała wrote:
> > On 0824T0731, Larry Rosenman wrote:
> >> On 2015-08-24 03:37, Edward Tomasz Napierała wrote:
> >> > On 0823T2028, Larry Rosenman wrote:
> >> >> got the below panio, on a linux (world community grid) proces
On 2015-08-24 11:07, Edward Tomasz Napierała wrote:
On 0824T0731, Larry Rosenman wrote:
On 2015-08-24 03:37, Edward Tomasz Napierała wrote:
> On 0823T2028, Larry Rosenman wrote:
>> got the below panio, on a linux (world community grid) process exit.
>>
>>
>> borg.lerctr.org dumped core - see /va
On 0824T0731, Larry Rosenman wrote:
> On 2015-08-24 03:37, Edward Tomasz Napierała wrote:
> > On 0823T2028, Larry Rosenman wrote:
> >> got the below panio, on a linux (world community grid) process exit.
> >>
> >>
> >> borg.lerctr.org dumped core - see /var/crash/vmcore.5
> >>
> >> Sun Aug 23 20
On 2015-08-24 03:37, Edward Tomasz Napierała wrote:
On 0823T2028, Larry Rosenman wrote:
got the below panio, on a linux (world community grid) process exit.
borg.lerctr.org dumped core - see /var/crash/vmcore.5
Sun Aug 23 20:14:24 CDT 2015
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CU
On 0823T2028, Larry Rosenman wrote:
> got the below panio, on a linux (world community grid) process exit.
>
>
> borg.lerctr.org dumped core - see /var/crash/vmcore.5
>
> Sun Aug 23 20:14:24 CDT 2015
>
> FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #46 r287028: Sat
> Aug 22 18:34:
got the below panio, on a linux (world community grid) process exit.
borg.lerctr.org dumped core - see /var/crash/vmcore.5
Sun Aug 23 20:14:24 CDT 2015
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #46 r287028: Sat Aug
22 18:34:59 CDT 2015 r...@borg.lerctr.org:/usr/obj/usr/src/
Alan Cox wrote:
On Thu, Sep 25, 2003 at 11:15:57AM -0400, Robert Watson wrote:
...
#6 0xc049f355 in vm_fault (map=0xc6fc1700, vaddr=0, fault_type=1 '\001',
fault_flags=0) at /usr/src/sys/vm/vm_fault.c:219
#7 0xc04eddd9 in trap_pfault (frame=0xdd699b18, usermode=0, eva=0)
at /usr/src/sy
On Thu, Sep 25, 2003 at 11:15:57AM -0400, Robert Watson wrote:
> ...
> #6 0xc049f355 in vm_fault (map=0xc6fc1700, vaddr=0, fault_type=1 '\001',
> fault_flags=0) at /usr/src/sys/vm/vm_fault.c:219
> #7 0xc04eddd9 in trap_pfault (frame=0xdd699b18, usermode=0, eva=0)
> at /usr/src/sys/i386/i
Running -CURRENT from yesterday:
FreeBSD paprika 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Wed Sep 24 19:42:45
EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PAPRIKAMAC i386
MAC, mac_mls, mac_biba, X11, KDE, vic, sdr, xchat. When I ran aim, the
system panicked. Trace below. Please let me know i
On Tue, Mar 25, 2003 at 12:58:35AM +0900, [EMAIL PROTECTED] wrote:
> On Mon, Mar 24, 2003 at 08:40:55AM -0700, M. Warner Losh wrote:
> > I had a working Linux world on my laptop. I upgraded my kernel and
> > acroread4 stopped working. Now all I get is:
> >
> > Exited with error code: 0x400e0009.
[EMAIL PROTECTED] wrote:
> Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>:
> | I had a working Linux world on my laptop. I upgraded my kernel and
> | acroread4 stopped working. Now all I get is:
> |
> | Exited with error code: 0x400e0009.
> |
> | after a whole lot of disk access when I t
Hi,
On Mon, Mar 24, 2003 at 08:40:55AM -0700, M. Warner Losh wrote:
> I had a working Linux world on my laptop. I upgraded my kernel and
> acroread4 stopped working. Now all I get is:
>
> Exited with error code: 0x400e0009.
>
> after a whole lot of disk access when I try to run it. This worke
orking for me; I don't know if this because the new
glibc 2.2.93 ( I upgraded at the same time to RH 8.0 ) or something
in the linux emulation ( I couldn't spot any relevant change there).
I didn't have yet the time to investigate, but:
- I could reproduce it with small multithreaded
> Date: Mon, 24 Mar 2003 08:40:55 -0700 (MST)
> From: "M. Warner Losh" <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> I had a working Linux world on my laptop. I upgraded my kernel and
> acroread4 stopped working. Now all I get is:
>
> Exited with error code: 0x400e0009.
>
> after a whole
Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>:
| I had a working Linux world on my laptop. I upgraded my kernel and
| acroread4 stopped working. Now all I get is:
|
| Exited with error code: 0x400e0009.
|
| after a whole lot of disk access when I try to run it. This worked on
| a De
I had a working Linux world on my laptop. I upgraded my kernel and
acroread4 stopped working. Now all I get is:
Exited with error code: 0x400e0009.
after a whole lot of disk access when I try to run it. This worked on
a December kernel for sure. I'm pretty sure it was working as late as
a Jan
nt FreeBSD-current ( ~ 4 days ago ).
>
> Since I upgraded my linux installation to RH 8.0
> ( ~ 2 months ), I'm not able to run multithreaded binaries under
> linux emulation any more.
>
> ( I hope you understand me - I don't want to install another
> set of native m
I'm using a very recent FreeBSD-current ( ~ 4 days ago ).
Since I upgraded my linux installation to RH 8.0
( ~ 2 months ), I'm not able to run multithreaded binaries under
linux emulation any more.
( I hope you understand me - I don't want to install another
set of native mozil
On Mon, Jan 13, 2003 at 10:59:08AM -0800, Chuck McCrobie wrote:
> Two panics produced when using Linux emulation on a
> machine CVSUP'ed two hours ago. Both very easy to
> produce.
What? You didn't want accurate Linux emulation. ;-)
To Unsubscribe: send mail to [EM
kernel=cvsup
kernelname=/boot/cvsup/kernel
module_path=/boot/cvsup
then I use:
loader> read-conf cvsup.conf
but the changes don't take effect. Oh well, maybe
some more experimentation later...
Thanks,
Chuck McCrobie
--- Kenneth Culver wrote:
>What exactly were you running
d do what you want for this
case. (Booting from a differently named kernel than the
default)
> Thanks,
>
> Chuck McCrobie
>
>
> --- Kenneth Culver <[EMAIL PROTECTED]> wrote:
>> What exactly were you running? I use linux emulation
>> on -CURRENT right now
>
h well, maybe
some more experimentation later...
Thanks,
Chuck McCrobie
--- Kenneth Culver <[EMAIL PROTECTED]> wrote:
> What exactly were you running? I use linux emulation
> on -CURRENT right now
> for mozilla and a few other packages, and havn't had
> any panics... you
&g
What exactly were you running? I use linux emulation on -CURRENT right now
for mozilla and a few other packages, and havn't had any panics... you
might have your kernel modules out of sync with your kernel.
Ken
On Mon, 13 Jan 2003, Chuck McCrobie wrote:
> Two panics produced when usi
Two panics produced when using Linux emulation on a
machine CVSUP'ed two hours ago. Both very easy to
produce. Am I the only one running Linux emulation on
-current? Or is something wacked-ifed with this
machine?
Thanks,
Chuck McCrobie
[EMAIL PROTECTED]
1. cd /usr/ports/emul
Hi!
While using Mulberry (mail/mulberry) the system often locks up completely.
Nothing but reset helps then. I don't get any error (WITHNESS* is on).
Marc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]>, Ian Dowse writes
:
>IP, but we were throwing away the modified version). Commit if it
>works, and I'll look properly tomorrow. Sorry for the breakage.
With the one compile error fixed, this seemed to make `telnet 0.0.0.0'
work again, so I went ahead and checked it i
In message <[EMAIL PROTECTED]>, Peter Wemm writes:
>Has anybody else noticed this in -current? Mozilla hangs for a minute or
>so at regular intervals..
>16:07:31.896548 216.145.52.172.20167 > 0.0.0.0.16001: S 1175926117:1175926117(
Sounds like something I may have broken... Need to sleep now, but
On Wed, 23 Oct 2002, Peter Wemm wrote:
>
> Isn't this a rather strange address to try and connect to? :-]
>
> Wasn't somebody tinkering with the sin_len stuff recently? COMPAT_43 used
> to do evil things, and the linux emulation depended on that.
mini did bu tI hit
0) win
65535
Isn't this a rather strange address to try and connect to? :-]
Wasn't somebody tinkering with the sin_len stuff recently? COMPAT_43 used
to do evil things, and the linux emulation depended on that.
This particular mozilla is rather old, but neither it nor the rest of t
Andrea Campi wrote:
>
> When running a Linux binary in Linux compat mode, all calls to open(),
> readdir() and such, end up calling linux_emul_find() from linux_util.c.
> This functions looks for a directory/file with the same name in the
> /compat/linux hierarchy.
> The net effect is that there
On Wed, Jan 31, 2001 at 12:50:58PM +, Christian Weisgerber wrote:
> Andrea Campi <[EMAIL PROTECTED]> wrote:
>
> > The net effect is that there is no way to, for instance, back up the
> > real /usr from Tivoli, etc... as there is no way to get to a real path
> > if there is anything with the s
Andrea Campi <[EMAIL PROTECTED]> wrote:
> The net effect is that there is no way to, for instance, back up the
> real /usr from Tivoli, etc... as there is no way to get to a real path
> if there is anything with the same name inside /compat/linux.
Loopback NFS mount.
--
Christian "naddy" Weisg
Background:
When running a Linux binary in Linux compat mode, all calls to open(),
readdir() and such, end up calling linux_emul_find() from linux_util.c.
This functions looks for a directory/file with the same name in the
/compat/linux hierarchy.
The net effect is that there is no way to, for in
I'm not sure who all has been messing with the linuxulator in the last
couple of days but as of my last several builds (the latest of a cvsup
this afternoon) any attempt to manipulate entries in /compat/linux/dev
(even to look at them with ls) causes a kernel page fault.
--
Michael D. Harnois, R
On Wed, Nov 01, 2000 at 11:40:15PM -0800, Marcel Moolenaar wrote:
> [cc'd to [EMAIL PROTECTED]; please remove -current on future
> replies]
>
> It's quite likely we don't support less frequently used or very
> specialized ioctls. These are mostly implemented on a need-to-have basis
> triggered by
[cc'd to [EMAIL PROTECTED]; please remove -current on future
replies]
Bernd Walter wrote:
>
> It seems that linux progs are using foreign ioctls on tape drives
> which of course will fail.
Of course?
> Is there anyone already working on an emulation for these?
AFIACT, no.
> Are there similar
Marcel Moolenaar <[EMAIL PROTECTED]> writes:
> Linux has the distinction between block and character devices. I don't
> see any evidence that block devices can be accessed as character devices
> as well (ie: there's /dev/fd0, but no /dev/rfd0).
You can do this in Linux, but the way it works is p
In message <[EMAIL PROTECTED]>, Marcel Moolenaar writes:
>> In that case, makebdev() has been wrong ever since we changed to
>> mount cdevs in FreeBSD.
>
>In the sense that we would never find the vnode and thus always return
>zero stats, right?
No, depends on the bmaj <-> cmaj mapping and the t
Poul-Henning Kamp wrote:
>
> So, where do the programs that call this syscall have the udev_t from ?
Most likely from stat, lstat and fstat.
> Do they know it to be a mountpoint ?
That is implied by the way they get the dev_t.
> Do the know it to be a bmajor
> or cmajor style udev_t ?
AFAICT
In message <[EMAIL PROTECTED]>, Marcel Moolenaar writes:
>Poul-Henning Kamp wrote:
>>
>> >In short: given the (u)dev_t, get the FS statistics and return the
>> >number of free blocks and inodes of the FS on that device.
>>
>> But the udev_t is a (32bit truncated to) 16bit one, right ?
>
>Correct
Poul-Henning Kamp wrote:
>
> >In short: given the (u)dev_t, get the FS statistics and return the
> >number of free blocks and inodes of the FS on that device.
>
> But the udev_t is a (32bit truncated to) 16bit one, right ?
Correct.
> In that case it will usually not work:
>
> crw-r- 1 ro
Andrew Gallatin wrote:
>
> Marcel Moolenaar writes:
> > Wesley Morgan wrote:
> > >
> > > Anyone having problems with the linuxulator the past couple days?
> >
> > Define "past couple of days". I have a working linuxulator made on Oct
> > 29, 12:25 PST.
>
> phk took away mkbdev on 10/31. T
In message <[EMAIL PROTECTED]>, Marcel Moolenaar writes:
>Poul-Henning Kamp wrote:
>>
>> I was just looking at that piece of code, and I couldn't entirely
>> make out what it was even trying to do. Can somebody more
>> linuxolator savy explain what the function linux_ustat() should
>> produce.
>
Poul-Henning Kamp wrote:
>
> I was just looking at that piece of code, and I couldn't entirely
> make out what it was even trying to do. Can somebody more
> linuxolator savy explain what the function linux_ustat() should
> produce.
The following comment explains what linux_ustat should do:
I was just looking at that piece of code, and I couldn't entirely
make out what it was even trying to do. Can somebody more
linuxolator savy explain what the function linux_ustat() should
produce.
I also find this comment rather interesting...
/*
* XXX - Don't return an error
Marcel Moolenaar writes:
> Wesley Morgan wrote:
> >
> > Anyone having problems with the linuxulator the past couple days?
>
> Define "past couple of days". I have a working linuxulator made on Oct
> 29, 12:25 PST.
phk took away mkbdev on 10/31. The following "fixes" it, but I
have no id
It seems that linux progs are using foreign ioctls on tape drives
which of course will fail.
Is there anyone already working on an emulation for these?
Are there similar problems for seriel devices?
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED]
From: Marcel Moolenaar <[EMAIL PROTECTED]>
Date: Tue, 31 Oct 2000 22:59:48 -0800
::> Anyone having problems with the linuxulator the past couple days?
::
::Define "past couple of days". I have a working linuxulator made on Oct
::29, 12:25 PST.
By following commit, makebdev() went away.
But there
On Tue, Oct 31, 2000 at 10:59:48PM -0800, Marcel Moolenaar wrote:
> Wesley Morgan wrote:
> >
> > Anyone having problems with the linuxulator the past couple days?
>
> Define "past couple of days". I have a working linuxulator made on Oct
> 29, 12:25 PST.
Mine:
Mon Oct 30 17:01:15 CET 2000 and
Wesley Morgan wrote:
>
> Anyone having problems with the linuxulator the past couple days?
Define "past couple of days". I have a working linuxulator made on Oct
29, 12:25 PST.
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe: send mail
Wesley Morgan wrote:
> Anyone having problems with the linuxulator the past couple days?
> Module fails to load for me, with this message:
> link_elf: symbol makebdev undefined
Yah, i do.
--
// Donny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bod
Anyone having problems with the linuxulator the past couple days?
Module fails to load for me, with this message:
link_elf: symbol makebdev undefined
--
_ __ ___ ___ ___ ___
Wesley N Morgan _ __ ___ | _ ) __| \
In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
: > By ETTW i mean estimated time to work :D
:
: It works right now and has for the last week. If you get out of date
: with your modules, on the other hand, you're shooting your own feet off.
And the move to the new layout may be shooting y
> By ETTW i mean estimated time to work :D
It works right now and has for the last week. If you get out of date
with your modules, on the other hand, you're shooting your own feet off.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
Tobias Fredriksson wrote:
> By ETTW i mean estimated time to work :D
> since the last compile a 1/2 days ago the linux emulation on my non-smp
> station has failed. Everything that has to use linux emulation crashes the
> kernel which is rather bad :/
>
> Anybody know when thi
On 14-Sep-00 Tobias Fredriksson wrote:
> By ETTW i mean estimated time to work :D
> since the last compile a 1/2 days ago the linux emulation on my non-smp
> station has failed. Everything that has to use linux emulation crashes the
> kernel which is rather bad :/
>
>
By ETTW i mean estimated time to work :D
since the last compile a 1/2 days ago the linux emulation on my non-smp
station has failed. Everything that has to use linux emulation crashes the
kernel which is rather bad :/
Anybody know when this is schedueled to be looked at / fixed?
To
On Sun, May 14, 2000 at 06:29:59PM +0200, Eric Jacoboni wrote:
> > "Jesper" == Jesper Skriver <[EMAIL PROTECTED]> writes:
>
> Jesper> Just upgraded my laptop from a late march -current to
> Jesper> -current as of a couple of hours ago.
>
> Jesper> When it loads the "Linux binary
> "Jesper" == Jesper Skriver <[EMAIL PROTECTED]> writes:
Jesper> Just upgraded my laptop from a late march -current to
Jesper> -current as of a couple of hours ago.
Jesper> When it loads the "Linux binary compatibility" it
Jesper> shutdown, if apm is enabled it looks like wh
Hi,
Just upgraded my laptop from a late march -current to -current as of a
couple of hours ago.
When it loads the "Linux binary compatibility" it shutdown, if apm is
enabled it looks like when one do a 'shutdown -p now'.
When I set linux_enable="NO" in /etc/rc.conf the machine boots properly,
b
The linux emulation patch has been committed to -current, you must
recompile your linux emulation kld.
This patch will be MFC'd to 4.x on Friday.
-Matt
Matthew D
Martin Blapp wrote:
> I really like to see your fix committed to STABLE. It fixes also the
> bad designed Staroffice 5.2 installation for some part (/usr/sbin/test).
...as well as the WordPerfect 2000 for Linux installation. Basically, it
sounds like it makes Linux emulation really co
On Sun, 23 Apr 2000, Matthew Dillon wrote:
> There's another good reason to MFC the linux patch on wednesday...
> that is, to do it at the same time the SMP cleanup is MFC'd, and that
> is because both patch sets require the linux kernel module to be
> recompiled and I'd rather
Hi Matt,
I really like to see your fix committed to STABLE. It fixes also the
bad designed Staroffice 5.2 installation for some part (/usr/sbin/test).
Thank you for your work !
Martin
Martin Blapp, [EMAIL PROTECTED]
Improware AG, UNIX solution a
>
> BTW; whilst I think Poul was entirely the wrong person to raise the
> issue, I agree that you probably want to hang back on MFCing the linux
> scripting changes for a week or so. This is really just common sense.
>
recently i added autoload to a usb related kernel module.
very ha
Mike Muir wrote:
>
> Nate Williams wrote:
>
> > I was under the impression that 4.x hasn't been designated as the stable
> > branch (yet). That will happen when 4.1 is released, but until that
> > happens 3.x is still considered the -stable release.
>
> That would kinda make sense since cvsupi
Nate Williams wrote:
> I was under the impression that 4.x hasn't been designated as the stable
> branch (yet). That will happen when 4.1 is released, but until that
> happens 3.x is still considered the -stable release.
That would kinda make sense since cvsuping with tag=RELENG_3 seems to
give
:
:>I do not consider the linux scripting patch to be a major infrastructure
:>change, I consider it to be a simple bug fix. If you have a functional
:>issue with the patch I'm all ears. If you disagree with my assessment of
:>the triviality of the linux scripting patch, then I
> I wonder if it makes sense to add a release id to the module header
> and have the module loader refuse (unless forced) to load modules that
> are out-of-date with the kernel?
We actually have a whole module dependancy and versioning system more or
less ready to go into -current.
>I do not consider the linux scripting patch to be a major infrastructure
>change, I consider it to be a simple bug fix. If you have a functional
>issue with the patch I'm all ears. If you disagree with my assessment of
>the triviality of the linux scripting patch, then I will as
On Sun, 23 Apr 2000, Matthew Dillon wrote:
> If core wants to change the current rules, that's fine by me. As I
> said before I think the breakage that we thought would happen with 5.x
> due to the BSDI merger that prompted the loose rules for 4.x is
> overrated, and the rules should
> >Core should consider reverting the special rules that were originally
> >created with the expectation of major breakage in 5.x back to
> >the set of rules we had for 3.x and 4.x.
>
> I have no idea what special rules you are talking about for 4.x/5.x.
>
> 4.x-stable is a -stable
:
:In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
:
:>Core should consider reverting the special rules that were originally
:>created with the expectation of major breakage in 5.x back to
:>the set of rules we had for 3.x and 4.x.
:
:I have no idea what special rules you are
:
:
:Matt,
:
:I will say it this last time:
:
: Your patch does not qualify for immediate MFC.
:
:--
:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
And I will say this to you for the last time: Under the current rules
my patch DOES qualify for an immediate MFC. Hell, by t
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>Core should consider reverting the special rules that were originally
>created with the expectation of major breakage in 5.x back to
>the set of rules we had for 3.x and 4.x.
I have no idea what special rules you are talking a
:> :
:> :--
:> :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
:>
:>I think you're confused, Poul. I've gone over the commits made
:>to the tree by people over the last few months and frankly there
:>are dozens of simultanious -current and -stable commits. A quick
:>check
>
> :
> :In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> :
> :>There's another good reason to MFC the linux patch on wednesday...
> :>that is, to do it at the same time the SMP cleanup is MFC'd, and that
> :>is because both patch sets require the linux kernel module to be
>
Matt,
I will say it this last time:
Your patch does not qualify for immediate MFC.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be
> There's another good reason to MFC the linux patch on wednesday...
> that is, to do it at the same time the SMP cleanup is MFC'd, and that
> is because both patch sets require the linux kernel module to be
> recompiled and I'd rather not force people to do that twice.
>
>
:
:In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
:
:>There's another good reason to MFC the linux patch on wednesday...
:>that is, to do it at the same time the SMP cleanup is MFC'd, and that
:>is because both patch sets require the linux kernel module to be
:>recompile
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>I'm sorry, Poul, but you are going to have to come up with better
>reasoning then that.
>
>Not all changes committed to -current require a waiting period before
>being MFC'd to stable. Specifically, simple and obvious bug f
:In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
:
:>:I don't see anything justifying an immediate MFC in this patch. Please
:>:allow the normal waiting period to elapse before you MFC.
:>
:>Unless you can justify a reason for it NOT to be MFC'd immediately, I
:>see no reason to wa
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>There's another good reason to MFC the linux patch on wednesday...
>that is, to do it at the same time the SMP cleanup is MFC'd, and that
>is because both patch sets require the linux kernel module to be
>recompiled and I'd
There's another good reason to MFC the linux patch on wednesday...
that is, to do it at the same time the SMP cleanup is MFC'd, and that
is because both patch sets require the linux kernel module to be
recompiled and I'd rather not force people to do that twice.
The SMP pat
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>:I don't see anything justifying an immediate MFC in this patch. Please
>:allow the normal waiting period to elapse before you MFC.
>
>Unless you can justify a reason for it NOT to be MFC'd immediately, I
>see no reason to wait for
justifying an immediate MFC in this patch. Please
:allow the normal waiting period to elapse before you MFC.
:
:--
:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
It's such a simple patch, and it fixes problems that would otherwise
exist under 4.x's linux emulation, and
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>I intend to commit this to -current and immediately MFC it to -stable.
>I don't expect there to be any controversy though I'm sure there is a
>cleaner way to do it.
I don't see anything justifying an immediate MFC in this patch.
racle
installer stuff).
http://www.backplane.com/FreeBSD4/linux-script-01.diff
This patch fixes #! paths in scripts run under linux emulation, causing
/compat/linux to be searched for the script binary when the script
is exec'd from a program running under emulation.
At 11:09 AM -0700 2000/4/10, Matthew Dillon wrote:
> I can't say I'm impressed. Oracle itself is a very complete relational
> database, but their replication capabilities suck. They only do
> non-quorum fully synchronous replication or non-quorum fully
> asynchronous replica
Matthew Dillon wrote:
> Basically I had to take the linux_base port, and then chroot into
> /usr/compat/linux and install the rpm's for most of redhat, including
> the compiler environment, and the ld.so and ldd piece from slackware
> (because redhat's is broken under emulation).
ackdown JDK, are you?
:
:--
:Marcel Moolenaar
Yes. I've managed to get oracle-8i installed on FreeBSD under linux
emulation, but it was a chore. It took 30 hours before I was able to
figure it out from a combination of playing around and locating the
redhat install support
also noted another major issue with the linux emulation, and that
> is with shell script execution.
>
> If you are running a linux binary which then fork/exec's a shell script,
> the interpreter path at the top of the shell script does not undergo
> the path mungi
wrong.
I've also noted another major issue with the linux emulation, and that
is with shell script execution.
If you are running a linux binary which then fork/exec's a shell script,
the interpreter path at the top of the shell script does not undergo
the path mu
On Wed, 23 Feb 2000, Victor A. Salaman wrote:
> Anyways, after sending email to marcel and peter with the patches, I haven't
> even received a reply. :-(
>
> So therefore, I'm posting them here, in case anyone wants to commit
> them at all. I feel 4.0 shouldn't go
Hi:
I was wondering who
mantains the Linux Emulation? I have some patches that were sent to me for
FreeBSD-3.4, I have converted them to FreeBSD 4.0-Current for Linux emulation
problems. Specifically anyone trying to use any program that opens a server
socket will get bitten by the
Fritz & Doug,
Doug White <[EMAIL PROTECTED]> writes:
> On Thu, 27 Jan 2000, F. Heinrichmeyer wrote:
>
> > I would like to use an ASDM (backup software) with linux-emulation. I
> > get
> > the following in /var/log/messages:
> >
> > es-i2
On Thu, 27 Jan 2000, F. Heinrichmeyer wrote:
> I would like to use an ASDM (backup software) with linux-emulation. I
> get
> the following in /var/log/messages:
>
> es-i2 /kernel: linux: syscall setresuid is obsoleted\
> or not implemented (pid=41052)
> Jan 27 13:12:42 es-
On Thu, Jan 27, 2000 at 01:39:38PM +0100, F. Heinrichmeyer wrote:
> I would like to use an ASDM (backup software) with linux-emulation. I
> get
> the following in /var/log/messages:
Have you tried the SCO client with the IBCS module loaded? I've been using it
with great succe
1 - 100 of 122 matches
Mail list logo
