[oi-dev] adding aok=1 and set zfs_recover=1 to live CD's /etc/system as well?
On 09/10/2012 09:14 AM, Sašo Kiselkov wrote:
I recommend losing some large unused app blobs that nobody needs on a
Live CD. I don't know what you've got in there, but I recommend you
throw out stuff like image editing software and the like. A Live CD is
primarily for installation and rescue, not for regular work.
While we're at it, can we also add these two lines to the live CD's
/etc/system if they're not detrimental to installing OI? It's kind of
annoying to do it from grub when it's needed and I've found them to be
very useful when recovering, but I added them to the installed OS, and
now I'm in a situation where I want to recover from a messed up rpool. (
set zfs:zfs_recover=1
set aok=1
(Obviously don't want those to be added by default to the installed OI,
but rather on the live CD/USB images.)
Not to get too far off topic, but just last week I have my machine that
reboots in a loop before it gets even to single user mode, and even with
these lines, doing zfs import -F -f -R oldrpoolid newpoolname causes OI
to panic and reboot after about 5-6 minutes... last thing I did on it
was to install squid, but I don't believe that caused it.
format/analyze/read shows no bad blocks, booting off the other drive in
the mirror shows the same issue.
So I expect there's some issues where it can't even read the
kernel/drivers fully before it his the wall, so I'm messing around with
zdb trying to get it to rollback whatever got messed up, but the last
thing it said was that rpool was already imported. (I used the zpool ID,
not rpool as a parameter to zdb, but since a live CD wouldn't have an
rpool already mounted, it wouldn't cause this error. There's probably
some way to force the issue... Of the top of my head, I did zdb -e -bbb
{zpoolid} )
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Building a component package
Hi Andreas, I packaged erlang for userland gate more than year ago. So you can take inspiration from here: http://src.illumos.org/source/xref/illumos-userland/components/erlang/ And a bit modern version here: http://src.illumos.org/source/xref/illumos-userland/components/erlang/ To be fair, erlang is one of the worst thing to package in userland gate. Contact me out of the list and we can discuss how you can package things. Best regards, Milan Andreas Stenius píše v út 04. 09. 2012 v 16:01 +0200: Hi, I'm looking into updating the erlang package, and are working on a clone of https://hg.openindiana.org/oi-build/ I've managed to get it to build, but it fails on some package depend stuff, complaining about some dir not being found (defined by COMPONENT_SRC). [ console log: http://pastebin.com/Cvvp7ny5 ] Looking at the make files, I wonder how it could ever have worked... the proto dirs is setup in https://hg.openindiana.org/oi-build/file/d858f73d2aa9/make-rules/ips.mk#l85 as PKG_PROTO_DIRS += $(MANGLED_DIR) $(PROTO_DIR) $(@D) $(COMPONENT_DIR) $(COMPONENT_SRC) However, the component source is unpacked into a source subdirectory of the component dir, defined by SOURCE_DIR as SOURCE_DIR = $(COMPONENT_DIR)/source/$(COMPONENT_SRC) in https://hg.openindiana.org/oi-build/file/d858f73d2aa9/make-rules/shared-macros.mk#l102 So, I'd guess it would work better if the PKG_PROTO_DIRS referenced the SOURCE_DIR rather than COMPONENT_SRC, but then again, I must assume that I'm missing something; since it can't all be so fundamentally broken, now can it? Any pointers to my oversight much appreciated, thank you. //Andreas ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Post 151 development
Hi All, I'll allow myself to add my 2 cents... Alasdair Lumsden wrote: Hi All, I'd like to raise the topic of post-151 development. Jon (Tibble/Meths) - obviously you've been doing great work on the prestable builds. I think I asked when we should ship to /stable, and basically I got the impression you weren't comfortable doing that until we had most of the CVEs fixed and could support it from a security standpoint. I don't think that's realistic right now, as CVEs are coming out faster than we can fix them. So as such, I'd like to propose that one of the next prestables be a candidate for being shipped to /release, rather than /stable and the notion of /stable be abandoned for now. We could do something like aim to push a /release every 6 to 12 months, and we can aim to backport critical bug and security fixes to it from /dev. But it will give users a bit of stability and free us up to move /dev forward faster. That fits in with OpenSolaris, where /release wasn't guaranteed free of security holes (you had to pay for that). Obviously we can still ship CVE and bug fixes to it, but it sets realistic expectations and hopefully addresses your concern with using the name /stable ... Me and my organisation, we're interested in a Solaris replacement OS for some number of infrastructure servers (mail, dns, directory, web, ...). I've seen many people using OI as a home desktop or home server. Some people around me aren't even testing it, but just observing. I have now two physical machines running OI, not yet in production, but I'm testing all software I use - I usually compile them myself. And it seems that, for the moment, all works fine. I think that to begin being really used there should be a official release, as suggested by Alasdair. To do this, it could be enough to solve the serious issues and list the other minors as known issues. Let's say, solve issues preventing OI to be used as a production server. OK, OK, there are more talkers than doers, and I'm one of them... Unfortunately, I was quite busy in the last four years and I'll still be in the next 6 months, but I hope I'll be able to dedicate some time sometime in the future to contribute to oi. Best regards and thank you very much for the enormous good job done here. José-Marcio ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] adding aok=1 and set zfs_recover=1 to live CD's /etc/system as well?
Assertions are a necessary aid to debugging, do not disable them in a default environment, be in the live CD or post-install environment. -- Rich ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
