On Thu, Aug 13, 2009 at 12:57:07PM -0500, Shawn Walker wrote:
Jan Friedel wrote:
On Wed, Aug 12, 2009 at 05:04:26PM -0700, Alan Coopersmith wrote:
AFAICT, Indiana by default comes with a PATH that has /usr/gnu/bin
in front of the rest
That is the default environment for the new user
przemol...@poczta.fm wrote:
On Thu, Aug 13, 2009 at 12:57:07PM -0500, Shawn Walker wrote:
Jan Friedel wrote:
On Wed, Aug 12, 2009 at 05:04:26PM -0700, Alan Coopersmith wrote:
AFAICT, Indiana by default comes with a PATH that has /usr/gnu/bin
in front of the rest
That is the default
przemol...@poczta.fm wrote:
On Thu, Aug 13, 2009 at 12:57:07PM -0500, Shawn Walker wrote:
Configuration options like this belong in the firstboot configuration
setup, or in visual panels where they don't add to the complexity of the
installer.
But one of the (hidden ?) goals of
On Fri, Aug 14, 2009 at 01:49:40AM -0500, Shawn Walker wrote:
przemol...@poczta.fm wrote:
On Thu, Aug 13, 2009 at 12:57:07PM -0500, Shawn Walker wrote:
Jan Friedel wrote:
On Wed, Aug 12, 2009 at 05:04:26PM -0700, Alan Coopersmith wrote:
AFAICT, Indiana by default comes with a PATH that has
The point is that they don't *need* or have to be in the installer.
They're just as beneficial and useful at firstboot, in a Visual Panel,
or somewhere else. There is no overwhelmingly great reason to force
them to be part of the install process. Installation should be about
installation
Our customers want an hands-off install; an install which can be
customized to a point where the system reboots and nothing needs to
be done.
Visual panels do not work when you need to install 100s of systems.
The fact that you are required to configure a system after it is installed
is a
+ 1 for the visual panel idea.
I still think however that by default Solaris and OpenSolaris should present
it's own personality rather than putting linuxiness before quality
On Fri, Aug 14, 2009 at 4:49 PM, Shawn Walker swal...@opensolaris.orgwrote:
przemol...@poczta.fm wrote:
On Thu, Aug
I am trying to do static link aggregation using a Netgear switch.Open solaris
System has an aggregation that consists of two interfaces, bge0 and bge1.
These interfaces are connected to the switch through aggregated ports. If both
links are connected, in Netgear, traffic is only on one link
I am unable to share cifs share on open solaris with authentication from
windows machine. I followed the following steps
# svcadm enable -r smb/server
# zfs create tank/cifs0
# zfs set sharesmb=on tank/cifs
# sharemgr show -vp
default nfs=()
zfs
zfs/tank/cifs0 smb=()
On 08/14/09 07:46, rudro wrote:
I am trying to do static link aggregation using a Netgear switch.Open solaris
System has an aggregation that consists of two interfaces, bge0 and bge1. These
interfaces are connected to the switch through aggregated ports. If both links are
connected, in
i'm not sure how cifs deals with roles, and root is a role in
opensolaris, can you try with another user?
On Fri, Aug 14, 2009 at 8:56 AM, rudrorudro.chatter...@tcs.com wrote:
I am unable to share cifs share on open solaris with authentication from
windows machine. I followed the following
This is something that should be configurable globally and when an account is
created. Globally in cases where it's required for applications (think
monitoring software, commercial apps, etc.). That should be done with a command
like the netservices and through an AI variable for network
Totally agree Casper! The power of Jumpstart has enabled customers to deploy
servers from scratch with little to no manual configuration after doing a boot
net -install. AI has to be as flexible and hopefully easier to configure by
learning from what customers do with Jumpstart (take a look at
rudro stated:
I am trying to do static link aggregation using a Netgear switch.Open
solaris System has an aggregation that consists of two interfaces, bge0 and
bge1. These interfaces are connected to the switch through aggregated ports. If
both links are connected, in Netgear, traffic is
casper@sun.com wrote:
The point is that they don't *need* or have to be in the installer.
They're just as beneficial and useful at firstboot, in a Visual Panel,
or somewhere else. There is no overwhelmingly great reason to force
them to be part of the install process. Installation
Volker A. Brandt wrote:
Visual panels do not work when you need to install 100s of systems.
Just a thought, couldn't you use a USB Stick to save configuration
files, so the next 99 installs take data from there?
Hmmm the 100s of systems will usually be installed
Visual panels do not work when you need to install 100s of systems.
Just a thought, couldn't you use a USB Stick to save configuration
files, so the next 99 installs take data from there?
Hmmm the 100s of systems will usually be installed *simultaneously*.
Also, it's no fun to crawl
On 08/14/2009 10:47 AM, Volker A. Brandt wrote:
Visual panels do not work when you need to install 100s of systems.
Just a thought, couldn't you use a USB Stick to save configuration
files, so the next 99 installs take data from there?
Hmmm the 100s of systems will usually be installed
I'd love to do the same for my few opensolaris systems, but we use
static IPs so I can't use AI. I hope that gets fixed soon.
Maybe this was mentioned already, but why can't you statically assign
IPs in DHCP, then use AI?
___
opensolaris-discuss
On 08/14/2009 11:29 AM, Ethan Erchinger wrote:
I'd love to do the same for my few opensolaris systems, but we use
static IPs so I can't use AI. I hope that gets fixed soon.
Maybe this was mentioned already, but why can't you statically assign
IPs in DHCP, then use AI?
We aren't running a
I will concur. The single most important issue to me with regards to
installing a system is that I be able to do it automatically and
remotely.
I have quite literally installed thousands of Solaris instances on
dozens of hardware platforms - less than a hundred have been
interactively and
On Fri, Aug 14, 2009 at 10:47 AM, Volker A. Brandtv...@bb-c.de wrote:
Visual panels do not work when you need to install 100s of systems.
Just a thought, couldn't you use a USB Stick to save configuration
files, so the next 99 installs take data from there?
Hmmm the 100s of systems will
Thanks again to Evan Layton - all fixed now!
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
And who's going to go run around with this USB stick in a data center? Doesn't
sound like a realistic solution.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web: http://unixconsole.blogspot.com
Yup, I opened a bug on this exact issue.. 10543. It makes no sense to be unable
to do that with the create-client subcommand to installadm.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web:
casper@sun.com wrote:
The point is that they don't *need* or have to be in the installer.
They're just as beneficial and useful at firstboot, in a Visual Panel,
or somewhere else. There is no overwhelmingly great reason to force
them to be part of the install process. Installation
This concept was discussed a few months ago on indiana-discuss as a beta test
project, after looking at this more closely I refocused it on Use Cases since
that is what we really are needing. There were several people interested in
being part of a project like this.
All input welcome.
* casper@sun.com (casper@sun.com) wrote:
The point is that they don't *need* or have to be in the installer.
They're just as beneficial and useful at firstboot, in a Visual Panel,
or somewhere else. There is no overwhelmingly great reason to force
them to be part of the install
Hi Kerry,
* Kerry Cox (kerryj...@gmail.com) wrote:
Just picked up an Ultra 10 Sun Workstation Elite 3D from my company.
Wanting to install Open Solaris 0906 on it. I downloaded the latest
Sparc build, but it did not seem to want to take. Not sure how to
proceed. I am not seeing Ultra 10 on
Unfortunately this isn't possible at this time.
However, as a temporary measure (this won't be possible forever), you
could use SXCE until a text install powered SPARC version becomes
available. It's not what you want right now, but until Caiman is
finished on SPARC it may work for you. And
Background:
Secure environment forces us to use out of the box features.
Basic needs:
Place Solaris files to be backed up on a Windows server
Enable indows server to place files on a Solaris filesystem
I am looking for the simplest possible solution. I have been looking at LDAP
authenticating
Great idea! +1 for Documentation community sponsorship.
-alan
Jim Walker wrote:
This concept was discussed a few months ago on indiana-discuss as a
beta test
project, after looking at this more closely I refocused it on Use
Cases since
that is what we really are needing. There were several
Hi Jim.
I'm still very much interested in participating in this effort.
Thanks and take care.
--joanie
On Fri, 2009-08-14 at 11:07 -0600, Jim Walker wrote:
This concept was discussed a few months ago on indiana-discuss as a beta test
project, after looking at this more closely I refocused it
Randy Wynn wrote:
Background:
Secure environment forces us to use out of the box features.
Basic needs:
Place Solaris files to be backed up on a Windows server
Enable indows server to place files on a Solaris filesystem
By on a Windows server do you mean physically on the box?
If not, use
Count on me for OpenSolaris Desktop and Development Tools.
OpenSolaris is basically development platform and I think
these two areas are of high importance for developers.
Uros Nedic
Belgrade, Serbia
Date: Fri, 14 Aug 2009 11:07:18 -0600
From:
Currently the storage is attached to the Windows server and I need to place
files there to be backed up to tape. I am trying to get the Windows admin to
add an ssh server so I could just scp the files via script.
The CIFS on Solaris looks like a future item to solve storage both directions.
My
Jim Walker wrote:
This concept was discussed a few months ago on indiana-discuss as a beta
test
project, after looking at this more closely I refocused it on Use Cases
since
that is what we really are needing. There were several people interested in
being part of a project like this.
All
I'd like to help out where possible. There are definitely use cases that the
sysadmin community could help out with. There has been a lot of discussion
lately about installation, configuration, and management of opensolaris. In the
LDoms community, we could also get involved.
38 matches
Mail list logo
