clear

if a scsi hba is updaing pkt_resid upon command completion (either success or partial transfer w/ error), should STAT_XFERRED_DATA be set in pkt_state?

or maybe saying it differently, are there any situations where you'd update pkt_resid and _not_ set STAT_XFERRED_DATA ?

#define STATE_XFERRED_DATA 0x08 /* Data transfer took place */

This stuff was always a bit unclear to me but I believe that is what it means, yes

[illumos-gate] 15349 dtrace should accept comma after last item in enum -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15379 libefi: efi_getenv should return buffer size with EFI_BUFFER_TOO_SMALL -- Toomas Soome <tsoome⊙mc>

[illumos-gate] 15373 Don't print cmdname of a.out core file on _LP64 platforms. -- Marco van Wieringen <marco.van.wieringen⊙pen>

ok -- that's what I thought, but just want to be sure there wasn't some subtlety i missed

[illumos-gate] 15378 multiboot2.h: MULTIBOOT_MOD_ALIGN is generic constant -- Toomas Soome <tsoome⊙mc>

andyf: since jperkin is on vacation and we forgot: Could you give my two ld fixes a spin over omnios and omnios-extra? Extra useful if you have binutils 2.40 in the mix to really check it out.

danmcd: and anything else you might want I've badly expressed.

THe works-with-2.40 is icing on the cake AFAIC.

Anyone with thoughts, recommendations on brandx for applications? Are the branded machines implemented?

So I can run archaic AIX within archaic Solaris?

for example.

Is the lx brand, "advertised" on Wikipedia present? Any way to implement the zone under a code space?

How much of the Sun developer environment is implemented under Illumos? Any?

Is it best practices to spin Python or even Jira/Java constructs rather than traverse the brand zones?

The lx brand is present in OmniOS and SmartOS.

Then topicbox is a good resource on these issues?

With the four year old topics on Smartos and Omnios - which appears to include people in this room?

It kinda suggest my expectation that the bhyve just implemented should have the look and feel of minix on top of DOS.

Might not be far off the bow.

Well the zones guides also exist for bHyve omnios.org/info/bhyve_kvm_brand.html

but branded zones just re-interpret system calls, they don't emulate other CPUs, so if you created an AIX brand, it would only work with x86 binaries not Power or PowerPC

creating such a brand would be quite challenging, as you'd need to find both the libraries from an ancient AIX/x86 release and documentation of their system calls detailed enough to completely reimplement them on top of the Solaris kernel

err, illumos kernel