Re: [osol-discuss] How to edit files inside a ISO-image?
You must be talking to me... Here is what I first did to get a bootable DVD: http://blogs.sun.com/tdh/entry/kanigix_an_experiment_in_packaging4 You can look at earlier entries to find out what didn't work. When I redid my steps a couple of months ago, I just followed this article... This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any interest in a Solaris 10 / OpenSolaris Industrial PC
David Clack wrote: Hi, So this is the interesting problem, what to actually expose. On a server in a computer room or out in a telco CO, do you need sound ? For the customers on the list for BlueWonder, it's not important. Sound is not important until you are trying to hear POST code beeps on a system which will not boot. I will however agree that should be less of an issue on a preassembled unit with a serial console. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any interest in a Solaris 10 / OpenSolaris Industrial PC
David Clack wrote: Hi, No fans, no noise. I really designed it for Solaris X86 and Real Time Java. It's going to be the same price range as Siemens MicroPC 427b, Bechoff, MPL or PDSI. Just more ports of everything. Dave Any pictures online? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to edit files inside a ISO-image?
Joerg Schilling wrote: [EMAIL PROTECTED] wrote: cpio has a bug with hard link handling that will cause real problems if you use the outdated mkisofs that currently comes with Solaris. What kind of bug (it always works for me and makes the proper hardlinks) Run setup-install-server on a recent Solaris release. Jörg I just did the cpio thing to edit the default option for grub for a Nevada 79 ISO. I then created the new image with the stock mkisofs. The install went cleanly. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] gcc not installed properly in solaris 10
vinay simha bn wrote: i installed solaris developer edition,when i give command gcc,shell shows gcc not found but if i give man page i'l get man page of gcc and it's version is 3.4.3,so how to intsall gcc properly in solaris 10 This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Vinay, Perhaps gcc is not in your path? iquad which gcc /usr/sfw/bin/gcc You'll need to consult your shell's man page on how to set your PATH variable to include this... Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to boot into console mode?
Tom Chen wrote: Hello, I have a IBM server that can install the latest Solaris Express without a problem, however the graphics card is not good or fully compatible, menu display looks too fuzzy. I want to use this server for remote testing at console mode. I am wondering how I can boot directly into console mode login rather than GUI login menu? Tom This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Edit your grub menu list: # To enable grub serial console to ttya uncomment the following lines # and comment out the splashimage line below # WARNING: don't enable grub serial console when BIOS console serial # redirection is active!!! serial --unit=0 --speed=9600 terminal serial # # Uncomment the following line to enable GRUB splashimage on console #splashimage /boot/grub/splash.xpm.gz And: title Solaris Nevada snv_61 X86 kernel$ /platform/i86pc/kernel/$ISADIR/unix -B console=ttya module$ /platform/i86pc/$ISADIR/boot_archive The key is to get the grub to go to the console to allow you to select which kernel you want and then to add -B console=ttya to tell the kernel to use that same console port. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to boot into console mode?
Tom Chen wrote: Thanks. But I just want to make the server stop at console login prompt and let me input username and password, rather than showing Java desktop login menu. I hope I don't need another PC to connect to its serial port . I do not know how to modify the following boot script to archieve that: kernel$ /platform/i86pc/kernel/$ISADIR/unix module$ /platform/i86pc/$ISADIR/boot_archive This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Ahh, I answered a different question that what you asked :- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] proposal to add Nigel Smith as a core contributor to Opensolaris storage community
Aaron Dailey wrote: I'd like to propose Nigel Smith to be a core contributor in the Opensolaris storage community. I've been impressed by his aid to the community especially around iSCSI. The voting procedures are here: http://opensolaris.org/os/community/ogb/governance/ We need a consensus vote - three total core contributors (two besides myself) to approve. Thanks, Aaron Dailey ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org +1 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Apple bought CUPS source code.
Scott Rotondo wrote: Brian Gupta wrote: Here's the basic truth about Apple and OpenSource: http://ezine.daemonnews.org/200602/apple.html The first half-dozen paragraphs, describing the obstacles facing external developers when the Apple source was still reasonably open, seem eerily familiar. s/Apple/Sun/g s/2000/2005/g Scott ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org With the exception that Sun is trying to open things up. I.e., an external person can attend the ARC meetings now, no? And we are trying to open up the closed bits, not add more to them. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Which NFS server version Sol 10 has?
Tatyaso wrote: What is the default NFS server version available on Solaris 10? When I do rpcinfo it shows version3. Is it correct? How can I have NFS v4 on Solaris? # rpcinfo -u localhost nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting -- Tatyaso This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Tatyaso, NFS questions should go to nfs-discuss. I'm going to push the discussion there and BCC opensolaris-discuss. Anyway, NFSv4 is the default version on both Solaris 10 and OpenSolaris. Here is some interesting data: [EMAIL PROTECTED] ~] rpcinfo -u localhost nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting [EMAIL PROTECTED] ~] rpcinfo localhost | grep 13 132udp6 ::.8.1 nfs1 133udp6 ::.8.1 nfs1 132tcp6 ::.8.1 nfs1 133tcp6 ::.8.1 nfs1 134tcp6 ::.8.1 nfs1 132udp 0.0.0.0.8.1 nfs1 133udp 0.0.0.0.8.1 nfs1 132tcp 0.0.0.0.8.1 nfs1 133tcp 0.0.0.0.8.1 nfs1 134tcp 0.0.0.0.8.1 nfs1 [EMAIL PROTECTED] ~] rpcinfo -s | grep nfs 13 4,3,2 tcp,udp,tcp6,udp6nfs 1 100227 3,2 tcp,udp,tcp6,udp6nfs_acl 1 [EMAIL PROTECTED] ~] rpcinfo -T tcp localhost 13 program 13 version 2 ready and waiting program 13 version 3 ready and waiting program 13 version 4 ready and waiting [EMAIL PROTECTED] ~] rpcinfo -T tcp localhost nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting program 13 version 4 ready and waiting I think that you have found a bug with the 'rpcinfo -u'. You should file a bug report. Another area for you to look at would be /etc/default/nfs, it would tell you the min and max version of NFS on your system: #NFS_SERVER_VERSMIN=2 #NFS_SERVER_VERSMAX=4 #NFS_CLIENT_VERSMIN=2 #NFS_CLIENT_VERSMAX=4 Enjoy, Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[Fwd: Re: [nfs-discuss] Re: [osol-discuss] Which NFS server version Sol 10 has?]
And this didn't make it to the list: ---BeginMessage--- Just as a followup to some email that Tatyaso and I had: [EMAIL PROTECTED] ~] rpcinfo -t localhost nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting program 13 version 4 ready and waiting [EMAIL PROTECTED] ~] rpcinfo -u localhost nfs program 13 version 2 ready and waiting program 13 version 3 ready and waiting NFSv4 is only available over TCP and not UDP. That was what rpcinfo was showing us. ---End Message--- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: SAM-QFS
Holger Berger wrote: Ted, when will this project go public? Holger It just did this week, no? http://opensolaris.org/os/project/samqfs/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Changes to Contributor status
Jim Walker wrote: This would mean anyone who has signed the Sun Contributor Agreement or is an employee of a company that has (ie. Sun). I'm glad you brought this up. I'm working on establishing test resources on opensolaris.org (ie. self-service testing and test farm), and need a way to limit who gets access, since I won't be able to support everyone with an OpenSolaris user name. I'm targeting non-Sun code contributors (ie. OpenSolaris users that can putback to the OpenSolaris code base and don't work for Sun). Your redefinition points things in the right direction for this. Alternatively, since Contributor is already defined. How about Code Contributor? One problem with using contributers as defined by cr.opensolaris.org is that list has not been updated since the elections. http://poll.opensolaris.org/ has stale data and I think a better source needs to be in place to catch updates. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] zfs and Kernel memory usage
Gary Peck wrote: We were going to have user home directories be ZFS files systems, but found that the shutdown and startup times were to long with 15, ZFS file systems. By the way, we've been addressing this serious scaling issue. Look at Doug's blog entry: http://blogs.sun.com/dougm/entry/recent_performance_improvement_in_zfs It talks about his work with sharemgr and my work with in-kernel sharetab to reduce the startup times of having many filesystems. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: zfs and Kernel memory usage
Gary Peck wrote: Thanks for the information. I was getting worried that I was going to have to go back and ask my supervisors for money to by more memory. That would not have been pretty. Thanks, Gary This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Gary, I was only talking about the scaling issues with respect to mounting 15k filesystems. I purposely cut out any other text from your posting. I.e., I don't know enough to answer your main question. I think it is still a concern you need addressed. Thanks, Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris Storage Wishlist
This is just a heads up that the OpenSolaris Storage community is seeking discussion on a project wishlist. You can view and contribute to the thread on the storage-discuss forum over here: http://www.opensolaris.org/jive/thread.jspa?threadID=30269 This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blogs.sun.com invaded by marketing ?
So I have the problem that when I blog, I might be doing it on OpenSolaris, soccer coaching, science fiction, etc. While that is good in that it shows I have interests outside of work, it creates many threads of conversation which it can be hard to navigate through. I just recently learned that for the blog feeds for projects and communities, you could differentiate based on category. So, for the NFS community, I could tell it to only pull my NFS blog entries and not my science fiction blog entries. I think that some people are also confused about this and want to focus attention just to the specific project. Instead of learning how to aggregate on a web page or to redistribute a feed (like planet.opensolaris.org), they focus in on a group blog. I wouldn't call this organized marketing, I'd liken it more to grassroots or guerrilla marketing. The difference being that it isn't the marketing department driving some agenda, it is simply a development group pushing awareness of their own work on the world. I'd also argue that most corporate based blogging falls under this category. And most open source developers are probably just as proud to get their products out in the open. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: bug_id=6497363 : rge should support RealTek RTL8110SC/RTL8169SC
Dennis Clarke wrote: Well in that case you're welcome is the correct response here because I got there first and hit this wall and bashed my brains out on trying to get that RTL8110SC based ethernet to work with the available drivers. So if you were thanking me for blowing the time energy and money so that you don't have to ... you're welcome is all I can say. Also .. stay away from the Jetway motherboard. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org So Peter (added to CC:) is using a Jetway as an appliance. Note that I'm not sure the chipsets match, but I did want to give an example of someone using these mini-ITX boards with OpenSolaris. - Jetway Hybrid J7F2WE1G2E Mini-ITX Motherboard with VIA C7 1.2GHz Fanless Processor - Jetway AD3RTLANG 3 x Gigabit LAN Daughter Board ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bug_id=6497363 : rge should support RealTek RTL8110SC/RTL8169SC
Matt Ingenthron wrote: While it's possible to go ping the engineer and that's valuable for Dennis, it does nothing to raise the profile of the bug to Solaris engineering, does it? How should a community member raise the profile of a bug affecting them? email the engineer? email opensolaris-discuss? My suggestion did not grow out of trying to discourage people from working together in the OpenSolaris community... The same way that an internal developer would? Sending email to the RE (responsible engineer). And note, I'm only talking in the context of OpenSolaris. I've got an open bug against the nge driver for my home desktop. Do I want it fixed? Yes. Do I want to raise the priority of the bug? Yes. But those choices lay with the RE - they have to prioritize fixing bugs versus project work. This doesn't mean you should be quiet - it might turn out you can provide more information or show that the bug is hitting more than just one system. I haven't overwhelmed the RE for my nge bug with email - but then again I do not have anything new to report. By the way, my experience with the nge bug was that the engineer did some initial triaging with me and then it sat there for some months. Then the engineer wrote back asking me to try again because of a recent putback fixing a driver issue for another motherboard. Note that he may have been working that issue all along, expecting that it just might fix my problem as well. When that code change didn't work, he told me that he was ordering my motherboard and would start attacking the issue then. I've got a work around in place ($10 network card) and I'm okay with the pace. I guess I could have offered to punch a hole in my firewall to let him debug the issue live on my box. I am happy that evidently device driver engineers have a budget to get test equipment to diagnose system issues. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bug_id=6497363 : rge should support RealTek RTL8110SC/RTL8169SC
Matt Ingenthron wrote: This makes sense and I've had similar experiences myself. I guess the reason I suggested it is there has been, historically, a formal/scalable way to raise the profile on bugs affecting Solaris that is not always well understood by people outside Sun. email definitely works, makes a more personal connection that allows for the kind of collaboration you describe above, and I don't want to discount it. Still, it's susceptible to getting lost in a mailbox/organization change/etc., where the bug record lives on with an RE and responsible manager in perpetuity. That's why I suggested it. Since I'm not the expert and in the minority here, I'll consider it a lesson learned and be quiet now. :) - Matt I'm not trying to school you here Matt - I'm sorry if it came across that way. What I was trying to say is that there isn't a process where as an internal contributer, I can really raise the priority on a bug. I've been in the same boat at other companies. If we step back here, I think what you are saying is that you would like a way to add a note to the bug itself. And that feature is lacking. I agree that this is a feature we need to develop, in part because of the reasons you list. For example, I recently had a discussion with another engineer on a bug and he said there was some issue in that area of code. It wasn't recorded in a bug comment somewhere, it was in some email from 3 years ago. And his archives only went back 2 years. :- I imagine the main issues with opening up the bug database for input would be: 1) Confidential information may be present. 2) Spammers or irresponsible additions are easy. If you can think of other issues with opening things up or ways that we could handle the above issues, I'd be interested in hearing your opinion. (And that is all my emails are anyway, opinions, I'm not an expert on this stuff and I don't work on it.) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] bug_id=6497363 : rge should support RealTek RTL8110SC/RTL8169SC
Dennis Clarke wrote: Re : bug_id=6497363 How do I reach the engineer with this bug on his desk ? http://bugs.opensolaris.org/view_bug.do?bug_id=6497363 Get the engineer's name from there and send email to [EMAIL PROTECTED] I leave it as an exercise to avoid spambots killing the engineer. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: SAM-QFS
Joerg Schilling wrote: Ted Pogue [EMAIL PROTECTED] wrote: Project Overview: I propose the creation of a project on opensolaris.org, to bring to the community Solaris host-based data services; namely the Storage Archive Manager or SAM and the Solaris shared file system QFS. These data services exist today and are distributed commercially by Sun as the Sun StorageTek Storage Archive Manager and Sun StorageTek QFS shared file system. The software is delivered unbundled commercially for Solaris 9 and 10, but also is compiled for and runs on Open Solaris. While doing this is a really good idea, I see potential name conflicts with older softare. Since 20..25 years, I create and publish programs like: smake, star, sformat, sfind (a bit newer), and I recently got some information that SAMFS may include progran names like star and sfind. I support this project, but I would like to see that the programs are renamed into something like: 'sam*' in order to avoid confusion. Jörg Considering these are currently unbundled and shipping products, that might be hard. I.e., would you want to tell customers that they need to learn new commands, change all of their scripts, etc? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: SAM-QFS
Alan Coopersmith wrote: Ted Pogue wrote: I propose the creation of a project on opensolaris.org, to bring to the community Solaris host-based data services; namely the Storage Archive Manager or SAM and the Solaris shared file system QFS. The project proposal draft being considered by the OGB right now would require all Projects to be affiliated with one of the existing community groups - would it be fair to assume this project will be affiliated with the existing Storage community? Have the Storage community leaders agreed to this affiliation? Yes, we actually did a dry run on the proposal yesterday. It was a lively discussion. And I'll take your point as an issue for us to make sure new proposals list which communities are going to host it. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NFS mounted Home Directories
Elton wrote: I have setup a small (5 machines) development/test network using Solaris 10 11/06 (I know this is an OpenSolaris forum). I have an LDAP server configured and running which also serves as the Home Directory Server. The problem I have encountered is when users access there machines they can not read down and traverse their home directories. For example, a user logs in and has access to 2 labeled zones FOO and FOBAR. (FOBAR dominates FOO) So, the user is currently in the FOBAR labeled zone but CAN NOT access there home directory using the /zone/FOO/export/home path. You can access the directory but nothing is there. I have set-up the home directory per the install instruction with 1 exception. The installation instructions state, For every labeled zone, create a new dfstab file. Each zone shares the home directories at the label of the zone. a. Go to the zone’s /etc/dfs directory. # cd /zone/zone-name/root/etc/dfs I created the files as stated above but the files cannot be share from non-global zones (according to the error message I recieve) Also, I tried just rebooting the box and the nfs/server service was disabled and would not start until I removed the entries in each zone. Therefore, I added the entries the dfstab in the global zone. Now this is all on the LDAP server, is there anything I need to do to the clients? Any suggestions would be greatly appreciated. Elton This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Elton, Are you trying to have each zone export their own shares? If so, that is not supported. Look at http://www.opensolaris.org/os/project/nfs-zones/ Thanks, Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Xorg blows up on SXCE B61
Jürgen Keil wrote: I've run across what appears to be a bug with Xorg on SXCE B61. While installing Sun's web proxy 4.0.4, Xorg blew up, and kicked me out, requiring me to login again. I'd seen similar behavior with the bundled Firefox, but I was unable to reliably repeat it. Did you perhaps type control + backspace on the keyboard, while num_lock was active? With some (all?) keyboard layouts, this terminates the Xorg server: http://www.opensolaris.org/jive/thread.jspa?threadID=27754tstart=0 Or do you get an Xorg SEGFAULT? Check /var/dt/Xerrors and /var/log/Xorg.0.log for a stack backtrace of the fault; see also: http://www.opensolaris.org/jive/thread.jspa?threadID=27882tstart=0 This message posted from opensolaris.org ___ opensolaris-discuss mailing list [EMAIL PROTECTED] With Firefox, just loading some pages does it. So it is just a mouse click... ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Xorg blows up on SXCE B61
John Weekley wrote: I've run across what appears to be a bug with Xorg on SXCE B61. While installing Sun's web proxy 4.0.4, Xorg blew up, and kicked me out, requiring me to login again. I'd seen similar behavior with the bundled Firefox, but I was unable to reliably repeat it. I downloaded Mozilla.org's latest firefox build and the problem did not reappear with firefox. With the proxy server's java installer splash screen the failure is repeatable. B61 is installed on a Ferarri 3400, 768 MB RAM. Thanks, John ___ opensolaris-discuss mailing list [EMAIL PROTECTED] I've seen the same problem with Firefox - just on one of my machines. The other one is fine. ___ opensolaris-discuss mailing list [EMAIL PROTECTED]
Re: [osol-discuss] Reviewing projects, assigning mentors
Glynn Foster wrote: Please, if you are interested in mentoring a student or reviewing proposals this summer, please join [EMAIL PROTECTED] or contact me directly. I'm not going to mail opensolaris-discuss about it again. Please also feel free to forward to interested sub-communities or colleagues. thanks, Glynn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Glynn, One of the things throwing me is what do you (and the other emails before this) mean by join [EMAIL PROTECTED] ? Do you want us to send email to that address? Are we supposed to subscribe to the list? Is the list archived? Thanks, Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Reviewing projects, assigning mentors
Glynn Foster wrote: Hey, Tom Haynes wrote: One of the things throwing me is what do you (and the other emails before this) mean by join [EMAIL PROTECTED] ? Do you want us to send email to that address? Are we supposed to subscribe to the list? Yes, ideally. It'll be a forum that is used for communication with the students. Is the list archived? Yes. As part of the mentor submission, you also have to add yourself using Google's webapp, here - http://code.google.com/soc/mentor.do Unfortunately it does need a Google login, but I assume most people have that. Once you add yourself as a mentor, I can then accept you as OpenSolaris admin for the program. thanks, Glynn Sweet, that was easy. You ought to see a mentor request come across from me. I hope other people take the time to register ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: NWS (Network Storage)
John Forte wrote: The NWS project consists of drivers, libraries and utilities in support of storage interconnect technologies including both Fibre Channel and iSCSI. The NWS project source code has been available since 2/06, however, the project does not have its own project page but rather exists as part of the Storage Community. This proposal provides for NWS to be treated as a real project within OpenSolaris. Initially, it will be endorsed by the Storage Community. The NWS project currently includes: o iSCSI (software initiator) o Fibre Channel Transport o Interfaces for Fibre Channel HBA drivers o Storage Management APIs o Storage Management Utilities The initial leaders for this project would be: - Charles Baker - Aaron Dailey - John Forte - Stephen Salbato This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org +1 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: NWS (Network Storage)
Erast Benson wrote: So, could we assume that NWS now will not be delivered as a separated tarball and will be part of ON tarball? Or this is just an effort to get dedicated web page on opensolaris.org? Erast, You ask a good question. It isn't aimed as much to get a new project page in order to have yet another project going. It is aimed at clearing off the Storage community page such that it can be redesigned to fit the needs of all of Storage and not just one subset. We now have other projects linked off of that page - it seems odd to continue the NWS information on that page. Thanks, Tom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: NFSv4 namespace extensions
Robert Thurlow wrote: I propose a new project that delivers the NFSv4 extensions for Mirror Mounts, Referrals, and Replication Migration. This project should be endorsed by the NFS community. What's a mirror mount? It's a way to make the client automatically mount filesystems from the same server as it discovers them. The current Solaris NFS client code does not do this, which forces admins to update their automounter maps when new filesystems are created. ZFS admins would rather be free to create new filesystems and have them discovered. Mirror mounts are described in the NFSv4 RFC 3530, related to the server namespace. For more about how we would like this to work, please see: http://blogs.sun.com/tdh/entry/how_nfsv4_should_work_when What's a referral? It's a pointer a server can give to a client that means, I don't have the filesystem, but you can find it here. The client will redirect its access to the referred location transparently and continue. A global namespace can be constructed with a mechanism to find an initial global root and referrals. The current project is working on NFSv4.0 (RFC 3530) referral support on the client, with work to follow on NFSv4.1 referral extensions. What's replication migration? RFC 3530 defines support for a server to be able to say, that filesystem is no longer here, it's over there now or another copy of this filesystem lives here. This links the idea of a referral to the actions needed to resynchronize state of files the client was already using prior to the migration event. Being able to move and replicate filesystems freely is another part of a global namespace. Initial team: Evan Layton, Alok Aggarwal, Calum Mackay, Rob Thurlow. Rob T ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org +1 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Project Proposal: NFS Server in Local Zones
Last month I started a discussion about what should a NFS server in a zone look like? What were the goals? How did people want to use it to provide solutions for their customers? Etc. At this time, I want to propose a project to get a NFS server in a zone. I think it makes sense for the project to be contained within the NFS community, but to also have sponsorship from the zones community. Initial Project Goals: 1) Turn the requirements feedback into a document. 2) Create a design document for the project. 3) Engage the larger community into helping review these documents. Proposed project leaders: Tom Haynes, Rob Thurlow This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: help burning opensolaris express
brad kelley wrote: yes I had never done it before so hope i did it correctly. I opened the file md5sumDVD-x86-list and printed the results it showed 5 long numbers each corrosponding to one of the a-e zip files (again from my first post I did not unzip these but there was a non zipped file of the same name minux the .zip so I didn't think I had to). I printed this out and then ran the command md5sum for the zip files from a to e. the resluts matched up with what I printed out from the mdrsumDVD-x86-list. I am new to all of this so I hope i did it correctly. actually I hope I did it wrong so I can correct it and then get the darn dvd downloaded and burnt...:) thanks in advance for helping this frustrated noobanyway just to clarify again in case this is an issue, I never opened the zip files because there are files of the same name slighly bigger so I ASSUME (yea assume) that the sun download manger created these files from the zip files. the md5 sum that I ran was on the zip files...hmm hope I did this right... This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Look at Dennis Clarke's instructions here: burning snv_55b DVDs while watching for black helicopters http://www.blastwave.org/dclarke/blog/?q=node/22 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Re: help burning opensolaris express
brad kelley wrote: hmm can you suggest anything reliable...and no it can't be the solaris burning tool.(unless you want to make me cry...) in the mean time I will fish around the internet for linux burning tools...this k3b thing is not as free as it advertises...I'm on my 7th dvd! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Look to see if you can loopback mount the DVD image. http://www.linuxhelp.net/linux_downloads/ Once you do that, see if ls show interesting stuff. Try just burning the first image as a CD. You should be able to boot off of that. What about cdrecord? I don't have a Solaris DVD image on my Linux box, but this is how you can tell is the image is good: [EMAIL PROTECTED] ~] sudo mkdir /mnt/ubuntu [EMAIL PROTECTED] ~] sudo mkdir /mnt/solaris [EMAIL PROTECTED] ~] sudo mount -o loop -t iso9660 ubuntu-6.10-dvd-i386.iso /mnt/ubuntu [EMAIL PROTECTED] ~] ls -la /mnt/ubuntu total 1100 dr-xr-xr-x 14 root root 4096 Oct 25 09:35 . drwxr-xr-x 6 root root 4096 Feb 20 22:59 .. dr-xr-xr-x 2 root root 2048 Oct 25 09:30 .disk -r--r--r-- 1 root root218 Oct 25 09:30 README.diskdefines -r-xr-xr-x 1 root root 42 May 28 2006 autorun.inf dr-xr-xr-x 10 root root 6144 Oct 25 09:35 bin dr-xr-xr-x 2 root root 2048 Oct 25 09:36 casper -r-xr-xr-x 1 root root955 Sep 28 05:09 cdromupgrade dr-xr-xr-x 5 root root 2048 Oct 25 09:35 disctree dr-xr-xr-x 3 root root 2048 Oct 25 09:30 dists dr-xr-xr-x 3 root root 2048 Oct 25 09:30 doc dr-xr-xr-x 3 root root 2048 Oct 25 09:36 install dr-xr-xr-x 2 root root 14336 Oct 25 09:36 isolinux -r--r--r-- 1 root root 447171 Oct 25 09:36 md5sum.txt dr-xr-xr-x 2 root root 2048 Oct 25 09:30 pics dr-xr-xr-x 4 root root 2048 Oct 25 09:30 pool dr-xr-xr-x 2 root root 2048 Oct 25 09:30 preseed dr-xr-xr-x 8 root root 2048 Oct 25 09:35 programs -r-xr-xr-x 1 root root 390368 Oct 21 08:09 start.bmp -r-xr-xr-x 1 root root 38912 Nov 17 2003 start.exe -r-xr-xr-x 1 root root 95 Jun 29 2005 start.ini lr-xr-xr-x 1 root root 1 Oct 25 09:30 ubuntu - . -r-xr-xr-x 1 root root 193110 May 28 2006 ubuntu.ico [EMAIL PROTECTED] ~] uname -a Linux adept.internal.excfb.com 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 i686 i386 GNU/Linux [EMAIL PROTECTED] ~] sudo mount -o loop -t iso9660 sol-10-ccd-GA-x86-iso.iso /mnt/solaris [EMAIL PROTECTED] ~] ls -la /mnt/solaris/ total 28 drwxr-xr-x 4 root sys 2048 Jan 10 2005 . drwxr-xr-x 6 root root 4096 Feb 20 22:59 .. -r--r--r-- 1 root sys77 Jan 10 2005 .cdtoc drwxr-xr-x 5 root sys 2048 Jan 10 2005 .install -rw-r--r-- 1 root sys 3649 Jan 5 2005 README drwxr-xr-x 16 root sys 4096 Jan 10 2005 components -rwxr-xr-x 1 root sys 6465 Jan 5 2005 installer -rwxr-xr-x 1 root sys 636 Jan 5 2005 volstart ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] What keeps 6414874 Revive le(7D) driver from being done?
Description In order to make the revival of UltraSPARC I support useful on non-1E Ultra 1 systems, the le(7D) driver and its companions (ledma(7D), lebuffer(7D)) should be revived as well. ... * Revive the driver from old sources: I happen to have S9 sources via the Solaris University Source program, but obviously am not allowed to post them. To legally do so, I'd need help from Sun to have the pre-rip-out sources released. This shouldn't be much of a problem since this is Sun's own hardware, so I wouldn't expect 3rd-party IP to be involved (but who knows ...). Are there any legal ramifications in open sourcing the le(7D) driver? I don't see any non-Sun copyrights in the Solaris 9 code for it. Is it as simple as someone inside Sun pushing requests/documentation through channels to free this up? I'm willing to drive that effort if someone points me in the right direction... This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Community participation
Josh Hurst wrote: You could make it a community phenomenon quite like Linux if you would allow people to participate without waiting months to see the submitted patches integrated. It sucks when a five line patch for a very dumb bug is queued and no one cares. It sucks when projects like the ksh93 integration need a year, which is 12 months, 367 days or just a painful long time to integrate. Do you really think this encourages contributors? Come and wait a year to see your code rejected is the current official slogan of Opensolaris.org Which kind of contributor treatment is that? Josh ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Why do you have to get your patches integrated? Why can't people go to your web-site and get your contributions? Seems to have worked for frkit as provided by Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Community participation
Richard Lowe wrote: Tom Haynes wrote: Josh Hurst wrote: You could make it a community phenomenon quite like Linux if you would allow people to participate without waiting months to see the submitted patches integrated. It sucks when a five line patch for a very dumb bug is queued and no one cares. It sucks when projects like the ksh93 integration need a year, which is 12 months, 367 days or just a painful long time to integrate. Do you really think this encourages contributors? Come and wait a year to see your code rejected is the current official slogan of Opensolaris.org Which kind of contributor treatment is that? Josh Why do you have to get your patches integrated? Why can't people go to your web-site and get your contributions? ... I can't easily word a response to those questions, but I can only imagine they come from a complete and utter misunderstanding of this conversation, and the purposes of the project in general. The whole point is that people can contribute their changes. The whole point is that those changes go back into a source tree shared by all. -- Rich If someone makes changes to OpenSolaris and Sun decides not to take them, does that invalidate the changes? Look at the Linux kernel debugger work that wasn't being taken back because Linus didn't believe in kernel debuggers. People still found those changes useful. Right now, OpenSolaris implies Sun. It doesn't have to. You could take the latest source code drop and fork it for your development effort. Lets say someone decides to use OpenSolaris to control an appliance. They take the fork and are careful to not take new changes because it will cause their QA cycle to restart. They ship their product and as part of being good open source citizens, they provide their source tree on the install CD and on their website. Perhaps during the development process, they sent patches back to the community. But because they had no desire to pull a new drop, they didn't care whether or not the changes got in right away. Is this an OpenSolaris system or not? My point is do not get too worked up into whether or not Sun pulls your changes back into their gate - that is not what makes your contribution OpenSolaris or not. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Making automatic fresh installs easier
Stephen Lau wrote: Tom Haynes wrote: Could we get links for the latest SUNWpro, SUNWonbld, and closed binaries added? That way, instead of having to know the date, we could automate pulling down the latest bits from the mecurial repository and also getting the matching bits needed to do a full build. That way, instead of doing something like: wget http://dlc.sun.com/osol/on/downloads/current/on-closed-bins-20070122.sparc.tar.bz2 We could do: wget http://dlc.sun.com/osol/on/downloads/current/on-closed-bins-latest.sparc.tar.bz2 I'll automate the script, I just need someone to add the symlinks on the web server. Thanks, Tom Hi Tom, If you're pulling down bits via the Hg repository, you probably want to grab coordinating closed-bins from the nightly-bins dir: http://dlc.sun.com/osol/on/downloads/nightly-bins The suffix of each filename is the Hg changeset hash that matched what it built from - and -latest is a symlink to the most current one. I'm not sure what SUNWpro is.. ? Fat fingers - that is what it is: SUNWspro I can add SUNWonbld - but if you're using Hg, you probably want to be using your repository's own tools. Starting with tomorrow's delivery, you should be able to get http://dlc.sun.com/osol/on/downloads/current/SUNWonbld-latest.i386.tar.bz2 http://dlc.sun.com/osol/on/downloads/current/SUNWonbld-latest.sparc.tar.bz2 (they won't show up in the index.html page though) I'm thinking about the initial build. Once it is done, the repository's tools would be in place. cheers, steve ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Making automatic fresh installs easier
Could we get links for the latest SUNWpro, SUNWonbld, and closed binaries added? That way, instead of having to know the date, we could automate pulling down the latest bits from the mecurial repository and also getting the matching bits needed to do a full build. That way, instead of doing something like: wget http://dlc.sun.com/osol/on/downloads/current/on-closed-bins-20070122.sparc.tar.bz2 We could do: wget http://dlc.sun.com/osol/on/downloads/current/on-closed-bins-latest.sparc.tar.bz2 I'll automate the script, I just need someone to add the symlinks on the web server. Thanks, Tom This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Making automatic fresh installs easier
Just not obvious it is there. The onbld is date stamped - we should still be able to get at the latest without knowing the exact stamp. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SXCR Build 55 available
James Carlson wrote: But I think you have to be in the bad habit of logging in as root first. First time install will do that for you - there are no other users. That gets you 19 entries in / ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Release of OS/Net B56 source ?
Roland Mainz wrote: Hi! Does anyone know when the B56 sources will be released ? Seems that this may be the version we'll pick for final code review of the ksh93-integration tree... Bye, Roland http://www.opensolaris.org/os/downloads/ And Solaris Express, Community Release DVD: Download | CD: Download Solaris Express, Community Release is Sun's binary release for developers (code named "Nevada"). It contains the latest, unsupported release of the OpenSolaris bits as well as additional technology that has not been released into the OpenSolaris source base. Developers can build the OpenSolaris source by using this release as the base system. It is updated every other Friday. Since B55b just went up 1/19, my guess is that you can expect to see B56 on 2/2. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Proposal for In-Kernel Sharetab
The proposal is to move the sharetab info out of /etc/dfs/sharetab and into memory. Users can still get to the data via a filesystem interface - think of the mnttab. Problem Statement The /etc/dfs/sharetab file is used to store the currently shared exports. It contains all of the security information. Some services which reference it have a cache of entries, but for the most part, to access information on a share, you need to open and read in this file. Since the sharetab data is stored in this file, to update the sharetab, you need permissions to write to the file: [EMAIL PROTECTED] ~] ls -la /etc/dfs/sharetab -rw-r--r-- 1 root root 84176 Oct 27 11:58 /etc/dfs/sharetab A desired feature for ZFS is the ability to delegate filesystem creation to normal users. Because the parent filesystem properties are inherited, it is very possible that a share point may need to be created for the child. Since you need to be root to write to the file, we either need to open up the permissions on the file or use some mechanism to change the effective uid of the user. We don't want to change the permissions, in fact, we would prefer that there was no means to manually write to the file. Reading from the file is okay, but any changes made can bring down NFS access to the system. Since ZFS does not use RBAC (it has its own security/authorization mechanism based on ACLs), this means that we will have to use a setuid program to change the file. setuid programs are not allowed in ON. The root of the problem is that the sharetab data is backed in a file. If we were instead to keep the data in the kernel, we could avoid this problem. The data is not persistant across a reboot and thus does not need to be stored on disk. It is currently stored in a file to keep the data persistant across mountd being restarted. A secondary concern is that because the sharetab is stored in /etc/dfs/sharetab and all entries need to be sequential, the adding of new shares has to in turn be sequential. In order to gain the scalability inherent in the sharemgr's concept of share groups, we want to parallelize access to the sharetab. If all of the entries are in memory and only serialized when needed instead of all of the time, we could see scalability performance gains. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal - OpenSolaris Migration Tools
Seconded. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
