Hi,
I just upgraded one of my boxes to openSolaris 2009.06 that's been running with
the same /etc/ipf/ipnat.conf file since openSolaris 2008.05
My ipnat.conf looks like:
ext_if = aggr2;
baransky = "192.168.230.130"; # Wiki
rdr $ext_if $baransky port https -> $baransky port 8443
# /usr/sbin/ipnat
Sorry, the 268 should 168. Just my bad typing
--
This message posted from opensolaris.org
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
Hi,
Did you ever get this sorted?
Reason I ask is, I have a similar problem on a bost I just upgraded to
openSolaris 2009.06
My ipnat.conf looks like:
ext_if = aggr2;
baransky = '192.268.230.130'; # Wiki
rdr $ext_if $baransky port https -> $baransky port 8443
# /usr/sbin/ipnat -CF -f /
Hey Guys-
I am having issues installing 2009.06. No matter which option i choose from the
grub install menu on the livecd, I get the following error and am sent down to
a system admin prompt.
ata_id_common: BUSY STATUS 0x80 error 0x80
Anyone have any idea what could be going on? I searched aro
I had a similar issue with an Nvidia NV34 (GeForce FX 5200). Neither
2009.06 nor SXCE snv_115 were able to even probe it, even after
installing drivers (I used the onboard graphics instead).
I wonder if anyone has looked into bringing the nouveau driver to osol.
Kamin Horvath
Fedora Ambassad
If there is problem with boot archive then you can try updating it. Do the
following:
1. Edit line in grub menu containing "kernel" keyword and add "-s" at the end.
2. This will boot system in single user mode. Log in as root.
3. After logging in use this command to update the archive:
# bootadm u
yes i want to install nativly, not in a virtual machine.
i guess i need to wait for NVIDIA to release a MCP79 (ION) driver for
(open)Solaris.
--
This message posted from opensolaris.org
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
Let me also attach the dmesg output :)
--
This message posted from opensolaris.org
dmesg_output
Description: Binary data
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
Hi Kennedy,
Did you also install GlassFish using IPS? Here's a blog a wrote on
installing GlassFish for production:
http://blogs.sun.com/observatory/entry/glassfish_in_production
The same should also work in a zone.
Hope that helps,
Brian
Kennedy Ganti wrote:
I am really excited to discover
Hello,
Here's the situation: I have Opensolaris 2009.06 with X11 forwarding enabled.
From my mac I open a terminal, open the ssh -X session, and open an
application, for example, firefox. Everything works to this point. I can click
around, whatever, no issues.
BUT when I start typing anythin
Hi jkeil,
thanx for your reply. I don't have a physical floppy drive in my box, but it
was enabled in the bios, so I disabled it. I still get the console-login
instead of Gnome though.
One of the messages printed to the console is:
opensolaris svc.startd[7]: system/hal:default failed fatally: t
Hi everyone,
Today, I updated my OpenSolaris from v2008.11 to v2009.06 and I got a big
problem.
After I ran the command
$ pkg image-update
OpenSolaris could successfully download, install and index; however, there was
a warning kind of boot-archive unable to create. In the end, it said that
> # dd if=/mnt/iso/boot/x86.miniroot of=/dev/null
> read: No such device or address
> 0+0 records in
> 0+0 records out
>
> # ls -l /mnt/iso/boot/x86.miniroot
> -r--r--r-- 1 root root 106921672 May 18 17:47
> /mnt/iso/boot/x86.miniroot
Did you see Tom's reply?
http://www.opensolaris.org
> When i do a svcs -vx, i see that a couple of services
> aren't running:
>
> - application/graphical-login/gdm:default
> - system/hal:default
> - net/inetd-upgrade:default
In which state is the hal service?
There is a known problem with the PS/2 floppy driver
on some systems, and the result is
Oke, i've tried all night to boot into the live-cd environment to install
OpenSolaris, without success. Instead, i get the console login screen. I login
with jack/jack.
When i do a svcs -vx, i see that a couple of services aren't running:
- application/graphical-login/gdm:default
- system/hal:
I'm trying to do a live upgrade because that's apparently the only way, if I'm
using ZFS.
But now if live upgrade doesn't work, I'm stuck at b105, on which xorg crashes
whenever I go to certain websites in firefox.
Does that mean the only thing I can do is wipe out everything with a fresh
inst
Boot into the GUI and do it there, it's much easier.
You need to copy /etc/nsswitch.dns -> /etc/nsswitch.conf and reboot.
HTH
ET
--
This message posted from opensolaris.org
___
opensolaris-help mailing list
opensolaris-help@opensolaris.org
Based on your first post, I assume it was being installed on the HW not
VirtualBox, you should submit a RFE with the original /var/log/Xorg.0.log
errors, from before when you had first tried to install, to reproduce it remove
your /etc/X11/Xorg.conf file and if there is a .file i.e /etc/X11/.Xor
I don't know if it this helps, but I saw a notice that SATA (Sil type?)
multiplexers will be supported in builds 120+. This can reduce the cost to
make a NAS device extensible with external disk boxes. Right now I've got 5
SATA cables running from my controller to an external disk tower. I co
OK, the problem is simple and very common it seems:
- RAIDZ for data storage
- low wattage motherboard and CPU, since it will be on 24/7.
- mainstream components if possible, to keep costs in control
The motherboard should have at least 4 SATA connectors, preferably more, let's
say 6 or 8 to keep
20 matches
Mail list logo
