Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
On Mon, Dec 20, 2010 at 6:55 PM, Andrew Myers wrote: > Thanks to Apostolos for the suggestion of installing snv_134. Maybe > there's more going on here than I realised, as this doesn't work for > me either. > > The first message I see is a warning: > > /p...@0,0/pci1028,2...@1a,2 (uhci2): Connecting device on port 2 failed > > Then it says "Console login services cannot run". It then goes to > system maintenance mode, and I can log in as root / jack, however I > don't know what to do after that :-). I did note that some of the > commands I tried, such as "shutdown -r now" didn't work - not sure if > these are invalid commands or whether something still hasn't become > available that should be. Check the output of svcs -xv (possibly /usr/sbin/svcs -xv if it's not in your PATH). The first service listed is the failed one, and will have a log file. shutdown does not accept an -r option, try 'init 6'. -Albert ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] opensolaris non-global zone to OI 147
On Mon, Dec 20, 2010 at 10:53 PM, Anil wrote: > I am trying to hack this to work, but this is quite annoying. > I tried doing a image-update on the zone root, after manually mounting it. > > r...@sjc:~# pkg -R /zones/sofa/root image-update > Packages to remove: 56 > Packages to install: 110 > Packages to update: 3 > Create boot environment: No > Services to restart: 2 > DOWNLOAD PKGS FILES XFER (MB) > Completed 169/169 11648/11648 100.8/100.8 > > PHASE ACTIONS > Removal Phase 2643/2643 > Install Phase 18262/18262 > Update Phase 4292/4292 > > PHASE ITEMS > Package State Update Phase 172/172 > Package Cache Update Phase 59/59 > Image State Update Phase 2/2 > > --- > NOTE: Please review release notes posted at: > > http://docs.sun.com/doc/821-1479 > --- > That for some reason only updated to build 134, instead of build 147. Why? > > Then, I did zoneadm -z sofa attach -u. > > [Monday, December 20, 2010 07:45:51 PM PST] Attaching... > [Monday, December 20, 2010 07:45:51 PM PST] existing > [Monday, December 20, 2010 07:45:51 PM PST] > [Monday, December 20, 2010 07:45:51 PM PST] Sanity Check: Passed. > Looks like an OpenSolaris system. > [Monday, December 20, 2010 07:45:54 PM PST] preferred global > publisher: openindiana.org > [Monday, December 20, 2010 07:45:55 PM PST] Global zone > version: ent...@0.5.11,5.11-0.147:20100914T054011Z > [Monday, December 20, 2010 07:45:55 PM PST] Non-Global zone > version: ent...@0.5.11,5.11-0.134.0.2:20100528T233058Z > > [Monday, December 20, 2010 07:45:55 PM PST] > Cache: Using /var/pkg/download. > [Monday, December 20, 2010 07:45:55 PM PST] Updating non-global > zone: Output follows > pkg: No solution was found to satisfy constraints > [Monday, December 20, 2010 07:46:47 PM PST] ERROR: Could not update > attaching zone > [Monday, December 20, 2010 07:46:47 PM PST] > Result: Attach Failed. > > > > > > On Mon, Dec 20, 2010 at 5:32 PM, Anil wrote: >> Trying to upgrade OpenSolaris 2009.06 non-global zone to OI 147, using >> detach/attach method. >> >> r...@sjc:~# pkg publisher >> PUBLISHER TYPE STATUS URI >> openindiana.org (preferred) origin online >> http://pkg.openindiana.org/dev/ >> opensolaris.org (non-sticky) origin online >> http://pkg.openindiana.org/legacy/ >> r...@sjc:~# >> >> >> >> r...@sr1-sjc:~# zoneadm -z sofa attach -u >> Log File: /var/tmp/sofa.attach_log.YnayVp >> Attaching... >> >> preferred global publisher: openindiana.org >> Global zone version: ent...@0.5.11,5.11-0.147:20100914T054011Z >> Non-Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z >> >> Cache: Using /var/pkg/download. >> Updating non-global zone: Output follows >> Creating Plan | >> ERROR: Could not update attaching zone >> Result: Attach Failed. >> r...@sr1-sjc:~# >> >> >> Log file: >> [Monday, December 20, 2010 05:24:31 PM PST] Log File: >> /var/tmp/sofa.attach_log.YnayVp >> [Monday, December 20, 2010 05:24:32 PM PST] Attaching... >> [Monday, December 20, 2010 05:24:32 PM PST] existing >> [Monday, December 20, 2010 05:24:33 PM PST] >> [Monday, December 20, 2010 05:24:33 PM PST] Sanity Check: Passed. >> Looks like an OpenSolaris system. >> [Monday, December 20, 2010 05:24:36 PM PST] preferred global >> publisher: openindiana.org >> [Monday, December 20, 2010 05:24:37 PM PST] Global zone >> version: ent...@0.5.11,5.11-0.147:20100914T054011Z >> [Monday, December 20, 2010 05:24:37 PM PST] Non-Global zone >> version: ent...@0.5.11,5.11-0.111:20090518T052643Z >> >> [Monday, December 20, 2010 05:24:37 PM PST] >> Cache: Using /var/pkg/download. >> [Monday, December 20, 2010 05:24:37 PM PST] Updating non-global >> zone: Output follows >> pkg: No solution was found to satisfy constraints >> [Monday, December 20, 2010 05:25:49 PM PST] ERROR: Could not update >> attaching zone >> [Monday, December 20, 2010 05:25:50 PM PST] >> Result: Attach Failed. >> >> >> How do I know what pkg's are not meeting the constraints? >> Directly updating from 2009.06 is not supported. The publisher configuration should match the global zone's (opensolaris.org must be non-sticky), see the http://wiki.openindiana.org/oi/Installing+or+Upgrading which also has debugging info. -Albert ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] opensolaris non-global zone to OI 147
I am trying to hack this to work, but this is quite annoying. I tried doing a image-update on the zone root, after manually mounting it. r...@sjc:~# pkg -R /zones/sofa/root image-update Packages to remove:56 Packages to install: 110 Packages to update: 3 Create boot environment:No Services to restart: 2 DOWNLOAD PKGS FILESXFER (MB) Completed 169/169 11648/11648 100.8/100.8 PHASEACTIONS Removal Phase 2643/2643 Install Phase18262/18262 Update Phase 4292/4292 PHASE ITEMS Package State Update Phase 172/172 Package Cache Update Phase 59/59 Image State Update Phase 2/2 --- NOTE: Please review release notes posted at: http://docs.sun.com/doc/821-1479 --- That for some reason only updated to build 134, instead of build 147. Why? Then, I did zoneadm -z sofa attach -u. [Monday, December 20, 2010 07:45:51 PM PST] Attaching... [Monday, December 20, 2010 07:45:51 PM PST] existing [Monday, December 20, 2010 07:45:51 PM PST] [Monday, December 20, 2010 07:45:51 PM PST] Sanity Check: Passed. Looks like an OpenSolaris system. [Monday, December 20, 2010 07:45:54 PM PST] preferred global publisher: openindiana.org [Monday, December 20, 2010 07:45:55 PM PST]Global zone version: ent...@0.5.11,5.11-0.147:20100914T054011Z [Monday, December 20, 2010 07:45:55 PM PST]Non-Global zone version: ent...@0.5.11,5.11-0.134.0.2:20100528T233058Z [Monday, December 20, 2010 07:45:55 PM PST] Cache: Using /var/pkg/download. [Monday, December 20, 2010 07:45:55 PM PST] Updating non-global zone: Output follows pkg: No solution was found to satisfy constraints [Monday, December 20, 2010 07:46:47 PM PST] ERROR: Could not update attaching zone [Monday, December 20, 2010 07:46:47 PM PST] Result: Attach Failed. On Mon, Dec 20, 2010 at 5:32 PM, Anil wrote: > Trying to upgrade OpenSolaris 2009.06 non-global zone to OI 147, using > detach/attach method. > > r...@sjc:~# pkg publisher > PUBLISHER TYPE STATUS URI > openindiana.org (preferred) origin online > http://pkg.openindiana.org/dev/ > opensolaris.org (non-sticky) origin online > http://pkg.openindiana.org/legacy/ > r...@sjc:~# > > > > r...@sr1-sjc:~# zoneadm -z sofa attach -u > Log File: /var/tmp/sofa.attach_log.YnayVp > Attaching... > > preferred global publisher: openindiana.org > Global zone version: ent...@0.5.11,5.11-0.147:20100914T054011Z > Non-Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z > > Cache: Using /var/pkg/download. > Updating non-global zone: Output follows > Creating Plan | > ERROR: Could not update attaching zone > Result: Attach Failed. > r...@sr1-sjc:~# > > > Log file: > [Monday, December 20, 2010 05:24:31 PM PST] Log File: > /var/tmp/sofa.attach_log.YnayVp > [Monday, December 20, 2010 05:24:32 PM PST] Attaching... > [Monday, December 20, 2010 05:24:32 PM PST] existing > [Monday, December 20, 2010 05:24:33 PM PST] > [Monday, December 20, 2010 05:24:33 PM PST] Sanity Check: Passed. > Looks like an OpenSolaris system. > [Monday, December 20, 2010 05:24:36 PM PST] preferred global > publisher: openindiana.org > [Monday, December 20, 2010 05:24:37 PM PST] Global zone > version: ent...@0.5.11,5.11-0.147:20100914T054011Z > [Monday, December 20, 2010 05:24:37 PM PST] Non-Global zone > version: ent...@0.5.11,5.11-0.111:20090518T052643Z > > [Monday, December 20, 2010 05:24:37 PM PST] > Cache: Using /var/pkg/download. > [Monday, December 20, 2010 05:24:37 PM PST] Updating non-global > zone: Output follows > pkg: No solution was found to satisfy constraints > [Monday, December 20, 2010 05:25:49 PM PST] ERROR: Could not update > attaching zone > [Monday, December 20, 2010 05:25:50 PM PST] > Result: Attach Failed. > > > How do I know what pkg's are not meeting the constraints? > > Thanks > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Poor text antialiasing behaviour in Firefox
On 20 Dec, 2010,at 04:21 AM, Guido Berhoerster wrote:
* Dave Koelmeyer [2010-12-19 14:13]:
> Hi,
>
> I posted this over on OpenSolaris.org, but FWIW:
>
> This has always bugged me for as long as I can remember, and I
> wonder if anyone knows why.
>
> Firefox 3.6.8 in Ubuntu:
>
> http://www.davekoelmeyer.co.nz/docs/Ubuntu1004Firefox368.png
>
> All headings and text are antialised, and page appears fine.
>
> Now, compare with the same page in Firefox 3.6.12 on
> OpenSolaris/OpenIndiana:
>
> http://www.davekoelmeyer.co.nz/docs/oi_147Firefox3612.png
>
> Most text elements by comparison are pretty jagged, but the headings
> are particularly ugly.
>
> Interestingly, this is the same page, but zoomed in two increments:
>
> http://www.davekoelmeyer.co.nz/docs/oi_147Firefox3612-zoomed.png
>
> Note that main heading ("DATAZUUL") is now displaying with nicely
> antialiased edges.
>
> All the above examples are on stock-standard installs of Firefox,
> with fonts settings left at defaults.
>
> Any ideas?
If you want to get completely rid of bitmaps font in applications
that use fontconfig you can either enable
/etc/fonts/conf.avail/70-no-bitmaps.conf (which is what Ubuntu
does) or put its contents in your ${HOME}/.fonts.conf. For
details see fonts.conf(5)
Hi All,
The workaround in comment 13 here did the trick:
https://defect.opensolaris.org/bz/show_bug.cgi?id=4605#c13
alanc also helpfully provided the following info:
http://opensolaris.org/jive/thread.jspa?threadID=136192&tstart=0
As I understand it, the Opensolaris Extras repository is now closed to new
users, so I wonder if the above workaround or something similar would be a
useful thing to do to ensure a good-looking browsing experience out of the box?
Cheers,
Dave
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] opensolaris non-global zone to OI 147
Trying to upgrade OpenSolaris 2009.06 non-global zone to OI 147, using detach/attach method. r...@sjc:~# pkg publisher PUBLISHER TYPE STATUS URI openindiana.org (preferred) origin online http://pkg.openindiana.org/dev/ opensolaris.org (non-sticky) origin online http://pkg.openindiana.org/legacy/ r...@sjc:~# r...@sr1-sjc:~# zoneadm -z sofa attach -u Log File: /var/tmp/sofa.attach_log.YnayVp Attaching... preferred global publisher: openindiana.org Global zone version: ent...@0.5.11,5.11-0.147:20100914T054011Z Non-Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z Cache: Using /var/pkg/download. Updating non-global zone: Output follows Creating Plan | ERROR: Could not update attaching zone Result: Attach Failed. r...@sr1-sjc:~# Log file: [Monday, December 20, 2010 05:24:31 PM PST] Log File: /var/tmp/sofa.attach_log.YnayVp [Monday, December 20, 2010 05:24:32 PM PST] Attaching... [Monday, December 20, 2010 05:24:32 PM PST] existing [Monday, December 20, 2010 05:24:33 PM PST] [Monday, December 20, 2010 05:24:33 PM PST] Sanity Check: Passed. Looks like an OpenSolaris system. [Monday, December 20, 2010 05:24:36 PM PST] preferred global publisher: openindiana.org [Monday, December 20, 2010 05:24:37 PM PST]Global zone version: ent...@0.5.11,5.11-0.147:20100914T054011Z [Monday, December 20, 2010 05:24:37 PM PST]Non-Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z [Monday, December 20, 2010 05:24:37 PM PST] Cache: Using /var/pkg/download. [Monday, December 20, 2010 05:24:37 PM PST] Updating non-global zone: Output follows pkg: No solution was found to satisfy constraints [Monday, December 20, 2010 05:25:49 PM PST] ERROR: Could not update attaching zone [Monday, December 20, 2010 05:25:50 PM PST] Result: Attach Failed. How do I know what pkg's are not meeting the constraints? Thanks ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
Thanks to Apostolos for the suggestion of installing snv_134. Maybe there's more going on here than I realised, as this doesn't work for me either. The first message I see is a warning: /p...@0,0/pci1028,2...@1a,2 (uhci2): Connecting device on port 2 failed Then it says "Console login services cannot run". It then goes to system maintenance mode, and I can log in as root / jack, however I don't know what to do after that :-). I did note that some of the commands I tried, such as "shutdown -r now" didn't work - not sure if these are invalid commands or whether something still hasn't become available that should be. I'm happy to keep testing this if it's something that could be helpful to others but if not then I might just have to play with open indiana on my other machine instead... ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] time-slider is snapshotting swap and dump after upgrading to oi_147
* Jeremy Thornhill [2010-12-20 22:21]:
> I have created an issue in the Opensolaris bug tracker and I've
> updated the Illumos ticket with the URL. Hopefully they will fix it,
> if not I'd be glad to hack together a patch that makes this not happen
> in OI. I'm no python guru but this should be a pretty easy fix :)
>
> Oh, and should anybody else encounter this issue, if you'd rather not
> hack zfs.py, a workaround is to *also* set
> com.sun:auto-snapshot:{frequent|hourly|daily|monthly|weekly}=false on
> any of the volumes that are being snapshotted incorrectly.
>
Thanks a lot.
--
Guido Berhoerster
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] time-slider is snapshotting swap and dump after upgrading to oi_147
On Mon, Dec 20, 2010 at 3:17 PM, Guido Berhoerster wrote:
> Thanks for investigating this, time-slider is still developed in
> the open by Oracle, see
> http://src.opensolaris.org/source/xref/jds/time-slider/
> We currently ship the latest version so this has not been fixed
> upstream.
> So I figure in this case it would make sense to raise this issue
> upstream with the information you already provided at the OI
> tracker. If they do not fix it in a reasonable timeframe we'll
> have to come up with a fix on our own.
> Would you mind filing a bug at http://defect.opensolaris.org/ and
> linking to it from the OI bug afterwards?
I have created an issue in the Opensolaris bug tracker and I've
updated the Illumos ticket with the URL. Hopefully they will fix it,
if not I'd be glad to hack together a patch that makes this not happen
in OI. I'm no python guru but this should be a pretty easy fix :)
Oh, and should anybody else encounter this issue, if you'd rather not
hack zfs.py, a workaround is to *also* set
com.sun:auto-snapshot:{frequent|hourly|daily|monthly|weekly}=false on
any of the volumes that are being snapshotted incorrectly.
Jeremy
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] man pages to solaris cmds
On Sun, Dec 19, 2010 at 8:46 PM, Harry Putnam wrote: > I couldn't make heads or tails of that. . sorry. Perhaps the kinder, gentler heads up message will make more sense. http://hub.opensolaris.org/bin/view/Community+Group+on/2008051501 -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] man pages to solaris cmds
Albert Lee writes:
[...]
Harry Wrote:
>> Someone advised me to set LANG=en_US.ISO8859-1. When I did that, it
>> does cure my on-going problem, but now wondering if when calling
>> `man /bin/ls' ... it may act differently with LANG set that way.
>>
>> Yup... I just tested that theory out.
>>
>> When I do a fresh login (to oi 148) $LANG is en_US.UTF-8. On that
>> setting all man pages have goofy characters like this (from man ls)
>>
>>
>> DESCRIPTION
>> List information about the FILEs (the current directory by
>> default). Sort entries alphabetically if none of ââctuvSUX
>> nor ââsort.
>>
>> But I can call `man /bin/ls' and it opens the right page... with no
>> warnings about binary, but it does have the guff above in it.
>>
>> If I set LANG=en_US.ISO8859-1 then man pages open nice and clean but
>> it does cause the warnings about binary files (and fail) if I should
>> try `man /bin/ls' with that setting.
>>
>> Another poster here or on openindiana explained it best he could to me
>> and seems a mismatch of some sort between my terminal program and
>> $LANG setting. I can correct if I happen to be using putty from
>> windows, but logging in from linux or another solaris machine... I'm
>> not really sure what terminal program is involved... the TERM setting
>> when from linux is `TERM=linux', when from solaris TERM=sun-color.
>>
>> But what actual program is running the terminal... I don't know for sure.
>>
Albert Responded:
> The problem is probably not the terminal application itself, but TERM
> which tells applications which terminal definition to use to
> communicate with it. It's a relic of the days of physical terminals
> when every vendor had its own incompatible protocol.
>
> (That said, the standard terminal app is gnome-terminal and has a
> Help->About dialog which should be impossible to miss...)
That would not hold true if the connection is to console mode would
it? I mean the oi install is not running an X desktop.
When I login from a linux desktop running X, my TERM becomes `xterm'.
When I login from a windows machine using putty, my TERM becomes
`xterm'.
When I login at the oi console my TERM becomes `sun-color'
I don't think gnome-terminal comes into play ...
I've already described the difference in behavior when LANG is set
differently.
Briefly:
In order to see man pages without odd characters in them when man is
called in the normal way ( man ls) I find it necessary to set the
LANG variable to en_US.ISO8859-1
As to different behaviors according to LANG setting:
LANG set to en_US.UTF-8
Calling man normally (man ls) reveals unusual char in the pages
makeing it difficult to read them.
There is no error when calling `man /bin/ls', however the manpage
revealed has unusual characters in it:
man /bin/ls
[...]
SYNOPSIS
/usr/bin/ls [ââabccdeeffghhikllmnopqrrsstuuwv...@]
[ââ/c | ââ/] [ââ%atime | crtime | ctime | mtime | all]
[ââblockâsize size] [ââcolor[=when]] [ââfileâtype]
[ââsi] [ââtimeâstyle style] [file]...
[...]
---- ---=--- -
LANG set to en_US.ISO8859-1
Now man pages called with the normal `ls man' are clean and
readable, however calling `man /bin/ls' now provokes the error, and
the page displayed if I answer `y' is even harder to read and seems
to contain a different sort of mess ... looks like escape sequences
I think.
man /bin/ls
"/usr/share/man/cat1/ls.1" may be a binary file. See it anyway? y
SYNOPSIS
/usr/bin/ls [â<80><90>â<80><90>abccdeeffghhikllmnopqrrsstuuwv...@]
[â<80><90>â<80><90>/c | â<80><90>â<80><90>/]
[â<80><90>â<80><90>%atime | crtime | ctime | mtime | all]
[â<80><90>â<80><90>blockâ<80><90>size size]
[â<80><90>â<80><90>color[=when]] [â<80><90>â<80><90>fileâ<80><90>type]
[â<80><90>â<80><90>si] [â<80><90>â<80><90>timeâ<80><90>style
style] [file]...
---- ---=--- -
> Anyway, I can't reproduce the problem here. What would help is to provide:
> The output of 'env', the error you're seeing from 'man /bin/ls' and
> the file contents from 'truss -f man /bin/ls 2>logfile'.
I've inlined env output below, but `truss -f man /bin/ls 2>logfile' has
been running for 13 minutes now with no evidence of returning the
command prompt, as can be seen from the following output.
reader > ps wwaux|awk 'NR==1{firstline = $0}
/truss.*man/{print}END{print firstline}';date
reader1622 0.0 0.2 2440 1876 pts/5S 13:54:38 0:00 truss -f man
/bin/ls
reader1625 0.0 0.2 2448 1612 pts/5S 13:54:39 0:00 truss -f man
/bin/ls
USER PID %CPU %MEM SZ RSS TT SSTART TIME COMMAND
Monday, December 20, 2010 02:07:15 PM CST
Started at 1:54 and still running at 2:07
Is that the expected outcome?
When I kill the command, a file of 359 lines is produced and a
Re: [OpenIndiana-discuss] time-slider is snapshotting swap and dump after upgrading to oi_147
* Jeremy Thornhill [2010-12-20 20:02]: > On Sun, Dec 19, 2010 at 10:27 AM, Jeremy Thornhill > wrote: > > > > FWIW I've created an issue for this http://www.illumos.org/issues/537 > > and if I find any useful info I'll post it there. > > To reply to myself - I believe I've identified a bug in the > time-slider code and I've added what I think is happening to that > ticket. I don't know whether time-slider has a maintainer, but > hopefully I've provided enough information to fix the bug. It's > possible that this has already been fixed upstream but I have no way > to verify that at the moment. Thanks for investigating this, time-slider is still developed in the open by Oracle, see http://src.opensolaris.org/source/xref/jds/time-slider/ We currently ship the latest version so this has not been fixed upstream. So I figure in this case it would make sense to raise this issue upstream with the information you already provided at the OI tracker. If they do not fix it in a reasonable timeframe we'll have to come up with a fix on our own. Would you mind filing a bug at http://defect.opensolaris.org/ and linking to it from the OI bug afterwards? TIA, -- Guido Berhoerster ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] time-slider is snapshotting swap and dump after upgrading to oi_147
On Sun, Dec 19, 2010 at 10:27 AM, Jeremy Thornhill wrote: > > FWIW I've created an issue for this http://www.illumos.org/issues/537 > and if I find any useful info I'll post it there. To reply to myself - I believe I've identified a bug in the time-slider code and I've added what I think is happening to that ticket. I don't know whether time-slider has a maintainer, but hopefully I've provided enough information to fix the bug. It's possible that this has already been fixed upstream but I have no way to verify that at the moment. Thanks, Jeremy ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI_148 available
The update from oi_147 went smoothly, thanks for your work! Hillel. On Fri, Dec 17, 2010 at 6:36 PM, Jon Tibble wrote: > Project OpenIndiana is pleased to announce the next development release, > oi_148, is available. > > Existing users can image-update from their current repositories. > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] OI_148 available
* Nikola M. [2010-12-20 13:59]: > On 12/18/10 12:36 AM, Jon Tibble wrote: > >Project OpenIndiana is pleased to announce the next development > >release, oi_148, is available. > Hi, thanks for work and some questions: > > 1.Update from Media to newer OI: > Can one update current oi_147 installation using downloaded oi_148.iso > Live DVD image? No, you have to use a repository to update. > 2. Fresh install of new BE of OI on existing zpool: > Is there a manual how to install fresh copy of OpenIndiana 148 in the > new Boot Environment, like fresh install on existing root zpool? > I would like to have a fresh start OI, beside previous BEs and > programs/installs At least the installer is not capable of handling this. Why do you want to do that anyway? > 3. Dev /update publisher for Program and system updates: > How program updates (like Firefox, Thunderbird, security updates of > other packages) will be handled at a later time (We need to have IPS dev > /update publisher for this) We are still far away from a stable release and have not decided how to handle updates, I suppose a separate /stable or /release repo recieving updates would do. > 4. Illumos OS/Net integration: > If I install OI_148 and then compile Illumos OS/Net and use it that way, > will everything work fine? > E.G. What would be best/major steps for users in doing testing and > contributing to Illumos integration in OpenIndiana? Since I am not working in this area I leave that for others to comment on. One major issue with the transition to Illumos is that we need to get the adapt the G11n to Illumos, so far it is quite broken and does not even build on OpenSolaris/current OpenIndiana. > BTW, I could not do GUI log in into 148 after update from 147, since > X freezes the next moment (bug is there since snv_132 and it seems > that I am unable to use it anymore on Dell Latitude D620 Nbook. Please report a bug to http://www.illumos.org/projects/openindiana/issues with more details (exact hardware, logs etc.) > Not to mention that Suspend to ram worked on Illumos ON months ago > and it still does not on OpenIndiana. > Also VirtualBox internal networking does not work for me on Please report that to the VirtualBox project, see http://www.virtualbox.org/wiki/Bugtracker > OpenIndiana AND USB support is not activating since closed source > .pkg package of Virtualbox is not recognizing oi_ but expects snv_ > version of the OS. Any workarounds? There is a fix for the version detection in the VirtualBox repo, see http://www.virtualbox.org/changeset/33039 You could apply this to the postinstall script before installing the package. > Also How to update FF/TB, etc, before new /dev OI release? You could try installing the contributed builds listed on http://hub.opensolaris.org/bin/view/Community+Group+desktop/development Please note that we do not support this, any issues should be reported to desktop-disc...@opensolaris.org > Should we not have some kind of service publisher for dev releases? What do you mean by that? > When first dev release with Illumos bits will be there? The next dev release will have Oracle ON replaced with Illumos, it will be released when it's ready. -- Guido Berhoerster ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
> I am observing this on both 147 and 148. The exact same DVD's boot fine on > an old IBM ThinkPad R40 which I have, so I do not believe the media to be > the problem. > > Is there anything else I can try to assist with debugging this? I had observed the same problem in two machines while other identical machines had no problem with the same media. At any rate, I had to install snv_134 and then to upgrade... A.S. -- Apostolos Syropoulos Xanthi, Greece ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] OI_148 available
On 12/18/10 12:36 AM, Jon Tibble wrote: Project OpenIndiana is pleased to announce the next development release, oi_148, is available. Hi, thanks for work and some questions: 1.Update from Media to newer OI: Can one update current oi_147 installation using downloaded oi_148.iso Live DVD image? 2. Fresh install of new BE of OI on existing zpool: Is there a manual how to install fresh copy of OpenIndiana 148 in the new Boot Environment, like fresh install on existing root zpool? I would like to have a fresh start OI, beside previous BEs and programs/installs 3. Dev /update publisher for Program and system updates: How program updates (like Firefox, Thunderbird, security updates of other packages) will be handled at a later time (We need to have IPS dev /update publisher for this) 4. Illumos OS/Net integration: If I install OI_148 and then compile Illumos OS/Net and use it that way, will everything work fine? E.G. What would be best/major steps for users in doing testing and contributing to Illumos integration in OpenIndiana? BTW, I could not do GUI log in into 148 after update from 147, since X freezes the next moment (bug is there since snv_132 and it seems that I am unable to use it anymore on Dell Latitude D620 Nbook. Not to mention that Suspend to ram worked on Illumos ON months ago and it still does not on OpenIndiana. Also VirtualBox internal networking does not work for me on OpenIndiana AND USB support is not activating since closed source .pkg package of Virtualbox is not recognizing oi_ but expects snv_ version of the OS. Any workarounds? Also How to update FF/TB, etc, before new /dev OI release? Should we not have some kind of service publisher for dev releases? Nikola M. When first dev release with Illumos bits will be there? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI_148 available
Contributing some torrent bandwidth as well, even though at the moment it's already pretty fast, I downloaded at something like 5 MB/s :-) :MF 2010/12/18 Kees Nuyt : > > On Sat, 18 Dec 2010 20:06:50 +0100, Jesus Cea wrote: > >>I stop seeding 147. Stats: >> >>oi-dev-147-x86.usb: 56.38GB >>oi-dev-147-x86.usb.writable with-dd: 48.35GB >>oi-dev-147-x86.iso: 87.80gGB >> >>Seeding 148 now. Thanks. >> >>I don't have enough space in my HD now for all the files, so my download >>will be partial until tomorrow, when I clean up things. >> >>PS: When the new dd->usb file is available, let me know to seed it too. > > I stopped seeding oi-dev-147-x86.iso about a month ago. > stats: uploaded 59.8 GB (ratio 68.7). > > Now seeding oi-dev-148-x86, both the .iso and the .usb, at just 100 > kByte/sec total (yeah, home ADSL, Europe). > .usb is more popular than .iso right now. > -- > ( Kees Nuyt > ) > c[_] > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI hangs early in boot when drives are connected
On Mon, Dec 20, 2010 at 11:59, Tom Fanning wrote:
> On Sun, Dec 19, 2010 at 5:15 AM, Albert Lee wrote:
>> On Mon, Dec 13, 2010 at 10:28 AM, Tom Fanning wrote:
>>> Hi all
>>>
>>> oi-dev-147-text-x86.usb hangs at the start of the boot at "All rights
>>> reserved. Use is subject to license terms" when my SATA drives (4x
>>> 1TB) are plugged in.
>>>
>>> If I unplug the drives, the machine boots.
>>>
>>> Where do I start with this one? My hardware is an Atom D510 on a
>>> Gigabyte GA-D510UD board.
>>>
>>> Drives are known good and contain an exported zpool (from FreeBSD)
>>> which I intend to import and upgrade.
>>>
>>
>> I suspect your pool's constituent devices have no GPT (EFI label) as
>> required by Solaris/OpenIndiana ZFS, as FreeBSD does not enforce this
>> requirement when creating pools. The failure mode is rather odd,
>> though.
>>
>> -Albert
>>
>
>
> Hi Albert,
>
> Thanks for your reply.
>
> Can I safely add a GPT to these drives retrospectively?
as I understand GPT, you can't - it's the description of how the disk
is partitioned ("divvied up"), and is quite different from the
traditional "MBR"-style partition table. changing this type will lose
all data on the disk.
HTH
Michael
--
regards/mit freundlichen Grüssen
Michael Schuster
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
Sorry to jump in late on this thread, but I'm seeing the error described by Kostas Oikonomou on my Dell e6400. (original post here: http://www.mail-archive.com/openindiana-discuss@openindiana.org/msg01290.html ) I am observing this on both 147 and 148. The exact same DVD's boot fine on an old IBM ThinkPad R40 which I have, so I do not believe the media to be the problem. Is there anything else I can try to assist with debugging this? Many thanks, Andrew. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI hangs early in boot when drives are connected
On Sun, Dec 19, 2010 at 5:15 AM, Albert Lee wrote: > On Mon, Dec 13, 2010 at 10:28 AM, Tom Fanning wrote: >> Hi all >> >> oi-dev-147-text-x86.usb hangs at the start of the boot at "All rights >> reserved. Use is subject to license terms" when my SATA drives (4x >> 1TB) are plugged in. >> >> If I unplug the drives, the machine boots. >> >> Where do I start with this one? My hardware is an Atom D510 on a >> Gigabyte GA-D510UD board. >> >> Drives are known good and contain an exported zpool (from FreeBSD) >> which I intend to import and upgrade. >> > > I suspect your pool's constituent devices have no GPT (EFI label) as > required by Solaris/OpenIndiana ZFS, as FreeBSD does not enforce this > requirement when creating pools. The failure mode is rather odd, > though. > > -Albert > Hi Albert, Thanks for your reply. Can I safely add a GPT to these drives retrospectively? Kind regards Tom ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
I can confirm that this is a corrupted media. I've faced similar errors, and had to create new media. OI build 147 works flawlessly on a Dell D6510 :) -- Ram On Mon, Dec 20, 2010 at 1:29 PM, Albert Lee wrote: > On Wed, Dec 8, 2010 at 1:32 PM, Kostas Oikonomou > wrote: >> Hi, >> >> I'm trying to install the live CD on a Dell 6510 laptop. The installation >> fails fairly early on, with a message to the effect that libfmevent.so >> cannot be found: >> >> ld.so.1: svc.startd: fatal: libfmevent.so.1: open failed: No such file or >> directory >> >> Has anyone else seen this, and is there anything to be done? >> > > This indicates an attempt to report an error to FMA early in boot, but > there is a bug (probably http://www.illumos.org/issues/562 ) which > prevents FMA from working a this stage so you don't get the actual > error message. Most likely cause is corruption on the DVD. > > -Albert > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- Belenix: www.belenix.org ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] libfmevent problem with installing oi_147
On Wed, Dec 8, 2010 at 1:32 PM, Kostas Oikonomou wrote: > Hi, > > I'm trying to install the live CD on a Dell 6510 laptop. The installation > fails fairly early on, with a message to the effect that libfmevent.so > cannot be found: > > ld.so.1: svc.startd: fatal: libfmevent.so.1: open failed: No such file or > directory > > Has anyone else seen this, and is there anything to be done? > This indicates an attempt to report an error to FMA early in boot, but there is a bug (probably http://www.illumos.org/issues/562 ) which prevents FMA from working a this stage so you don't get the actual error message. Most likely cause is corruption on the DVD. -Albert ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
