from cd9660:/dev/iso9660/nanoISO [ro]...
Thanks
On Mon, Jul 15, 2013 at 3:56 PM, Olivier Nicole wrote:
> Ganesh,
>
> > I am new to Nanobsd and trying to create an iso image which can be
> > installed on vmware machine.
> >
> > I created an iso image usin
Ganesh,
> I am new to Nanobsd and trying to create an iso image which can be
> installed on vmware machine.
>
> I created an iso image using the disk image
> (/usr/obj/nanobsd.full/_.disk.image) generated according to steps
> given in NanoBSD
> How To <http://www.fre
Dear Friends,
I am new to Nanobsd and trying to create an iso image which can be
installed on vmware machine.
I created an iso image using the disk image
(/usr/obj/nanobsd.full/_.disk.image) generated according to steps
given in NanoBSD
How To <http://www.freebsd.org/doc/en/articles/nano
Hi,
I am trying to create a virtual machine of PC-BSD release 9.1 64 bit in VMware
Workstation Version 98.02 build-1031769 based on PCBSD9.1-x64-DVD.iso
downloaded from ftp://mirrors.isc.org/pub/pcbsd/9.1/amd64/PCBSD9.1-x64-DVD.iso
in Windows 7 64 bits system. The screen resolution is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/8/13 7:09 AM, Olivier Nicole wrote:
> Hi,
>
> I am running an ESXi 5.1 VMware server, with one FreeBSD (8.3)
> guest.
>
> I am trying to figure how to install the VMware tools:
>
> - the linux one are working, but I wo
If this is a production server operation VMWare will *only* support you
running their list of supported FreeBSD versions and their official VMWare
Tools. This means you'll often be left behind several releases with the
most recent available being completely abandoned by the FreeBSD pr
Hi,
I am running an ESXi 5.1 VMware server, with one FreeBSD (8.3) guest.
I am trying to figure how to install the VMware tools:
- the linux one are working, but I woul prefere a more native FreeBSD
- should I install /usr/ports/emulators/vmware-guest6d ? It fails with
not finding vmware
Just curious if anyone has any good recommendations of settings for
running FreeBSD under VMware ESXi 5.1 with PCI(e) pass through enabled.
I have been doing some initial testing with a new motherboard processor
and RAM. That I am hoping to be able to run 3 Servers on.
The intended virtual
On 18 December 2012 15:27, Devin Teske wrote:
>
> On Dec 18, 2012, at 6:35 AM, Luke Bakken wrote:
> Live resize (without reboot even) is something being worked on for the future
> 10.x series.
Looking forward to this, we can't offer cloud instances with FreeBSD
until this happens.
__
On Dec 18, 2012, at 6:35 AM, Luke Bakken wrote:
>> You'll of course need to boot from another medium to do this.
>>
>
> That's my main question - can a larger disk be detected *without* a
> reboot. On FreeBSD instances running within VMWare I have been able to
&
On Tue, 18 Dec 2012, Luke Bakken wrote:
You'll of course need to boot from another medium to do this.
That's my main question - can a larger disk be detected *without* a
reboot. On FreeBSD instances running within VMWare I have been able to
add new disks without a reboot but, as I
> You'll of course need to boot from another medium to do this.
>
That's my main question - can a larger disk be detected *without* a
reboot. On FreeBSD instances running within VMWare I have been able to
add new disks without a reboot but, as I described below, have not
found
It can be done but it's not easy and not pretty.
You'll have to rewrite the partition scheme to grow *only* the last partition
and then use growfs on the last partition to zero the new inodes within its
newly defined range.
You'll of course need to boot from another medium to do this.
I usuall
Hello everyone -
I'm looking for a way to get FreeBSD 8 / 9 to detect that an already
existing disk has grown. I have FreeBSD running as a guest within
vSphere ESX 5. Here is the output of camcontrol showing how the disks
are detected within the OS:
[root@QA1HWFBSD83201 ~]# camcontrol inquiry da0
On Mon, 01 Oct 2012 15:00:40 -0500, wrote:
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): WRITE(10). CDB: 2a 0 5
ee 60 16 0 1 0 0
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): CAM status: SCSI
Status Error
Sep 21 02:14:55 backups kernel: (da1:mpt0:0:1:0): SCSI status: Busy
Sep 21 0
On Wednesday, June 6, 2012 8:36:04 PM UTC-5, Mark Felder wrote:
> Hi guys I'm excitedly posting this from my phone. Good news for you guys, bad
> news for us -- we were building HA storage on vmware for a client and can now
> replicate the crash on demand. I'll be posting deta
If you did your research in advance you'd realize you're in for a flame war.
On 7/13/2012 9:48 AM, Edwin Abl wrote:
Hi,
Looking for the contact information of Linux server users across the USA and
UK? Or VMware users globally?
We have a segmented database of 50
Hi,
Looking for the contact information of Linux server users across the USA and
UK? Or VMware users globally?
We have a segmented database of 50,000+ SUSE Linux Enterprise Server (SLES)
and Red Hat Enterprise Linux (RHEL) users. We also have large databases of
Microsoft SharePoint
On Fri, Jun 22, 2012 at 3:13 PM, UNIX developer @ Google.com <
developeru...@gmail.com> wrote:
> Ok, I understud!
> I remove from rc.conf this rows:
> static_routes="clnet"
> route_clnet="-net 192.168.2.0/24 192.168.1.10"
>
> new rc.conf:
> ifconfig_em0=" inet 192.168.1.10 netmask 255.255.255.0"
>
Thank you, Mark!
All work!
-
Вы писали 22 июня 2012 г., 16:31:39:
> On Fri, 22 Jun 2012 08:10:43 -0500, UNIX developer @ Google.com
> wrote:
>> now after reboot the problem still the same.
>> ping -S 192.168.2.1 192.168.1.1
>> PING 192.168.1.1 (192.168.1.1) from 192.168.2.1: 56 d
On Thu, 21 Jun 2012 15:59:36 -0500, UNIX developer @ Google.com
wrote:
/etc/rc.conf
ifconfig_em0=" inet 192.168.1.10 netmask 255.255.255.0"
ifconfig_em1=" inet 192.168.2.1 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
gateway_enable="YES"
static_routes="clnet"
route_clnet="-net 192.168.2
Hi!
I have problem with routing on FreeBSD.
I have ESXi 5 host. In there is 5 VMs and one of them is a BSD.
I need create router on BSD.
I try to setting up it with this manual:
http://www.freebsd.org/doc/handbook/network-routing.html
but problem is still the same...
I cant ping external network f
Hi guys I'm excitedly posting this from my phone. Good news for you guys, bad
news for us -- we were building HA storage on vmware for a client and can now
replicate the crash on demand. I'll be posting details when I get home to my PC
tonight, but this hopefully is enough to rep
On Thursday, May 31, 2012 11:11:11 am Mark Felder wrote:
> So when this hang happens, there never is a real panic. It just sits in a
> state which I describe as like being in a deadlock. How would I go about
> getting a crashdump if it never panics? Is it possible to do the dump over
> a netw
So when this hang happens, there never is a real panic. It just sits in a
state which I describe as like being in a deadlock. How would I go about
getting a crashdump if it never panics? Is it possible to do the dump over
a network or something because I don't believe it can write through the
On Wednesday, May 30, 2012 3:56:02 pm Mark Felder wrote:
> On Wed, 30 May 2012 12:17:07 -0500, John Baldwin wrote:
>
> >
> > Humm, can you test it with 2 CPUs?
> >
>
> We primarily only run with 1 CPU. We have seen it crash on multiple CPU
> VMs. Also, Dane Foster appeared to have been using m
On Wed, 30 May 2012 12:17:07 -0500, John Baldwin wrote:
Humm, can you test it with 2 CPUs?
We primarily only run with 1 CPU. We have seen it crash on multiple CPU
VMs. Also, Dane Foster appeared to have been using multiple CPUs in his
video transcoding VMs.
Unfortunately I can't give
On Wed, 30 May 2012 10:06:13 -0500, John Baldwin wrote:
Do you only have one CPU in this VM? If not, do you know which threads
the other CPUs were running (e.g. do you have ps7.png, etc.)?
correct, only one CPU in the VM
___
freebsd-questions@free
>
> I'd be glad to post a PR and assist in helping to get it permanently
> fixed. I certainly don't want this data to get lost and honestly our
> business uses FreeBSD on VMWare so much that we really need a permanent
> fix as much as anyone else :-)
>
> The re
Hi,
You guys now absolutely, positively have enough information for a PR.
It's still not clear whether it's a device/interrupt layer issue in
FreeBSD, or whether vmware is doing something wrong with how it
implements shared interrupts, or a bit of both..
Adrian
On 24 May 2012 1
be glad to post a PR and assist in helping to get it permanently fixed. I
> certainly don't want this data to get lost and honestly our business uses
> FreeBSD on VMWare so much that we really need a permanent fix as much as
> anyone else :-)
>
> The reason I've hesita
#x27;d be glad to post a PR and assist in helping to get it permanently fixed. I
> certainly don't want this data to get lost and honestly our business uses
> FreeBSD on VMWare so much that we really need a permanent fix as much as
> anyone else :-)
>
> The reason I'
to get lost and honestly our
business uses FreeBSD on VMWare so much that we really need a permanent
fix as much as anyone else :-)
The reason I've hesitated to post a PR so far is that I didn't have any
truly useful or concrete evidence of where the problem lies. After Dane
Fos
iate it if you and the other people who can reproduce
this could work with the em/mpt driver people and root cause why this
is going. I think having FreeBSD on vmware work stable out of the box
without these kinds of tweaks is the way to go - who knows what else
is lurking here..
I'm very v
t ... 0. Interesting.
The obvious thing here is we are comparing a userland Vbox guest to a
VMWare
hypervisor. From what little I know concerning any of this, to me it
sounds
vaguely like an APIC, LAPIC, and IO/APIC bug. There are known bugs wrt to
BIOS setting up IRQ routing incorrectly, and/or
ubdevice=0x8000 class=0x01
dev.mpt.0.%parent: pci0
dev.mpt.0.debug: 3
dev.mpt.0.role: 1
Very curious how 'irq 22 at device 22.0' and 'dev.mpt.0.%location: slot=22'
all match with a '22'.
The obvious thing here is we are comparing a userland Vbox guest to a VM
On Mon, 21 May 2012 12:01:19 -0500, Andrew Boyer
wrote:
You could try switching mpt to MSI. MSI interrupts are never shared.
Add this to /boot/device.hints:
hint.mpt.0.msi_enable="1"
Currently implementing this on the known crashy servers. I've been looking
around and all of our VM
On May 21, 2012, at 12:41 PM, Mark Felder wrote:
> OK guys I've been talking with another user who can recreate this crash and
> the last bit of information we've learned seems to be leaning towards
> interrupts/IRQ issues like someone (bz@ perhaps?) suggested.
>
> I'm still trying to test thi
OK guys I've been talking with another user who can recreate this crash
and the last bit of information we've learned seems to be leaning towards
interrupts/IRQ issues like someone (bz@ perhaps?) suggested.
I'm still trying to test this myself, but the other user was able to
recreate my cra
build of ESXi in the past that had a
different setting for video memory when you selected FreeBSD?
Another change people might want to do as suggested to us by VMWare
Support:
- Change CPU/MMU Virtualization to the bottom option -- "Use Intel
VTx/AMD-V for instruction set virtualizatio
I've installed the compat6x libraries and made a symlink to /lib for
libc.so.6 as per some docs I found; however, the vmware tools
installation is still failing with:
Unable to copy the source file
/usr/local/lib/vmware-tools/modules/binary/FreeBSD8.0-amd64/vmxnet.ko to
the
destination
On 4/2/2012 3:59 PM, Joe Greco wrote:
>> On 4/2/2012 11:43 AM, Joe Greco wrote:
>>> As a user, you can't win. If you don't report
>>> a problem, you get criticized. If you report a problem but can't figure
>>> out how to reproduce it, you get criticized. If you can reproduce it
>>> but you don't
Guys,
The crash on my machine with debugging has evaded me for a few days. I'm
still looking for further suggestions of things I should grab from the DDB
when it happens again.
Thanks for the help everyone!
___
freebsd-questions@freebsd.org mailin
> On 4/2/2012 11:43 AM, Joe Greco wrote:
> > As a user, you can't win. If you don't report
> > a problem, you get criticized. If you report a problem but can't figure
> > out how to reproduce it, you get criticized. If you can reproduce it
> > but you don't submit a workaround, you get criticize
On 4/2/2012 11:43 AM, Joe Greco wrote:
> As a user, you can't win. If you don't report
> a problem, you get criticized. If you report a problem but can't figure
> out how to reproduce it, you get criticized. If you can reproduce it
> but you don't submit a workaround, you get criticized. If you
t; these may serve to help shed light on where the
problem lies.
The interesting thing is that I took it and looked at it and came to a
conclusion that might have been wrong, though I think the trail of
reasoning I used was itself reasonable, given my exceedingly small (one
example of problem) samp
On 03/30/2012 07:41, Joe Greco wrote:
>> On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
> FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a he
Mark Felder wrote:
On Thu, 29 Mar 2012 12:24:30 -0500, wrote:
I just started reading this tread, but I am wondering if I missed
something here. What does this have to do with "Windows 7"?
I emailed him off-list but I'm guessing he thought this was on VMWare
Workstation or
On Fri, 30 Mar 2012 11:53:10 -0500, Joe Greco wrote:
On the same vmdk files? "Deleting the VM" makes it sound like not.
Fresh new VMDK files every time, and always thick provisioned.
None of the other VM's, even the VM's that had been abused in this
horribly insensitive manner of being pla
> On Fri, 30 Mar 2012 09:44:47 -0500, Joe Greco wrote:
> > Have you migrated these hosts, or were they installed in-place and
> > never moved?
> > fwiw the apparent integrity of things on the VM is consistent with
> > our experience too.
>
> VMMotion and StorageVMMotion does not seem to affect th
We don't have any indications that before the crash processes will take
unusual amounts of CPU. The only time there is high CPU usage is at the
point where it does enter the crashed state and no longer seems to be able
to communicate with the disk.
I'm not sure this is the same bug but we'l
On Fri, 30 Mar 2012 09:44:47 -0500, Joe Greco wrote:
Have you migrated these hosts, or were they installed in-place and
never moved?
fwiw the apparent integrity of things on the VM is consistent with
our experience too.
VMMotion and StorageVMMotion does not seem to affect the stability. Even
> On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco wrote:
>
> > It also doesn't explain the experience here, where one VM basically
> > crapped out but only after a migration - and then stayed crapped out.
> > It would be interesting to hear about your datastore, how busy it is,
> > what technology,
> On 3/29/2012 7:01 AM, Joe Greco wrote:
> >> On 3/28/2012 1:59 PM, Mark Felder wrote:
> >>> FreeBSD 8-STABLE, 8.3, and 9.0 are untested
> >>
> >> As much as I'm sensitive to your production requirements, realistically
> >> it's not likely that you'll get a helpful result without testing a newer
>
isk - very important if you can't
run sysctl because your disk IO has locked up!) to see what the
current state of things.
It's likely that the BSD mpt(4) and other storage drivers, and/or our
interrupt handling code, is just slightly different enough to confuse
the snot out of VMWare. I
ted (Sorry, not possible in
our production at this time, and we were hoping we could base some
stuff on 8.3 for long term stability...)
ESXi: Confirmed ESXi 4.0 - 5.0 has this problem. Haven't tested on
others.
History:
Over the course of the last 2 years we've been banging our head
On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco wrote:
It also doesn't explain the experience here, where one VM basically
crapped out but only after a migration - and then stayed crapped out.
It would be interesting to hear about your datastore, how busy it is,
what technology, whether you're us
crashes now that I'm using
> LSI SAS emulated controller. If it still crashes, we'll see what happens
> after that with those loader.conf options enabled.
Um, if I may, that's something completely different.
VMDirectPath, or PCIe passthru, is making a hardware device on a VMwar
On 3/29/2012 7:01 AM, Joe Greco wrote:
>> On 3/28/2012 1:59 PM, Mark Felder wrote:
>>> FreeBSD 8-STABLE, 8.3, and 9.0 are untested
>>
>> As much as I'm sensitive to your production requirements, realistically
>> it's not likely that you'll get a helpful result without testing a newer
>> version. 8.
On Thu, 29 Mar 2012 15:53:52 -0500, Adam Vande More
wrote:
Doesn't VMWare offer different types of emulated disk controllers? If
so,
that might be the easiest way to narrow the field. Another thing maybe
to
try would be to backport the mpt
Yes, they offer Paravirtual
On Thu, Mar 29, 2012 at 1:22 PM, Mark Felder wrote:
>
> If we assume mpt is the culprit
>
Doesn't VMWare offer different types of emulated disk controllers? If so,
that might be the easiest way to narrow the field. Another thing maybe to
try would be to backport the mpt
> On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
> > > On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
> > > > > Hi,
> > >
> > > Do both 32- and 64-bit versions of FreeBSD crash?
> >
> > We've only seen it happen on one virtual machine. That was a 32-bit
> > version. And it's not so mu
On Thu, 29 Mar 2012 11:53:02 -0500, Alan Cox wrote:
Not so long ago, VMware implemented a clever scheme for reducing the
overhead of virtualized interrupts that must be delivered by at least
some
(if not all) of their emulated storage controllers:
http://static.usenix.org/events/atc11
On Thu, 29 Mar 2012 12:24:30 -0500, wrote:
I just started reading this tread, but I am wondering if I missed
something here. What does this have to do with "Windows 7"?
I emailed him off-list but I'm guessing he thought this was on VMWare
Workstation or another pro
On Thu, 29 Mar 2012 12:05:30 -0500, Mark Atkinson
wrote:
If this is an interrupt problem with disk i/o, then you might want to
look into (DDB(4))
show intr
show intrcount
maybe
show allrman
Thank you! I really don't know what things we should be running in DDB to
diagnose this and we wi
ESXi 4.0 - 5.0 has this problem. Haven't tested on
> > others.
> >
> >
> > History:
> >
> > Over the course of the last 2 years we've been banging our heads on
> > the wall. VMWare is done debugging this. They claim it's not a
> > VM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/29/2012 07:03, Mark Felder wrote:
> Alright, new data. It happened to crash about 10 minutes after I
> came in this morning and I ran some stuff in the DDB. I have no
> idea what information is useful, but perhaps someone will see
> something out
74769460
> cpu0: timer 246571507400
> Total 550242125892
>
>
Not so long ago, VMware implemented a clever scheme for reducing the
overhead of virtualized interrupts that must be delivered by at least some
(if not all) of
se some
stuff on 8.3 for long term stability...)
ESXi: Confirmed ESXi 4.0 - 5.0 has this problem. Haven't tested on
others.
History:
Over the course of the last 2 years we've been banging our heads on
the wall. VMWare is done debugging this. They claim it's not a VMWare
issue. T
On Thu, 29 Mar 2012 10:49:30 -0500, Joe Greco wrote:
I explained it at the time to one of my VMware friends:
This is 100% identical to what we see, Joe! And we're so unlucky that we
have this happen on probably a dozen servers, but a handful are the really
bad ones. We've re
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky
wrote:
It almost sounds like the lost interrupt issue I've seen with USB EHCI
devices, though disk I/O should have a retry timeout?
What does "wmstat -i" output?
--HPS
Here's a server that has a week uptime and is due for a crash any
On Thu, 29 Mar 2012 10:31:24 -0500, Eduardo Morras
wrote:
Don't know about ESXi but on others VM Managers i can change the chipset
emulation from ICH10 to ICH4. Can you change it to an older chipset too?
Unfortunately there's no setting in the GUI for that but I'll keep looking
to see
On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
> > On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
> > > > Hi,
> >
> > Do both 32- and 64-bit versions of FreeBSD crash?
>
> We've only seen it happen on one virtual machine. That was a 32-bit
> version. And it's not so much a crash as it
n the VM. I wasn't able to prove it. I tried a read-dd of the
entire disk - passed, flying. I tried several things to duplicate
the nightly periodic tasks where it seemed so prone to locking up.
They all ran fine. But if I left the machine run, it'd do it
again eventually.
I explaine
At 16:03 29/03/2012, you wrote:
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
Don't
On Thu, 29 Mar 2012 09:58:16 -0500, Hans Petter Selasky
wrote:
Do both 32- and 64-bit versions of FreeBSD crash?
Correct, we see both i386 and amd64 flavors crash in the same way.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd
> On 3/28/2012 1:59 PM, Mark Felder wrote:
> > FreeBSD 8-STABLE, 8.3, and 9.0 are untested
>
> As much as I'm sensitive to your production requirements, realistically
> it's not likely that you'll get a helpful result without testing a newer
> version. 8.2 came out over a year ago, many many thing
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
> > Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
--HPS
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
gone
awry in the virtual machine, probably in the disk image, but I could
not identify it without significant digging that I had no particular
reason or inclination to do; since it appeared to be a VMware problem,
the "reload it and be done with it" seemed the quickest path to
resolution.
Th
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
Thanks...
__
Thank you for the suggestion. We'll put it in our toolbox and see if it
helps!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@fr
then.
The sad part is that VMWare's "supported FreeBSD versions" are a joke, and
we've been trying to keep VMWare happy by only running "supported
versions". I honestly don't think they even test. It's so stupid.
On Wed, 28 Mar 2012 18:31:38 -0500, Adrian Chadd
wrote:
* have you filed a PR?
No
* is the crash easily reproducable?
Unfortunately not. It's totally random. Some servers will "get the bug"
and crash daily, some will crash weekly, some might seem to be fine but 3
months later hit th
Mark Felder wrote:
> Alright guys, I'm at the end of my rope here. For those that haven't seen
> my previous emails here's the (not so) quick breakdown:
>
> Overview:
>
> FreeBSD ?? - 7.4 never crash
> FreeBSD 8.0 - 8.2 crashes
> FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not possible i
On 3/28/2012 1:59 PM, Mark Felder wrote:
> FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have chang
Hi,
* have you filed a PR?
* is the crash easily reproducable?
* are you able to boot some ramdisk-only FreeBSD-8.2 images (eg create
a ramdisk image using nanobsd?) and do some stress testing inside
that?
It sounds like you've established it's a storage issue, or at least
interrupt handling for
on at this time, and we were hoping we could base some stuff on
8.3 for long term stability...)
ESXi: Confirmed ESXi 4.0 - 5.0 has this problem. Haven't tested on others.
History:
Over the course of the last 2 years we've been banging our heads on the
wall. VMWare is done debugging
On Apr 18, 2011, at 2:45 PM, Chuck Swiger wrote:
> On Apr 18, 2011, at 11:35 AM, Sascha Vieweg wrote:
>>> man syscons | less -p'Back Scrolling'
>>
>> ... Says: press the `slock' key (with some PC keyboard description).
>> However, I have got a MB Pro where no such key is available. Thus, I may
On Apr 18, 2011, at 11:35 AM, Sascha Vieweg wrote:
>> man syscons | less -p'Back Scrolling'
>
> ... Says: press the `slock' key (with some PC keyboard description). However,
> I have got a MB Pro where no such key is available. Thus, I may repeat my
> question: How can I get console scolling wor
On 11-04-09 17:17, Warren Block wrote:
On Fri, 8 Apr 2011, Sascha Vieweg wrote:
As a curious beginner I am running FreeBSD on VMWare Fusion
3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on
the normal (startup) console:
(1) use my apple keyboard, especially, scro
On Fri, 8 Apr 2011, Sascha Vieweg wrote:
As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a
MacBook Pro 13'' i5, and I want to do two things on the normal (startup)
console:
(1) use my apple keyboard, especially, scroll through console output
man syscons | le
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 tri
On Apr 8, 2011, at 12:22 PM, Sascha Vieweg wrote:
> As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a
> MacBook Pro 13'' i5, and I want to do two things on the normal (startup)
> console:
>
> (1) use my apple keyboard, especially, scroll throu
On Apr 8, 2011, at 12:22 PM, Sascha Vieweg wrote:
> As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a
> MacBook Pro 13'' i5, and I want to do two things on the normal (startup)
> console:
>
> (1) use my apple keyboard, especially, scroll throu
As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2
on a MacBook Pro 13'' i5, and I want to do two things on the
normal (startup) console:
(1) use my apple keyboard, especially, scroll through console
output
(2) have a screen resolution of at least 800x600.
Both t
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
>
On 08/04/2011 12:17, Dimitry Andric wrote:
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
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
Hello,
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 works fine.
Any idea how to solve
On Wed, Apr 6, 2011 at 04:12, wrote:
> Kevin Wilcox wrote:
>
>> If you're just using the 192.168.4.129 - 254 addresses
>> I would change it to
>>
>> subnet 192.168.4.0 netmask 255.255.255.0
>
> Shouldn't that be netmask 255.255.255.128?
That's what I thought at first as well.
Then I saw the r
1 - 100 of 669 matches
Mail list logo
