Bernd Haug's questions

Is there any way to log a whole machine / Docker daemon into a registry?

Everything I see about docker login and various proprietary credentials helpers uses ~/.docker/config.json, i.e. is per-user.

I have a situation where I would like to pull images from a private registry; multiple people have both arbitrary sudo access on those machines and should be able to use Docker against our registry.

Since Docker access should be read as root access to a machine anyway (i.e. user credentials are not mutually safe if they can run Docker), and sudo access is same but directly, I would like to just cut to the chase and log the whole machine in without every user having to jump through hoops.

I could provide one file that everyone could link to their config.json, but I would prefer if it was just taken care of from the first login on each machine.

On Snow Leopard, I can give access to services like SSH only to specific users by using the "only these users:" option in the sharing tab of the System preferences.

This is bothersome to use when configuring multiple machines, and some accounts such as the root user do not show up there, so I'd like to script it.

Is there a way to add access to given services to arbitrary users on the command line?

I have a bunch of .to6-Files that get opened without a problem with FileMaker Server 9 on Mac.

Now I copied them to a Windows box with FMS9, and they are not even detected by the admin console. Is there anything Mac-specific about ".TO6"-Files?

We have a new iMac on Snow Leopard authenticating against an OpenLDAP directory. Homes are on (automounted) NFSv3 (Linux, kernel-server).

NFS seems to work pretty well (if a bit slow, but we don't want to risk not using locking).

When a user logs in using an LDAP account, however, weird things happen: Sometimes the machine hangs even before all the Desktop icons had been initialized, sometimes the user can work for a little while, but after a while the machine starts hanging: New processes by the user don't get off the ground, old processes cannot be quit (even force quit hangs). Sometimes early on, sometimes later, the dock doesn't react at all (does not show context menu for programmes) and the Finder won't take focus.

All the same, even if everything else seems to hang, I can log in via SSH and at least cleanly reboot the machine. SSH login works even for LDAP users. If I disable LDAP, everything seems to work normal for local users.

We used the OpenLDAP directory with RFC 2307 mapping. We only really use it for account data, so I tried removing any mappings except the Person, User and Group mappings in the Directory Utility. Both mappings have the same resulting misbehaviour.

Edit: This seems to be the same problem as this gentleman has: Apple Forums 1/2

If I install Leopard on an Intel Mac 32 bit and make a SuperDuper! copy of it, will I be able to deploy that image to Intel and Power Macs and have it boot on both?

Will that image support 64 bit apps on x64 Intel Machines or G5 Power Macs?

Due to a special customer requirements situation, I'm in a position where I will have to run two old (rather, one old and one ancient) FileMaker Server instances -- 5.5 and 9.

If at all possible, I'd like to run both of those on one(!) Windows XP Pro machine.

Setting aside the security implications (which can be controlled rather reliably in this setting) - is it possible to run FMS 5.5 and 9 on one machine?

Will they both work on Windows XP Pro?

FileMaker states that FMS 5.5 on XP is not "supported", but -- will it work in practice? 5.5 is EOL'd anyway and I need to keep this setup running for a while longer, until the replacement can be put into service.

(Reasoning for doing a new setup with this: They databases have been served from two Macs that will be consolidated into windows VM(s) - one if at all possible.)

I have a customer - a small business where IT is a cost center, not a profit driver - with six high-end PowerPC machines (dual-CPU Power Mac G5, 2G RAM, the works...).

These machines will shortly be obsolete because Snow Leo won't support them:

Performance-wise, those boxen would be enough for them pretty much until heck freezes over[a] but since Apple seems to EOL everything older than the previous release even for security fixes, the machines will be obsolete within about 1.5y.

Few major upgrades for third-party software come out for old Mac OS releases, degrading their value even before that.

Age-wise, they are in the awkward spot where they're pretty much written off, but still in very good shape.

Austrian law for companies (not incorporated) applies to this, just in case that is important for your ideas.

So, finally, the question: What to do? I have thought of the following things:

• Trying to go for a good buy-back offer and upgrade?
• Same, but with leasing the new kit (the owner doesn't like leasing too much, but in this situation there might be an exception)?
• For the versions above: ASAP, ALAP, something in between?
• Giving them to a school (charitable institution, etc) right now and take a tax credit for the remaining value on the books?

What do you think of those? Other ideas are welcome, too, of course.