Re: [OpenIndiana-discuss] Updates in OI
On 5/4/2021 8:59 AM, Yassine Chaouche wrote: > Le 5/4/21 à 1:43 PM, Stephan Althaus a écrit : >> >> Hello! >> >> We have "Boot environments" >> >> On every "pkg update" you get a new BE that will be used on next reboot. > > This is just > ... > Is this done by issuing a ZFS snapshot of the whole root partition ? or > is it more granular ? > > If this is done via snapshots, this means writing to an evergrowing file > on disk until the snapshot is removed. So the longer you keep a snapshot, > the bigger the file gets. > Yes, boot environments in the OpenSolaris-derived OS's are implemented using ZFS snapshots/clones of the root datasets. Combined with IPS's optimizations to only update objects that have changed between package versions, you may find that boot environments for an update may not be nearly as large as the initial installation; it all depends on how much has changed. Reclaiming space is as simple as deleting older boot environments when they're no longer needed. It's not at all unusual for a system to have a dozen or more boot environments; some of the more masochistic among us used to have systems with 100 or more. Dave ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] About deleting past BEs
On 09/26/17 12:59 PM, Harry Putnam wrote: How to tell which BEs are ok to delete. What is common practice regarding deletion of BEs? (I do know what the `N' and `R' mean and so not to delete them) In my current list of BE's (shown at end of post) I see one marked as backup-1... this is not something I did purposely so must be the result of an update. Is there any reason not to delete that one? If you haven't needed it by now, I wouldn't think you will. I'm thinking I could delte 0-11 including `4-backup-1' without expecting any bad repercussions. Is that about right? Yes. I do notice that 1 and 7 are quite a lot larger than the others (not including the one designated `14 R') and wonder how that happens and if it has baring on what to delete? Depends on activity while that BE was running and the difference in package content between it and the prior one. Larger ones will be expected to free up more space. Dave --- --- ---=--- --- --- beadm list BE Active Mountpoint Space Policy Created openindiana- - 15.2M static 2017-04-09 11:07 openindiana-1 - - 3.58G static 2017-04-09 13:20 openindiana-2 - - 31.7M static 2017-04-09 13:55 openindiana-3 - - 487M static 2017-04-14 00:50 openindiana-4 - - 34.5M static 2017-04-15 11:52 openindiana-4-backup-1 - - 219K static 2017-04-16 13:21 openindiana-5 - - 63.9M static 2017-05-03 06:15 openindiana-6 - - 615M static 2017-05-25 12:00 openindiana-7 - - 1.77G static 2017-07-08 14:07 openindiana-8 - - 223M static 2017-07-13 09:05 openindiana-9 - - 254M static 2017-07-24 10:50 openindiana-10 - - 17.3M static 2017-07-27 12:24 openindiana-11 - - 326M static 2017-08-18 10:04 openindiana-12 - - 16.7M static 2017-08-25 07:59 openindiana-13 N / 6.26M static 2017-09-05 07:57 openindiana-14 R - 78.2G static 2017-09-26 12:41 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what to expect setting timeslider to `all'
On 09/ 5/17 07:48 AM, Harry Putnam wrote: [...] Harry Wrote: Running: Openindiana/hipster updated today (170825) With timeslider tool enabled and set to `all' should I expect snapshots only to appear at zfs filesystems that are an endpoint? An example I see here: With these filesystems created: p1/vb p1/vb/vm No snapshots are created at /vb/.zfs/snapshot That directory exists, but does not get snapshots. But, the usual stuff appears at /vb/vm/.zfs/snapshot frequent, hourly, daily, weekly etc updates appear there. Dave Miner <dave.mi...@oracle.com> writes: Sounds like an old bug that was fixed some time ago in Solaris, where the exclusion check for recursive snapshots isn't correct. This is happening on a recently updated (about 170825 or so) hipster OS. So if an old bug has recurred somehow, one would think it would be getting reported by others on this list. If hipster is still using old time-slider tarballs from the OpenSolaris days then it's probably never been fixed and others aren't reporting it for whatever reason. In a lot of situations it's benign as data is more in the leaf datasets than intermediate. Dave ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] what to expect setting timeslider to `all'
Sounds like an old bug that was fixed some time ago in Solaris, where the exclusion check for recursive snapshots isn't correct. Dave On 08/25/17 08:00 PM, Harry Putnam wrote: [Note: this message was inadvertently posted to gmane.os.illumos.general but was intended for gmane.os.openindiana.general] , | Subject: what to expect setting timeslider to `all' | Newsgroups: gmane.os.illumos.general | To: disc...@lists.illumos.org | Date: Fri, 25 Aug 2017 19:35:53 -0400 (20 minutes, 23 seconds ago) | Message-ID: <87inhb5ig6@local.lan> ` Running: Openindiana/hipster updated today (170825) With timeslider tool enabled and set to `all' should I expect snapshots only to appear at zfs filesystems that are an endpoint? An example I see here: With these filesystems created: p1/vb p1/vb/vm No snapshots are created at /vb/.zfs/snapshot That directory exists, but does not get snapshots. But, the usual stuff appears at /vb/vm/.zfs/snapshot frequent, hourly, daily, weekly etc updates appear there. Another Example: p1/rhosts p1/rhosts/2x2 p1/rhosts/Images/ Mount point is `/rhosts' p1/rhosts/.zfs/snapshot/ p1/rhost/2x2/.zfs/snapshot/ p1/rhosts/2x2/Images/.zfs/snapshot/ All the usual snapshots are here `frequent, hourly, daily etc. Consider again, that timeslider is enabled and set to `all' ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] The end is near
On 01/19/17 09:04 AM, Dmitry Kozhinov wrote: The most interesting thing in http://www.oracle.com/us/products/servers-storage/servers/sparc/oracle-sparc/sparc-roadmap-slide-2076743.pdf for me is "Software in Silicon". I may be wrong, but I'm under impression that Oracle integrates parts of Solaris into hardware. Not really. I'd suggest https://community.oracle.com/docs/DOC-932216 as a starting point for what that term means. Dave ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] What Do I Have To Install To Get A GUI ?
On 07/22/14 10:36, Ron Dawson wrote: On Wed, Jul 16, 2014 at 12:58 AM, Alan Coopersmith alan.coopersm...@oracle.com wrote: Things work much better if you use the GUI installer to install systems on which you want to run a GUI. On Solaris 11, pkg install solaris-desktop would get you all the bits as well, but since OpenIndiana still uses the old names, the packages from the GUI install media are grouped under the more obscure name, pkg install slim_install. I've been curious for a while where the group name slim_install came from. Is slim an acronym for something? No, it was just a name we chose during OpenSolaris development to differentiate it from a more complete install that included all locales and some other things (that was known as babel_install). slim was a decidedly relative term :-) Dave ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI 151_a7 install on 4k sector disk
On 01/29/13 06:56, Jim Klimov wrote: On 2013-01-28 19:54, Reginald Beardsley wrote: My understanding is that it is not possible to boot from an EFI labeled disk. Has that changed? In a way it's moot as I just got the UPS tracking info for 3x2 TB disks. But the info might help someone else. The Oracle docs I was pointed to were very specific that you couldn't have a VTOC label larger than 2 TB and couldn't boot from an EFI label. http://docs.oracle.com/cd/E19082-01/819-2723/disksconcepts-14/index.html Given the statement that Oracle managed to change something in this regard in recent Solaris, I wonder what it was? Ditch the VTOC-only support in installer/GRUB/rpool import and mount, and allow use of plain GPT partitions? Yes, the boot loader was changed to GRUB2, and support for EFI partitions was added to the boot and installation infrastructure. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI 151_a7 install on 4k sector disk
On 01/26/13 09:44, Jan Owoc wrote: On Sat, Jan 26, 2013 at 7:08 AM, Reginald Beardsleypulask...@yahoo.com wrote: I'm trying to install on a 3 TB HGST disk which reports 512 byte sectors using the text installer. The system is an HP N40L and is intended to be a ZFS based NFS server for a Solaris 10 workstation. format(1m) correctly sees the size of the disk and I'm able to create a 128 GB slice for a root pool and the rest (2.6 TB) for the eventual RAIDZ pool. However, the installer keeps telling me that I can't use more than 2 TB. I can't find anything about installing onto 4K sector disks in the wiki or elsewhere. I'm not aware of OpenIndiana-specific documentation to this problem, but I recall reading that both the most recent OpenSolaris as well as the current Solaris 11 can't be installed on disks2TB. It had something to do with booting off a disk with a GPT label. Solaris 11.1 added the capability to fully utilize 2 TB disks for the root pool. The installer version that OI is using doesn't have any of that support. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Synchronizing Sun DHCP servers
On 08/09/12 07:59, James Carlson wrote: Jim Klimov wrote: I wondered if the Sun DHCP server, also provided in OI, supports synchronization of instances - i.e. two boxes providing addresses for the same range, should support interchange of leased address lists, defined macros (dhcptab) and so on. Yes. The simplest answer is to use the SUNWfiles backend (see dhcp_modules(5)), and share the files via NFS between servers. The more complex (but much more scalable) way is via NIS+ (on Solaris 10, but not OpenIndiana; NIS+ is dead). Amusingly, the man page still talks about three built-in mechanisms but then describes only two. Good to see you're still better at noticing details than most anyone I know :-) You can also write your own backend to do anything you want; see the Solaris DHCP Service Developer's Guide: http://docs.oracle.com/cd/E19253-01/806-6829/806-6829.pdf That would be my suggestion, too. Perhaps a shared LDAP backend can be implemented? I'm sure that could be done as well. I don't recall if it was ever done, but I would have expected that it would have been an ARC-required portion of the NIS+ to LDAP transition strategy. I'd expect that Dave Miner at Oracle would know for sure if anyone does. No, we never got around to building one; I seem to recall we'd started a prototype back in the late '90's but it never got to be a priority. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
beadm is missing a qualifier on mount to specify the pool name under which the named BE is located, so it mounts the first BE it finds with the name you specify. Since you had the same BE name present in your existing root pool, that gets in the way. Your workaround removed the conflict and that's why it worked. Dave On 03/19/12 23:18, Reginald Beardsley wrote: Well, not quite. Look at my more recent post. I'm not yet 100% sure of the details, but it revolves around how zfs be interact. And most likely the namespace collision between rpool fpool. However, you can see manipulate things w/ beadm that you can't access w/ zfs. There are doubtless sound reasons for this hidden in the implementation details. fpool was mounted under /mnt, it just wasn't the portion of fpool I wanted to access. My observation of df over the past few years is that it doesn't quite grok zfs yet. I find myself using zfs list quite a bit. In any event, the confluence of comments got me to the solution. Which is what matters. So thanks again to all. Have Fun! Reg --- On Mon, 3/19/12, James Carlsoncarls...@workingcode.com wrote: From: James Carlsoncarls...@workingcode.com Subject: Re: [OpenIndiana-discuss] Access to /etc on a pool from another system? To: openindiana-discuss@openindiana.org Date: Monday, March 19, 2012, 8:15 PM On 03/19/12 17:16, Reginald Beardsley wrote: I would expect /mnt to contain /mnt/etc also. rhb@openindiana:~# df /mnt /� � � � � � � � � (rpool/ROOT/oi_151 ):360070851 blocks 360070851 files rhb@openindiana:~# Well, there's your problem.� /mnt isn't mounted.� All you're looking at is your native rpool root file system, not the one in fpool. Now that I think about it, the problems seemed to revolve around the special way that zfs and beadm treat /. Other than being canmount=no, it's not too special.� Just look at the ZFS attributes; they tell you everything you might want to know. zfs get -o all all fpool/ROOT/opensolaris -- James Carlson� � � ���42.703N 71.076W� � � ���carls...@workingcode.com ___ 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 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] USB - RS-232 adaptors
I've owned the Keyspan for several years, using it for tip access to my old Netra X1. Has worked perfectly up through Solaris 11. Dave On 12/26/11 21:43, Richard L. Hamilton wrote: http://www.amazon.com/Keyspan-USA-19HS-Hi-Speed-supports-Sequence/dp/BVYJRY (Keyspan by Tripp-Lite USA-19HS) is listed on http://www.oracle.com/technetwork/server-storage/solaris/overview/keyspan135279.html for Solaris 10 update 5 and later. Linux�I think it should work _depending_ on the distro, but some things I've seen suggest one may need to manually build and/or install the driver for Ubuntu and Debian; but that was a few years old, and the situation may have changed. The only two choices I've seen repeatedly mentioned for Solaris are Edgeport and Keyspand, and the Edgeport seem to be more expensive. I haven't used either myself; I probably know of some that have used some such thing, but not that I could find out any time soon. On Dec 26, 2011, at 8:46 PM, Reginald Beardsley wrote: Does anyone have any suggestions for a reasonably priced unit? The one I have is MIA and was somewhat problematic. I'm sure it will turn up as soon as I buy a new one. Ideally I'd like something OI, Solaris 10 and Linux supported, but I'd be happy to live w/ just OI, or if all else fails Linux. Alternatively suggestions on inexpensive PCI RS-232 cards that work w/ both Solaris 10 U9 Linux also welcome.(The OI box is a nettop). I just need to talk to some embedded processor development boards and don't want to use Windows. Thanks, Reg ___ 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] distro_const package caching
On 12/20/11 06:51, Gabriele Bulfon wrote: Hi, anyone knows a way to let distro_const cache the downloaded packages from IPS, avoiding download on every run??? The version of DC from back around 161 didn't allow this to be controlled. If you're just re-running with the same package set but different post-processing then you can just resume from the checkpoint after the image is populated with packages. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Building an Installer
On 06/ 4/11 01:57 PM, Gabriele Bulfon wrote: Thanks ;) I followed instructions as here: http://wiki.openindiana.org:8080/display/oi/Creating+Distribution+Images and it seem to work fine even on dev-il. The only problem I see is the repo: creating the iso by downloading all the packages from a remote repo sounds very busy. If you're adjusting package sets a lot, yes, it will be. But if you're doing customizations after the package download stage (which is the first one) then you can use the DC's resume from a checkpoint feature to avoid redoing that part. Sorry for the silly question, butmaybe I should create a clone of the repo once? How? If you're going to do a lot of builds with DC, you'll likely find this helpful. pkgrecv is the tool to replicate IPS repositories. Then...how do I update the repo without recreating from scratch? Again, pkgrecv. Dave Da: ken mays A: Discussion list for OpenIndiana Cc: gbul...@sonicle.com Data: 4 giugno 2011 14.31.32 CEST Oggetto: Re: [OpenIndiana-discuss] Building an Installer Use it under the OI environment. --- On Sat, 6/4/11, Gabriele Bulfon wrote: From: Gabriele Bulfon Subject: Re: [OpenIndiana-discuss] Building an Installer To: Discussion list for OpenIndiana Date: Saturday, June 4, 2011, 8:08 AM Thanx a lot for all the suggestions. A last question before starting: should I use it under OI or under a bare IllumOS? -- Da: Deano A: 'Discussion list for OpenIndiana' Data: 3 giugno 2011 9.07.12 CEST Oggetto: Re: [OpenIndiana-discuss] Building an Installer Yes OI is built with distro-constructor and caimen. If you do manage get some experience with it, it would be great to write up your notes on the wiki. Customizing the installer works, but its currently a bit hidden, so any extra info you could add would be appreciated. The oi-dev IRC channel and ML will also be able to help you out, as there the devs who use it to produce the main OI installers with distro-constructor hang out. Bye, Deano -Original Message- From: Gabriele Bulfon [mailto: gbul...@sonicle.com ] Sent: 03 June 2011 07:52 To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Building an Installer Yes, I remember looking at it for OpenSolaris. Is it still usable on IllumOS/OI? I remember it didn't work correctly for some reasons on IllumOS. Is OI built with it? -- Da: Dave Miner A: openindiana-discuss@openindiana.org Data: 2 giugno 2011 19.49.11 CEST Oggetto: Re: [OpenIndiana-discuss] Building an Installer On 06/ 2/11 07:18 AM, Gabriele Bulfon wrote: Hi, don't know if this is a silly question, but I'd like to know if there is any chance to have an installer tool for bulding a customized installer of openindiana that would contain what I need by default, including additional software of mine. That's what the Distribution Constructor tool is used for. Dave ___ 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 -Inline Attachment Follows- ___ 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 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Building an Installer
On 06/ 2/11 07:18 AM, Gabriele Bulfon wrote: Hi, don't know if this is a silly question, but I'd like to know if there is any chance to have an installer tool for bulding a customized installer of openindiana that would contain what I need by default, including additional software of mine. That's what the Distribution Constructor tool is used for. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Update info?
On 05/24/11 08:54 AM, Gary Mills wrote: On Tue, May 24, 2011 at 06:26:33AM -0600, Ken Gunderson wrote: On Tue, 2011-05-24 at 09:21 +0100, Alasdair Lumsden wrote: Hi All, I too don't appreciate the flamewar on here of Solaris vs Linux, sudo vs pfexec. With all due respect, I think the technical signal is high enough to qualify as relevant discussion. My preference would be to: 1. Make root a role 2. Retain sudo as an option 3. Find a secure way to use RBAC for system administration Not surprisingly, that's what we are trying to do, the decision that prompted this sub-thread was about moving in that direction and removing a security issue we'd created with the experimentation in OpenSolaris releases. RBAC. properly configured, is highly secure, but doesn't provide one important thing yet: authentication of the user (using his password) at the keyboard when assuming privileges. A solution to that will happen and allow us to refine what we're doing with Solaris. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] install OSOL 134/sparc fails in LDOM
On 03/ 4/11 04:50 AM, Olaf Bohlen wrote:
Hi,
I want to install OSOL 134 in a LDOM on my T2000 to upgrade to OI 148.
So I got the AI sparc iso from genunix.org and set up my LDOM as following:
-- snip --
(448) foo:/root# ldm list -l osol
NAME STATE FLAGS CONSVCPU MEMORY UTIL UPTIME
osol active -n 50016 4G 0.0% 1d 19h 6m
SOFTSTATE
Solaris running
MAC
00:14:4f:bb:cc:f3
HOSTID
0xaabbccf3
CONTROL
failure-policy=ignore
DEPENDENCY
master=
VCPU
VIDPIDUTIL STRAND
0 8 0.1% 100%
1 9 0.0% 100%
2 10 0.0% 100%
3 11 0.0% 100%
4 12 0.1% 100%
5 13 0.0% 100%
MEMORY
RA PA SIZE
0x8000x20800 4G
VARIABLES
auto-boot?=false
NETWORK
NAME SERVICE DEVICE MAC
MODE PVID VID MTU
vnic2vsw1@primarynetwork@0
00:14:4f:bb:cc:ed1 1500
DISK
NAME VOLUME TOUT DEVICE SERVER
MPGROUP
dvd1 sol10u9-iso@primary-vds0 disk@2 primary
zdisk0 osol-zdisk0@primary-vds0 disk@0 primary
dvd0 osol-iso@primary-vds0disk@1 primary
VCONS
NAME SERVICE PORT
osol primary-vcc0@primary5001
-- snip --
I configured also an Sol10 U9 iso as dvd1 to the LDOM for testing purposes.
So, when I boot up from dvd0 the install hangs:
-- snip --
Sun Fire T200, No Keyboard
Copyright (c) 1998, 2010, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.30.4.b, 4096 MB memory available, Serial #aabbccdd.
Ethernet address 0:14:aa:bb:cc:dd, Host ID: aabbccdd.
{0} ok boot dvd0
Boot device: /virtual-devices@100/channel-devices@200/disk@1 File and args:
SunOS Release 5.11 Version snv_134 64-bit
Copyright 1983-2010 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: opensolaris
Remounting root read/write
Probing for device nodes ...
Preparing automated install image for use
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass):
-- snip --
After a bit debugging I think the reason is that the wanboot driver is
not correctly loaded, so the image on the iso containing the wandboot
config can't be mounted and the wanboot.conf of course cannot be
loaded.
-- snip --
root@:/lib/svc/method# more ./live-fs-root-minimal
[...]
#
# Depending upon how we are booted, enable either the
# 'live-media' instance or the 'net' instance of the
# filesystem/root service
#
if [ $ISA_INFO = sparc ]; then
# check if the wanboot device exists
BOOTFS_DISK=/devices/ramdisk-bootfs:a
if [ -b $BOOTFS_DISK ]; then
#
# booting off of the net
/usr/sbin/svcadm enable svc:/system/filesystem/root:net
/usr/sbin/svcadm disable svc:/system/filesystem/root:media
fi
else
MEDIA=`$PRTCONF -v | $SED -n '/install_media/{;n;p;}'`
if [ ! -z $MEDIA ]; then
/usr/sbin/svcadm enable svc:/system/filesystem/root:net
/usr/sbin/svcadm disable svc:/system/filesystem/root:media
fi
fi
root@:/lib/svc/method# ls /devices
iscsipseudo:devctlscsi_vhci
iscsi:devctl ramdisk-root scsi_vhci:devctl
options ramdisk-root:a virtual-devices@100
pseudo ramdisk-root:a,raw
-- snip --
Can anybody confirm this (and has a work-around)?
No, the wanboot fs only appears if you've booted from the network; in
this case you've booted from a local CD (virtually). It's possible this
didn't work in LDOMs back in 134, as the devices present a little oddly
there; I just don't remember. Your workaround in that case would be to
set up an AI server and boot it from the net.
Dave
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Proposal: OpenIndiana Stable Branch
On 01/18/11 05:01 PM, Alasdair Lumsden wrote: On 18 Jan 2011, at 18:31, Gordon Ross wrote: Dave Miner writes: [...] Perhaps refactoring of Caiman is needed, where the Live CD ships with a pkg repo, starts a pkg server, and does an install from that. Not sure how feasible this would be. Given how complete pkg is, probably not all that hard. We looked into this a little quite some time ago. The problem with doing IPS-based installation from CD's or DVD's is that IPS's data access patterns during package installation are relatively random, not streaming, and so you will get utterly abysmal installation performance (orders of magnitude worse than anything you've ever used) when using physical CD or DVD media. That storage technology just isn't designed for random access. This doesn't apply much if you're using an ISO image as a virtual CD or using USB flash memory media. Dave Interesting. Thanks, Dave. Yes - thank you for this info, very helpful! One way around that is to do sort of a two stage install, where the first stage, running from the CD installs a bare minimum system (from a cpio image or whatever, to avoid the problems with poor random-access to the CD). Then for the second stage, boot into the new bare-minimum system and finish the install from IPS, perhaps allowing use of the CD as your repo, or a local copy, or get it off the net... This sounds like something worth exploring. There are a few options here.. just thinking out loud, a possibility would be: 1. Install the minimal base via CPIO 2. If more packages are requested than base, then extract the pkg repo to ram (tmpfs) or local disk 3. Install the additional software requested via pkg This may bump the RAM or Disk space requirements to do an install, but the OS needs a lot of that to run anyway. It will greatly increase both, in my experience, as any interesting package repo would seem to be quite large (multiple GB) and pkg has pretty substantial overhead in generating and executing a plan. Really, you'd probably be better off booting into the installed system before adding more software. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Proposal: OpenIndiana Stable Branch
On 01/17/11 05:44 AM, Alasdair Lumsden wrote: Hi Gabriel, On 01/17/11 10:07 AM, Gabriel de la Cruz wrote: Thanks! A place to start is a place to start, and an stable server release is the most urgent one among all the other options. Great - thanks for the feedback! Some people is talking about the server-desktop question, I particularly liked the old Solaris software groups concept (reduced network, core, end user, entire)... woulnt it be posible to have a non stable distro featuring the full range of up to date software, and a stable conservative one (behind in innovation but ahead in stability) allowing to either just keep the fully suported core of software or to add as well a less supported desktop enviroment?. Wouldnt this be almost same effort, example: Well, the thing is, this is already the case. All people have to do is use the Text Installer ISO (Or the Automated Installer ISO) - this installs a much smaller subset of software which doesn't include the full Gnome desktop software. Effectively the text installer ISO is the server release and the Live CD ISO is the desktop release. Perhaps we need to name them such to avoid the confusion, as it seems a lot of people on-list are confused about this. Unfortunately the Text Installer still installs quite a fat install, due to some packaging that needs improvement. Alan Coopersmith pointed us at some bugs on bugs.opensolaris.org related to this which was pretty helpful: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=7010355 - splitting tk bindings out of the core python package http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=7010324 - splitting X apps out of the core groff package http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6574610 - splitting glib out of the gnome-base-libs package The only differences between a server install and a desktop install are the packages installed, and they're already split up into fairly reasonable incorporations. I think the situation with OpenSolaris only having a graphical LiveCD for so long has led people to think that OpenSolaris and thus OpenIndiana is mainly a desktop OS. So I am starting to think that we should rename the Live CD to OpenIndiana-Desktop and the Text Installer to OpenIndiana-Server. Ideally the graphical installer, Caiman, would let you choose which package incorporations to install. But unfortunately I think it does a dumb install from a cpio archive. Perhaps refactoring of Caiman is needed, where the Live CD ships with a pkg repo, starts a pkg server, and does an install from that. Not sure how feasible this would be. Given how complete pkg is, probably not all that hard. We looked into this a little quite some time ago. The problem with doing IPS-based installation from CD's or DVD's is that IPS's data access patterns during package installation are relatively random, not streaming, and so you will get utterly abysmal installation performance (orders of magnitude worse than anything you've ever used) when using physical CD or DVD media. That storage technology just isn't designed for random access. This doesn't apply much if you're using an ISO image as a virtual CD or using USB flash memory media. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] patchadd: will it be used
On 12/28/10 02:39 PM, Edward Martinez wrote: On 12/28/10 16:47, Alan Coopersmith wrote: patchadd is already obsolete, and was removed from the OpenSolaris distro long ago, thanks for notifying me patchadd is no longer in use. i was under the impression it in some capacity was still in use, because OI has patchadd man page. We hadn't been particularly diligent about removing some of the obsolete man pages from OpenSolaris until fairly recently. OpenIndiana is just not yet caught up to where those removals occurred. Dave ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
