[osol-discuss] Perplexed on installing OpenSOLARIS
Hello ... I'm new to Solaris and just installed 5.10 onto a X86 AMD 64bit box. My questions (2 of them), are: 1. During the install, you're offered the choices of installing onto one of four partitions, of which one has to be SOLARIS or the whole disk ... you're not given the opportunity to build your own partitions (/, home, boot, opt, var, tmp ...) ... I realize it lays down a ZFS file system that contains all of those for you, but how do I give it more room? It only installed onto 4 GB of a 360 GB HDD. So how do I expand/enlarge/resize my root and etc? 2. I have two disks in the box. How do I see and install the second? Thanks JDL -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Perplexed on installing OpenSOLARIS
> Hello ... > > I'm new to Solaris and just installed 5.10 onto a X86 > AMD 64bit box. My questions (2 of them), are: > > 1. During the install, you're offered the choices of > installing onto one of four partitions, of which one > has to be SOLARIS or the whole disk ... you're not > given the opportunity to build your own partitions These are actually slices in Solaris parlance - don't mix them with FDISK partitions. You can modify them if you select UFS for the boot disk. If you select ZFS, the only choice you have is about separate /var (which I never bother with). > (/, home, boot, opt, var, tmp ...) ... I realize it > lays down a ZFS file system that contains all of > those for you, but how do I give it more room? It > only installed onto 4 GB of a 360 GB HDD. So how do I > expand/enlarge/resize my root and etc? You have to select options 3 or 4 - I usually go with 4 - just console. Only in this case you will get the choice between UFS and ZFS (apparently there are some reasons even now to go for UFS, but I don't know them, and frankly speaking, don't want to know them - ZFS all the way... ). > > 2. I have two disks in the box. How do I see and > install the second? You should get a screen with the discovered disks; it will show the first one as selected by default, but you can select the second one and deselect the first. It's your problem how to boot from it next, though - it may be a BIOS setting or you could install some boot manager on the first disk, capable of booting from the second (I usually use NetBSD boot manager - my laptop bots natively W7, OpenSolaris and NetBSD from the internal disk, plus some other systems - xBSD and various Solaris instances off external USB disk and even from stick). > > Thanks > > JDL Chreers, Chavdar Ivanov -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Perplexed on installing OpenSOLARIS
Du (Jim) schreibst: > Hello ... > > I'm new to Solaris and just installed 5.10 onto a X86 AMD 64bit box. My > questions (2 of them), are: > > 1. During the install, you're offered the choices of installing onto one of > four partitions, of which one has to be SOLARIS or the whole disk ... you're > not given the opportunity to build your own partitions (/, home, boot, opt, > var, tmp ...) ... I realize it lays down a ZFS file system that contains all > of those for you, but how do I give it more room? It only installed onto 4 GB > of a 360 GB HDD. So how do I expand/enlarge/resize my root and etc? That's a common misunderstanding. In the world of x86 disks, there are FDISK partitions. There can only be four of those of type PRIMARY. That's what the installer does offer you at that point. After that: Solaris uses only ONE such FDISK partition and puts it's SLICES inside one such FDISK partition. So, once you have choosen and sized a FDISK partition, that's then used for all of the pieces. So, in order to use all, either use the WHOLE DISK (if you do NOT want to do a dual-boot system), or size that partition BEFORE you install to a size that can accomodate all of the sapce, that you're going to need and use. You simply can not enlarge FDISK partitions, without need of re-install > 2. I have two disks in the box. How do I see and install the second? Install? What do you want to install on the second disk? Why do you NOT see it? How do you want to install it (UFS or ZFS)? What type of data do you want to put there? If you used ZFS in the beginning (which is a very good choice!), you should then consult the man page to the "zpool" command. If you run "format", you will at least see the disk, and get the name of the device, taht you might then use in "zpool create ..." Matthias > Thanks > > JDL > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- Matthias Pfützner | Tel.: +49 700 PFUETZNER | Was noch? Der Rest ist Lichtenbergstr.73 | mailto:matth...@pfuetzner.de | Begeisterung, und wo die D-64289 Darmstadt | AIM: pfuetz, ICQ: 300967487 | fehlt, ist sowieso alles Germany | http://www.pfuetzner.de/matthias/ | verloren. Durs Grünbein ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Perplexed on installing OpenSOLARIS
+-- | On 2010-10-27 05:11:32, Jim wrote: | | I'm new to Solaris and just installed 5.10 onto a X86 AMD 64bit box. My questions (2 of them), are: 5.10 is not OpenSolaris; it's Solaris 10. The OpenSolaris distribution was 5.11 and has been cancelled. Installing it seems rather pointless. Perhaps as an Oracle employee you have access to internal builds of Solaris 11 Express. | 1. During the install, you're offered the choices of installing onto one of four partitions, of which one has to be SOLARIS or the whole disk ... you're not given the opportunity to build your own partitions (/, home, boot, opt, var, tmp ...) ... I realize it lays down a ZFS file system that contains all of those for you, but how do I give it more room? It only installed onto 4 GB of a 360 GB HDD. So how do I expand/enlarge/resize my root and etc? You need to repartition your disk. Create a 100% SOLARIS fdisk partition. Install on that. Or just give it the whole disk. You don't need to create partitions... you are using ZFS, which is pooled storage. ZFS works best with whole disks. There is no real point in partitioning your root disk(s) into multiple partitions and creating multiple pools on them. It will just make ZFS grumpy. You can create datasets and set quotas on them if you care to, later. However, Solaris and Live Upgrade have historically had issues with /opt and /var being on seperate datasets. /tmp is a tmpfs and does not require its own partition. Maybe this will be helpful in understanding ZFS: http://hub.opensolaris.org/bin/download/Community+Group+zfs/docs/zfslast.pdf | 2. I have two disks in the box. How do I see and install the second? Use Jumpstart, a custom profile, or do it post-install. Solaris manual installation is not really the way Solaris meant to be installed. Investigate the Jumpstart Enterprise Toolkit. Read the Solaris Admin Guides, the ZFS Admin Guide, etc. "Solaris 10 System Administration Essentials"[1] might also be useful. [1] http://www.amazon.com/Solaris-10-System-Administration-Essentials/dp/01379X/ -- bdha cyberpunk is dead. long live cyberpunk. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
Mike Gerdts writes: > In which case you can edit the kernel line in grub to add a -k option > to the boot options. If the system panics, you will be dropped to a > kmdb prompt. You can manually enter kmdb with F1-A or shift-break > from a text console. You can use Ctrl-Alt-F1 to shift to the text > console if you aren't there already. Once at the kmdb prompt, you can > use ::msgbuf to see the things that have scrolled off the screen. You > should get the output a page at a time. If you need to provide this Thanks,, very helpful info there I'm a bit confused though is all of this dependent on having the system panic, or do you mean you can enter kmbd from a text console any time? For example, if I were to edit /rpool/boot/grub/menu.lst at this line: kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS # console=graphics by adding `-k' before the octothorpe above. On reboot, and from a text console I could enter kmbd as you describe? Oh, and by the way, what is `shift-break'... is it on a standard us qwerty keyboard? Maybe the `pause' key? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
Marion Hakanson writes: > As someone else mentioned, most of this stuff will end up in the > /var/adm/messages file. Except, of course, for the very interesting > lowest-level boot problems. yeah... I got a little carried away there... I had long ago setup a /var/adm/debug.log that catches everything log message issued. with *.debug /var/adm/debug.log in /etc/syslog.conf Then forgot I had done so... The messages are there alright but now I'm finding they are not all that helpful... an example at the end. > The reason why it's so primitive is that at this point (in Solaris, > OpenSolaris, Linux, or Windows), you're still pretty much dependent > on whatever features the BIOS provides you, which limits you just > to the old-fashioned, low-tech text-only console. There's just not > enough software running yet to give you a GUI. I'm not sure what you mean here With the same bios, linux manages to provide a text console that is vastly more useful... ie, it has gpm running. I wasn't asking for a gui, I like a text console... but do like to be able to mouse copy from the buffer. About the console messages; they were concerning how to find the output using fmdump, and using the `Event ID' to do so. Now armed with the Event IDs that had scrolled off the screen: I still learn nothing very useful, that is, unless by pounding away on man fmdump and probably a number of other man pages this can be made sense of. But not at all obvious what any of this might mean: fmdump -v -u 4021154c-2d57-c54e-ae82-ea27fc2d19fa TIME UUID SUNW-MSG-ID Oct 14 04:14:02.1292 4021154c-2d57-c54e-ae82-ea27fc2d19fa ZFS-8000-GH 100% fault.fs.zfs.vdev.checksum Problem in: zfs://pool=z3/vdev=e35825af18775fc2 Affects: zfs://pool=z3/vdev=e35825af18775fc2 FRU: - Location: - Oct 25 17:06:24.7775 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-4M Repaired 100% fault.fs.zfs.vdev.checksum Repair Attempted Problem in: zfs://pool=z3/vdev=e35825af18775fc2 Affects: zfs://pool=z3/vdev=e35825af18775fc2 FRU: - Location: - Oct 25 17:06:24.8987 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-6U Resolved 100% fault.fs.zfs.vdev.checksum Repair Attempted Problem in: zfs://pool=z3/vdev=e35825af18775fc2 Affects: zfs://pool=z3/vdev=e35825af18775fc2 FRU: - Location: - ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
On Wed, Oct 27, 2010 at 9:16 AM, Harry Putnam wrote: > Mike Gerdts writes: > >> In which case you can edit the kernel line in grub to add a -k option >> to the boot options. If the system panics, you will be dropped to a >> kmdb prompt. You can manually enter kmdb with F1-A or shift-break >> from a text console. You can use Ctrl-Alt-F1 to shift to the text >> console if you aren't there already. Once at the kmdb prompt, you can >> use ::msgbuf to see the things that have scrolled off the screen. You >> should get the output a page at a time. If you need to provide this > > Thanks,, very helpful info there > > I'm a bit confused though is all of this dependent on having the > system panic, or do you mean you can enter kmbd from a text console > any time? > > For example, if I were to edit /rpool/boot/grub/menu.lst at this > line: > > kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS # console=graphics > > by adding `-k' before the octothorpe above. > > On reboot, and from a text console I could enter kmbd as you > describe? Yes > > Oh, and by the way, what is `shift-break'... is it on a standard us > qwerty keyboard? Maybe the `pause' key? Quite likely. Your initial description implied to me that the system was in some state where you were stuck with just the text console, potentially locked up. The same text that is available with ::msgbuf in mdb is also available from the dmesg command. The dmesg command can be run from a more capable terminal than the console - such as from a GUI login session or remotely through ssh. Most of the output that goes to the console will also be logged by syslog - which I see you found in a message you sent just a couple minutes ago. If the system is behaving well and you want to poke around in it without pausing the kernel, you can use "mdb -k" as well. This can be run from any root (or otherwise appropriately privileged) shell - you don't have to be on the console. The use of "mdb -k" on a live system does not require that it was booted with the "-k" option. Also, if you can find services that were unable to start with "svcs -xv". Each of them will have a log file (see output of "svcs -xv") that may have more useful information. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
Let's turn the problem around: What's the problem, you try to get some infos on? Perhaps this way, we can help you in describing or explaining... Matthias You (Harry Putnam) wrote: > Marion Hakanson writes: > > > As someone else mentioned, most of this stuff will end up in the > > /var/adm/messages file. Except, of course, for the very interesting > > lowest-level boot problems. > > yeah... I got a little carried away there... I had long ago setup a > /var/adm/debug.log that catches everything log message issued. with > > *.debug /var/adm/debug.log > > in /etc/syslog.conf > > Then forgot I had done so... The messages are there alright but now > I'm finding they are not all that helpful... an example at the end. > > > The reason why it's so primitive is that at this point (in Solaris, > > OpenSolaris, Linux, or Windows), you're still pretty much dependent > > on whatever features the BIOS provides you, which limits you just > > to the old-fashioned, low-tech text-only console. There's just not > > enough software running yet to give you a GUI. > > I'm not sure what you mean here With the same bios, linux manages > to provide a text console that is vastly more useful... ie, it has gpm > running. I wasn't asking for a gui, I like a text console... but do > like to be able to mouse copy from the buffer. > > About the console messages; they were concerning how to find the > output using fmdump, and using the `Event ID' to do so. > > Now armed with the Event IDs that had scrolled off the screen: > > I still learn nothing very useful, that is, unless by pounding away on > man fmdump and probably a number of other man pages this can be made > sense of. But not at all obvious what any of this might mean: > > fmdump -v -u 4021154c-2d57-c54e-ae82-ea27fc2d19fa > > TIME UUID SUNW-MSG-ID > Oct 14 04:14:02.1292 4021154c-2d57-c54e-ae82-ea27fc2d19fa ZFS-8000-GH > 100% fault.fs.zfs.vdev.checksum > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 >Affects: zfs://pool=z3/vdev=e35825af18775fc2 >FRU: - > Location: - > > Oct 25 17:06:24.7775 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-4M Repaired > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 >Affects: zfs://pool=z3/vdev=e35825af18775fc2 >FRU: - > Location: - > > Oct 25 17:06:24.8987 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-6U Resolved > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 >Affects: zfs://pool=z3/vdev=e35825af18775fc2 >FRU: - > Location: - > > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- Matthias Pfützner | Tel.: +49 700 PFUETZNER | Gerhard Schröder ist der Lichtenbergstr.73 | mailto:matth...@pfuetzner.de | charakterloseste Heraus- D-64289 Darmstadt | AIM: pfuetz, ICQ: 300967487 | forderer, den ich kenne. Germany | http://www.pfuetzner.de/matthias/ | Helmut Kohl, 1.3.1998 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
On Wed, Oct 27, 2010 at 9:31 AM, Harry Putnam wrote: > Marion Hakanson writes: > >> As someone else mentioned, most of this stuff will end up in the >> /var/adm/messages file. Except, of course, for the very interesting >> lowest-level boot problems. > > yeah... I got a little carried away there... I had long ago setup a > /var/adm/debug.log that catches everything log message issued. with > > *.debug /var/adm/debug.log > > in /etc/syslog.conf > > Then forgot I had done so... The messages are there alright but now > I'm finding they are not all that helpful... an example at the end. > >> The reason why it's so primitive is that at this point (in Solaris, >> OpenSolaris, Linux, or Windows), you're still pretty much dependent >> on whatever features the BIOS provides you, which limits you just >> to the old-fashioned, low-tech text-only console. There's just not >> enough software running yet to give you a GUI. > > I'm not sure what you mean here With the same bios, linux manages > to provide a text console that is vastly more useful... ie, it has gpm > running. I wasn't asking for a gui, I like a text console... but do > like to be able to mouse copy from the buffer. > > About the console messages; they were concerning how to find the > output using fmdump, and using the `Event ID' to do so. > > Now armed with the Event IDs that had scrolled off the screen: > > I still learn nothing very useful, that is, unless by pounding away on > man fmdump and probably a number of other man pages this can be made > sense of. But not at all obvious what any of this might mean: > > fmdump -v -u 4021154c-2d57-c54e-ae82-ea27fc2d19fa > > TIME UUID SUNW-MSG-ID > Oct 14 04:14:02.1292 4021154c-2d57-c54e-ae82-ea27fc2d19fa ZFS-8000-GH > 100% fault.fs.zfs.vdev.checksum > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: - It looks to me like you got a checksum error in a zpool named z3. > > Oct 25 17:06:24.7775 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-4M Repaired > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: - It was repaired > > Oct 25 17:06:24.8987 4021154c-2d57-c54e-ae82-ea27fc2d19fa FMD-8000-6U Resolved > 100% fault.fs.zfs.vdev.checksum Repair Attempted > > Problem in: zfs://pool=z3/vdev=e35825af18775fc2 > Affects: zfs://pool=z3/vdev=e35825af18775fc2 > FRU: - > Location: - And it has been resolved - you don't have to worry about it any more. But, I would run "zpool status z3" to confirm that it says everything is healthy. It may also be advisable to run "zpool scrub z3" to have zfs look for any more problems (hopefully all correctable) before they pile up to a point where they aren't correctable. If you keep having problems, it may point to hardware problems (disk, cable, disk controller, memory, etc.). -- Mike Gerdts http://mgerdts.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Installing package
On 25 Oct 2010, at 07:53, Jackie Xie wrote: > Any utility that allow me to install a package with all required dependencies > at once? something like yum in Redhat That's what the OpenSolaris package manager does by default. The command line version is 'pkg', the GUI version is available from the top panel menu: System->Administration->Pacakge Manager. Cheeri, Calum. -- CALUM BENSON, Interaction Designer Oracle Corporation Ireland Ltd. mailto:calum.ben...@oracle.com Solaris Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Oracle Corp. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] luupdate specific list of preserved data
On 10/28/10 06:10 AM, Mr. Housey wrote: Hi, I am trying to obtain the list of files that are "preserved" during a Solaris Live Update using the luupdate command. Live Upgrade isn't part of OpenSolaris any more (it never was open source), so you should try one of the Solaris forums or news groups. Or you could just give it a try, your current BE will still be there to compare against. -- Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Jumping ship.. what of the data
[NOTE: This post was inadvertanly begun on the `zfs' list but belongs here so reposting with some changes, introducing another whole line of question] If I were to decide my current setup is too problem beset to continue using it, is there a guide or some good advice I might employ to scrap it out and build something newer and better in the old roomy midtower? I don't mean the hardware part, although I no doubt will need advice right through that part too, but here I'm asking about maintaining the data on 3 mirrored pools. I have: rpool @ 2 WD 500GB (old fashioned IDE) pool2 @ 2 WD 500GB sata pool3 @ 2 WD 750GB sata A total of something like 1.7 tb maybe 35% full of data I'm a bit worried about whether with modern hardware the IDE drives will even have a hookup. If it does, can I just hook the two rpool discs up to two of them and expect it to boot OK? I expect to make sure I have a goodly number of sata connections even if it means extra cards, but again, can just hook the other mirrored discs up and expect them to just work. Not likely is my guess, so what about some kind of brief outline to use for a plan of attack? Would I expect to need to reinstall for starters? ---- ---=--- - Another whole approach might be to host the Opensolaris OS on new powerful hardware setup running windows 7. This would be because I've become something of a semi-professional video and graphics editor since retirement... its starting to be a lot of what I do. All my tools rely on windows OS... like the adobe suites or the sony (Vegas) tools. There just are not really top notch tools that run on either linux or solaris. I've been using my Opensolaris machine as a home NAS for the hefty files involved in graphics work. So to host OSol on a windows machine running some of modern stuff like i7 920 CPUs and dual quad cores etc etc And especially really hefty amounts of ram. Adobe tools really love the RAM. But the rub would be how to get my current data onto a VM hosted Opensolaris OS. I don't think I could just attach the current disks and make the VM hosted OS use them... I'm not sure, but I'd need to move some 400-500GB of data. I'd like to hear a few ideas about that. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] luupdate specific list of preserved data
On Wed, Oct 27, 2010 at 1:10 PM, Mr. Housey wrote: > Hi, > > I am trying to obtain the list of files that are "preserved" during a Solaris > Live Update using the luupdate command. I haven't found anything useful on > the web, other than a one sentence snippet from an Oracle whitepaper on how > to upgrade, which states: > > Upgrading > Upgrading a system with a later version of Oracle Solaris instead of doing a > fresh install is a popular procedure because upgrading preserves all the > effort initially spent in configuring the system. Oracle offers two ways to > upgrade: > > It's the "preserves all the effort initially spent in configuring the system" > that I need to know. Does anyone know *exactly* what is preserved and in > what manner? > > Thanks for any information you can provide. All files modified by the user are preserved. After the LU process, /var/sadm/system/data/upgrade_cleanup on the upgraded BE contains a full list of files that need to be examined. You can parse the log programmatically. The policy decision to rename the existing file and install the new file in its place, or keep the existing file and install the new file under a new name, depends on the file in question. -Albert ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Jumping ship.. what of the data
On Wed, Oct 27, 2010 at 7:22 PM, Harry Putnam wrote: > I don't mean the hardware part, although I no doubt will need advice > right through that part too, but here I'm asking about maintaining the > data on 3 mirrored pools. > > I have: rpool @ 2 WD 500GB (old fashioned IDE) > pool2 @ 2 WD 500GB sata > pool3 @ 2 WD 750GB sata > > A total of something like 1.7 tb maybe 35% full of data > > I'm a bit worried about whether with modern hardware the IDE drives > will even have a hookup. If it does, can I just hook the two rpool > discs up to two of them and expect it to boot OK? ATA->SATA adapter hardware is < $5 US shipped. (All of the ones I've seen are actually bidirectional and do SATA->ATA as well). > > I expect to make sure I have a goodly number of sata connections even > if it means extra cards, but again, can just hook the other mirrored > discs up and expect them to just work. > > Not likely is my guess, so what about some kind of brief outline to > use for a plan of attack? > > Would I expect to need to reinstall for starters? Depends on what your current problems are, of course. > > --- - ---=--- - > > Another whole approach might be to host the Opensolaris OS on new > powerful hardware setup running windows 7. > > This would be because I've become something of a semi-professional > video and graphics editor since retirement... its starting to be a lot > of what I do. > > All my tools rely on windows OS... like the adobe suites or the sony > (Vegas) tools. Or you could run Windows in VirtualBox. Or both on VMware or something. > But the rub would be how to get my current data onto a VM hosted > Opensolaris OS. I don't think I could just attach the current disks > and make the VM hosted OS use them... I'm not sure, but I'd need to > move some 400-500GB of data. Yes, you should be able to just attach the disks to any regular VM. -Albert ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] prices for new Sparc T3 series and their sold on oracle store
whom ever needs one they are already available through oracle store starting at $18,639 :-) maybe somebody can give me one for my birthday;-) https://shop.sun.com/store/product/e823f71d-d883-11de-9869-080020a9ed93?intcmp=soc https://shop.oracle.com/pls/ostore/f?p=ostore:2:0::NO:RP,2:PROD_HIER_ID:7246562218191186367847 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] luupdate specific list of preserved data
Thanks Ian, I will post to a Solaris forum. -Original Message- From: Ian Collins [mailto:i...@ianshome.com] Sent: Wednesday, October 27, 2010 2:00 PM To: HOUSEY ED-MWN486 Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] luupdate specific list of preserved data On 10/28/10 06:10 AM, Mr. Housey wrote: > Hi, > > I am trying to obtain the list of files that are "preserved" during a Solaris Live Update using the luupdate command. > Live Upgrade isn't part of OpenSolaris any more (it never was open source), so you should try one of the Solaris forums or news groups. Or you could just give it a try, your current BE will still be there to compare against. -- Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
On Wed, Oct 27, 2010 at 7:39 AM, Mike Gerdts wrote: > The dmesg command can be run > from a more capable terminal than the console - such as from a GUI > login session or remotely through ssh. If you need to use the text console and don't have another machine handy, the "screen" utility can also be quite useful. It offers multiple virtual terminals, scrollback, and cut-and-paste capabilities. The commands take a little effort to learn (they're not terribly intuitive) but this gives you most of the functionality of the multiple text consoles you'd find on FreeBSD or Linux. Screen also lets you detach from a session and reattach to it later from another terminal, which can be very useful sometimes. -- David Brodbeck System Administrator, Linguistics University of Washington ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Jumping ship.. what of the data
Albert Lee writes: [...] > ATA->SATA adapter hardware is < $5 US shipped. (All of the ones I've > seen are actually bidirectional and do SATA->ATA as well). So that would appear as an IDE port then ... good. > Depends on what your current problems are, of course. Far as OS goes I don't think I have a problem any more. I was getting repeated corrupted data (in the snapshots) on one pool but I think I've got that cleaned up by moving the data and `zfs destroy -r' the problem filesystems, then running a scrub. `zpool status' now gives the thumbs up, and the pool that received the data has made no complaints so far. >> --- - ---=--- - >> >> Another whole approach might be to host the Opensolaris OS on new >> powerful hardware setup running windows 7. >> >> This would be because I've become something of a semi-professional >> video and graphics editor since retirement... its starting to be a lot >> of what I do. >> >> All my tools rely on windows OS... like the adobe suites or the sony >> (Vegas) tools. > > Or you could run Windows in VirtualBox. Or both on VMware or something. That was my first thought too. But then someone here pointed out that why would I make windows the guest when the work is all windows native tools and processes. And if I had a plenty of ram, opensolaris would run full tilt as guest... and doesn't need a good quality graphics card (which is not available in VM far as I've heard. So it seems to make more sense with Osol as guest. >> But the rub would be how to get my current data onto a VM hosted >> Opensolaris OS. I don't think I could just attach the current disks >> and make the VM hosted OS use them... I'm not sure, but I'd need to >> move some 400-500GB of data. > > Yes, you should be able to just attach the disks to any regular VM. Are you saying you can set things in Vbox or VMware so that the guest uses actual hardware with no `virtual' layer in there? In other words you could assign the set of 2 500gb IDE drives as boot and rpool mirror to the guest OS? And the data would be available like it was when it was installed on an Osol machine? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Jumping ship.. what of the data
Hello > But then someone here pointed out that > why would I make windows the guest when the work is all windows native > tools and processes. And if I had a plenty of ram, opensolaris would > run full tilt as guest... and doesn't need a good quality graphics > card (which is not available in VM far as I've heard. > > So it seems to make more sense with Osol as guest. I don't have a position on host versus guest to take at this stage. My point is: If I were you, and if your existing system is still working at all, I would _leave it alone_ and set up a brand new machine, configured the way you want to go forward. Then, connect a network wire between the two and transfer over your data. Yes, it may take a while to move your data, but by doing it this way you preserve your fallback-and-try-again options. Tearing apart or reinstalling an existing machine before the next one is up and ready is too terrifying for me to consider. It may cost more, but (IMO), hardware is cheap, and preserving that fallback option is worth it. Best Regards- Tim ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [b 133] Catching messages on reboot from failure
David Brodbeck writes: > On Wed, Oct 27, 2010 at 7:39 AM, Mike Gerdts wrote: >> The dmesg command can be run >> from a more capable terminal than the console - such as from a GUI >> login session or remotely through ssh. > > If you need to use the text console and don't have another machine > handy, the "screen" utility can also be quite useful. It offers > multiple virtual terminals, scrollback, and cut-and-paste > capabilities. The commands take a little effort to learn (they're not > terribly intuitive) but this gives you most of the functionality of > the multiple text consoles you'd find on FreeBSD or Linux. Screen > also lets you detach from a session and reattach to it later from > another terminal, which can be very useful sometimes. Yes, I know and use screen often. Not a superuser by any means but I'm familiar with it. The trouble is messages like those I referred too pop up as soon as you longin (in console (text) mode). Is it possible to make `screen' your login shell? I've never looked into that, but I've never heard of anyone doing it either. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Jumping ship.. what of the data
Tim Bell writes: > Tearing apart or reinstalling an existing machine before the next one > is up and ready is too terrifying for me to consider. It may cost > more, but (IMO), hardware is cheap, and preserving that fallback > option is worth it. Sound like a smart choice. I guess this is not the time to be a tightwad and try to go on the cheap. The only thing that would be able to be salvaged anyway is the case itself and even a nice roomy one like the antec sonata I have, with a power supply, would be less than $200 I guess. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Jumping ship.. what of the data
On Thu, Oct 28, 2010 at 12:08 AM, Harry Putnam wrote: > Tim Bell writes: > > > Tearing apart or reinstalling an existing machine before the next one > > is up and ready is too terrifying for me to consider. It may cost > > more, but (IMO), hardware is cheap, and preserving that fallback > > option is worth it. > > Sound like a smart choice. I guess this is not the time to be a > tightwad and try to go on the cheap. > > The only thing that would be able to be salvaged anyway is the case > itself and even a nice roomy one like the antec sonata I have, with a > power supply, would be less than $200 I guess. > > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > Hey, Not sure why anyone would run Win natively and guest UNIX of their own volition ... but hey, if someone has some data that supports that solution, cool. First consideration is _always_ backups. All the tools for storage are included with 'Solaris. Of course tar, rsync and friends are available (and a whack of solutions based on these as well). Externalizing your storage through a NAS/SAN would be an excellent direction to pursue as well. Hypervisors (Vmware and others) can make hardware available to guest(s) certainly. -- Cheers, Steven --- Steven Acres Toronto OpenSolaris User Group Leader http://opensolaris.org/os/project/torosug ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
