> Looks like this is another issue than this bug. I upgraded to b91
> this weekend and the kernel does not boot. If I file a bug report on
> this specific problem, should I enter the report into
> bugs.opensolaris.org or defect.opensolaris.org? And what log file,
> information,... should I provi
Hi,
> By "the kernel does not boot", do you mean you continue to see the hang
> during boot or did some other failure manifest itself?
I continue to see the hang during boot after loading the tzmon pseudo
device. As the bug mentioned by Randy was fixed in b91, I suppose
this is a different issue
> Trying to upgrade to snv_91 (same thing when I did snv_90), I get a
> very unhelpful error message. When I dig deeper, I grow concerned
> that I am hitting a stupid limit of zfs. Perhaps someone here can
> shed some light on whether this is a known issue that is being worked.
I've seen this is
> Previously I was able to upgrade from B86 to B90 by following the
> instructions. Now I could not upgrade it to B91.
> pkg: unable to activate opensolaris-2
You may be running into
2302 "beadm activate" fails to activate newly created, image-updated BE
How large of a drive did you ins
Hi,
> Sorry, I havn't been following this thread till now, but this seems
> a lot like 6691635.
Looks like this is another issue than this bug. I upgraded to b91
this weekend and the kernel does not boot. If I file a bug report on
this specific problem, should I enter the report into
bugs.open
> > Just yesterday I created a rather random poll for
> what things they'd
> > like to see in the package repository -
> >
> > http://forums.opensolaris.com/forum.jspa?forumID=6
> >
> > Go vote!
>
> Voted MPlayer, since multimedia's important to
> regular users. Would have
> been happier if th
Previously I was able to upgrade from B86 to B90 by following the
instructions. Now I could not upgrade it to B91.
What would be the exact steps to perform image update from B90 to B91?
Thanks,
Honglin
$ pfexec pkg refresh
$ pfexec pkg install pkg:/[EMAIL PROTECTED],5.11-0.90
$ pfexec pk
Sanjay G. Nadkarni wrote:
> I was able to successfully perform an pkg image-update from 2008.05 (86) to
> 91. For the heck of it, I tried without updating to the latest SUNWipkg.
> The only issue I hit was the pkg timeout which was addressed by setting the
> PKG_CLIENT_TIMEOUT to 120.
>
> O
Hi
What is the key comb for switching between the current active X
session and the login console?
In SuSe it is Ctl+Alt+FxxKey.
-H
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-dis
Ah... Now I understand. Thank you so much.
("`-''-/").___..--''"`-._ Qingye Jiang (John)
`6_ 6 ) `-. ( ).`-.__.`) Senior Manager
(_Y_.)' ._ ) `._ `. ``-..- Sun Developer Network, China
_..`--'_..-_/ /--'_.' ,'Phone: +86-10-62673347
(il),-'' (
On Mon, 2008-06-23 at 02:25 +0200, Francisco J. Tsao Santin wrote:
> On Sun, Jun 22, 2008 at 01:10:54PM -0700, Paul Harper wrote:
> > If Indiana is intended to be a distro for widespread adoption by
> > people who are not traditional Solaris users Vim (or Emacs) is a poor
> > choice for the text
That and because pico falls under the pine license which is less than
friendly to redistribution (especially modified versions).
2008/6/22 James Cornell <[EMAIL PROTECTED]>:
> pico is symlinked to nano because nano is based on the design (and
> maybe the code) of pico. Pico was used in Panther bu
pico is symlinked to nano because nano is based on the design (and
maybe the code) of pico. Pico was used in Panther but not Tiger and
not Leopard.
[EMAIL PROTECTED] ~$ which pico
/usr/bin/pico
[EMAIL PROTECTED] ~$ ls -l /usr/bin/pico
lrwxr-xr-x 1 root wheel 4 Jun 22 17:22 /usr/bin/pico ->
2008/6/22 Paul Harper <[EMAIL PROTECTED]>:
> If Indiana is intended to be a distro for widespread adoption by people who
> are not traditional Solaris users Vim (or Emacs) is a poor choice for the
> text editor on the Live CD.
>
> Nano or(something similarly 'braindead' as described to me on #ope
On Sun, Jun 22, 2008 at 01:10:54PM -0700, Paul Harper wrote:
> If Indiana is intended to be a distro for widespread adoption by
> people who are not traditional Solaris users Vim (or Emacs) is a poor
> choice for the text editor on the Live CD.
>
> Nano or(something similarly 'braindead' as desc
I noticed that MacOS 10.5 has pico but not pine.
("`-''-/").___..--''"`-._ Qingye Jiang (John)
`6_ 6 ) `-. ( ).`-.__.`) Senior Manager
(_Y_.)' ._ ) `._ `. ``-..- Sun Developer Network, China
_..`--'_..-_/ /--'_.' ,'Phone: +86-10-62673347
(il),
I just love nano. It is so easy to learn and use. I use it a lot. I
don't use vi because I am too lazy to remember all those tricks.
("`-''-/").___..--''"`-._ Qingye Jiang (John)
`6_ 6 ) `-. ( ).`-.__.`) Senior Manager
(_Y_.)' ._ ) `._ `. ``-..- Sun Develope
First sorry about the double posting. The slow net here made it appear I had
not posted. (Webmaster feel free to remove the duplicate post.)
I would definitely lean to nano. It basically is easy to move around in, type,
cut an paste without any instruction.
To get users who have never seen a c
I was able to successfully perform an pkg image-update from 2008.05 (86) to 91.
For the heck of it, I tried without updating to the latest SUNWipkg. The
only issue I hit was the pkg timeout which was addressed by setting the
PKG_CLIENT_TIMEOUT to 120.
One the negative side, HAL no longer r
This is an issue mirrored on all UNIX-like and UNIX systems. gksu gedit
might suit you. For practicality, running a GUI editor as root is a no-no.
Nano is the way to go, as pico is bundled with pine, which is dead news. I
just feel that starting up dependent gnome subsystems as root just to run
If Indiana is intended to be a distro for widespread adoption by people who are
not traditional Solaris users Vim (or Emacs) is a poor choice for the text
editor on the Live CD.
Nano or(something similarly 'braindead' as described to me on #opensolaris) is
the way to go.
Those who are smart e
If Indiana is intended to be a distro for widespread adoption by people who are
not traditional Solaris users Vim (or Emacs) is a poor choice for the text
editor on the Live CD.
Nano or(something similarly 'braindead' as described to me on #opensolaris) is
the way to go.
Those who are smart e
Stephen Hahn wrote:
> * Matt Ingenthron <[EMAIL PROTECTED]> [2008-06-21 19:10]:
>
>> Under what situation would I not have pkg:/[EMAIL PROTECTED],5.11-0.90 if
>> I'd already update to build 90?
>>
>
> Updated deliveries of -0.86 and -0.90 were made (as well as -0.91)
> which include th
* Matt Ingenthron <[EMAIL PROTECTED]> [2008-06-21 19:10]:
> Under what situation would I not have pkg:/[EMAIL PROTECTED],5.11-0.90 if
> I'd already update to build 90?
Updated deliveries of -0.86 and -0.90 were made (as well as -0.91)
which include the fixes for incorporations and for client
2008/6/22 Shawn Walker <[EMAIL PROTECTED]>:
> 2008/6/22 Juan Miguel Bernal Marcos <[EMAIL PROTECTED]>:
>> Hello,
>>
>> I couldn't install IPSgawk from IPS blastwave repository but I could
>> install: SUNWgcc, SUNWgmake, SUNWxorg-headers. This is the error message:
>>
>> $ pfexec pkg install IPSgaw
2008/6/22 Juan Miguel Bernal Marcos <[EMAIL PROTECTED]>:
> Hello,
>
> I couldn't install IPSgawk from IPS blastwave repository but I could install:
> SUNWgcc, SUNWgmake, SUNWxorg-headers. This is the error message:
>
> $ pfexec pkg install IPSgawk
> pkg: no package matching 'IPSgawk' could be foun
Hi,
just to support you - I've also updated to 2008.11 b91, and I'm not able to
install anything from the python2.4 gui.
..not that I used to use the gui, the commandline is just fine
It's just like it soesn't do anything at all when it should start the
download.
It does no
On Sat, 2008-06-21 at 23:42 -0700, Juan Miguel Bernal Marcos wrote:
> Hello,
>
> I couldn't install IPSgawk from IPS blastwave repository but I could install:
> SUNWgcc, SUNWgmake, SUNWxorg-headers. This is the error message:
>
> $ pfexec pkg install IPSgawk
> pkg: no package matching 'IPSgawk'
28 matches
Mail list logo
