Re: [OmniOS-discuss] libc.so.1 checksum
On Thu, Jan 09, 2014 at 15:04:45 +, Damian McD wrote: > I was following some security guidelines in Oracle's docs and get an > error regarding libc.so.1 via pkg verify > > > pkg://omnios/system/library > file: lib/libc.so.1 > Elfhash: 21008faaa95e095cdd5a6200dee4659db922fb66 should > be 560f24729aedd180595ce78e58e95432ea93f5ad > > ls -l /lib/libc.so.1 > -rwxr-xr-x 1 root bin 1575684 Dec 10 21:39 /lib/libc.so.1 This is not actually an issue because of the way we're delivering libc.so.1. If you look at your mounts you'll see that there's a mount for that file, which changes the elfhash. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Dell R720 & Broadcom ethernet
On Thu, Dec 26, 2013 at 19:27:35 +, Scott Roberts wrote: > To be clear, neither the onboard Gigabit or 10Gig links are shown, only > loopback, so running a pkg install fails. I don't have any PCI ethernet > cards to throw in this thing, either. I'm pretty much dead in the water. You can use an existing system to create a package archive of lspci, which you could then transfer over virtual disk in your IPKVM, via sneakernet, or other means. pkgrecv -a -d lspci.p5a -s http://pkg.omniti.com/omnios/release/ \ pkg:/system/pciutils Also of interest would be `prtconf -v` output, but admittedly without network that might be hard to acquire. The R720, according to the datasheet, uses the Intel C600 series chipset, and its NIC (the 82579LM) is listed in the HCL, so in theory it should work. It's not disabled in the BIOS, or anything silly like that, right? -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] zoneadm -z zone attach -u fails
On Fri, Dec 13, 2013 at 16:52:31 +0100, Natxo Asenjo wrote: > hi, > > Following the update I needed to update my only non-global zone as > well but this is the result: > > # /usr/sbin/zoneadm -z zone1 attach -u > Log File: /var/tmp/zone1.attach_log.X6ai9c >Attach Path: /tank/zones/zone1/root > Attach ZFS Dataset: tank/zones/zone1/ROOT/zbe-1 > > Installing: Using pre-existing data in zonepath > Result: Attach Failed. > > And in the log: > > [Fri Dec 13 16:38:35 CET 2013] Log File: /var/tmp/zone1.attach_log.X6ai9c > [Fri Dec 13 16:38:38 CET 2013]Attach Path: > /tank/zones/zone1/root > [Fri Dec 13 16:38:38 CET 2013] Attach ZFS Dataset: > tank/zones/zone1/ROOT/zbe-1 > > [Fri Dec 13 16:38:38 CET 2013] existing > [Fri Dec 13 16:38:38 CET 2013] Installing: Using > pre-existing data in zonepath > [Fri Dec 13 16:38:38 CET 2013] Sanity Check: Passed. Looks like an > OpenSolaris system. > Unable to get preferred publisher information for zone 'global'. > brand-specific usage: attach [-a archive] [-d dataset] [-n] [-r zfs-recv] [-u] > The -a archive option specifies a tar file or cpio archive. > The -d dataset option specifies an existing dataset. > The -r zfs-recv option receives the output of a 'zfs send' command > of an existing zone root dataset. > The -u option indicates that the software should be updated to match > the current host. > [Fri Dec 13 16:38:43 CET 2013] Result: Attach Failed. > > Any clues? This is an issue that we're looking into fixing. It looks like the zone attach script is expecting output that isn't there, or output in another format. More to come when we know more. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] r151008 ipkg zone attach problems
On Wed, Dec 11, 2013 at 10:16:13 +0200, Lauri Tirkkonen wrote: > On Sat, Dec 07 2013 18:52:59 +0200, Lauri Tirkkonen wrote: > > I noticed that I could not attach my non-global zones under r151008 > > after upgrading from r151006. I made a couple VMs to reproduce, and it > > turns out that ipkg zone attach is broken on r151008 even on a fresh > > install > > Just a heads up - this is still broken on r151008f. Should I make a bug > report on the tracker? Yes, please. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Updated releases: 151008f, 151006_32
This week brings us two new releases in each current stable branch. r151006_032 has a fix in the `entire` incorporation to allow users to upgrade and install new packages while staying on 151006, and r151008f brings a fix for pkg:/system/file-system/zfs for 4347 ZPL can use dmu_tx_assign(TXG_WAIT) (https://www.illumos.org/issues/4347). In addition, the documentation for upgrading from 151006->151008 has been updated to reflect the new incorporation fixes in 151006. These should fix present known upgrade and installation issues users are experiencing. As always, you can view the release notes on our site: http://omnios.omniti.com/wiki.php/ReleaseNotes Thank you so much for using OmniOS. I hope it is as useful for you as it is for us. Have fun! -- Chris Nehren Site Reliability Engineer, OmniTI pgp0IB3o09_d2.pgp Description: PGP signature ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Fixing a Package With Errors
The best way to fix this would be to roll back to a prior BE, figure out what broke you upgrade, fix i, and try again. On Tue, Dec 10, 2013 at 14:51:11 +0530, Sam M wrote: > Anyone? Am kind of stuck here. > > Thanks. > > On 04/12/2013, Sam M wrote: > > Hello. > > > > I'm running OmniOS Bloody. I was getting an error with visudo so I tried to > > fix this by re-0nstalling the package in question. But I'm unable to. How > > can I fix this? How do I create/modify an alternate boot environment? > > > > BTW, I upgraded from Release to Bloody, so I booted into a Release boot > > envirnment, and I'm seeing the same error with libc.so.1 as in Bloody. > > > > TIA. > > > > Sam > > > > System > > *# uname -a* > > SunOS sequoia 5.11 omnios-e97fba8 i86pc i386 i86pc > > > > Error - > > *# visudo* > > ld.so.1: visudo: fatal: libc.so.1: version 'ILLUMOS_0.7' not found > > (required by file /usr/sbin/visudo) > > ld.so.1: visudo: fatal: libc.so.1: open failed: No such file or directory > > Killed > > > > pkg fix error - > > *# pkg fix pkg://omnios/system/library * > > Verifying: pkg://omnios/system/library ERROR > > > > file: lib/libc.so.1 > > Elfhash: c31add3bd373a101cb7aa14a2185beef9bd6ad61 should be > > 2f678d3e88ee49238a7c4b87dfdcc92837ea5814 > > Created ZFS snapshot: 2013-12-04-14:00:23 > > > > Repairing: pkg://omnios/system/library > > pkg: Requested "fix" operation would affect files that cannot be modified > > in live image. > > Please retry this operation on an alternate boot environment. > > > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] userland woes
On Mon, Dec 09, 2013 at 12:08:59 -0500, Eric Sproul wrote: > On Mon, Dec 9, 2013 at 11:51 AM, Volker A. Brandt wrote: > > So the library/uuid pkg is my problem here? That's... interesting. > > Is deinstalling and not using ms.omniti.com any more the only option? > > The packages in ms.omniti.com were built for r151006, so they > appropriately use an incorporate dependency on entire@151006. > Eventually there will be r151008 versions in ms.omniti.com, so it's > your choice. You can wait for that to happen or you can remove uuid > and move the system forward. Or, since the build bits are open source, you can build your own local copies and use those. Yes, it's an inconvenience, but we're working on it, and there are ways forward beyond "don't use this thing that's critical for your app". -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] userland woes
On Mon, Dec 09, 2013 at 16:51:14 +0100, Tobias Oetiker wrote: > Hi Eric, > > Today Eric Sproul wrote: > > > You can check to see if any unexpected incorporate dependencies exist > > with pkg search: > > > > pkg search -H -o pkg.fmri -l 'depend:incorporate:*@*-0.151006' | sort | uniq > > > > Under normal circumstances (that is, you use only packages from the > > omnios publisher) you should see only entire, illumos-gate and > > omnios-userland. If you see anything else, that's something to > > investigate. > > ah, we are getting closer ... > > we have installed some packages from our own repository > pkg.oetiker.ch and these packages themselfe have dependencies on > ms.omniti.com stuff. > > namely the following: > > $ pkg uninstall -nv libgcrypt > Creating Planpkg uninstall: Cannot remove > > 'pkg://ms.omniti.com/omniti/security/libgcrypt@1.5.3,5.11-0.151006:20130810T181134Z' > due to the following packages that depend on it: > > pkg://pkg.oetiker.ch/system/collectd@5.4.0,5.11-0.151007:20131005T114950Z > > does this mean we have to rebuild the collectd package for 0.151008 > because its dependency on ms.omniti.com is going away ? Depending on stuff in ms.omniti.com violates http://omnios.omniti.com/wiki.php/KYSTY. For reasons you're seeing here, it really is better to package your own libgcrypt. Yes, it's duplication of effort, but it means you have fewer issues overall. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] New stable release: r151008
On Fri, Dec 06, 2013 at 11:12:44 -0500, John D Groenveld wrote: > In message <20131206154730.GM2078@eschaton.local>, Chris Nehren writes: > >You're missing omnios-userland, which is why you're having > >issues. Please install the latest version from 151006 (at time of > >writing this is > >incorporation/jeos/omnios-userland@11,5.11-0.151006:20131030T205312Z) > > Still no go. > John > groenv...@acm.org Hi John, Sorry for that. We just pushed a new omnios-userland incorporation that should fix your issues. Please install incorporation/jeos/omnios-userland@11,5.11-0.151006 (which should get you the latest version) and you should be able to continue. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Problem upgrading to r151008
On Fri, Dec 06, 2013 at 15:30:29 +, Andy wrote: > > On Fri, 6 Dec 2013, Chris Nehren wrote: > > ; On Fri, Dec 06, 2013 at 09:48:49 -0500, Chris Nehren wrote: > ; > On Fri, Dec 06, 2013 at 10:35:44 +, Andy wrote: > ; > > > ; > > Hi, > ; > > > ; > > pickle# (11) pkg list runtime/perl-64 > ; > > pkg list: no packages matching 'runtime/perl-64' installed > ; > > > ; > > pickle# (14) pkg update --be-name=r151008e > ; > > Packages to update: 96 > ; >^^ > ; > > ; > There should be far more packages than this. This means that > ; > something is being held back from being upgraded, which means... > ; > > ; > > ld.so.1: zsh: fatal: libc.so.1: version 'ILLUMOS_0.6' not found > (required > ; > > by file /usr/bin/zsh) > ; > > ld.so.1: zsh: fatal: libc.so.1: open failed: No such file or directory > ; > > ; > that you get this. I had this issue on my hetzner box as well. > ; > Something that you've installed might be holding back other > ; > packages. > ; > ; Following up on this, could we see the list of packages you have > ; installed right now, your configured publishers, and the output > ; of `pkg update -nv --be-name=r151008 entire@11-0.151008 > ; omnios-userland illumos-gate osnet-incorporation`? This'll help > ; us more usefully troubleshoot what's going on. > > Pkg can't find 'omnios-userland' but the full list of installed > packages is below. The lack of the userland incorporation might be the > problem. Would the output of 'pkg update -nv' without the userland > incorporation be useful? > > The output does include: > > No suitable version of required package > pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.151008:20131205T191259Z > found: You'll want to install incorporation/jeos/omnios-userland@11,5.11-0.151006:20131030T205312Z as I suggested to John and try again. There was an issue with omnios-userland that we're going to be fixing soon. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] New stable release: r151008
On Fri, Dec 06, 2013 at 10:18:30 -0500, John D Groenveld wrote: > In message <201312061343.rb6dhz8b018...@elvis.arl.psu.edu>, John D Groenveld > wr > ites: > >Upgraded with problem on one r151006 install, and fell over the > >incompatible libc in another. You're missing omnios-userland, which is why you're having issues. Please install the latest version from 151006 (at time of writing this is incorporation/jeos/omnios-userland@11,5.11-0.151006:20131030T205312Z) which should get you to a point that you can upgrade successfully. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Problem upgrading to r151008
On Fri, Dec 06, 2013 at 09:48:49 -0500, Chris Nehren wrote: > On Fri, Dec 06, 2013 at 10:35:44 +, Andy wrote: > > > > Hi, > > > > pickle# (11) pkg list runtime/perl-64 > > pkg list: no packages matching 'runtime/perl-64' installed > > > > pickle# (14) pkg update --be-name=r151008e > > Packages to update: 96 >^^ > > There should be far more packages than this. This means that > something is being held back from being upgraded, which means... > > > ld.so.1: zsh: fatal: libc.so.1: version 'ILLUMOS_0.6' not found (required > > by file /usr/bin/zsh) > > ld.so.1: zsh: fatal: libc.so.1: open failed: No such file or directory > > that you get this. I had this issue on my hetzner box as well. > Something that you've installed might be holding back other > packages. Following up on this, could we see the list of packages you have installed right now, your configured publishers, and the output of `pkg update -nv --be-name=r151008 entire@11-0.151008 omnios-userland illumos-gate osnet-incorporation`? This'll help us more usefully troubleshoot what's going on. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Problem upgrading to r151008
On Fri, Dec 06, 2013 at 10:35:44 +, Andy wrote: > > Hi, > > pickle# (11) pkg list runtime/perl-64 > pkg list: no packages matching 'runtime/perl-64' installed > > pickle# (14) pkg update --be-name=r151008e > Packages to update: 96 ^^ There should be far more packages than this. This means that something is being held back from being upgraded, which means... > ld.so.1: zsh: fatal: libc.so.1: version 'ILLUMOS_0.6' not found (required > by file /usr/bin/zsh) > ld.so.1: zsh: fatal: libc.so.1: open failed: No such file or directory that you get this. I had this issue on my hetzner box as well. Something that you've installed might be holding back other packages. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] New stable release: r151008
On Fri, Dec 06, 2013 at 03:26:42 +0100, Michael Rasmussen wrote:
> On Fri, 6 Dec 2013 01:59:46 +0100
> Michael Rasmussen wrote:
>
> > How does one upgrade from 15007?
> To answer myself:
> pkg set-publisher --approve-ca-cert /etc/ssl/pkg/OmniTI_CA.pem omnios
>
> But after upgrading and booting the new boot environment I get this
> error:
> [ Dec 6 01:17:25 Executing start method ("/lib/svc/method/svc-intrd").
> ] ld.so.1: perl: fatal: libc.so.1: version 'ILLUMOS_0.6' not found
> (required by
> file /usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64int/CORE/libperl.so)
> ld.so.1: perl: fatal: libc.so.1: open failed: No such file or directory
> [ Dec 6 01:17:25 Method "start" exited with status 0. ] [ Dec 6
> 01:17:25 Stopping because all processes in service exited. ] [ Dec 6
> 01:17:26 Executing stop method (:kill). ] [ Dec 6 01:17:26 Restarting
> too quickly, changing state to maintenance. ]
We don't support upgrading from bloody*. It's very much an "if it
breaks, you get to keep both pieces" system, much the way Debian
sid or FreeBSD -CURRENT are.
That said, I had that issue when I managed an incomplete upgrade
on a personal box. You'll want to reboot into the previous BE and
do a 'pkg update -nv' to see what's being upgraded. I'd guess
that something is holding back a required package but need to see
what you have installed and your publishers to be able to give
more advice.
* In fact we don't support bloody at all; there's a reason it has
the name it does.
--
Chris Nehren
Site Reliability Engineer, OmniTI
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Boot from mirrored USB?
On Thu, Oct 31, 2013 at 07:07:53 -0700, Sriram Narayanan wrote: > Some of my servers boot opendiana 151 from mirrored USB. I've tested this > on each server that we created a set for. > Very cool. Do you have docs somewhere for setting that up? -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited]
On Thu, Oct 31, 2013 at 12:37:48 +0530, Sam M wrote: > Chris, Thanks. I tried your suggestion, it's not working, output below. > Frankly, I don't understand what it means. > > # pkg install pkg@0.5.11,5.11-0.151007:20131027T234759Z > Creating Plan \ > [install fail snipped] Sam, I think this is due to some changes in the repo that happened in between the time I made my suggestion and the time you attempted to update your machine. I would suggest holding off updating until the next major stable release (r151008) comes, which should be Real Soon Now. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Boot from mirrored USB?
On Thu, Oct 31, 2013 at 11:54:50 +, Ben Summers wrote: > > Hello, > > I'm speccing out some new hardware. It seems challenging to get vendor > supported configurations which give you lots of discs on a Solarish OS, > rather than using horrid RAID cards. > > The best config I've found so far seems to be a Fujitsu RX200 with 4 internal > 15k SAS discs (the internal supported card can only do 8 drives if you use > RAID), plus a Fujitsu branded LSI controller connected to an Intel 3.5" JBOD > array for bulk storage and maybe an SSD for ZIL. > > Because I'd like to use all the internal discs for a database as a pair of > mirrors in a single JBOD, I was wondering if anyone boots from USB discs? SmartOS is designed to run from USB drives. I don't know if their configuration supports mirroring, though. -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited]
On Wed, Oct 30, 2013 at 18:16:40 +0530, Sam M wrote: > Hi Eric, > > The issue I'm having is that I had Bloody up and running and then my HD > crashed. While on bloody, I upgraded my 8 TB data zpool. Now, the same > zpool is not accessible when I'm running the release version of OmniOS. The > issue I mentioned in my original email seems minor but it's causing other > issues. > > I understand bloody is not supposed to be stable, but I can access the data > zpool in readonly mode. > > So I was hoping for a way to fix the pkg issue, or I guess I'll wait for > the updates to finish... If you install pkg@0.5.11,5.11-0.151007:20131027T234759Z (an unsigned version that supports signing), you should be able to use that as an interstitial version from which to do the rest of the upgrade. Let me know if this doesn't work for you. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Re-installing OmniOS after Crash, Errors with pkg [Subject Edited]
Are you on bloody? We're in the middle of getting signed packages ready. Hold off on updating for now. On Sun, Oct 27, 2013 at 17:46:40 +0530, Sam M wrote: > Hello all. > > After installing napp-it, OmniOS got hosed. Not sure what caused it, > probably not napp-it, because I couldn't boot up my system with any of the > boot images, including the original. > > Now, on a brand new installation, I'm getting the following error - > > *# pkg update web/ca-bundle pkg* > *Creating Plan -* > *pkg update: The certificate which issued this > certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release > Signing Certificate/emailAddress=omnios-supp...@omniti.com could not be > found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI > Certificate Authority* > *The package involved is:pkg://omnios/library/python-2/pybonjour@1.1.1 > ,5.11-0.151007:20130516T114553Z* > * > * > *# uname -a* > *SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris* > > There were no errors earlier after the installation when updating packages. > > How can I fix this? Where can I find OmniTI's CA certificate? > > TIA. > > Sam > ___ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] pkgsrc-2013Q3 binary packages for illumos now available
On Wed, Oct 23, 2013 at 09:55:30 +0100, Jonathan Perkin wrote: > - In pkgsrc we do not split packages into separate runtime and > developer components, which I believe IPS does. IPS doesn't do this either, at least not with the packages I've worked with. I know the Joyent folks don't like IPS, but please don't compare us to Linux that way. ;) -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] gcc : include path settings?
On Sat, Oct 12, 2013 at 13:36:08 -0400, Mayuresh Kathe wrote:
> hello, new here, just started off today.
> i've installed gcc47 from the pkg repository.
> how do i set the include path for gcc47?
> simple programs like the one below fail to compile.
>
> -- helloworld.c --
> #include
> int main(void) {
> printf("Hello, World!\n");
> return 0;
> }
> -- helloworld.c --
Please show the commandline you're using to build this
application, and all output until the next shell prompt.
> overall, the omnios environment feels good, just
> a bit strange for someone migrating from bsd. :)
It's a bit strange at first but, coming from BSD, I think you'll
grow to appreciate the minimalism and lack of nonsense that you
find in the Linux world.
--
Chris Nehren
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] file system organisation for pkg packages
On Thu, Sep 26, 2013 at 16:55:04 +0200, Tobias Oetiker wrote: > from a system management point of view I like to have a simple rule > to decide where the config is and where the 'data' is ... > > so keeping the application in /opt/vendor is perfect for the static > part of the application ... > > but having the configuration and the data in the same tree makes it > harder to know what is part of the distribution and what is part of > the application ... You could ship default configs and similar files with a .dist suffix, as some open source systems tend to do. Not sure if that would fully address your concern, but it's something to think about. -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] gettext 0.18.3.1 on OmniOS: libgomp.so.1 not found
On Sun, Sep 22, 2013 at 07:21:19 +0900, Ryo ONODERA wrote:
> Hi,
>
> I build gettext-0.18.3.1 from tarball.
> Build finished without error, but msgfmt command cannot start with
> following message.
> I have libgomp.so.1 in /opt/gcc-4.7.2 and /opt/gcc-4.7.2/amd64.
>
> How to fix this failure?
> (You can ignore libgettextsrc-0.18.3.so and libgettextlib-0.18.3.so part
> in this case, it is treated in wrapper shell script, src/msgfmt).
>
> $ cd gettext-0.18.3.1
> $ PATH=/opt/gcc-4.7.2/bin:${PATH} ./configure
> $ PATH=/opt/gcc-4.7.2/bin:${PATH} gmake
> $ ./gettext-tools/src/msgfmt
> ld.so.1: msgfmt: fatal: libgomp.so.1: open failed: No such file or directory
> $ ldd ./gettext-tools/src/.libs/msgfmt
> libgettextsrc-0.18.3.so => (file not found)
> libgettextlib-0.18.3.so => (file not found)
> libsec.so.1 => /lib/libsec.so.1
> libxml2.so.2 => /usr/lib/libxml2.so.2
> libcurses.so.1 =>/lib/libcurses.so.1
> libc.so.1 => /lib/libc.so.1
> libgomp.so.1 => (file not found)
> libpthread.so.1 => /lib/libpthread.so.1
> libavl.so.1 => /lib/libavl.so.1
> libidmap.so.1 => /usr/lib/libidmap.so.1
> libz.so => /usr/lib/libz.so
> liblzma.so.5 => /usr/lib/liblzma.so.5
> libm.so.2 => /lib/libm.so.2
> libsocket.so.1 =>/lib/libsocket.so.1
> libnsl.so.1 => /lib/libnsl.so.1
> libnvpair.so.1 =>/lib/libnvpair.so.1
> libuutil.so.1 => /lib/libuutil.so.1
> libmp.so.2 =>/lib/libmp.so.2
> libmd.so.1 =>/lib/libmd.so.1
Sounds like you need to use either -R or -Wl,-rpath on the gcc
command line to tell the linker where to find libgomp.so.1. This
should go in your $LDFLAGS.
--
Chris Nehren
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] OS architecture confusion.
On Sun, Sep 15, 2013 at 01:06:06 +0500, Muhammad Yousuf Khan wrote: > when i run isainfo it says 64bit. however when i run uname -a > SunOS omni 5.11 omnios-b281e50 i86pc i386 i86pc > > as both showing different outputs. which one should i consider correct > information. In comparison to other operating systems, i386 here refers to the architecture (as opposed to SPARC) and not 32/64bit. You can take a look in the source code using cscope or opengrok to see how this works. It's pretty educational IMO to dig down into the kernel and see how this stuff is implemented. -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] possible to read HFS+ from usb drives?
On Fri, Sep 13, 2013 at 22:41:40 +0200, Felix Nielsen wrote: > Hi > > Does anyone know if it's possible to read HFS+ filesystem from USB drives? You might be able to get something through FUSE (though doubtful) but otherwise your options are limited to ISO 9660 (called hsfs on illumos) and FAT (called pcfs on illumos). -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] how can i use handy utilities like top, htop, nano, etc in omniOS.
On Fri, Sep 06, 2013 at 16:47:20 +0500, Muhammad Yousuf Khan wrote: > i hope you guys are not getting bothered with my linux to unix comparative > questions. because the time when i migrated from MS windows to Linux i had > same comparative question. > > As working in linux i am very use to and kinda dependent on some small > utilities like > nano > htop > dstat > and count less other utilities. > is there any way to run those softwares in OmniOS. nano is available in the omniti-ms repository. htop, if it's anything like top, is horrible for CPU usage: http://www.brendangregg.com/DTrace/prstatvstop.html As for dstat, illumos follows the Unix philosophy of small tools that do one thing well at least in this regard. We have separate stat utilities for different aspects of system performance, and we have DTrace, which can do far more than dstat ever will. You may find the Unix rosetta stone useful: http://bhami.com/rosetta.html -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] lftp
On Sun, Sep 01, 2013 at 20:24:34 +0200, gi...@swipnet.se wrote: > Hi > > I've gone from openindiana to omnios and it works really well. > I do, however, miss lftp. When i try to compile it i get the following > when i run ./configure: > > checking term.h presence... yes > configure: WARNING: term.h: present but cannot be compiled > configure: WARNING: term.h: check for missing prerequisite headers? > configure: WARNING: term.h: see the Autoconf documentation > configure: WARNING: term.h: section "Present But Cannot Be Compiled" > configure: WARNING: term.h: proceeding with the compiler's result > configure: WARNING: ## ## > configure: WARNING: ## Report this to lftp-b...@lftp.yar.ru ## > configure: WARNING: ## ## > checking for term.h... no That's the least of your problems, actually. ISTR trying to build lftp and running into gnarly C++ issues. For that error you'll probably need to be careful about the 32/64-bitness of headers and whether you're using /usr/include/term.h or /usr/include/ncurses/term.h (you want the latter, most likely). ncurses is a little weird as-packaged. -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] SabNZBD - unrar
On Tue, Aug 27, 2013 at 09:53:08 +0200, Christian Flaig wrote: > Hello all, > > I'm trying to set up SabNZBD in a zone, has anyone done this and created > some instructions? I'm already struggling with the first step, getting > unrar. Where can I find unrar in OmniOS? > > Thanks alot for your help. http://omnios.omniti.com/wiki.php/Packaging lists third-party, unsupported-by-OmniTI repos. Jorge Schrauwen's repo at http://omnios.blackdot.be/ has sabnzbd, unrar, and probably everything else required. Give that a shot and see how things go? -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] multithreaded gzip (or equivalent) and moving some files while preserving file trees
On Sun, Aug 18, 2013 at 00:01:30 +0100, Valrhona wrote: > This is somewhat tedious and takes a while, but fortunately it's just > a few commands and I can let it run in the background. But I don't see > any better backup solution, because ZFS internally checksums, and I do > a manual backup and restore, and checksum before and after. I think > this is more intense in terms of verification than most of the other > solutions I know. > > It is also a bit more future-proof, since it relies only on ZFS, tar, > and md5sum, all of which are on live-CDs and standard illumos (without > any libraries). So with a tape, tape drive, enough space on a hard > disk subsystem, I can restore my filesystems without any additional > software (don't even need network connectivity), and have end-to-end > checksummng. > > But maybe there are things I could be doing better? You might want to take a look at zetaback (https://labs.omniti.com/labs/zetaback) which we've been using for a while for backups. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Omnios, VMware fusion
On Sun, Aug 18, 2013 at 12:54:21 +0200, Jan Holtzhausen wrote: > Omni needs a virtual floppy drive to install. > In OSX, open a terminal to a directory that fusion can browse to (~/Desktop > is fine) > ~> dd bs=512 count=2880 if=/dev/zero of=floppy.img > There's your blank image. > Now add a floppy device in fusion, point it to floppy.img. > Go ahead and install on fusion. This is a known issue. See http://omnios.omniti.com/wiki.php/VMwareNotes for our documentation of it. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Switching syslog with rsyslog
On Mon, Jul 15, 2013 at 19:47:26 -0700 , Carlos Cardenas wrote: > Has anyone switched syslog with rsyslog? Yes, in at least one of our environments. > In particular, I would like to use rsyslog 7.4.0, esp log signing with > Guardtime: > http://blog.gerhards.net/2013/05/rsyslogs-first-signature-provider-why.html > . I don't think we've tried this configuration, though. > If not, is there anything more substantial than > http://omnios.omniti.com/wiki.php/PackagingForOmniOS for creating new pkgs? It sounds like you're wanting to package rsyslog. That's unnecessary: we already have a package in the ms.omniti.com repository, documented at e.g. http://omnios.omniti.com/wiki.php/GeneralAdministration#ConfigurePublishers and http://omnios.omniti.com/wiki.php/Packaging . -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Build environment
On Mon, Jul 15, 2013 at 19:14:30 -0700 , Carlos Cardenas wrote: > I'm trying to get my toughbook's wifi to work (I think the iwp doesn't have > the PCI ids for the 6205) which I'm hoping is an easy fix. > > I have all pkgs installed, omnios-build cloned (I'm running the latest > stable release: b281e50) and when I attempt to run `buildcntl list` it > errors out saying I need to install gcc48, which is not in stable's repo. Do > I need to be on bloody using bloody repos? No, you do not need to be on bloody to build things from omnios-build. You should check out the branch for the release you're on (cat /etc/release) and build there. That way you're building the bits that you're running. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Building illumos-omnios
On Fri, Jun 14, 2013 at 16:02:23 -0700 , Paul B. Henson wrote: > I'm trying to get set up to do some forward development on illumos-gate > (using Theo's method of working with illumos-omnios). > > I checked out the stable branch of omnios-build (as the master branch > doesn't work with stable, and as this isn't omnios distribution > development, I'd prefer to do it under stable). I then checked out by > hand the master branch of illumos-omnios (rather than letting > omnios-build automatically check out the corresponding stable branch), > and did a test build. > > [snip] > > Is this a known issue? Did I do something wrong? Is this from the cross > pollination of stable omnios-build and master illumos-omnios? Quite probably. You'll want to match the version you're running with the version you're building. Check the branches in the repo you checked out--you should see e.g. r151004, r151006. Check out the one you're running on and try building again. -- Chris Nehren ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Lftp package
On Wed, Feb 13, 2013 at 10:52:49 -0500 , Chris Nehren wrote: > On Wed, Feb 13, 2013 at 10:31:57 +0530 , Ram Chander wrote: > > Hi, > > > > Currently there is no lftp package in the omnis repository. . Can we please > > add this ? > > Csw version of lftp doesnt work and hangs. > > From my FreeBSD machine: > > $ pkg info -d lftp > lftp-4.4.1 depends on: > expat-2.0.1_2 > gettext-0.18.1.1 > libiconv-1.14 > > $ > > All of these packages exist either in core OmniOS or in the omniti-ms > publisher (which OmniTI maintains). This suggests that the dependencies > are in place for lftp. A pain point, however, may be that lftp is > written in C++. You should be able to install the dependencies listed > above and at least give it a try using the instructions found here: > http://omnios.omniti.com/wiki.php/PackagingForOmniOS. Please feel free > to ask questions about that document so that we can improve it. Following on from this, I tried building it on my VPS before work this morning and got pretty far. This is the only error I encountered: /bin/sh ../libtool --silent --tag=CXX--mode=compile gcc -DHAVE_CONFIG_H -I. -I../lib -I../lib -I../trio -O2 -Wall -Wwrite-strings -Woverloaded-virtual -fno-exceptions -fno-rtti -fno-implement-inlines -MT buffer.lo -MD -MP -MF .deps/buffer.Tpo -c -o buffer.lo buffer.cc buffer.cc: In member function ‘virtual void DataRecoder::PutTranslated(Buffer*, const char*, int)’: buffer.cc:277:83: error: invalid conversion from ‘const char**’ to ‘char**’ [-fpermissive] /usr/include/iconv.h:44:15: error: initializing argument 2 of ‘size_t iconv(iconv_t, char**, size_t*, char**, size_t*)’ [-fpermissive] As the output suggests, using -fpermissive fixes the build. Once it's built, it seems to actually work, too, suggesting there aren't any ABI issues. I haven't had time to create a proper code patch, but at first glance it appears to be a simple fix. I'll try to have a package available tonight. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Lftp package
On Wed, Feb 13, 2013 at 10:31:57 +0530 , Ram Chander wrote: > Hi, > > Currently there is no lftp package in the omnis repository. . Can we please > add this ? > Csw version of lftp doesnt work and hangs. >From my FreeBSD machine: $ pkg info -d lftp lftp-4.4.1 depends on: expat-2.0.1_2 gettext-0.18.1.1 libiconv-1.14 $ All of these packages exist either in core OmniOS or in the omniti-ms publisher (which OmniTI maintains). This suggests that the dependencies are in place for lftp. A pain point, however, may be that lftp is written in C++. You should be able to install the dependencies listed above and at least give it a try using the instructions found here: http://omnios.omniti.com/wiki.php/PackagingForOmniOS. Please feel free to ask questions about that document so that we can improve it. -- Chris Nehren Site Reliability Engineer, OmniTI ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
