El día Monday, April 11, 2011 a las 09:31:47AM +0200, Matthias Apitz escribió:
> Hello,
>
> I removed the VMware' vmware-tools-freebsd and installed from the ports
> x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware;
>
> When I now run 'X -configure' the X.org server Seg faults af
El día Friday, April 08, 2011 a las 05:24:59PM -0400, Alexander Kabaev escribió:
> > > X.org 7.5 already has VMware drivers, so you can just install the
> > > x11-drivers/xf86-input-vmmouse and x11-drivers/xf86-video-vmware
> > > ports.
> > >
> > > Alternatively, run "make config" in x11-drivers/
On Apr 8, 2011, at 5:03 AM, Matthias Apitz wrote:
> El día Friday, April 08, 2011 a las 12:17:03PM +0200, Dimitry Andric escribió:
>
>> On 2011-04-08 10:42, Matthias Apitz wrote:
>>> I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and
>>> I tried to install the vmware-tools-f
On Fri, 8 Apr 2011 14:03:36 +0200
Matthias Apitz wrote:
> El día Friday, April 08, 2011 a las 12:17:03PM +0200, Dimitry Andric
> escribió:
>
> > On 2011-04-08 10:42, Matthias Apitz wrote:
> > >I have FreeBSD 9-CURRENT up and running in a VMware Workstation
> > >7.x and I tried to install the vmw
El día Friday, April 08, 2011 a las 12:17:03PM +0200, Dimitry Andric escribió:
> On 2011-04-08 10:42, Matthias Apitz wrote:
> >I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and
> >I tried to install the vmware-tools-freebsd of VMware to get the driver
> >for Xorg, but it seem
On 2011-04-08 10:42, Matthias Apitz wrote:
I have FreeBSD 9-CURRENT up and running in a VMware Workstation 7.x and
I tried to install the vmware-tools-freebsd of VMware to get the driver
for Xorg, but it seems that X.org 7.6.5. is not supported. My other VM
runs a 8-CURRENT with X.org 7.4_1 which
Thanks to everyone who suggested things... now the port's been updated it
compiles fine. Doesn't run, however, but I'll try to suss that out myself...
thanks,
Ben
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curr
Hello!
On Thu, Nov 20, 2003 at 04:53:57PM -0600, Eric Anderson wrote:
> >Guessing you're running -CURRENT you have the kernel source installed,
> >so my suggestion is to run vmware3.
> >
> >Unless you have a specific reason to run 2?
> >
> Maybe he doesn't run 3 because it also doesn't build:
>
Scott Likens wrote:
On Thu, 2003-11-20 at 12:38, Ben Paley wrote:
Hello all.
I think this is a -current issue. When I started using -current I began to get
weird behaviour from vmware2: eventually every time I powered on the virtual
machine the screen would freeze up so I couldn't get a cons
On Thu, 2003-11-20 at 12:38, Ben Paley wrote:
> Hello all.
>
> I think this is a -current issue. When I started using -current I began to get
> weird behaviour from vmware2: eventually every time I powered on the virtual
> machine the screen would freeze up so I couldn't get a console, and then
On Sat, 2003-08-30 at 04:32, Masahide -mac- NODA wrote:
> Sorry, this is repot only.
>
> I'm upgrading from 2003/08/19 current to 2003/08/30 current on vmware
> 3.x(host OS is Windows), and I tried to run vmware-guestd,
>
># ./vmware-guestd
>ELF binary type "0" not known.
>/usr/local/
On Fri, 2003-07-25 at 04:54, Sławek Żak wrote:
> vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
>
> (kgdb) bt
> #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
> #1 0xc02217d9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
> #2 0xc0221bb8 in panic
On Fri, 2003-07-25 at 07:54, Sławek Żak wrote:
> vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
>
> /S
I've been seeing these for a few days as well. I just did a quick
search for open PRs and found ports/54417 that says you should have
"options VFS_AIO" in your ker
Did you rebuild the Vmware kernel module(s) from scratch? Make sure you
do so each time you update to a newer kernel version, as it's important
the data structures referenced by the module be the same version as the
ones referenced by the kernel you're running. I've seen precisely this
output whe
VMWare.
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
On Mon, 30 Jun 2003, Eirik Oeverby wrote:
> Reinstalling what? VMWare or FreeBSD?
>
> On Mon, 30 Jun 2003, Lutz Bichler wrote:
>
> > I got the same problem/message and
Hi,
Reinstalling what? VMWare or FreeBSD?
/Eirik
On Mon, 30 Jun 2003, Lutz Bichler wrote:
> I got the same problem/message and "solved" it by reinstalling ;-)
>
> Lutz
>
> --
> Lutz Bichler
> Institute for Software Technology, Department of Computer Science
> Univ. of the Fed. Armed Forces Muni
No.
On Sun, 26 Jan 2003, Theodoor van der Kooij wrote:
> Hi all,
>
> is there a way to run VMWare 3.2 on FreeBSD 5.0?
>
> regards,
>
> Theodoor van der Kooij.
> --
> Windows: "Where do you want to go today?"
> Linux: "Where do you want to go tomorrow?"
> FreeBSD: "Are you guys coming, or what?"
>
On Mon, 1 Apr 2002, Makoto Matsushita wrote:
>
> never> Maybe it's better to make two different ports vmware-tools and
> never> vmware-tools3, first of which is for vmware2?
>
> Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for
> VMware _1.x_) is outdated for VMware 2.x; i
never> Maybe it's better to make two different ports vmware-tools and
never> vmware-tools3, first of which is for vmware2?
Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for
VMware _1.x_) is outdated for VMware 2.x; it doesn't have time sync
feature.
If you're VMware 2.x user
Hello, Makoto Matsushita!
On Mon, Feb 04, 2002 at 12:35:51AM +0900, you wrote:
> ggombert> VMware tools for FreeBSD is woefully out of date as well,
> % cd /usr/ports/emulators/vmware-tools
> % make -V PORTVERSION
> 3.0.0.1455
>
> VMware 3.0 bundles a new VMware tools, and it is up-to-date vers
> Does anyone know if there is an active effort to port VMware Workstation
> 3.0 for Linux to run under FreeBSD ?? Version 2 of Workstation is no
longer
> avaiable it seems...
It is still available, in the Support/Archive section of their website. I'd
love to know if someone plans to port 3.0 tho
I run VMware workstation under Windows 2000 on my laptop and install
FreeBSD as a 'guest' operating system, the verison of VMware tools for
FreeBSD dates all the way back to 1999 I think and has not been updated
since :)
At 12:35 AM 2/4/2002 +0900, Makoto Matsushita wrote:
>
>ggombert> VMware to
ggombert> VMware tools for FreeBSD is woefully out of date as well,
Really?
% cd /usr/ports/emulators/vmware-tools
% make -V PORTVERSION
3.0.0.1455
VMware 3.0 bundles a new VMware tools, and it is up-to-date version as
of Linux guests.
% cd /usr/ports/emulators/vmware-tools
% make -V MAINTAIN
Thanks for filing the incident report, VMware tools for FreeBSD is woefully
out of date as well, X11 and -Current run fine under VMware workstation,
with the patch that was mentioned several days ago :)
>
>matusita> I've just filed an incident (I have a license of VMware 3.0).
>
>I've received a
matusita> I've just filed an incident (I have a license of VMware 3.0).
I've received a reply from VMware:
> Thank you for submitting the incident and letting us know the
> potential workaround.
> I must apologize because we do not support FreeBSD 5.0 as a guest OS
> yet in Workstation 3.
I've got the 20020112 snapshot running in vmware. I did have similar
trouble booting initially; I was installing a base system off an old 4.2-
RELEASE CD I had and cvsuping straight to 5-CURRENT, and the system would
always hang when attempting to mount the root partition. I got it working
by cv
rwatson> If someone has a commercial license, it would make sense
rwatson> submitting this via a trouble ticket, as well as providing
rwatson> the VMware support people with some brief directions on
rwatson> installing 5.0.
I've just filed an incident (I have a license of VMware 3.0).
-- -
Mako
Have to wonder if it wouldn't be worth e-mailing the VMware people about
this -- they'd probably rather know in advance if there's a potential
problem hosting future versions of FreeBSD under VMWare. If someone has a
commercial license, it would make sense submitting this via a trouble
ticket, as
Here is an item that was mentioned sometime ago on the mailing list,
-CURRENT runs just fine under VMWare Workstation 3.0 (on Win2K
Professional) once this patch is made:
Glenn G.
>>>
Someone mentioned on a list somewhere that vmware takes forever to
emulate the cmpxchg inst
> "ID" == Ian Dowse <[EMAIL PROTECTED]> writes:
ID> In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
> I'll try. Oh, I forget to say I appiled des's linux_ioctl patch.
>
ID> Ah, that's different then. I assumed from the error that you had
ID> revision 1.76 of li
In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
>I'll try. Oh, I forget to say I appiled des's linux_ioctl patch.
>
Ah, that's different then. I assumed from the error that you had
revision 1.76 of linux_ioctl.c, but if that patch applied then you
don't. Try updating your sources again; revi
> "ID" == Ian Dowse <[EMAIL PROTECTED]> writes:
ID> In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
> Hmm.. I have experienced another problem(-current of 19 Nov.) with
> vmware. When it runs it comes up with the following dialog:
>
> "Encountered an error whi
In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
>Hmm.. I have experienced another problem(-current of 19 Nov.) with
>vmware. When it runs it comes up with the following dialog:
>
> "Encountered an error while initializing the ethernet address.
> You probably have an old vnet driver. Try in
> "HM" == Hellmuth Michaelis <[EMAIL PROTECTED]> writes:
HM> After this, vmware comes up and then complains about not able to use
HM> /dev/rtc (/dev/rtc is present in /compat/linux and is kld-loaded) but
HM> then continues to start up and runs.
Hmm.. I have experienced another pr
Hellmuth Michaelis writes:
> Today i got it to compile and run:
>
> - apply the patch from Munehiro Matsuda to hostif.c, this makes the vmware2
> port compile under -current as of today
>
> - as described above, use /dev/vmnet1 instead of /compat/linux/dev/vmnet1
> in /usr/local/etc/
>From the keyboard of Georg-W. Koltermann:
> At Sun, 18 Nov 2001 09:37:12 +0100 (MET),
> Hellmuth Michaelis wrote:
> >
> > Thought i update my current this morning and ran into two problem with
> > vmware:
> >
> > 1) when starting vmware, vmware.sh aborts with
> >
> >vmware.sh: cannot creat
In message <[EMAIL PROTECTED]>, "Georg-W. Koltermann" writes
:
>I also tried to update /compat/linux/dev/vmnet1 to match the
>/dev/vmnet1, and that got me just a litte bit farther. I now get
>"Could not get address for /dev/vmnet1: Invalid argument
>Failed to configure ethernet0." I added some pr
At Sun, 18 Nov 2001 09:37:12 +0100 (MET),
Hellmuth Michaelis wrote:
>
> Thought i update my current this morning and ran into two problem with
> vmware:
>
> 1) when starting vmware, vmware.sh aborts with
>
>vmware.sh: cannot create /compat/linux/dev/vmnet1: no such device
>or address
H
[EMAIL PROTECTED] writes:
> Has anyone seen similar problem on recent -current or has someone an
> idea why vmware is issuing a SIOCGIFCONF ioctl without providing an
> interface name?
>
> Oct 19 18:04:53 mp /boot/kernel/kernel: linux_ioctl_socket(): ioctl 35093 on
To clarify, this is from debug
On 19 Oct, Dag-Erling Smorgrav wrote:
> [EMAIL PROTECTED] writes:
>> The error
>>
>> Could not get address for /dev/vmnet1: argument is invalid
>> Failed to configure ethernet0
>>
>> is all I get... (this is the host-only case, for bridged it says
>> something like could not get bri
On Tue, Sep 12, 2000 at 04:44:41PM +0200, Reinier Bezuidenhout wrote:
> Let me first ask ... do you use the "suspend/resume" option??
Yep.
> This caused the same "lockup" every few seconds on my machine too -
> a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted
> it worked fine.
On Wed, Sep 13, 2000 at 10:48:20AM -0400, Brian A. Seklecki - Stargate Industries, LLC
- NOC wrote:
> You're running vmware sucsessfully in --current?
Yes. -current from August 18th, and I'm running the vmware2-2.0.2.621 port.
Installing Win98 took about 4 hours though -- most of that was wh
T)
> From: Reinier Bezuidenhout <[EMAIL PROTECTED]>
> To: "Brian A. Seklecki - Stargate Industries, LLC - NOC"
> <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: VMWare on -current, how fast should I expect it to be?
>
> Hi ..
>
> I d
Brian A. Seklecki - Stargate Industries, LLC - NOC wrote:
>
> You're running vmware sucsessfully in --current? I sync'd up the last
> time I was in the office (last...Friday?) and the linux emulation package
> refused to build in --current; complaining about an incopatible kernel
> module. In f
You're running vmware sucsessfully in --current? I sync'd up the last
time I was in the office (last...Friday?) and the linux emulation package
refused to build in --current; complaining about an incopatible kernel
module. In fact, i had to comment out the linux proc file system (from
the linux
On Tue, Sep 12, 2000 at 07:09:00AM -0700, Julian Elischer wrote:
> > atapci0: port 0xfc90-0xfc9f at device 7.1 on
>pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > ad0: 17301MB [35152/16/63] at ata0-master using UDMA33
> >
> > This is -current
On Tue, Sep 12, 2000 at 02:27:45PM +0100, Nik Clayton wrote:
> For those of you running VMWare (2) on -current, how fast do you expect it to
> be?
I'm running it on my PIII 366 laptop. It's not great, but it's usable.
The biggest factors I've seen effecting performance are memory related.
Runnin
On Tue, 12 Sep 2000 10:13:16 -0400 (EDT)
Thomas David Rivers <[EMAIL PROTECTED]> wrote:
>
> Julian Elischer ([EMAIL PROTECTED]) wrote:
> I'm confused...
'fraid so. It is raw devices (for discs) that linux doesn't have,
they are all block devices - although I may be out of date it's bee
I have seen this too ...
Let me first ask ... do you use the "suspend/resume" option??
If Yes then :)
This caused the same "lockup" every few seconds on my machine too -
a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted
it worked fine.
I guess it is something in VMware that s
Julian Elischer ([EMAIL PROTECTED]) wrote:
>
> Nik Clayton wrote:
> >
> > Hi guys,
> >
> > For those of you running VMWare (2) on -current, how fast do you expect it to
> > be?
> >
> > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the
> > following disk controller / dis
Nik Clayton wrote:
>
> Hi guys,
>
> For those of you running VMWare (2) on -current, how fast do you expect it to
> be?
>
> I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the
> following disk controller / disk
>
> atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0
>
In message <[EMAIL PROTECTED]> Mike Smith writes:
: As far as the loader is concerned, though, neither of these are on the
: boot path, so we can typically wait until the kernel's up and we can use
: some "real real" drivers. 8)
Well, I have seen boards that support booting off pccard devices..
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : > a larger issue. It is not the loader's job to detect the underlying
> : > hardware configuration.
> :
> : Actually, in a broad fashion, it _is_. This is why the loader
> : understands PCI and PnP, for example.
>
> How hard would it be t
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > a larger issue. It is not the loader's job to detect the underlying
: > hardware configuration.
:
: Actually, in a broad fashion, it _is_. This is why the loader
: understands PCI and PnP, for example.
How hard would it be to add usb and pc
In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > > It is not the loader's job to detect the underlying
> > > hardware configuration.
> >
> > I disagree. I would like to tell which machine I am booting on to
> > choose an appropriate kernel.
> >
> Eve
> In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > It is not the loader's job to detect the underlying
> > hardware configuration.
>
> I disagree. I would like to tell which machine I am booting on to
> choose an appropriate kernel.
>
Eventually (it may take a while) we should be able to boot any
> > > a larger issue. It is not the loader's job to detect the underlying
> > > hardware configuration.
> >
> > Actually, in a broad fashion, it _is_. This is why the loader
> > understands PCI and PnP, for example.
> >
> Why do we want to do that? Are we going to offload device probe routines
> > a larger issue. It is not the loader's job to detect the underlying
> > hardware configuration.
>
> Actually, in a broad fashion, it _is_. This is why the loader
> understands PCI and PnP, for example.
>
Why do we want to do that? Are we going to offload device probe routines to
the loader
> a larger issue. It is not the loader's job to detect the underlying
> hardware configuration.
Actually, in a broad fashion, it _is_. This is why the loader
understands PCI and PnP, for example.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn h
> Given the way VMware works, I'd have nothing against making it a FICL
> words, except...
>
> ...VMware is a port. For some reason, I dislike the idea of having
> support targetted at exclusively one specific port. Though we have
> features added specifically to deal with certain ports, they wer
At 10:47 AM -0700 6/11/00, Mike Smith wrote:
>It's not a port, it's a platform. We probably want to add extra
>words to detect other platform features, eg. i386, alpha, ia64,
>etc. but that doesn't invalidate the basic idea.
For instance, I might be running the vmware program itself under
linux,
> Mike Smith wrote:
> >
> > > ...VMware is a port. For some reason, I dislike the idea of having
> > > support targetted at exclusively one specific port. Though we have
> > > features added specifically to deal with certain ports, they were all
> > > more generic features.
> >
> > It's not a po
Mike Smith wrote:
>
> > ...VMware is a port. For some reason, I dislike the idea of having
> > support targetted at exclusively one specific port. Though we have
> > features added specifically to deal with certain ports, they were all
> > more generic features.
>
> It's not a port, it's a platf
Peter Wemm wrote:
>
> > 2) Add the VMware detecting to FICL, as originally suggested.
>
> Why make #2 vmware specific? Why not set $emulation to native,vmware,bochs,
> etc. This is applicable to any platform that may have some sort of emulator.
> Putting it in an environment variable has the a
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-specific word that detects the
> > presence of VMware i
"Daniel C. Sobral" wrote:
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-specific word that detects th
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-specific word that detects the
> > presence of VMware i
Mike Smith wrote:
>
> > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > register is set to a magic value, otherwise it would be handled as any
> > other ports.
>
> I think, again, that adding an i386-specific word that detects the
> presence of VMware is a perfectly se
> > As for setting registers ti specific values... huh? Why does this
> > matter? Can you explain exactly what your code does and how?
> >
> VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> register is set to a magic value, otherwise it would be handled as any
> other por
> As for setting registers ti specific values... huh? Why does this
> matter? Can you explain exactly what your code does and how?
>
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other ports.
-lq
T
Luoqi Chen wrote:
>
> > We have inb and outb. Can't vmware be written in Forth? If inl cannot be
> > replaced with inb, I'd rather add inl than vmware.
> But we can't set registers to specific values before inb/outb, which also
> means our inb/outb are quite useless in making BIOS calls.
BIOS c
> We have inb and outb. Can't vmware be written in Forth? If inl cannot be
> replaced with inb, I'd rather add inl than vmware.
>
But we can't set registers to specific values before inb/outb, which also
means our inb/outb are quite useless in making BIOS calls.
> IMHO, it would be better to add
Luoqi Chen wrote:
>
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine? I find it extremely useful when I'm running
> FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
> single kernel to boot both directly or inside th
Peter Wemm wrote:
>
> Christopher Masto wrote:
> > On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> > > I'm not sure it is a good idea to name this variable VMWare as
> > > that is implementation specific. It may be better to have a var
> > > named 'emulation' set to 'non
Christopher Masto wrote:
> On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> > I'm not sure it is a good idea to name this variable VMWare as
> > that is implementation specific. It may be better to have a var
> > named 'emulation' set to 'none' or 'vmware' or 'bochs' or ..
> > extern void ficlOutb(FICL_VM *pVM);
> > extern void ficlInb(FICL_VM *pVM);
I'm an idiot.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net
Free yourself, free your machine, free the d
On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> I'm not sure it is a good idea to name this variable VMWare as
> that is implementation specific. It may be better to have a var
> named 'emulation' set to 'none' or 'vmware' or 'bochs' or ...
Mmm.. or, giving forth the abi
Luoqi Chen wrote:
>
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine? I find it extremely useful when I'm running
> FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
> single kernel to boot both directly or inside th
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine?
Sounds good to me!
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a
On Sun, Mar 05, 2000 at 01:35:27PM +, Nick Sayer wrote:
> Ah! I found it!
>
> --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000
> +++ linux_ioctl.h Mon Feb 28 11:24:08 2000
> @@ -32,6 +32,25 @@
> #define_LINUX_IOCTL_H_
This patch is fubar'ed. Your mailer wrapped lines and tur
Ah! I found it!
--- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000
+++ linux_ioctl.h Mon Feb 28 11:24:08 2000
@@ -32,6 +32,25 @@
#define_LINUX_IOCTL_H_
/*
+ * disk
+ */
+#define LINUX_BLKROSET 0x125d
+#define LINUX_BLKROGET 0x125e
+#define LINUX_BLKRRPART
Andrew Atrens wrote:
>
> A missing (not implemented) linux ioctl is breaking VMWare 2.0 -
>
> > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented
I implemented this ioctl. It's not as hard as you think. You do a
DIOCGDINFO and return d_secperunit. But unfortunately, when I
did this, a wa
At Sun, 5 Mar 2000 01:32:39 -0500 (EST),
Andrew Atrens <[EMAIL PROTECTED]> wrote:
>
> A missing (not implemented) linux ioctl is breaking VMWare 2.0 -
>
> > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented
>
>
> After rummaging around in the 2.3 kernel, I found the following in
> `linu
On Thursday, 23 December 1999 at 21:29:08 -0800, Julian Elischer wrote:
>
> seems to work fine,
> except that now we don't have block devices any more
> so every time it gets stuff off disk, it's REALLY SLOW.
>
> I guess a virtual machine is the "App that no-one could put their finger
> on" that r
On Fri, 24 Dec 1999, Poul-Henning Kamp wrote:
>
> It is not out of the question to bring buffered disk access back,
> but it will be an ioctl enabled function for disks, not a vnode
> mode. Peter has suggested doing it with a layered device a'la vn(4).
Actually that was me.
To Unsubscribe
In message <[EMAIL PROTECTED]>, Thomas David Rivers writes
:
>> seems to work fine,
>> except that now we don't have block devices any more
>> so every time it gets stuff off disk, it's REALLY SLOW.
>>
>> I guess a virtual machine is the "App that no-one could put their finger
>> on" that really
> seems to work fine,
> except that now we don't have block devices any more
> so every time it gets stuff off disk, it's REALLY SLOW.
>
> I guess a virtual machine is the "App that no-one could put their finger
> on" that really could do with buffered (caching) devices.
Hmmm I wonder what
On Fri, Aug 06, 1999 at 11:49:33PM +0900, Kazutaka YOKOTA wrote:
>
> >> >At this point we must still be in freebsd xinit, then XF86_VMware(linux
> >> >server) get started. I'm running a linux X server under freebsd. Under
> >> >3.2R all I had to do was change the symlink for X to point to XF86_
On Fri, Aug 06, 1999 at 01:07:13PM +0200, Marcel Moolenaar wrote:
> Bernd Walter wrote:
>
> > It needs ttyp0 as tty0 and so on.
> > I tried it myself under current and got the X11 window.
> > but it complained that it can't find /proc/cpuinfo.
> > I never beleaved that it would work after that.
>
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote:
> >Hello
> >
> > I had tried it both ways, when I said having them symlinked to
> >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I
> >use ttyp0 and ttyp4 respectfully.
>
> I don't think ttyp* will work. I don't know who sug
>> >At this point we must still be in freebsd xinit, then XF86_VMware(linux
>> >server) get started. I'm running a linux X server under freebsd. Under
>> >3.2R all I had to do was change the symlink for X to point to XF86_VMware,
>> >under -current /dev/tty0 can't be found.
>> >
>> >Where was
On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote:
>
> >At this point we must still be in freebsd xinit, then XF86_VMware(linux
> >server) get started. I'm running a linux X server under freebsd. Under
> >3.2R all I had to do was change the symlink for X to point to XF86_VMware,
> >under -current /dev
>At this point we must still be in freebsd xinit, then XF86_VMware(linux
>server) get started. I'm running a linux X server under freebsd. Under
>3.2R all I had to do was change the symlink for X to point to XF86_VMware,
>under -current /dev/tty0 can't be found.
>
>Where was linux "/dev/tty0"
On Fri, 6 Aug 1999, Marcel Moolenaar wrote:
> "Eric J. Chet" wrote:
> >
> > On Wed, 4 Aug 1999, Bernd Walter wrote:
> >
> > > It needs ttyp0 as tty0 and so on.
> > > I tried it myself under current and got the X11 window.
> > > but it complained that it can't find /proc/cpuinfo.
> > > I never
Bernd Walter wrote:
> It needs ttyp0 as tty0 and so on.
> I tried it myself under current and got the X11 window.
> but it complained that it can't find /proc/cpuinfo.
> I never beleaved that it would work after that.
I assume you didn't try to make a regular file called cpuinfo in
/compat/linux
"Eric J. Chet" wrote:
>
> On Wed, 4 Aug 1999, Bernd Walter wrote:
>
> > It needs ttyp0 as tty0 and so on.
> > I tried it myself under current and got the X11 window.
> > but it complained that it can't find /proc/cpuinfo.
> > I never beleaved that it would work after that.
>
> Hello
> I
On Wed, 4 Aug 1999, Bernd Walter wrote:
> It needs ttyp0 as tty0 and so on.
> I tried it myself under current and got the X11 window.
> but it complained that it can't find /proc/cpuinfo.
> I never beleaved that it would work after that.
Hello
It should work, I used it under fbsd-3.2R f
On Tue, Aug 03, 1999 at 12:30:25PM -0400, Eric J. Chet wrote:
> On Tue, 3 Aug 1999, Matthew Dillon wrote:
>
> >
> > :--0-169768575-933691257=:71237
> > :Content-Type: TEXT/PLAIN; charset=US-ASCII
> > :
> > :Hello
> > : I have been using FreeBSD under vmware for a few weeks now,
> > :running 3.
On Tue, Aug 03, 1999 at 04:25:40PM -0400, Garance A Drosihn wrote:
> If you're asking for a freely-available open-source BSD-license
> product which does the same things vmware does, I am afraid I
> don't know what projects are underway.
The only one I know of at all is freemware (www.freemware.o
At 3:08 PM -0400 8/3/99, Ayan George wrote:
>I've been wondering -- are there any plans for a FreeBSD version
>of VMware?
The makers of VMware are probably wondering if they would sell
enough copies of a FreeBSD-based version. If you would buy
such a product, then let them know. Check www.vmwa
1 - 100 of 106 matches
Mail list logo
