Jumpstart , smf and scripts on first boot

Could anyone help me I am trying to work out how which is the best way to apply patches and customizations on first boot of a new machine that has just been jumpstarted. Does anyone have a example of a service that runs once to allow me to do this?

I want to be able to not just add patches I need to
add packages make system changes I used to be able to
do this with /etc/rc2.d scripts but now its smf in
solaris 10 and I need to be able to make this changes
at run level 2 and then reboot.You can do it just like before. Put a script in /etc/rc2.d.
You can also create a SMF manifest, and a custom "site" profile to activate/deactivate the services you want. Put them into the manifest and profile directories and they'll be loaded and activated/deactivated at first boot.
Darren

Similar Messages

Running unix scripts on first boot after imaging

Hi,
I have a setup in which student users at the school I work for log in via AD to create a mobile account on the local system. This all works great in snow leopard so far, the issue i am having is I have a couple of bash scripts that run at boot. They run ok, but one script opens up the folder the script is located in (script does run, and the folder doesn't open the next time a student logs in), and I also have a Acceptable Use Policy PDF the opens up on log in, the first time a user logs into a system, it opens in Safari, the second time it opens it is in Preview (I want it to open in preview each time).
These problems aren't exactly show stoppers, but they are pretty annoying (especially since students log in to 5 or 6 different computers per day, so the errors show up 5 or 6 time per day for the users.)
Any suggestions to get this fixed would be greatly appreciated!

osascript -e 'tell application "Preview"' -e 'open file "path:to:file.pdf"' -e 'end tell'

Razer Kayboard/Mouse and Mac Mini first Setup/Boot

G'day Apple Support Communities,
I'm purchasing a new MacMini in a few weeks. I'm wondering whether the new mac can detect/setup the mac compatible Razer kayboards and mouses upon first boot/setup. As I understand, a new mac will go through various steps, to select language and timezone. But when it needs to pair kayboards and mouses, will it detect the Razer gaming keyboards/mouses.
Kayboard: Razer BlackWidow Ultimate
http://au.razerzone.com/gaming-keyboards/mechanical/razer-blackwidow-ultimate/
Mouse: Razer DeathAdder
http://au.razerzone.com/razer-deathadder/
Both peripherals claim to be Mac Compatible
Ta, flakefrost

hey!
any mac can detect any usb mouse or keyboard, but depending on the company and the peripheral it's full functionality can be impaired or completely absent. for example the blackwidow ultimate keyboard has specific function keys for mac os x (mission control/expose) and a built-in macro automatization system which cannot be used without the driver for the keyboard. so the point is that you need the drivers :-)
i have a razer blackwidow ultimate mac edition and a razer mamba 2012.
the correct installation is as follows:
1.) go to razerzone.com
2.) move mouse over support
3.) klick on drivers, software, manuals
4.) find your product
5.) download mac drivers
6.) install drivers
7.) plug in devices
you have to restart after each individual driver installation and you should plug in the device after both drivers are installed, not before or during installation.
last but not least the mac drivers are only compatible with mac os 10.5-10.6, mac os 10.7 lion is not compatible with the drivers. i found out the hard way through freezing of the computer and kernel panics. after a clean install of lion and the drivers, i had a kernel panic the second time i turned it on after the clean installation. @ Razer: where are the updates??!! :-(

[solved] Large number of services enabled during first boot

I just set up Arch Linux on a VM and was surprised to see a large number of services enabled in systemd during the first boot, including ftpd! I have set up several Arch Linux installations before, and have never encountered this before.
To be sure, I installed a second time. While still booted in the install ISO, I checked and verified that only a few services were enabled. After the first boot into the system, sure enough, a large number of services were enabled.
Any ideas as to what might be causing this?
Edit #1: found the following in journalctl. It looks like a bunch of packages are missing systemd preset files, and services that are missing preset files are enabled by default.
Edit #2: filed a bug report: https://bugs.archlinux.org/task/41711
Edit #3: until this is fixed, a workaround is to get systemd-214-2 from ARM and downgrade to that before your first boot into the new installation. After you've booted, you should be able to upgrade back to the current systemd and have everything work out.
Edit #4: Fixed in systemd-216-3. If you installed and rebooted prior to 216-3 hitting [core], see here for a proper fix.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-root-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-networkd-wait-online.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about busnames.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-remount-fs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nscd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup-dev.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rlogin.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-trigger.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-config.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about gpm.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about paths.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system-update.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about quotaon.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about final.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-modules-load.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-kernel.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-mqueue.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kpropd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-parse-etc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-reboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.resolve1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kadmind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ftpd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about krb5-kdc.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about graphical.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysusers.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-kernel-debug.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-vconsole-setup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ldconfig.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about machine.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-flush.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rescue.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.timedate1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about proc-sys-fs-binfmt_misc.automount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-firstboot.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-catalog-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sockets.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hybrid-sleep.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-initctl.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-resolved.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hibernate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-wall.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-logind.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sys-fs-fuse-connections.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-done.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about slices.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about iptables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-quotacheck.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about tmp.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-done.timer.
Aug 27 02:53:41 host systemd[1]: Preset file says disable console-getty.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-localed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about printer.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.locale1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsh.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-timesyncd.service.
Aug 27 02:53:41 host systemd[1]: Preset file says disable kexec.target.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-collect.service.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-drop.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about suspend.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about mkinitcpio-generate-shutdown-ramfs.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable [email protected].
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-update-utmp-runlevel.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about cryptsetup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-fs.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about smartcard.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-ask-password-console.path, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-random-seed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about uuidd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about basic.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about remote-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dhcpcd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about logrotate.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshdgenkeys.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-fsck-root.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-suspend.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about swap.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.login1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-readahead-replay.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journald-dev-log.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about timers.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable rescue.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about user.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-sysctl.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about fstrim.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sysinit.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hybrid-sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dev-hugepages.mount, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-hwdb-update.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-upload.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-shutdownd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about emergency.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-user-sessions.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sound.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable poweroff.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dbus.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable systemd-journal-gatewayd.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about talk.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable remote-fs.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about system.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about bluetooth.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable syslog.socket.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about getty.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-kexec.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable halt.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about -.slice, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-online.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sleep.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about dm-event.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-tmpfiles-clean.timer, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about kmod-static-nodes.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about multi-user.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.machine1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about hibernate.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says enable systemd-networkd.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about nss-user-lookup.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-halt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about umount.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-timedated.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd-control.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about ip6tables.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sshd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about time-sync.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about updatedb.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about sigpwr.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-poweroff.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-udevadm-cleanup-db.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rpcbind.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shadow.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about network-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-switch-root.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable debug-shell.service.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-hostnamed.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about [email protected], enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about telnet.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file says disable reboot.target.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about org.freedesktop.hostname1.busname, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about rsyncd.socket, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-machined.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about local-fs-pre.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-journal-remote.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udev-settle.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-binfmt.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about systemd-udevd.service, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about shutdown.target, enabling.
Aug 27 02:53:41 host systemd[1]: Preset file doesn't say anything about initrd-cleanup.service, enabling.
Aug 27 02:53:41 host systemd[1]: Populated /etc with preset unit settings.
Things enabled before first boot (based on contents of /etc/system/systemd/*.wants):
getty.target.wants:
* [email protected]
multi-user.target.wants:
* [email protected]
* iptables.service
* remote-fs.target
* sshd.service
sysinit.target.wants:
(none)
Stuff additionally enabled and started during first boot (also based on /etc/system/systemd/*.wants):
default.target.wants:
* systemd-readahead-collect.service
* systemd-readahead-replay.service
multi-user.target.wants:
* dhcpcd.service * krb5-kpropd.service
* fstrim.service * nscd.service
* ftpd.service * rsyncd.service
* gpm.service * systemd-journal-upload.service
* ip6tables.service * systemd-networkd.service
* krb5-kadmind.service * systemd-resolved.service
* krb5-kdc.service
sockets.target.wants:
* krb5-kpropd.socket * systemd-journal-remote.socket
* rlogin.socket * talk.socket
* rsh.socket * telnet.socket
* rsyncd.socket * uuidd.socket
* sshd.socket
sysinit.target.wants:
* dm-event.service
* systemd-timesyncd.service
system-update.target.wants:
* systemd-readahead-drop.service
Explicitly installed packages:
dhcpcd iputils procps-ng systemd-sysvcompat
diffutils linux-grsec psmisc tar
dnsutils logrotate reflector vim-systemd
file mlocate rsync wget
gradm mtr s-nail which
grub openssh screen whois
inetutils pacman
Last edited by tazmanian (2014-09-10 23:11:42)

+1.
Here is the ports these services are listening:
$ ss -tpl
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 *:llmnr *:*
LISTEN 0 128 *:ssh *:*
LISTEN 0 128 :::llmnr :::*
LISTEN 0 128 :::19532 :::*
LISTEN 0 128 :::tell :::*
LISTEN 0 128 :::ssh :::*
LISTEN 0 128 :::telnet :::*
LISTEN 0 128 :::login :::*
LISTEN 0 128 :::shell :::*
LISTEN 0 128 :::rsync :::*
LISTEN 0 128 :::git :::*

Interactive service at first boot after jumpstart

I have a lot of issues/questions with smf, so this posting is abit long. Sorry for that.
So far we have installed our own software by jumpstarting entire Solaris, copying an rc script to rc2.d , rebooting, then have that rc script to the rest of the installation. This was necessary as some important parts of the installation required daemons that are installed and started at the early stages of that rc script. It cannot be done from the finish script with everything mounted under /a. And, to make things more complex, at the end of the installation I have some interaction prompting certain passwords.
This whole mechanism blew up with the introduction of smf. So I started reading about smf and am trying to convert all this to a service.
So far I have found that I need to setup a transient single instance service, with a :true stop method, my initial rc script in /lib/svc/method/oluinstall as the start method, the service enabled by default and put the manifest in /var/svc/manifest/site/oluinstall.xml. I have a manifest that I believe to be OK. All files in /var/svc and /lib/svc would be copied there by the finish script.
What is not yet clear to me is:
a) how to get all the output to be displayed on the console instead of (or in addition to) redirecting it all to a smf logfile and
b) how to become interactive, despite this stronlgy being discouraged?
Are any of these possible? Or is there another solution to my initial installation problem?
I haven't had a chance to test my manifest as I have hit another problem that is mentioned in the Beta 7 Bugs of the Release Notes: autofs does not start (5084183). I have adjusted my finish script to create /a/etc/defaultdomain to make keyserv happy, but autofs does still not come up. svcs reports various services as offline or unitialized and the system does not get to the multi-user-server milestone:
offline        15:41:34 svc:/network/inetd-upgrade:default
offline        15:41:34 svc:/network/inetd:default
offline        15:41:34 svc:/milestone/multi-user-server:default
offline        15:41:36 svc:/network/nfs/client:default
offline        15:41:36 svc:/system/filesystem/autofs:default
offline        15:41:36 svc:/system/dumpadm:default
offline        15:41:37 svc:/system/fmd:default
offline        15:41:38 svc:/application/print/ipp-listener:default
offline        15:41:39 svc:/system/zones:default
offline        15:41:41 svc:/network/nfs/server:default
offline        15:41:44 svc:/network/smtp:sendmail
uninitialized 15:41:36 svc:/network/rpc/gss:ticotsord
uninitialized 15:41:37 svc:/network/security/ktkt_warn:ticotsord
uninitialized 15:41:37 svc:/network/telnet:default
uninitialized 15:41:37 svc:/network/rpc/smserver:default
uninitialized 15:41:40 svc:/application/print/rfc1179:default
uninitialized 15:41:40 svc:/network/nfs/rquota:ticlts
uninitialized 15:41:41 svc:/network/nfs/rquota:udp
uninitialized 15:41:41 svc:/network/ftp:default
uninitialized 15:41:42 svc:/network/finger:default
uninitialized 15:41:42 svc:/network/login:rlogin
uninitialized 15:41:42 svc:/network/rpc/rstat:udp
uninitialized 15:41:43 svc:/network/rpc/rusers:udp
uninitialized 15:41:43 svc:/network/shell:tcp
uninitialized 15:41:43 svc:/network/shell:tcp6onlyThis impacts my oluinstall script as it depends on automounter running. I tried a lot of things but I don't know how to have the autofs service up by default after a fresh jumpstart with no NIS/NIS+ configured and an exsiting /etc/defaultdomain. Can you help here?
I also tried to validate my manifest with svccfg validate and all I got was "couldn't parse document". Not very helpful. I used a toll called "rxp" that I got fro ma colleague to help find me the problems. When I fixed that I now get the following:
# svccfg validate oluinstall.xml
oluinstall.xml:17: element service: validity error : Element service content does not follow the DTD, expecting (create_default_instance? ,
single_instance? , restarter? , dependency* , dependent* , method_context? , exec_method* , property_group* , instance* , stability? ,
template?), got (create_default_instance single_instance dependency dependent exec_method method_context exec_method property_group stability
template )
svccfg: Document is not valid.
Well, I guess I need to include my manifest now as well ...
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">

<service_bundle type='manifest' name='ubsjpstrt:oluinstall'>
<service
     name='site/oluinstall'
     type='service'
     version='1'>
     <create_default_instance enabled='true' />
     <single_instance />
     <dependency
          name='oluinstall_multi-user'
          type='service'
          grouping='require_all'
          restart_on='none'>
          <service_fmri value='svc:/milestone/multi-user' />
     </dependency>
     <dependent
          name='oluinstall_multi-user-server'
          type='service'
          grouping='require_all'
          restart_on='none'>
          <service_fmri value='svc:/milestone/multi-user-server' />
     </dependent>
     <exec_method
          type='method'
          name='start'
          exec='/usr/bin/rcwrapper /lib/svc/method/oluinstall'
          <method_context>
               <method_credential user='root' group='root' />
          </method_context>
          timeout_seconds='0' />
     <exec_method
          type='method'
          name='stop'
          exec=':true'
          timeout_seconds='3' />
     <property_group name='startd' type='framework'>
          <propval name='duration' type='astring' value='transient' />
     </property_group>
     <stability value='Unstable' />
     <template>
          <common_name>
               <loctext xml:lang='C'>
                    OLU Base jumpstart installation
               </loctext>
          </common_name>
          <documentation>
               <manpage title='oluinst' section='1M'
               manpath='/usr/share/man' />
          </documentation>
     </template>
</service>
</service_bundle>Finally, at the end of my install script, I need to remove the service as I need it to run only once. Before smf the rc script simply removed itself. How do I do this now?
svcadm disable svc:/site/oluinstall
svccfg delete svc:/site/oluinstall
Is that correct?
Thanks for any help!
- Tom

Tom:
Great questions. I'll try to answer them in order.
What is not yet clear to me is:
a) how to get all the output to be displayed on the console instead of
(or in addition to) redirecting it all to a smf logfile and
b) how to become interactive, despite this stronlgy being discouraged?Becoming a console interactive service requires two parts:
- You need to redirect your input and output to /dev/console. Example
services which do this are kdmconfig (x86 platforms) and the
sysidtools (all platforms)--that is, your fellow interactive services.
Please attempt to keep your error messages going to the logfile by
making the redirection only for specific commands, and not the entire
start method.
- More importantly, you also have to insert yourself before any of the
console-occupying login services and after the last of the configuration
services. On workstations, this set of services includes GDM (for
GNOME/JDS) and possibly CDE, depending on build.
(We're going to make this a little easier and then much easier in the
future. But you should only write interactive services if you are the
systems deployer, and not a software vendor.)
You can use svcs -l to list the dependencies on console-login, like so
$ svcs -l console-login
fmri         svc:/system/console-login:default
name         euro-friendly console login
enabled      true
state        online
next_state   none
restarter    svc:/system/svc/restarter:default
contract_id 133
dependency   optional_all/none svc:/platform/i86pc/kdmconfig:default (online)
dependency   exclude_all/none svc:/application/gdm-login:default (disabled)
dependency   require_all/none svc:/system/sysidtool:net (online) svc:/system/sysidtool:system (online)
dependency   require_all/none svc:/system/utmp:default (online)
dependency   require_all/none svc:/system/identity:node (online)
dependency   require_all/none svc:/system/filesystem/local (online)
I haven't had a chance to test my manifest as I have hit another
problem that is mentioned in the Beta 7 Bugs of the Release Notes:
autofs does not start (5084183). I have adjusted my finish script to
create /a/etc/defaultdomain to make keyserv happy, but autofs does
still not come up.I would actually disable keyserv, as what's happening is nfs/client is
probably enabled and getting stuck. The best way to report on this is
to run "svcs -xv".
I also tried to validate my manifest with svccfg validate and all I
got was "couldn't parse document". Not very helpful. I used a toll
called "rxp" that I got fro ma colleague to help find me the problems.
When I fixed that I now get the following:
# svccfg validate oluinstall.xml
oluinstall.xml:17: element service: validity error : Element service
content does not follow the DTD, expecting (create_default_instance? ,
single_instance? , restarter? , dependency* , dependent* ,
method_context? , exec_method* , property_group* , instance* ,
stability? , template?), got (create_default_instance single_instance
dependency dependent exec_method method_context exec_method
property_group stability template ) svccfg: Document is not valid. We ship xmllint(1), but I agree that svccfg validate should be more
helpful. Anyways, the point is that your method_context element needs to
precede your exec_method elements. If you want to override a single
method's context, you embed the method_context element.
/var/svc/manifest/network/ldap/client.xml has a non-trivial example.
Finally, at the end of my install script, I need to remove the service
as I need it to run only once. Before smf the rc script simply removed
itself. How do I do this now?
svcadm disable svc:/site/oluinstall
svccfg delete svc:/site/oluinstallWe have use a similar approach for singly-run upgrade services, like
network/inetd-upgrade. I discourage deleting the service (and deletion
after disable is a race between the restarter and the repository anyway).
I hope these answers are helpful.
- Stephen

Need script to run on first boot then remove itself

I am working on panther and tiger images to deploy in labs at middle schools. There is a piece of software that the district owns that is network aware and each computer on a network running this software needs its own individual station number set in a config file. I have written a script that will set this number to be the last 3 digits of the static ip address of the computer and i can run this from ard on multiple computers but i would like to somehow include this script in the image so it is run the first time the computer boots up after being cloned and then does not run again. We also use virex on these computers and when we clone with virex installed we are having problems updating the defs. I would like to also be able to have a folder with the virex package file in it and on first bootup after the clone have a script run and install virex on the first boot.
I am sure this is not too difficult but I have not done anything like this before, maybe a couple oneliners to get me started, Thanks.
Do not want to use post action items in netrestore.
Mark

You may want to post your question in the Unix discussions:
http://discussions.apple.com/forum.jspa?forumID=735

How can I find what apple ID I used to register my iMac when I first booted up? I am being told that by using this ID I will be able to go on to the App store and down load iPhoto at no cost. Is this true? My iMac does not have iPhoto resident on it now

How can I find what apple ID I used to register my iMac when I first booted up? I am being told that by using this ID I will be able to go on to the App store and down load iPhoto at no cost. Is this true? My iMac does not have iPhoto resident on it now and I only purchased my new iMac in December 2012
Thanks....

Launch Keychain Access and click on Login in the left hand pane and then on Passwords. Next do search for Apple in the search field at the top and click on Apple ID Authenicication in the list that comes up. That will give you the ID no. and password.
OT

Mac Mini first boot and bluetooth keyboard not recognised

Hi Apple Support Community-
I have just purchased a brand new Mac Mini and App Wireless Keyboard. Unfortunately upon first boot, the Mac Mini is requesting I connect my bluetooth keyboard by switching it on, however even though the green light flashes, after the 5 second startup acknowledgement, there is no response from the Mac Mini.
To confirm the keyboard is working, I have successfully paired it with my MacBook. I do not have a USB Keyboard or Mouse and without purchasing additional hardware, do you have any suggestions to work around this problem?
Thanks, Julian

Hi Julian,
Sometime a Mac can't pickup the connection of a bluetooth keyboard or mouse is normal. Whatever your Mac is brand new or not.
I will do the following if the brand new Mac can't pickup the bluetooth connection, but make sure the bluetooth keyboard and mouse is not yet paired with other computer, that means you have to un-pair the keyboard and mouse from your MacBook before you perform the follow step:
- Switch off the Mac
- Switch off the Keyboard and Mouse which not yet paired with other computer, remove its battery, and re-install the battery after 10 seconds
- Switch on the Keyboard and Mouse first, make sure both devices have a green light flashes (the light flashed at intervals, like a pulse **...**...sorry my poor English), that means the devices is discoverable.
- Switch on the Mac asap if all the bluetooth keyboard and mouse is ready, and let the Mac pair both device (according the screen instruction)
If the method still doesn't work, the worst case is: i'm afraid you have to connect wired keyboard and mouse to finish the Setup Assistant, and pair both bluetooth devices by Bluetooth Preferences. Once both bluetooth devices connected, disconnect wired keyboard and mouse.

Upgrade and Install fails after first boot. Then I am unable to repair

I don't know if anyone else has experienced this?
I've experienced the aqua screen of death with the Upgrade option and was unable to resolve it, even after trying the APE removing technique.
So, I decided to restore back to Tiger 10.4.10 (thanks to Super Dupering prior to upgrade) and try the archive and install option. All appeared to go well, installed fine, allowed me to login and run all my apps. But, upon doing my first reboot after the 'sucessful' install the system just hangs at the gray screen. I tried using Disk Utility from the Leopard DVD, but it's unable to repair permissions.
I got this error message: 'The underlying task reported failure on exit'. Tried many times, I also tried the /sbin/fsck -fy in single user mode.
I tried booting into DiskWarrior 4's. Once in DW4 I ran the Repair function there... Here I got another error message.
This error being: 'Error -9997'.
OK I thought, something random must have happened. Soooo I restored to Tiger again and ran the Archive and Install option once again.
I'm am again experiencing the exact same problems with freezing gray boot screen and the inability to repair permissions (all after doing my first boot after sucessful install and login/opening of many apps)
Please please please can anyone she some light on this problem???
I'm going to try one more option:
Upgrade after I've disable all startup options and removing anything to do with APE....
I will report back!
This is really really crap Apple, I can't believe I've spent £85 and probably 15 hours on this sloppy release. Utterly disapointed

Just me it seems then....
Right, I think it's finally resolved, only after the fifth time. I've now rebooted twice and so far so good.
There was a new message when I powered down for the first time, something along the lines of:
Please wait while your Boot Caches are updated.
This seems to be a reasuring message, I feel almost confident in restarting again.
I upgraded using the following method:
1. Disabled ALL startup items (System Preferences>Accounts>Login items)
2. Removed all traces of APE (Application Enhancer) using Finder:
/Library/Preference Panes/Application Enhancer.prefpane
/Library/Frameworks/Application Enhancer.framework
/System/Library/SystemConfiguration/Application Enhancer.bundle
/Library/Preferences/com.unsanity.ape.plist
3. Repaired Permissions
Right, before I perform a new backup I think I'll see how she runs for a week, so I'm sure the boot problem is definitely gone.

MacBook Pro freezes when idle and while first boot.

Hi everyone, sorry for my english i'm not a native speaker.
I have a problem with my MacBook Pro "Core i7" 2.2 15" Late 2011 (MD318LL)
Specs:
- Intel I7-2675QM 2.2GHz
- 4Gb 1333 DDR3
- Radeon HD 6750M and Intel HD Graphics 3000
- 500 GB (5400 RPM)
I bought it while i was in USA it was refubished
Everything was fine while i was in USA.
In russia (yep i'm from russia) macbook started to freeze while first boot (while it cold) and in idle (only in mac os x 10.8.2, i think it's becouse macbook cools down, in windows efi don't give acces to intel hd 3000, so macbook stays hot: cpu 60C\140F )
I changed ram,hdd nothing helped. Ran Apple Service Diagnostic nothing wrong (except for hdd test: error -33000 [wrong drive type] but i think it's becouse of ssd (i changed hdd to ssd to test if hdd is ok)).
Reinstalled Mac OS X same, installed windows same.
Everything fine in startup manager, or while installing mac os x, or while downloading mac os x (cmd+r in start up manager) and laptop is cold.
In games, programs, test everything fine. I think that problem in microcrack (hair crack not sure how in english). Any ideas? Ask any question.

I'm having the exact same issue. It came out of nowhere. I think I should get it serviced first and if will still have it, I will get it fixed.
I have Macbook Pro 2.4 GHz Intel Core 2 Duo with 4 GB 1067 MHz DDR3. I bought this in early 2011 which is 2010 Model.

AMD/ATI fglrx and 3d, only after booting first into windows

I have a x1600pro agp and I can only get 3d acceleration to work if I first boot into windows. Every time after i turn off my PC, i first have to boot into windows or 3d wont work. It also happened with a 9600xt agp card.
I'm wondering if it has happened to somebody else, and if it is because they are agp cards?
It happens connecting with the vga or the dvi outputs of the cards.
Is there a way around this? It gets really annoying having to boot first into windows.
I also think many people having trouble getting they're 3d to work is because of this.
Last edited by tacita (2007-11-07 18:05:45)

tacita wrote:MrWeatherbee: thank you for the link, i have searched high and low (maybe in the wrong places) and didnt find anything before.
Cerebral: yes, but then i guess it is a nice excuse to upgrade. And stay away from the Nforce3.
I congratulate you for making the connection between Windows and 3D functionality in your Linux installation. That's the hardest part to figure out. Loss of hair can result wondering why 3D comes and goes without any apparent reason. However, once you know the secret, the behavior is 100% consistent. I rarely notice it because I rarely turn off the PC in question, and once the correct settings are locked-in by a single boot to Windows, 3D acceleration in your Linux distros will remain through any number of reboots. The only thing that requires a repeat of the Windows touch-n-go is when you power-off.

After install and first boot, Grub shows only flashing cursor

Hi so I recently successfully installed the archlinux image on my netbook. after finishing the config files and rebooting, he started grub normally, I could choose from all the menu entries I set. I had 3 other partitions before I installed arch, these were windows 7 starter, system (dont know what that is, he showed me that under windows but it is unrecognized under linux) and a windows 7 recovery partition (from samsung).
so I first checked if he would boot the windows partition but I forgot also to configure the windows partition entry in the grub config so he loaded the recovery partition. after a reboot he showed me just a black screen with a flashing cursor at the bottom of the display that moves from the left side to the right constantly. there is no error or anything, he even shows the text "loading grub" at the beginning but then I get that screen.
I still can boot my arch live image, here's the output of fdisk -l
/dev/sda1 * 1 1959 15728640 27 Unknown
/dev/sda2 1959 1972 102400 7 HPFS/NTFS
/dev/sda3 1972 20841 151565496 7 HPFS/NTFS
/dev/sda4 20841 30401 76798472+ 83 Linux
also I tried to manually mount the partitions from the live image but I'm still kind of a noob with linux, should this be the right command?
mount /dev/sda4
because that doesnt work, he says he "cant find /dev/sda4 in /etc/fstab or /etc/mtab".
I hope you can help me, thx

well...no I just let pacman do the update (where some things with renaming kernel files were mentioned). but considering the fact that I didnt update the system the first time the problem occured and the fact that booting from the windows recovery partition triggers the problem I dont think that the problem lies within linux or updating.
besides that I dont even come to the grub menu, he only displays "grub loading stage1.5" and then the screen with the cursor comes. He doesnt react on anything I try except the reboot shortcut.
and can you help me with my previous question? "And how can I manually install grub from the live image? I dont want to go through the whole installation again, only overwrite the existing grub and with it the mbr."

Will i be able with Mac mini to connect a wireless keyboard and mouse (via USB) for first boot ?

Please answer . I ask that because I saw on a video showing its first boot , saying" connect a Bluetooth keyboard" . So I am worried . It's about its latest version . Thanks!

If your devices are using a USB dongle, the Mini will
likely see a mouse or keyboard connected via this method as
"wired" devices. These dongles are configured this way
so that the host computer need not know anything about
the wireless connection.

First boot of local zone - how to determine when sysidtool has finished

Hello,
we use a /etc/sysidcfg in order to do the solaris base configuration automatically. After the first boot of a local zone I recognized that some tools are started by solaris (sysidtool, etc.) which apply the settings mentioned in /etc/sysconfig.
Since we want to script some post-install set-ups I need to know, when the first boot including all "first-boot-scripts" has completely finished. Is it possible to query this information, maybe by calliing a special tool or by looking up some string within an logfile?
I would be grateful for any hints,
Thomas

I haven't checked, but I assume they have normal dependencies in the SMF tree so that other services don't start until they complete.
I would probably look at the milestone/multi-user-server service and see if it's online yet. If it is, they're probably done.
Darren

First boot copy files from server

My computers set themselves up from a netboot image (i know, i'm still using monolithic imaging, but plan to learn deploy studio, I swear).
Anyway, it would help me a ton if I could figure out how to have my first boot script copy some directories off the server onto the client, but i'm not sure how to build that command. Can anyone help point me in the right direction?

It's might be easiest inside an action in Deploy Studio - it configures a startup script to do tasks for you after the image is restored, then it cleans the scripts up & reports success to the server. There is no problem with using monolithic images with Deploy Studio either (last time I checked).
Otherwise make a launchd job that runs your own script. Make the job delete the script and launchd plist on completion.
You need to take into account any authentication on the server (don't leave passwords in plaintext) - I assume these files are not on a public/ guest share? Work out how to handle failures so you know which machines need attention. curl or scp could work from shell scripts. Copy it to the image before any deployment is done.
See what others say, but I think Deploy Studio may be worth learning. Apple's System Image Utility had features for doing this too, but Deploy Studio seemed better to me.

Jumpstart , smf and scripts on first boot

Similar Messages

Maybe you are looking for