Re: [OmniOS-discuss] iscsi timeouts
On 2/3/14, 10:51 AM, Tobias Oetiker wrote: a short update on the matter for anyone browsing the ML archives: The affected system runs on an S2600CP motherboard with RMM4 remote management. RMM comes with the ability to use any of the existing Ethernet ports on the MB for its communication needs ... we have configured it with a separate hw port, but it seems that this ability the access the other ports can interfere with omnios operation. 10 days ago, we have upgraded the bios to version SE5C600.86B.02.01.0002.082220131453 08/22/2013 since then we have not seen any issues ... I am not 100% sure that this is the solution to the problem, as we only found the behaviour after several weeks of uptime ... in any event, for now things look good. Interesting observation, thanks for keeping the list updated! Best wishes, -- Saso ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
Hello, running 'pkg update' I get the following result: pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151008:20131204T022427Z pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.151008:20131206T160517Z pkg://omnios/entire@11,5.11-0.151008:20131205T195242Z pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151008:20131204T024149Z Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. Is this simply a matter of waiting until something in the repository is fixed or am I supposed to do anything? Thanks a lot, Kai ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 7:19 AM, Kai Meder k...@meder.info wrote: Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. Is this simply a matter of waiting until something in the repository is fixed or am I supposed to do anything? What version of OmniOS are you currently on (see /etc/release)? Are you using packages from any publishers other than omnios? Others that have run into this were using packages from ms.omniti.com that require r151006. The errors from pkg(1) are, it's safe to say, less than helpful here. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] industrial usb flash
Hi to all People are talking about industrial grade usb flash storage to use as boot device for Omni and napp-it . Exactly witch brand build this kind of device ? I just can not find anything like that on amazon Fábio Rabelo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
On 2/3/14, 3:06 PM, Matthew Mabis wrote: Hello, I have a few questions about a project that i am trying to work on, needless to say i have 1 80GB SSD Drive that i can fit in this case, the rest of the drives are a RaidZ2 configuration and there cannot be anymore added Disks to this system period! My goal is to make the SSD capable of making NFS run better (Slog/ZIL/L2ARC) whatever... but i need the OS to go somewhere! My Questions are 1) Splitting the SSD into partitions and running is that bad i always heard it was my question is why? 2) Can Omni be run from say a 32GB USB3 key directly? 3) What options do i have here outside of adding a drive. I have SATA Slots on the mobo just no place to add an additional drive! Yes, you can partition the SSD and it works okay. For the OS, set aside something like 10GB and turn on compression. Although the standard installer doesn't let you set compression on the root pool before starting installation, there's a trick to doing it. Before firing up the installation, get a shell from the installer menu and run the following commands: # screen # while ! zpool set compress=lz4 rpool; do sleep 1; done (after this hit 'Ctrl-A' + 'D' and type 'exit' to return to the installer menu and leave the loop running) The loop will try to set compression on the newly created root pool as soon as the installer creates it, so that the OS's data itself will be installed compressed. For slog (aka ZIL) you don't need much - usually around 1-2GB is more than enough, since it only needs to hold the sync write data from the last transaction (by default: the last 5 seconds). Use the rest of the SSD for L2ARC. Depending on the SSD type you may also want to keep around 10-20% of the SSD unallocated, so that the garbage collector on the controller always has blocks available it can pre-erase - this can boost long-term slog performance quite a bit. YMMV Cheers, -- Saso ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
On 2/3/2014 10:12 AM, Dan Swartzendruber wrote: Hello, I have a few questions about a project that i am trying to work on, needless to say i have 1 80GB SSD Drive that i can fit in this case, the rest of the drives are a RaidZ2 configuration and there cannot be anymore added Disks to this system period! My goal is to make the SSD capable of making NFS run better (Slog/ZIL/L2ARC) whatever... but i need the OS to go somewhere! My Questions are 1) Splitting the SSD into partitions and running is that bad i always heard it was my question is why? 2) Can Omni be run from say a 32GB USB3 key directly? 3) What options do i have here outside of adding a drive. I have SATA Slots on the mobo just no place to add an additional drive! Yes, we do this all the time. The OS image doesn't take that much space. Just carve off 8GB partition on your SSD for the ZIL, and you are set. It vastly improves NFS synchronous operations such as deletes, metadata changes, and small file writes. What kind of SSD is it? I wouldn't recommend on an X-25M because there's no cap to write it out on power failure, but the Intel-320 line is a very good choice in general. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
Kai Meder schrieb: Eric Sproul schrieb: On Mon, Feb 3, 2014 at 7:19 AM, Kai Mederk...@meder.info wrote: Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. Is this simply a matter of waiting until something in the repository is fixed or am I supposed to do anything? What version of OmniOS are you currently on (see /etc/release)? Are you using packages from any publishers other than omnios? Others that have run into this were using packages from ms.omniti.com that require r151006. The errors from pkg(1) are, it's safe to say, less than helpful here. I am on OmniOS v11 r151006. I am indeed using php and lighttpd from ms.omniti.com, how would I resolve this error? I have installed those packages: pkg list | grep ms.omniti.com omniti/database/mysql-55 (ms.omniti.com) 5.5.31-0.151004 i-- omniti/database/mysql-55/library (ms.omniti.com) 5.5.31-0.151004 i-- omniti/editor/nano (ms.omniti.com)2.2.6-0.151002 i-- omniti/library/freetype2 (ms.omniti.com) 2.4.10-0.151002 i-- omniti/library/gd (ms.omniti.com) 2.0.35-0.151002 i-- omniti/library/libjpeg (ms.omniti.com)8.4-0.151002 i-- omniti/library/libmcrypt (ms.omniti.com) 2.5.7-0.151002 i-- omniti/library/libpng (ms.omniti.com) 1.5.12-0.151002 i-- omniti/library/libpq5 (ms.omniti.com) 9.2.0-0.151002 i-- omniti/library/libssh2 (ms.omniti.com)1.4.2-0.151002 i-- omniti/library/mhash (ms.omniti.com) 0.9.9.9-0.151002 i-- omniti/runtime/php-54 (ms.omniti.com) 5.4.19-0.151006 i-- omniti/server/lighttpd (ms.omniti.com)1.4.32-0.151004 i-- omniti/system/storage/smartmontools (ms.omniti.com) 6.0-0.151004 i-- How do I find out which one breaks the update? Thanks! ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
Its an Intel 320 80GB Drive I ensured to buy SSDs for my lab that have the power Caps didnt want to make that mistake! Matt - Original Message - From: Doug Hughes d...@will.to To: omnios-discuss@lists.omniti.com Sent: Monday, February 3, 2014 7:34:29 AM Subject: Re: [OmniOS-discuss] Where to Run Omni On 2/3/2014 10:12 AM, Dan Swartzendruber wrote: Hello, I have a few questions about a project that i am trying to work on, needless to say i have 1 80GB SSD Drive that i can fit in this case, the rest of the drives are a RaidZ2 configuration and there cannot be anymore added Disks to this system period! My goal is to make the SSD capable of making NFS run better (Slog/ZIL/L2ARC) whatever... but i need the OS to go somewhere! My Questions are 1) Splitting the SSD into partitions and running is that bad i always heard it was my question is why? 2) Can Omni be run from say a 32GB USB3 key directly? 3) What options do i have here outside of adding a drive. I have SATA Slots on the mobo just no place to add an additional drive! Yes, we do this all the time. The OS image doesn't take that much space. Just carve off 8GB partition on your SSD for the ZIL, and you are set. It vastly improves NFS synchronous operations such as deletes, metadata changes, and small file writes. What kind of SSD is it? I wouldn't recommend on an X-25M because there's no cap to write it out on power failure, but the Intel-320 line is a very good choice in general. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com https://urldefense.proofpoint.com/v1/url?u=http://lists.omniti.com/mailman/listinfo/omnios-discussk=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0Ar=yqgQ6LhGnfWMd79QvLrmWsnr%2FlpWj5c0oy4MpT8%2Bgik%3D%0Am=jbXB0E2AdHLBwrLyWlAxJtx7ZA5Rg7gTJaePeKew70Y%3D%0As=b5c7784a65fcfa3c44e8f9f89d910678eda6fe717feb159eba020e2d1bab7582 ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
This is perfect, I was reading on Hardforum from a user named GEA saying that its unsupported and not recommended about a year ago so i figured why not bring the question to the forum and get the answer to Why! This information will get things rolling! Thanks! Matt Mabis - Original Message - From: Saso Kiselkov skiselkov...@gmail.com To: omnios-discuss@lists.omniti.com Sent: Monday, February 3, 2014 7:23:05 AM Subject: Re: [OmniOS-discuss] Where to Run Omni On 2/3/14, 3:06 PM, Matthew Mabis wrote: Hello, I have a few questions about a project that i am trying to work on, needless to say i have 1 80GB SSD Drive that i can fit in this case, the rest of the drives are a RaidZ2 configuration and there cannot be anymore added Disks to this system period! My goal is to make the SSD capable of making NFS run better (Slog/ZIL/L2ARC) whatever... but i need the OS to go somewhere! My Questions are 1) Splitting the SSD into partitions and running is that bad i always heard it was my question is why? 2) Can Omni be run from say a 32GB USB3 key directly? 3) What options do i have here outside of adding a drive. I have SATA Slots on the mobo just no place to add an additional drive! Yes, you can partition the SSD and it works okay. For the OS, set aside something like 10GB and turn on compression. Although the standard installer doesn't let you set compression on the root pool before starting installation, there's a trick to doing it. Before firing up the installation, get a shell from the installer menu and run the following commands: # screen # while ! zpool set compress=lz4 rpool; do sleep 1; done (after this hit 'Ctrl-A' + 'D' and type 'exit' to return to the installer menu and leave the loop running) The loop will try to set compression on the newly created root pool as soon as the installer creates it, so that the OS's data itself will be installed compressed. For slog (aka ZIL) you don't need much - usually around 1-2GB is more than enough, since it only needs to hold the sync write data from the last transaction (by default: the last 5 seconds). Use the rest of the SSD for L2ARC. Depending on the SSD type you may also want to keep around 10-20% of the SSD unallocated, so that the garbage collector on the controller always has blocks available it can pre-erase - this can boost long-term slog performance quite a bit. YMMV Cheers, -- Saso ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com https://urldefense.proofpoint.com/v1/url?u=http://lists.omniti.com/mailman/listinfo/omnios-discussk=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0Ar=yqgQ6LhGnfWMd79QvLrmWsnr%2FlpWj5c0oy4MpT8%2Bgik%3D%0Am=SIl8BuMbKpDSpCGhnR41LKGpg8kFruHNVH1eJ2FH%2BGE%3D%0As=c03620d2a0c94f3a2b271e1c23f59d4e9b986a1c1dadcc8744a1ca51a20fc7af ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
This is perfect, I was reading on Hardforum from a user named GEA saying that its unsupported and not recommended about a year ago so i figured why not bring the question to the forum and get the answer to Why! I seem to recall there being sound reasons not to share the same device between SLOG and L2ARC (or anything else, for that matter...) ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 10:45 AM, Kai Meder k...@meder.info wrote: I have installed those packages: pkg list | grep ms.omniti.com omniti/database/mysql-55 (ms.omniti.com) 5.5.31-0.151004 i-- omniti/database/mysql-55/library (ms.omniti.com) 5.5.31-0.151004 i-- omniti/editor/nano (ms.omniti.com)2.2.6-0.151002 i-- omniti/library/freetype2 (ms.omniti.com) 2.4.10-0.151002 i-- omniti/library/gd (ms.omniti.com) 2.0.35-0.151002 i-- omniti/library/libjpeg (ms.omniti.com)8.4-0.151002 i-- omniti/library/libmcrypt (ms.omniti.com) 2.5.7-0.151002 i-- omniti/library/libpng (ms.omniti.com) 1.5.12-0.151002 i-- omniti/library/libpq5 (ms.omniti.com) 9.2.0-0.151002 i-- omniti/library/libssh2 (ms.omniti.com)1.4.2-0.151002 i-- omniti/library/mhash (ms.omniti.com) 0.9.9.9-0.151002 i-- omniti/runtime/php-54 (ms.omniti.com) 5.4.19-0.151006 i-- omniti/server/lighttpd (ms.omniti.com)1.4.32-0.151004 i-- omniti/system/storage/smartmontools (ms.omniti.com) 6.0-0.151004i-- How do I find out which one breaks the update? I'm going to surmise that it is php-54. More recent builds in ms.omniti.com began incorporating on the 'entire' package of the version they were built on, because we could not know whether they would work properly on future versions of the OS. You can try this to confirm my suspicion: pkg search -H -l -o pkg.name 'depend:incorporate:entire' That generates a list of pkg.name values (from pkg metadata) of locally installed (-l) packages that have a dependency of type incorporate on entire. The -H eliminates the header line in output. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
On 2/3/2014 10:53 AM, Matthew Mabis wrote: This is perfect, I was reading on Hardforum from a user named GEA saying that its unsupported and not recommended about a year ago so i figured why not bring the question to the forum and get the answer to Why! This information will get things rolling! Thanks! Matt Mabis On a normal spinning disk this has the potential to be questionable because the head has to seek to get to the zil, and then back again, especially if you have swap enabled and in use. The OS, though, really doesn't do much disk activity after being loaded (unless you have a lot of logging going on), and SSD has no seek penalty, per se. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Fwd: omnios-b281e50: No solution was found to satisfy constraints
Forgot to reply-all -- Forwarded message -- From: Eric Sproul espr...@omniti.com Date: Mon, Feb 3, 2014 at 11:28 AM Subject: Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints To: Ben Summers b...@fluffy.co.uk On Mon, Feb 3, 2014 at 11:20 AM, Ben Summers b...@fluffy.co.uk wrote: On 3 Feb 2014, at 16:16, Eric Sproul espr...@omniti.com wrote: I'm going to surmise that it is php-54. More recent builds in ms.omniti.com began incorporating on the 'entire' package of the version they were built on, because we could not know whether they would work properly on future versions of the OS. The expectation of someone from the Solaris world is that if it works now, it'll work on any future version of the OS. Should OmniOS users expect this to be the case, or should we recompile for new versions of the OS? That's only for libc ABI. Those promises do not extend to userland libraries, which is where we would most likely expect breakage for high-level apps. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
Eric Sproul schrieb: On Mon, Feb 3, 2014 at 10:45 AM, Kai Mederk...@meder.info wrote: I have installed those packages: pkg list | grep ms.omniti.com omniti/database/mysql-55 (ms.omniti.com) 5.5.31-0.151004 i-- omniti/database/mysql-55/library (ms.omniti.com) 5.5.31-0.151004 i-- omniti/editor/nano (ms.omniti.com)2.2.6-0.151002 i-- omniti/library/freetype2 (ms.omniti.com) 2.4.10-0.151002 i-- omniti/library/gd (ms.omniti.com) 2.0.35-0.151002 i-- omniti/library/libjpeg (ms.omniti.com)8.4-0.151002 i-- omniti/library/libmcrypt (ms.omniti.com) 2.5.7-0.151002 i-- omniti/library/libpng (ms.omniti.com) 1.5.12-0.151002 i-- omniti/library/libpq5 (ms.omniti.com) 9.2.0-0.151002 i-- omniti/library/libssh2 (ms.omniti.com)1.4.2-0.151002 i-- omniti/library/mhash (ms.omniti.com) 0.9.9.9-0.151002 i-- omniti/runtime/php-54 (ms.omniti.com) 5.4.19-0.151006 i-- omniti/server/lighttpd (ms.omniti.com)1.4.32-0.151004 i-- omniti/system/storage/smartmontools (ms.omniti.com) 6.0-0.151004i-- How do I find out which one breaks the update? I'm going to surmise that it is php-54. More recent builds in ms.omniti.com began incorporating on the 'entire' package of the version they were built on, because we could not know whether they would work properly on future versions of the OS. You can try this to confirm my suspicion: pkg search -H -l -o pkg.name 'depend:incorporate:entire' That generates a list of pkg.name values (from pkg metadata) of locally installed (-l) packages that have a dependency of type incorporate on entire. The -H eliminates the header line in output. pkg search -H -l -o pkg.name 'depend:incorporate:entire' omniti/runtime/php-54 OK, you hit it. What am I supposed to do now? I did not really understand the 'entire'-incorporation... Thank you ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] industrial usb flash
The SanDisk Extreme USB3.0 32GB is said to be good. http://www.sandisk.com/products/usb/drives/extreme/ But this is still far from industrial grade if you're talking about SLC heavy-write-endurance drives... Would be interested too for my next Avoton/Rangeley build using OmniOS. Anyone any advice? Fábio Rabelo schrieb: Hi to all People are talking about industrial grade usb flash storage to use as boot device for Omni and napp-it . Exactly witch brand build this kind of device ? I just can not find anything like that on amazon Fábio Rabelo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 1:57 PM, Kai Meder k...@meder.info wrote: pkg search -H -l -o pkg.name 'depend:incorporate:entire' omniti/runtime/php-54 OK, you hit it. What am I supposed to do now? I did not really understand the 'entire'-incorporation... The php-54 package declares that it requires entire@11-0.151006 and only that version. 'entire' is a package that controls (directly or indirectly) the versions of all the packages available in the omnios publisher, so php-54 uses that as a way to say I will only run on r151006. You can remove that package and upgrade, or you can stay on r151006 if you want to keep using the php-54 package. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 3:19 PM, Kai Meder k...@meder.info wrote: Eric Sproul schrieb: You can remove that package and upgrade, or you can stay on r151006 if you want to keep using the php-54 package. OK, but since there is no php-55, I can't currently use PHP if I want to stay upgradeable, do I? My server-WebInterface is based on PHP5, so I need any PHP5-version... There certainly is PHP 5.5 available as source. ;) You cannot use the ms.omniti.com php-54 package on anything except r151006. You can always roll your own. On the other hand, note that r151006 is a long-term support release with security updates through 2016, so unless you have some non-negotiable reason to go to r151008, perhaps you could stay on 006. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 3:32 PM, Kai Meder k...@meder.info wrote: Do you actually plan to change php-54's 'entire' incorporation? I am willing to stay on LTS for the time being but not for the next 3 years ;) Thank you very much for these explanations The ms.omniti.com package set is what OmniTI uses internally for hosting and other production purposes. We prefer the stability of LTS for that, so I can't say if/when there will be builds for r151008. If you really need both php 5.4 *and* always the latest-and-greatest OS every 6 months, then you should invest in rolling your own packages, as you have needs that aren't being met by the available community packages. Eric ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 4:13 PM, Kai Meder k...@meder.info wrote: OK, this is perfectly acceptable. How do I tell my OmniOS to update anything possible but stop whining about php's and possible future 'entire'-dependencies? You cannot do that. A package (php-54) has declared that it must have r151006. The only way to upgrade would be to remove that package, and accept that it will not be installable on the upgraded system. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] [discuss] overriding serial port IRQ
From: Albert Lee [mailto:tr...@nexenta.com] Sent: Sunday, February 02, 2014 2:27 PM Are you sure it's still ttyc/COM3? asy should pick up the device name from the I/O address, which is why I used 0x3e8. Pretty sure. Linux works okay on ttyS2 (COM3) with the irq overridden to 10. I also see the first bit of booting under omnios with the console set to ttyc, and I also see rebooting on the serial console when I reboot. The behavior is very similar to a problem I had with openbsd and the SOL console when it was using the wrong irq, it would print out like 16 characters or so until the buffer was full and then hang waiting for an interrupt that never came. Also, echo ::interrupts | mdb -k should show the current assignments. Arg, looks like it didn't get the override after all: CPU/Vect IRQ IPL BusTrg Type Share APIC/INT# ISR 10/0x20 3 5 ISAEdg Fixed 1 0x0/0x3 asyintr 11/0x20 4 5 ISAEdg Fixed 2 0x0/0x4 asyintr 11/0x20 4 5 ISAEdg Fixed 2 0x0/0x4 asyintr I've seen some other examples for asy.conf that look more like: name=asy class=sysbus interrupts=12,10 reg=0x3e8,0,0 ioaddr=0x3e8; As opposed to the one I have now: name=asy parent=isa reg=1,0x3e8,8 interrupts=10; I'm not sure if that was for an older version of Solaris though… ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
Eric Sproul schrieb: On Mon, Feb 3, 2014 at 3:19 PM, Kai Mederk...@meder.info wrote: Eric Sproul schrieb: You can remove that package and upgrade, or you can stay on r151006 if you want to keep using the php-54 package. OK, but since there is no php-55, I can't currently use PHP if I want to stay upgradeable, do I? My server-WebInterface is based on PHP5, so I need any PHP5-version... There certainly is PHP 5.5 available as source. ;) You cannot use the ms.omniti.com php-54 package on anything except r151006. You can always roll your own. On the other hand, note that r151006 is a long-term support release with security updates through 2016, so unless you have some non-negotiable reason to go to r151008, perhaps you could stay on 006. Do you actually plan to change php-54's 'entire' incorporation? I am willing to stay on LTS for the time being but not for the next 3 years ;) Thank you very much for these explanations ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
Eric Sproul schrieb: On Mon, Feb 3, 2014 at 1:57 PM, Kai Mederk...@meder.info wrote: pkg search -H -l -o pkg.name 'depend:incorporate:entire' omniti/runtime/php-54 OK, you hit it. What am I supposed to do now? I did not really understand the 'entire'-incorporation... The php-54 package declares that it requires entire@11-0.151006 and only that version. 'entire' is a package that controls (directly or indirectly) the versions of all the packages available in the omnios publisher, so php-54 uses that as a way to say I will only run on r151006. You can remove that package and upgrade, or you can stay on r151006 if you want to keep using the php-54 package. OK, but since there is no php-55, I can't currently use PHP if I want to stay upgradeable, do I? My server-WebInterface is based on PHP5, so I need any PHP5-version... Thanks, Kai ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios-b281e50: No solution was found to satisfy constraints
On Mon, Feb 3, 2014 at 4:24 PM, Olaf Marzocchi li...@marzocchi.net wrote: Il giorno 03/feb/2014, alle ore 22:16, Eric Sproul espr...@omniti.com ha scritto: On Mon, Feb 3, 2014 at 4:13 PM, Kai Meder k...@meder.info wrote: OK, this is perfectly acceptable. How do I tell my OmniOS to update anything possible but stop whining about php's and possible future 'entire'-dependencies? You cannot do that. A package (php-54) has declared that it must have r151006. The only way to upgrade would be to remove that package, and accept that it will not be installable on the upgraded system. Kai, I had the same problem with perl provided by ms.omniti and the suggestion was to take it out and compile my own perl. It seemed a burden, it took only 10 minutes. Now I also enjoy some advantages I didn't think about. I think php is about as complex as perl :) It's even easier because there's an existing build you can look at: https://github.com/omniti-labs/omnios-build/tree/omniti-ms/build/php-54 There is a single patch to fix a zlib issue, but otherwise it just works. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
On 2/3/14, 9:30 PM, Paul B. Henson wrote: From: Saso Kiselkov Sent: Monday, February 03, 2014 7:23 AM something like 10GB and turn on compression. Although the standard installer doesn't let you set compression on the root pool before starting installation, there's a trick to doing it. Before firing up the With a little more effort: http://omnios.omniti.com/wiki.php/ISOrpoolCustomize You can configure the size of the rpool partition, provide arbitrary pool creation options including compression, and also size swap/dump explicitly rather than use the installer defaults. Oh wow, configure network, download script, make executable, execute, bootstrap pre-install environment, edit perl script, then cross fingers that it works as expected (be sure to read the log!). I mean I understand that this is more flexible than just running stuff in a screen, but if you were willing to go to such lengths to create this script, what's the problem with fixing the installer to simply prompt for some of these options in the first place? You know, things like swap/dump size, fs options, etc - little things. Doesn't have to be a full installer rewrite. Cheers, -- Saso ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Where to Run Omni
From: Saso Kiselkov Sent: Monday, February 03, 2014 2:26 PM Oh wow, configure network, download script, make executable, execute, bootstrap pre-install environment, edit perl script, then cross fingers that it works as expected (be sure to read the log!). The omnios installer itself has a log, do you cross your fingers when you use it? I really don't think you can correlate something creates a log you can look at in case something goes wrong with something is likely to go wrong. I haven't had any problems with it, but if somebody doesn't like how it works out for them, they're more than welcome to a full refund ;). understand that this is more flexible than just running stuff in a screen, but if you were willing to go to such lengths to create this script, what's the problem with fixing the installer to simply prompt for some of these options in the first place? I think you overestimate considerably how much time I put into whipping up this little workaround. I can't imagine it took more than 30 minutes all told. Good luck reengineering the text based installer in that timeframe 8-/. Dunno, it scratched my itch, I know of at least a couple of other people it worked out for, and if somebody gets a good chuckle out of making fun of it, I suppose that's better than nothing. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] industrial usb flash
On Feb 3, 2014, at 7:12 , Fábio Rabelo fa...@fabiorabelo.wiki.br wrote: People are talking about industrial grade usb flash storage to use as boot device for Omni and napp-it . I haven’t tried them but Transcend have various SLC flash form factors: http://us.transcend-info.com/industry/products.asp?CatNo=2LangNo=0Func1No=1Func2No=171 Including a USB connected drive: http://us.transcend-info.com/industry/products.asp?CatNo=2LangNo=0Func1No=1Func2No=171 Ask ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
