[OpenIndiana-discuss] Remote KVM, SOL, virtual media and power management on generic PCs
Hello all, A slightly off-topic question: I plan to visit a remote location where I manage a problematic OpenIndiana storage server built from whatever desktop remnants were around into a Home-NAS. Sometimes it hangs or gets otherwise inaccessible, so I want to plug in some solution for remote access to this box. Are there any cheap (within approx $100) solutions for remote KVM, SOL, virtual media and power (reset, on/off) management on generic PCs? Something that the IPMI-enabled servers have, but usable with an ordinary PC, probably as a PCI (legacy PCI 2.2 or newer PCI-E) card that looks to the computer like a video card and USB hub with keyboard, mouse and storage, and optionally as a serial port for SOL emulation? Or some external box that would intercept the video output (DSUB15/DVI) and plug USB cables into the PC's inputs, and add the short-circuiting headers onto power and reset jumpers on the motherboard? Remote video is not a strict requirement, a reliably working SOL (compatible with OI/illumos) would suffice. Remote media may be more needed however, to allow for upgrades/repairs of the OS. And the thing should work over the internet when published over NAT (can make static port mappings with static external IP address). So far all I've found are either largish KVM switches or eRIC cards that cost close to a new PC, and replacing the old box completely is out of the budget both monetarily and in time constraints (I won't be there long enough) :( I see that there are some solutions from SuperMicro AOC lineup, and ASUS as well (the said computer's Mobo is an ASUS P5B-Delixe/WiFi-AP) but I can't make out from the internet documentation whether these would work on generic desktop computers, or require some BMC, or some special connectors, or other components on the motherboard. Any insights, or links to Amazon/eBay offers, are welcome :) Thanks, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Selecting video mode for text mode in OI
Hello all, Has anybody bothered trying larger resolutions (80x50 or so) in text-mode OI/illumos/Solaris-x86 outputs? This would help in systems debugging a lot :) I guess something of the kind could be inherited from GRUB, but my first tests did not get it to do the job either :\ //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Missing dladm show-dev
Hello all, Back in Solaris 10 I used dladm show-dev to list the devices (and more importantly bound drivers) for NICs. In Openindiana this command seems not implemented, or possibly removed? What gives? :) Thanks, //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Missing dladm show-dev
On 11/15/13, 4:51 PM, Jim Klimov wrote: Hello all, Back in Solaris 10 I used dladm show-dev to list the devices (and more importantly bound drivers) for NICs. In Openindiana this command seems not implemented, or possibly removed? What gives? :) Hi Jim, Don't know about show-dev, but does show-phys not serve the purpose? (at least guessing from what you described above) -- Saso ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Missing dladm show-dev
On 2013-11-15 17:54, Saso Kiselkov wrote: On 11/15/13, 4:51 PM, Jim Klimov wrote: Hello all, Back in Solaris 10 I used dladm show-dev to list the devices (and more importantly bound drivers) for NICs. In Openindiana this command seems not implemented, or possibly removed? What gives? :) Hi Jim, Don't know about show-dev, but does show-phys not serve the purpose? (at least guessing from what you described above) Yes, it does... but old scripts on new OSes complain and need some hammering ;) sol10-1# dladm show-dev nge0link: unknown speed: 0 Mbps duplex: unknown nge1link: unknown speed: 0 Mbps duplex: unknown e1000g0 link: upspeed: 1000 Mbps duplex: full e1000g1 link: unknown speed: 0 Mbps duplex: half sol10-2# dladm show-dev e1000g0 link: upspeed: 1000 Mbps duplex: full e1000g1 link: upspeed: 1000 Mbps duplex: full e1000g2 link: upspeed: 1000 Mbps duplex: full e1000g3 link: unknown speed: 0 Mbps duplex: half vboxnet0link: unknown speed: 0 Mbps duplex: unknown oi# dladm show-phys LINK MEDIASTATE SPEED DUPLEXDEVICE e1000g2 Ethernet unknown0 half e1000g2 e1000g0 Ethernet up 1000 full e1000g0 e1000g3 Ethernet up 1000 full e1000g3 e1000g1 Ethernet unknown0 half e1000g1 The last two examples are from identical servers with different OSes. And dladm show-link aggregates the different link types (as James pointed out)... I was just a bit annoyed at a new box which was expected to have Intel gigabit NICs but refused to plumb e1000g. Ultimately dladm reminded me that igb is also in the business, and apparently this was some slightly different revision of the server than those before it... and even the cheat-sheet diagnostics failed with unknown-parameter stuff ;) But thanks for reminding me anyway, and sorry for the noise :) //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Missing dladm show-dev
On 11/15/13 12:34, Jim Klimov wrote: On 2013-11-15 17:54, Saso Kiselkov wrote: On 11/15/13, 4:51 PM, Jim Klimov wrote: Hello all, Back in Solaris 10 I used dladm show-dev to list the devices (and more importantly bound drivers) for NICs. In Openindiana this command seems not implemented, or possibly removed? What gives? :) Hi Jim, Don't know about show-dev, but does show-phys not serve the purpose? (at least guessing from what you described above) Yes, it does... but old scripts on new OSes complain and need some hammering ;) I hope you're using the -p (parseable output) mode when you use this in a script. The default human-readable output has changed many times and may change again. As for the show-dev bit, I don't recall how that came to be, but I can make a guess. The previous stability level was Evolving and the PSARC case I cited changed it to Obsolete. Normally, you can't just remove (or otherwise change incompatibly) something even though it's Obsolete; the previous stability matters, as does the engineering work to determine if anyone is relying on the thing to be changed. This implies that someone felt that OpenSolaris was the one thing Sun promised never to do again: a new Major Release. I was just a bit annoyed at a new box which was expected to have Intel gigabit NICs but refused to plumb e1000g. Ultimately dladm reminded me that igb is also in the business, and apparently this was some slightly different revision of the server than those before it... and even the cheat-sheet diagnostics failed with unknown-parameter stuff ;) There are several different Intel-related drivers, depending on chipset. I remember at least 82586 iee, 82595 eepro, 825[59]6 ieef, 8255[789] iprb, 82575 igb, 8259[89] ixgbe, and 8254x e1000g for wired, and 5[13]00 iwh, 2200 ipw, and 2100 iwk/iwp for wireless. I would not be shocked if there were a few more lurking out there somewhere. The families are (apparently!) different enough that having a separate driver for each was the solution. (Well, there were other internal reasons that happened, but it's all ancient history now.) -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Fwd: 2nd round - Bug 1204 zoneadm cannot create clone of zone from snapshot
In regard to: Re: [OpenIndiana-discuss] Fwd: 2nd round - Bug 1204 zoneadm...: I would prefer the for ((; ; )) syntax over the x=0;while ... ; x=x+1 ; done syntax because its IMHO more readable for people coming from C. No offense intended, but shell is not C and trying to make a shell script look more C-ish is just going to be confusing for people that are familiar with shell idioms. It strikes me as another variant of Bournegol. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Bind 9.9.4
Hi, I recently built Bind 9.9.4 and find that if I enable DNSSEC it causes OpenIndiana OI_151_a8 hipster release to freeze within a couple of minutes and reboot. The previous release of Bind 9.9.3 did not exhibit this behaviour. Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] starting BIND 9.9.4 Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] built with '--prefix=/opt/gnu' '--sysconfdir=/etc' '--enable-threads' '--enable-largefile' '--enable-ipv6' '--enable-shared' '--disable-static' 'CC=gcc' Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] BIND 9 is maintained by Internet Systems Consortium, Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] Inc. (ISC), a non-profit 501(c)(3) public-benefit Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] corporation. Support and training for BIND 9 are Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] available at https://www.isc.org/support Nov 15 18:00:21 test named[535]: [ID 873579 daemon.notice] ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] hangs on terminal back-space and iwi0 disconnects
Quite frequently ( about every 1.5 hours ) whenever I get disconnected from a wireless network, the system seems to hang. Assumed I needed to reboot, but lasts for about a minute and everything resumes. This also happens ( frequently ) whenever I backspace under vi as to cause a system 'beep'. ( Also does this in gedit as well, or generally while using terminal. I thought that it *might* be related to the audio drives because I'm not 100% on whether or not system beep is directly implemented through a bios call or not. It seems that problems that present this way are documented somewhat, but I'm not sure of a work-around ( or not ). Wireless hardware: Intel Pro/Wireless 2200bg node name: pci8086,2711 Vendor: Intel Corporation Device: PRO/Wireless 2200BG [Calexico2] Network Connection Sub-Vendor: Intel Corporation binding name: pci8086,4220 devfs path: /pci@0,0/pci8086,2448@1e/pci8086,2711@2 bus addr: 2 pci path: 2,2,0 compatible name: (pci8086,4220.8086.2711.5)(pci8086,4220.8086.2711)(pci8086,2711)(pci8086,4220.5)(pci8086,4220)(pciclass,028000)(pciclass,0280) driver name:iwi Audio hardware: Vendor: Intel Corporation Device: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller Sub-Vendor: IBM Sub-System: ThinkPad T41 binding name: pci8086,24c5 devfs path: /pci@0,0/pci1014,537@1f,5 bus addr: 1f,5 pci path: 0,1f,5 compatible name: (pci8086,24c5.1014.537.1)(pci8086,24c5.1014.537)(pci1014,537)(pci8086,24c5.1)(pci8086,24c5)(pciclass,040100)(pciclass,0401) driver name:audio810 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working?
G'day, Before I do it myself, has anyone got VB 4.3.2 on OI 151a8 running? All good? No good? Thanks! Carl ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working?
Ran it last week, perfect access to underlying hardware... VM's RAM gets stuck in swap often on a 1gb ram machine. Aggrivating and painful. Date: Sat, 16 Nov 2013 11:10:27 +1100 From: c...@bl.echidna.id.au To: openindiana-discuss@openindiana.org Subject: [OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working? G'day, Before I do it myself, has anyone got VB 4.3.2 on OI 151a8 running? All good? No good? Thanks! Carl ___ 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] Virtualbox 4.3.x (2!) and oi 151a8? working?
On 16/11/2013 11:21 AM, tyrrell t wrote: Ran it last week, perfect access to underlying hardware... VM's RAM gets stuck in swap often on a 1gb ram machine. Aggrivating and painful. so stick with 4.2.x for now I guess? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Virtualbox 4.3.x (2!) and oi 151a8? working?
On 13-11-15 04:21 PM, tyrrell t wrote: Ran it last week, perfect access to underlying hardware... VM's RAM gets stuck in swap often on a 1gb ram machine. Aggrivating and painful. Hi Tyrrell. Did you file a bug? It would be good to keep an eye on it. They have done a lot of work in the performance side with vbox, so it would be good to get it working. Geoff ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Fwd: lint libraries
Hello. I have a question about lint libraries. We need Studio lint to generate them. But a) I'd like to avoid using closed compiler; b) I don't know if anyone actually needs them. So, does anybody actually use llib-* stuff? --- System Administrator of Southern Federal University Computer Center ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
