OpenSolaris
x86 and SPARC (and ARM). DTrace, ZFS, SMF, FMA, pkg(5), Caiman, and more.
Rajongók

6/1.379 rajongóÖsszes

Jegyzetek

3 jegyzetÖsszes

Social RSS

Report this feed

You are about to report that this RSS feed has violated the RSS-Connect Terms of Service, the Facebook Terms of Use, the Facebook Code of Conduct or the Facebook Copyright Policy.

All reports are strictly confidential.

Reason:
(Required)
 
Feed icon OpenSolaris Observatory  | Report
Defects
16 Nov 2009, 9:48 am

As a user of OpenSolaris, one of the best ways you can contribute to the community is by taking the time to submit the bugs you find in the product. You may also find that you get better traction with OpenSolaris engineering than raising the same issue in the forums - bug counts are reviewed weekly, forum postings are not.

The OpenSolaris project uses Bugzilla as its tracking system and its home page is at http://defect.opensolaris.org. Note, it uses a separate registration database then opensolaris.org, so you'll have to create a new account.

Before filing a bug you should first search to see if it's already being tracked. If so, feel free to add additional information or just CC yourself on the bug to keep informed of its progress. For example, I've CC'd myself on over 140 bugs.

The advanced search form is very powerful, which also makes it somewhat daunting. I mostly use the simple text based search form on the home page. Here are some basic tips I've found helpful for getting the most out of the simple text search:

  • By default, only open bugs are returned. Since the problem you are looking for might very well have already been fixed in a development build, prefix your search with ALL, for example, ALL mouse wheel.
  • Don't worry about case - table, Table and TABLE are all the same.
  • Substrings are searched - so use localiz instead of localize or localization, which will find both occurrences of the word.
  • Use quotes to search for exact words or phrases

See the Bugzilla QuickSearch page for more tips.

You'll notice at the bottom of the search results there's an option to "Remember search as":


This is very handy, especially if you've taken the time to cobble together an advanced search. Saved searches are then set up as links in the page footer. In the image above you can see I currently have 2 saved searches: "My Bugs" and "My CC'd Bugs".

Once you're reasonably sure the bug you've found hasn't been filed yet, click the File a Bug button on the home page. You'll be prompted to select a classification, for which you want to choose Distribution.


This will take you to the Enter Bug form:

Select the Component that is most closely related to your problem. As you select the components you'll see their description in the text box to the right. If you are still unsure, you can look at similar bugs you found during your search. Don't worry if it's mis-classified - it will get corrected.

After selecting the Version of OpenSolaris you are using, select the Severity. Although all bugs may feel like mission critical blockers to you, please try to be realistic with this setting:

Blocker Blocks development and/or testing work
Critical crashes, loss of data, severe memory leak
Major major loss of function
Normal regular issue, some loss of functionality under specific circumstances
Minor minor loss of function, or other problem where easy workaround is present
Trivial cosmetic problem like misspelled words or misaligned text
Enhancement Request for enhancement

Note the Enhancement value. I use this one a lot to request features I'd like to see in the product.

The two most important fields are the Summary and the Description. A good summary will quickly and uniquely identify the bug. Provide as much detail in the description as you can, ideally providing the exact steps on how to reproduce the bug and any possible work-arounds you may have discovered (documented work-arounds are one of the great benefits of searching through the bug database). Finally, don't clutter the Description field with large amounts of output or log text. Rather, use the attachment button to attach the text or log. Likewise, if you can take a snapshot of the problem, attach that as well (there's a screen shot tool in Applications > Graphics > Save Screenshot).

See the Bug Writing Guidelines for more information.

When satisfied, press Commit to submit your bug. And thank you, you've just made a valuable contribution to OpenSolaris.


Read more >>


Send story to other website
A D Script for Observing the Network
10 Nov 2009, 11:21 am
Crossbow Virtual Wire Demo Tool
30 Oct 2009, 10:22 am
D Script Archeology
28 Oct 2009, 6:39 am
DTrace Quick Start Guide
23 Oct 2009, 6:28 am
DTrace Toolkit
21 Oct 2009, 8:14 am
A Busy Weekend for OpenSolaris at Linux Conferences
20 Oct 2009, 7:25 am
vi colors
8 Oct 2009, 12:00 pm
Find out about Social RSS
Videó

2 videóÖsszes

2:48 Körülbelül 12 hónapja feltöltve
1:58 Körülbelül 12 hónapja feltöltve
Még senki nem töltött fel rajongói videókat.
Események

2 múltbeli eseményÖsszes

 
Michael Widmann

Michael Widmann See Announce: No SXCE Build 128 - Problem with Fletcher4 hashes. Waiting for build 129...

november 25., 8:39 · Jelentem
Remy Meneda

Remy Meneda is it possible to implement in future zfs the possibility to change zfs uuid ?

november 24., 14:10 · Jelentem
Dominic Bashford

Dominic Bashford I just installed this on my Windows Vista computer. I love it! Why do Windows users use Windows? This is so much better. Never, and I say never, using Windows again.

november 22., 18:07 · Jelentem
Stephan

Stephan I installed build 127 from scratch, after having used 09.06 .... now, where's the Package Manager? Can't find it in GUI or bash ...

november 21., 11:15 · Jelentem
OpenSolaris

OpenSolaris The OpenSolaris development repository is now serving Build 127 packages. See http://mail.opensolaris.org/pipermail/indiana-discuss/2009-November/016991.html
for more details.

mail.opensolaris.org
Next message: [indiana-discuss] [osol-announce] OpenSolaris package repository update, development build 127, x86/x64/SPARC (15 new packages)
Garland Sexton

Garland Sexton I have updated to build 127, now when I connect to the dev repository it shows no packages. Is this a known issue or is the dev repository down?

november 18., 8:25 · Jelentem
Hubert

Hubert Is Nexenta a good choice for a home file server using ZFS? Want to build a server with a few 1.5 or 2 TB drives and use Raid-Z. What kind of SATA controller should I go for?

november 17., 7:02 · Jelentem
William Peroche

William Peroche has anyone know if there is a live cd for opensolaris sparc?

november 17., 4:33 · Jelentem
Michael Widmann
www.cuddletech.com
ZFS Deduplication was recently putback (Sun terminology for "commit") to ON (Solaris's primary codebase). That means it should go out at snv_128 (Build 128) due later this week.
Daniel Denson

Daniel Denson I am seeing a lot about deduplication but I cant figure out how to get it. I updated via 'pfexec pkg image-update' then did my zpool upgrade and zfs upgrades but I am still at version 18 of zfs. how do I get up to version 21 that provides deduplication?

november 15., 8:52 · Jelentem
Unni Krishnan

Unni Krishnan i installed opensolaris x86 in my dell inspiron 12
need help with this
i cant get connected to internet using opensolaris

november 15., 3:48 · Jelentem
Unni Krishnan

Unni Krishnan can someone help me with this

november 15., 3:46 · Jelentem
Unni Krishnan

Unni Krishnan hi im new to open solaris.i installed it as dual boot with my win vista
but cant get network to work in solaris..but it works fine in windows

november 15., 3:45 · Jelentem
Michael Widmann

Michael Widmann The Development repositories packages were updated to build 127 on Nov. 11

november 14., 2:47 · Jelentem
Michael Widmann
blogs.sun.com
If you already know what dedup is and why you want it, you can skip the next couple of sections. For everyone else, let's start with a little background.