Re: [osol-discuss] simple Raid-Z question
Peter wrote: Is it possible to enlarge the initial RAID size by adding single drives later on? If i start off with 4*500gb (should give me 1.5tb), can I add one 500gb to the raid later, and will the total size then grow 500gb and still have the same protection? You cannot expand a RAID-Z stripe by adding a disk. Take a look at this thread (look for Eric Schrock's replies). http://www.opensolaris.org/jive/thread.jspa?messageID=15219 For more information on RAID-Z, please see http://blogs.sun.com/bonwick/entry/raid_z The ZFS experts can be found on [EMAIL PROTECTED] Hope that helps! Regards, Manoj ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: joining Sun
Peter C. Norton [EMAIL PROTECTED] wrote: On Fri, Apr 06, 2007 at 11:14:14PM +0200, Joerg Schilling wrote: The problem is that the creators of the Linux distributions keep their users uninformed. They don't know that the command line features they see are features from bash. ... and they don't know that Linux does not come with tar but with GNU tar. It's not Solaris that created the ignorance of the Linux users that cry for Linux compatibility. Solaris users and Sun however need to inform people. Maybe something like you want solaris so you can feel the pain, b***h! Makes for a snappy marketing campaign. Well, it seems that you don't know enough about the problems... Do you really believe Solaris should e.g. adopt to the broken GNU tar just because Linux uses it and people on Linux create non-conforming archives? If people are informed ybout _why_ they have problems, they won't cry Solaris is bad. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: joining Sun
Shawn Walker [EMAIL PROTECTED] wrote: Solaris was designed to meet specific goals and needs, just because it doesn't meet someone else's specific goals or needs does not mean it is faulty :) Solaris does have dofferent defaults than Linux. It is not a fault from Solaris if Linux users don't even know that some properties may be changed. I don't believe we should change the defaults but rather inform people. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Project Proposal: Tesla, Solaris Enhanced Power Management
I'd like to propose a project to provide an enhanced platform independent power management architecture...to be known as Project Tesla. From a high level, this project would implement a set of kernel policies (including a default) that would leverage existing (and forthcoming) platform specific power management mechanisms (including PowerNow and Enhanced Speedstep). A second goal of the project would be to implement a platform independent power management administrative paradigm, though which administrators could specify (to start) power and performance objectives that the system would then attempt to honor though employment of one of the aforementioned policies. Longer term, it is conceivable that other types of objectives could be expressed. Implementation of power aware scheduling policy that meshes well with the kernel's existing CMT and NUMA policy would be an initial focus for the project, along with exploration, and prototyping of an administrative facility. Thanks, -Eric ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: Tesla, Solaris Enhanced Power Management
On 4/7/07, Eric Saxe [EMAIL PROTECTED] wrote: I'd like to propose a project to provide an enhanced platform independent power management architecture...to be known as Project Tesla. From a high level, this project would implement a set of kernel policies (including a default) that would leverage existing (and forthcoming) platform specific power management mechanisms (including PowerNow and Enhanced Speedstep). A second goal of the project would be to implement a platform independent power management administrative paradigm, though which administrators could specify (to start) power and performance objectives that the system would then attempt to honor though employment of one of the aforementioned policies. Longer term, it is conceivable that other types of objectives could be expressed. Implementation of power aware scheduling policy that meshes well with the kernel's existing CMT and NUMA policy would be an initial focus for the project, along with exploration, and prototyping of an administrative facility. Sounds like a good thing. +1 -- Regards, Cyril ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] was something else, now Packaging
Doing a dist-upgrade for a new driver seems a bit of an overkill and highly unlikely. Do you have a better example? Haha, well that was what I could come up with because that is how I got the si3124 driver on Nexenta. Is there a source tarball or a binary package for the si3124 driver? Is it possible to just plug a si3124 driver into the version of the Solaris kernel that comes with b50 on which nexenta alpha6 is based? That is, does the b50 kernel have the sata framework available? How am I supposed to find out this kind of information besides bugging people on a list? Of course, a dist upgrade would be overkill for a driver...it is more appropriate when we want a whole bunch of tool chains that was not previously available. But then, I do not know much about what is in a certain Solaris kernel let alone how to compile one or a driver (i guess this is documented on docs.sun.com?) so I can only rely on a packager to do it for me and if package don't provide said driver at a certain dist version but do at a later one am I supposed to get smart and try to look for the sources and if I find them, to then compile it for the currently installed image? Send instant messages to your online friends http://uk.messenger.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: joining Sun
Exactly, and what is the point of Solaris if it is only to make it just like GNU/Linux? That's what Nexenta is for ;) Yup. Which is why I am asking that there be no gcc + gnome (okay maybe gnome is stretching it given that Sun is behind the GNOME band wagon) entrenchment in nevada. A standard desktop that does not depend on gcc or glibc is necessary imho. Send instant messages to your online friends http://uk.messenger.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The shell project now open...
Rolland, Good luck with this project as i'm a newbie to Unix and Solaris experiencing these frustrations. My learning failures comes from their inconsistencies of language dialectics and the command terminal's syntactic stage before getting to the script's language part . A proper language theory approach to making regular expressions consistent, script language constructs easier to write should be the future goal. The lack of proper compiler (commad line interpretor) error messages to the author becomes a debug-by-trial-and-error. For example look at the staging diagram of how a token is arrived at from the book Classic Shell Scripting by Robbins Beebe. How would a newbie arrive at this? Each script variant was locally developed to the parsing experience of the author at the time of creation . A proper compiler / compiler with consistent published grammars would help across the different script languages. Having possibly an universal script language that takes the best features from each might also be investigated. Bitting the bullet to correct the past sins on language inconsistency I commend as your stated goals. Like any project having an accompanying lint type evaluator(s) on past-to-future targeting problems should at least lower the grep reaction about things that are going to be broken cuz of the (dis) respect of the past. I'm all fore respecting the past if there is merit but past experiences with inconsistencies that hampers the future so be removed. My 2 bits worth Thank u for your ears Dave Bone On 5-Apr-07, at 6:44 PM, Roland Mainz wrote: Hi! Just a quick announcement that the shell project is now open. What are we are doing ? The shell project should investigate and execute improvements related to shells and the shell environment in (Open-)Solaris: * Improve usuablity for plain users, including beginners and admins * Maintain/update various shells in Solaris (including bash, csh, ksh93, tcsh, zsh, /usr/bin/sh, /usr/xpg4/bin/sh, etc.) * Implement /etc/env.d/ to provide a way to add plugable shell scriptfragments for startup/shutdown of user sessions (login, interactive) * Improve the default shell environment, including: + Manual-page subsystem, e.g. the defaults of MANPATH, PAGER, etc., the related tools and their default configuration + Per-user temporary directories (TMPDIR), e.g. /tmp/ username instead of putting everything into /tmp + More ideas welcome * Implement tools like /usr/sbin/chsh (change user shell) and /usr/bin/chfn (change finger/GCOS information) * Improve internationalisation (=i18n) and localisation must (=l10n) support in the shell environment * Followup of the ksh93-integration project, including: + ksh93 busybox project + ksh93 Dtrace project + shcomp - shell script compiler and shbinexec kernel module * Start the work on a future POSIX shell standard which may include some of the newer ksh93/bash features. Why are we doing this ? * Improve the user-friendliness of the Solaris shell environment, via enhancements of the default setup, history, builtins etc Further information can be found on the project home page at http://www.opensolaris.org/os/project/shell/ or in the project mailinglist (see http://mail.opensolaris.org/mailman/listinfo/shell-discuss/ for instructions how to subscribe and/or access the list archives (please _subscribe_ before posting...)). Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, CJAVASunUnix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: joining Sun
On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: Exactly, and what is the point of Solaris if it is only to make it just like GNU/Linux? That's what Nexenta is for ;) Yup. Which is why I am asking that there be no gcc + gnome (okay maybe gnome is stretching it given that Sun is behind the GNOME band wagon) entrenchment in nevada. A standard desktop that does not depend on gcc or glibc is necessary imho. I'm not sure how GNOME depends on gcc or glibc...what am I missing? Besides, what other desktop option do we have right now? GNOME is the best for accessibility, etc. KDE isn't an option due to licensing, C++, etc. XFCE and others aren't mature enough yet, and CDE is dead, long live CDE. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] was something else, now Packaging
On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: Doing a dist-upgrade for a new driver seems a bit of an overkill and highly unlikely. Do you have a better example? Haha, well that was what I could come up with because that is how I got the si3124 driver on Nexenta. Is there a source tarball or a binary package for the si3124 driver? Is it possible to just plug a si3124 driver into the version of the Solaris kernel that comes with b50 on which nexenta alpha6 is based? That is, does the b50 kernel have the sata framework available? How am I supposed to find out this kind of information besides bugging people on a list? Yes. In fact, it's usually possible to use drivers that were created for Solaris 8 or 9 with the newest versions of Solaris. *Unlike* GNU/Linux, Solaris has a very stable and well-documented driver API. This means that when your kernel changes, generally speaking, your drivers don't have to either. For example, the OSS drivers I installed on Solaris 10 Update 3 were copied directly over the Solaris Developer Express b55, Solaris Express Community Edition b60, and Solaris Express Community Edition b61, and it worked on all of them... But then, I do not know much about what is in a certain Solaris kernel let alone how to compile one or a driver (i guess this is documented on docs.sun.com?) It depends on the individual driver. Usually it's as simple as make; make install and maybe an update_drv run or two -- *if* it has be compiled. If it's already compiled for you, it's usually as easy as something like running pkgadd -d MYdriver.pkg. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: simple Raid-Z question
Two conflicting answers to the same question? I guess we need someone to break the tie :) Hello, I have been reading alot of good things about Raid-z, but before I jump into it I have one unanswered question i can't find a clear answer for. Is it possible to enlarge the initial RAID size by adding single drives later on? If i start off with 4*500gb (should give me 1.5tb), can I add one 500gb to the raid later, and will the total size then grow 500gb and still have the same protection? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Fresh Install Problems
Invidia 256 mb grahics. Root login gave me enough time once. Got incorrect. Seems to me if you create a username and password during install, it should work. Yes I am a microsoft user from the beginning. many years with old dos all the way to XP and Vista. If a login is stopping me because things are so different with Solaris 10, I must be an idiot. I actually thought that you typed your user name in the box, and then your password in the password box. I agree, something is wrong, maybe during the download something got corrupted, but there was no indication in SDM of that. There is an outside chance that something went sour during the iso burn, but again, there was not any indication of that either. I am considering a drive format and a fresh download, start from scratch. If I have to try tricks to log in, I'm sure there will be more problems beyond that, and I care to deal with any work arounds of a brand new install. The PC and hardware were not an issue at any time during the install. Thanks for the suggestions, I must find out what is wrong before I go any further. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Solaris 10: The Complete Reference
Anyone read this? I just ordered a copy from: http://www.amazon.com/Solaris-10-Complete-Reference/dp/0072229985/ref=sr_1_1/103-2214988-8871063?ie=UTF8s=booksqid=1175966813sr=1-1 I was wondering how compatible this would be with somelike belenix or another distro built on Solaris. Thanks This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 10: The Complete Reference
On 4/7/07, Mike [EMAIL PROTECTED] wrote: I was wondering how compatible this would be with somelike belenix or another distro built on Solaris. As far as the commands are concerned, and the underlying technologies like Zones, Dtrace, ZFS, etc.. it would be completely compatible. Regards Anil ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: It works when I choose the console install mode:
Through my recent exprience choosing option : 1. Express ( not development) causes same issue as described by Tunla. When system got installed usbkey automount was not working. Trying to find out how to mount mannualy. Confirm, that AHCI driver developed by Ying Tian works with Intel ICH8R Hardware:- CPU Core2duo E6400 MB ASUS P5B Deluxe SATA HDD 160 GB attached to ICH8R (in AHCI) mode. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Fresh Install Problems
Passwords on Solaris are not limited to 8 characters, but the default password hashing algorithm only looks at the first 8 characters, with the result that passwords which have the same first 8 characters are treated as being identical. Cheers Andrew. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SNV_59 doesn’t recognize linu x partitions existing on second SATA HDD
SNV_59 doesn’t recognize already existing CentOS 4.4 (openSUSE 10.2 ) partitions on second (not bootable SATA HDD). Attempt to load CentOS 4.4 (openSUSE 10.2) instance modifying /boot/grub/menu.lst under Solaris failed. SNV_52 didn’t experience such kind of problems on old IDE system with Pentium 3GHZ (Prescott),Elite Groupe 865PE,2 Seagate Barracuda IDE drives (80 GB) Hardware for SNV_59: CPU Core2duo E6400 ASUS P5B Deluxe 2 SATA HDDs atached to INTEL ICH8R (in AHCI mode) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Fresh Install Problems
On 07/04/07, Richard Raymond [EMAIL PROTECTED] wrote: Invidia 256 mb grahics. Root login gave me enough time once. Got incorrect. Seems to me if you create a username and password during install, it should work. Yes I am a microsoft user from the beginning. many years with old dos all the way to XP and Vista. If a login is stopping me because things are so different with Solaris 10, I must be an idiot. I actually thought that you typed your user name in the box, and then your password in the password box. I agree, something is wrong, maybe during the download something got corrupted, but there was no indication in SDM of that. There is an outside chance that something went sour during the iso burn, but again, there was not any indication of that either. I am considering a drive format and a fresh download, start from scratch. If I have to try tricks to log in, I'm sure there will be more problems beyond that, and I care to deal with any work arounds of a brand new install. The PC and hardware were not an issue at any time during the install. Thanks for the suggestions, I must find out what is wrong before I go any further. Unfortunately, nVidia 256mb graphics doesn't tell me what video card you are using, though it helps somewhat. Unfortunately, the information you have provided is not yet enough to determine the real issue. However, this may provide us with more information that will help a lot: http://www.sun.com/bigadmin/hcl/hcts/device_detect.html Run the detection tool under Windows or Linux, then post the output of it here or somewhere we can get to it. That will tell us what specific hardware you have, and hopefully help shed some light on this issue. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Fresh Install Problems
On 07/04/07, Andrew Pattison [EMAIL PROTECTED] wrote: Passwords on Solaris are not limited to 8 characters, but the default password hashing algorithm only looks at the first 8 characters, with the result that passwords which have the same first 8 characters are treated as being identical. That's slightly disturbing, though not terribly surprising. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SNV_59 doesn’t recognize linux partitions existing on second SATA HDD
On 07/04/07, Boris Derzhavets [EMAIL PROTECTED] wrote: SNV_59 doesn't recognize already existing CentOS 4.4 (openSUSE 10.2 ) partitions on second (not bootable SATA HDD). Attempt to load CentOS 4.4 (openSUSE 10.2) instance modifying /boot/grub/menu.lst under Solaris failed. SNV_52 didn't experience such kind of problems on old IDE system with Pentium 3GHZ (Prescott),Elite Groupe 865PE,2 Seagate Barracuda IDE drives (80 GB) Hardware for SNV_59: CPU Core2duo E6400 ASUS P5B Deluxe 2 SATA HDDs atached to INTEL ICH8R (in AHCI mode) Could be for any number of reasons. However, have you trained using a chainloader +1 style boot if you have grub installed on your Linux partition's MBR? -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 10: The Complete Reference
Send it back. Seriously, it has *nothing* in it about Solaris 10 - no zones, dtrace or zfs. On 07/04/07, Mike [EMAIL PROTECTED] wrote: Anyone read this? I just ordered a copy from: http://www.amazon.com/Solaris-10-Complete-Reference/dp/0072229985/ref=sr_1_1/103-2214988-8871063?ie=UTF8s=booksqid=1175966813sr=1-1 I was wondering how compatible this would be with somelike belenix or another distro built on Solaris. -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] simple Raid-Z question
ok, here I go.. Is it possible to enlarge the initial RAID size by adding single drives later on? Yes, I had a two mirrored hard drives, when I enlarged with one more, automagically I ended up with a raid-5 setup and more space for those hungry mf users... If i start off with 4*500gb (should give me 1.5tb), can I add one 500gb to the raid later, and will the total size then grow 500gb and still have the same protection? I cannot clarify this, perhaps someone else. Sorry for the misunderstanding. HTH. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] snv_61 system/webconsole:console failed fatally
anyone else seen this on snv_61 ? # Apr 7 19:06:53 mercury svc.startd[7]: system/webconsole:console failed fatally: transitioned to maintenance (see 'svcs -xv' for details) # svcs -xv svc:/system/webconsole:console (java web console) State: maintenance since Sat Apr 07 19:06:53 2007 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log Impact: This service is not running. svc:/system/postrun:default (Postponed package postinstall command execution) State: offline since Sat Apr 07 19:02:57 2007 Reason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: /var/svc/log/system-postrun:default.log Impact: This service is not running. # - Dennis Clarke ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] no CDDL on /bin/which
Is this intended ? # uname -a SunOS mercury 5.11 snv_61 sun4u sparc sun4u # # cat /bin/which #! /usr/bin/csh -f # # Copyright 2005 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # Copyright (c) 1980 Regents of the University of California. # All rights reserved. The Berkeley Software License Agreement # specifies the terms and conditions for redistribution. # #ident @(#)which.csh 1.1005/06/12 SMI # # which : tells you which program you get # # Set prompt so .cshrc will think we're interactive and set aliases. # Save and restore path to prevent .cshrc from messing it up. . . . etc etc I note that dmesg has the CDDL as well as nearly everything else. I say nearly only because I am not certain. - Dennis Clarke ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: joining Sun
--- Shawn Walker [EMAIL PROTECTED] wrote: On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: Exactly, and what is the point of Solaris if it is only to make it just like GNU/Linux? That's what Nexenta is for ;) Yup. Which is why I am asking that there be no gcc + gnome (okay maybe gnome is stretching it given that Sun is behind the GNOME band wagon) entrenchment in nevada. A standard desktop that does not depend on gcc or glibc is necessary imho. I'm not sure how GNOME depends on gcc or glibc...what am I missing? Since GNOME is a GNU project, I was under the impression that the GNOME libraries were highly dependent on gcc and glibc extensions/behaviour. Besides, what other desktop option do we have right now? GNOME is the best for accessibility, etc. KDE isn't an option due to licensing, C++, etc. XFCE and others aren't mature enough yet, and CDE is dead, long live CDE. Yeah, I guess a GPL desktop environment is tough. However, Open Solaris needs more mindshare. Adding KDE will at the very least only help in that regard. It is just as well that something is getting started on that front. I have this acqaintance who got put off by GNOME on Nexenta and who asked me whether there was some other desktop available. Maybe nevada + CDE might change his mind :D Send instant messages to your online friends http://uk.messenger.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Fresh Install Problems
On 07/04/07, Jason King [EMAIL PROTECTED] wrote: On 4/7/07, Shawn Walker [EMAIL PROTECTED] wrote: On 07/04/07, Andrew Pattison [EMAIL PROTECTED] wrote: Passwords on Solaris are not limited to 8 characters, but the default password hashing algorithm only looks at the first 8 characters, with the result that passwords which have the same first 8 characters are treated as being identical. That's slightly disturbing, though not terribly surprising. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org That is the traditional behavior on most UNIX platforms, so it's nothing new. If you want to enable passwords that can have more than 8 significant characters, just update /etc/security/policy.conf and change the default crypt algorithm to something other can the traditional UNIX crypt ( i.e. md5 or blowfish). I believe both of those allow for up to 256 (or 255 somewhere around that) character passwords. Also, if you would prefer something other than md5 or blowfish, it appears the implementation is modular (though I do not know if it is a public interface or not). Perhaps it might be worthwhile to add the ability to specify the default encryption algorithm or encryption policy as part of the install or sysidcfg? Most GNU/Linux distribution installers *used* to ask if you want to use a more secure method of password encryption. I believe slackware used to ask if you wanted to use the default, or md5/blowfish. Most of the ones I've seen these days default to md5. Is there any reason why it is bad to default to md5? I assume it causes system upgrade / migration issues... -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Fresh Install Problems
I don't grok Root login gave me enough time once. If he's got an unsupported hardware issue, I missed that; it sounds like he gets the X server and XDM up. My reading of his posts was that he's telling us XDM isn't able to authenticate him but X seems to be working. Perhaps we should have him boot into single user mode and see if he can get in as root that way. But by all means the device detection tool output will be valuable. Shawn Walker wrote: On 07/04/07, Richard Raymond [EMAIL PROTECTED] wrote: Invidia 256 mb grahics. Root login gave me enough time once. Got incorrect. Seems to me if you create a username and password during install, it should work. Yes I am a microsoft user from the beginning. many years with old dos all the way to XP and Vista. If a login is stopping me because things are so different with Solaris 10, I must be an idiot. I actually thought that you typed your user name in the box, and then your password in the password box. I agree, something is wrong, maybe during the download something got corrupted, but there was no indication in SDM of that. There is an outside chance that something went sour during the iso burn, but again, there was not any indication of that either. I am considering a drive format and a fresh download, start from scratch. If I have to try tricks to log in, I'm sure there will be more problems beyond that, and I care to deal with any work arounds of a brand new install. The PC and hardware were not an issue at any time during the install. Thanks for the suggestions, I must find out what is wrong before I go any further. Unfortunately, nVidia 256mb graphics doesn't tell me what video card you are using, though it helps somewhat. Unfortunately, the information you have provided is not yet enough to determine the real issue. However, this may provide us with more information that will help a lot: http://www.sun.com/bigadmin/hcl/hcts/device_detect.html Run the detection tool under Windows or Linux, then post the output of it here or somewhere we can get to it. That will tell us what specific hardware you have, and hopefully help shed some light on this issue. -- Jerry Sutton[EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Fresh Install Problems
On 07/04/07, Jason King [EMAIL PROTECTED] wrote: On 4/7/07, Shawn Walker [EMAIL PROTECTED] wrote: On 07/04/07, Andrew Pattison [EMAIL PROTECTED] wrote: Passwords on Solaris are not limited to 8 characters, but the default password hashing algorithm only looks at the first 8 characters, with the result that passwords which have the same first 8 characters are treated as being identical. That's slightly disturbing, though not terribly surprising. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org That is the traditional behavior on most UNIX platforms, so it's nothing new. If you want to enable passwords that can have more than 8 significant characters, just update /etc/security/policy.conf and change the default crypt algorithm to something other can the traditional UNIX crypt ( i.e. md5 or blowfish). I believe both of those allow for up to 256 (or 255 somewhere around that) character passwords. Also, if you would prefer something other than md5 or blowfish, it appears the implementation is modular (though I do not know if it is a public interface or not). Perhaps it might be worthwhile to add the ability to specify the default encryption algorithm or encryption policy as part of the install or sysidcfg? Most GNU/Linux distribution installers *used* to ask if you want to use a more secure method of password encryption. I believe slackware used to ask if you wanted to use the default, or md5/blowfish. Most of the ones I've seen these days default to md5. Is there any reason why it is bad to default to md5? I assume it causes system upgrade / migration issues... Something I have been doing for years now, setting TCP_STRONG_ISS=2 and CRYPT_DEFAULT=1 along with using xyzzy as a magic word. Two of those work well and the last gets you stuck looking at some stupid building with a stream nearby. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Fresh Install Problems
If you are working on a project using, say, Solaris/OpenSolaris, HP-UX, and Linux, and you want to use NIS (ick), you want the same authentication mechanism everywhere. Otherwise (voice of experience here), you will change the password with one mechanism, wind up with old password on some systems, new on others, and sooner or later you will forget what's where. The least common denominator is plain old UNIX password, 8 chars. With just a single type of OS, I favor the more secure mechanisms. I don't know about other considerations. Shawn Walker wrote: snip Is there any reason why it is bad to default to md5? I assume it causes system upgrade / migration issues... -- Jerry Sutton[EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: snv_61 system/webconsole:console failed fatally
anyone else seen this on snv_61 ? # Apr 7 19:06:53 mercury svc.startd[7]: system/webconsole:console failed fatally: transitioned to maintenance (see 'svcs -xv' for details) # svcs -xv svc:/system/webconsole:console (java web console) State: maintenance since Sat Apr 07 19:06:53 2007 eason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log act: This service is not running. svc:/system/postrun:default (Postponed package postinstall command execution) State: offline since Sat Apr 07 19:02:57 2007 eason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: /var/svc/log/system-postrun:default.log Impact: This service is not running. # Wow a new feature. I have to upgrade. :-) ---Bob This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: snv_61 system/webconsole:console failed fatally
anyone else seen this on snv_61 ? # Apr 7 19:06:53 mercury svc.startd[7]: system/webconsole:console failed fatally: transitioned to maintenance (see 'svcs -xv' for details) # svcs -xv svc:/system/webconsole:console (java web console) State: maintenance since Sat Apr 07 19:06:53 2007 eason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log act: This service is not running. svc:/system/postrun:default (Postponed package postinstall command execution) State: offline since Sat Apr 07 19:02:57 2007 eason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: /var/svc/log/system-postrun:default.log Impact: This service is not running. # Wow a new feature. I have to upgrade. :-) I don't know what it is. This is a fresh install minutes old. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] 2.1 GHz UltraSPARC IV+ seen in the wild ?
re: http://www.sun.com/aboutsun/pr/2007-04/sunflash.20070403.1.xml Anyone seen one of these monsters yet ? Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_61 system/webconsole:console failed fatally
On Sat, 2007-04-07 at 19:08 -0400, Dennis Clarke wrote: # svcs -xv svc:/system/webconsole:console (java web console) State: maintenance since Sat Apr 07 19:06:53 2007 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log So what does the log file say? Impact: This service is not running. svc:/system/postrun:default (Postponed package postinstall command execution) State: offline since Sat Apr 07 19:02:57 2007 Reason: Start method is running. See: http://sun.com/msg/SMF-8000-C4 See: /var/svc/log/system-postrun:default.log Impact: This service is not running. This seems normal. Based on the http link above, it means that it's still running. Laca ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: joining Sun
On Sun, 2007-04-08 at 07:42 +0800, Chung Hang Christopher Chan wrote: I'm not sure how GNOME depends on gcc or glibc...what am I missing? Since GNOME is a GNU project, I was under the impression that the GNOME libraries were highly dependent on gcc and glibc extensions/behaviour. It's not at all dependent on either gcc or glibc. We've been building GNOME using Sun Studio since the GNOME 2.0 days and glibc was never shipped in Solaris. People often mistake glib for glibc but glib is an entirely different thing. Laca ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] was something else, now Packaging
--- Shawn Walker [EMAIL PROTECTED] wrote: On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: Doing a dist-upgrade for a new driver seems a bit of an overkill and highly unlikely. Do you have a better example? Haha, well that was what I could come up with because that is how I got the si3124 driver on Nexenta. Is there a source tarball or a binary package for the si3124 driver? Is it possible to just plug a si3124 driver into the version of the Solaris kernel that comes with b50 on which nexenta alpha6 is based? That is, does the b50 kernel have the sata framework available? How am I supposed to find out this kind of information besides bugging people on a list? Yes. In fact, it's usually possible to use drivers that were created for Solaris 8 or 9 with the newest versions of Solaris. *Unlike* GNU/Linux, Solaris has a very stable and well-documented driver API. This means that when your kernel changes, generally speaking, your drivers don't have to either. Yes, I know this. You still have not however answered my question about where do I find a binary package or a source tarball for the si3124 driver. Maybe this is an edge case but I would not rule out a dist-upgrade for a driver especially one that comes with open solaris and is not third-party. Not everyone wants to maintain their own kernel or what not. You mentioned Sun Update Connection previously...are you referring to that wget script for patches? Is not there a problem with dependecies or something with patches? Is this available for Open Solaris? Besides the kernel, what if I want to maintain my own set of packages for my servers? With apt or yum, one can create one's repository and even using Debian or Centos as the base, one can combine the OS repository with one's custom packages and manage your servers that way. Say Open Solaris/Solaris comes with a certain version of sendmail but I need the features that come with a newer version or I am patching sendmail to get those features. On Linux with apt/dpkg or yum/rpm, you can build your package and then deploy it by adding that package to your repository and running an update on servers concerned. The whole thing could be such that a single command will get all those servers to come and get it. I do not see anything that will provide this kind of functionality for Open Solaris/Solaris deployments. For example, the OSS drivers I installed on Solaris 10 Update 3 were copied directly over the Solaris Developer Express b55, Solaris Express Community Edition b60, and Solaris Express Community Edition b61, and it worked on all of them... Exactly why I want to move to Solaris from Linux. No stupid politics about drivers, no stupid politics about code maintenance for new features, no recompiling everytime the kernel gets a new release. But then, I do not know much about what is in a certain Solaris kernel let alone how to compile one or a driver (i guess this is documented on docs.sun.com?) It depends on the individual driver. Usually it's as simple as make; make install and maybe an update_drv run or two -- *if* it has be compiled. If it's already compiled for you, it's usually as easy as something like running pkgadd -d MYdriver.pkg. Great. Not much different from Linux for binary drivers. Now if you can tell me the same for those that come with Open Solaris no matter what release you are running... Send instant messages to your online friends http://uk.messenger.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_61 system/webconsole:console failed fatally
On Sat, 2007-04-07 at 19:08 -0400, Dennis Clarke wrote: # svcs -xv svc:/system/webconsole:console (java web console) State: maintenance since Sat Apr 07 19:06:53 2007 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M smcwebserver See: /var/svc/log/system-webconsole:console.log So what does the log file say? I'll take a look .. just for morbid curiosity # cat /var/svc/log/system-webconsole:console.log [ Apr 7 18:05:33 Disabled. ] [ Apr 7 18:05:34 Rereading configuration. ] [ Apr 7 18:06:50 Enabled. ] [ Apr 7 18:07:04 Rereading configuration. ] [ Apr 7 19:04:43 Executing start method (/lib/svc/method/svc-webconsole start) ] Starting Sun Java(TM) Web Console Version 3.0.2 ... The console failed to start. [ Apr 7 19:06:53 Method start exited with status 95 ] # dc ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] was something else, now Packaging
On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: --- Shawn Walker [EMAIL PROTECTED] wrote: On 07/04/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: Doing a dist-upgrade for a new driver seems a bit of an overkill and highly unlikely. Do you have a better example? Haha, well that was what I could come up with because that is how I got the si3124 driver on Nexenta. Is there a source tarball or a binary package for the si3124 driver? Is it possible to just plug a si3124 driver into the version of the Solaris kernel that comes with b50 on which nexenta alpha6 is based? That is, does the b50 kernel have the sata framework available? How am I supposed to find out this kind of information besides bugging people on a list? Yes. In fact, it's usually possible to use drivers that were created for Solaris 8 or 9 with the newest versions of Solaris. *Unlike* GNU/Linux, Solaris has a very stable and well-documented driver API. This means that when your kernel changes, generally speaking, your drivers don't have to either. Yes, I know this. You still have not however answered my question about where do I find a binary package or a source tarball for the si3124 driver. Maybe this is an edge case but I would not rule out a dist-upgrade for a driver especially one that comes with open solaris and is not third-party. It depends on the hardware. Since I don't personally have the si3142, I would search for it. Chances are that if the driver isn't included, it either isn't supported by Solaris directly yet, and the driver is available somewhere on the web. In this particular case, it looks like the SUNWsi3124 package contains the driver you want. However, that driver is not yet part of older versions of solaris (as far as I can tell) and apparently depends on the new SATA framework that Solaris Express builds feature. Not everyone wants to maintain their own kernel or what not. You mentioned Sun Update Connection previously...are you referring to that wget script for patches? Is not there a problem with dependecies or No, see here for more about Sun Connection: http://www.sun.com/service/sunconnection/gettingstarted.jsp something with patches? Is this available for Open Solaris? No. Sun Connection is currently only supported for released versions of Solaris 10. Besides the kernel, what if I want to maintain my own set of packages for my servers? With apt or yum, one can create one's repository and even using Debian or Centos as the base, one can combine the OS repository with one's custom packages and manage your servers that way. Say Open Solaris/Solaris comes with a certain version of sendmail but I need the features that come with a newer version or I am patching sendmail to get those features. On Linux with apt/dpkg or yum/rpm, you can build your package and then deploy it by adding that package to your repository and running an update on servers concerned. The whole thing could be such that a single command will get all those servers to come and get it. I do not see anything that will provide this kind of functionality for Open Solaris/Solaris deployments. You can build your own packages using easy scripts such as gnutopkg from Philip Brown: http://www.bolthole.com/solaris/gnutopkg or: http://icculus.org/~eviltypeguy/pkg/gnutopkg I have several examples of Solaris packages here that I made myself: http://icculus.org/~eviltypeguy/pkg/ You could even use OpenPKG to build your own entire software stack or use the one they provide: http://www.openpkg.org/ The nice thing about OpenPKG is that it works on more operating systems than just Solaris. If it's already compiled for you, it's usually as easy as something like running pkgadd -d MYdriver.pkg. Great. Not much different from Linux for binary drivers. Now if you can tell me the same for those that come with Open Solaris no matter what release you are running... In this case, you probably can't get the si3124 package working on older versions of Solaris. From what I understand, drivers that worked on b16 of Solaris Express should still work on b61. This means that yes, even between OpenSolaris releases, drivers should work *going forward*. Going backward may not be true. There are some special exceptions at the moment such as things that use the GLDv3, and so on, but for the most part, yes. Someone correct me if this is no longer true or there are further caveats. -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] How do I dual boot my machine?
Hi. I have Windows XP on my primary hardrive and Solaris on my slave. How do I dual boot the Machine from grub? Thanx, Jim Adams This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: joining Sun
On 4/8/07, Chung Hang Christopher Chan [EMAIL PROTECTED] wrote: However, Open Solaris needs more mindshare. Adding KDE will at the very least only help in that regard. I have this acqaintance who got put off by GNOME on Nexenta and who asked me whether there was some other desktop available. Maybe nevada + CDE might change his mind :D Other desktops are indeed supported, but those might not be available as default along with the OS installation (in SXCR). Getting other desktops is not an issue. One may get them at - blastwave, sunfreeware, KDE project on opensolaris.org KDE has been available in the Companion CD since Solaris_8 ( ftp://ftp.sunfreeware.com/pub/freeware/companioncd/intel/8/). Companion CD is now hosted on sunfreeware.com. Blastwave has pre-built packages for Xfce, KDE and some window managers. Belenix has KDE and Xfce by default. regards Shiv ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: SNV_59 doesn’t recogni ze linux partitions existing on second SATA HDD
Yes,I have. It didn't help. Moreover grub.conf generated by system, before been mannualy touched, contained commented out references about unknown boot partitions on (hd1). I suspect that , killing process java sysid as was advised by Tunla (view: http://www.opensolaris.org/jive/thread.jspa?threadID=26038tstart=0) to unlock install procedure might be a reason This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: SNV_59 doesn’t recogni ze linux partitions existing on second SATA HDD
One more issue:- Usbkey automount doesn't work. Looks like system doesn't recognize USB ports on MB . I cannot see usual flashing when inserting usbkey into port. Several usbkeys have been tested. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
