> Yes, let's ignore Ubuntu or anything else as a > reference and instead > focus on what specific OpenSolaris services you and > others are finding > objectionable. Below's the list of services enabled > on first boot: > > # uname -a > SunOS whitestar1-9.East.Sun.COM 5.11 snv_68 i86pc > i386 i86pc > # svcs > STATE STIME FMRI > legacy_run 17:20:14 lrc:/etc/rcS_d/S50sk98sol > legacy_run 17:21:54 lrc:/etc/rc2_d/S10lu > legacy_run 17:21:55 lrc:/etc/rc2_d/S20sysetup > legacy_run 17:21:55 lrc:/etc/rc2_d/S40llc2 > legacy_run 17:21:55 lrc:/etc/rc2_d/S42ncakmod > legacy_run 17:21:55 lrc:/etc/rc2_d/S47pppd > legacy_run 17:21:55 lrc:/etc/rc2_d/S70uucp > legacy_run 17:21:56 lrc:/etc/rc2_d/S72autoinstall > legacy_run 17:21:56 lrc:/etc/rc2_d/S73cachefs_daemon > legacy_run 17:21:56 lrc:/etc/rc2_d/S81dodatadm_udaplt > legacy_run 17:22:06 lrc:/etc/rc2_d/S89PRESERVE > legacy_run 17:22:06 lrc:/etc/rc2_d/S94ncalogd > legacy_run 17:22:06 lrc:/etc/rc2_d/S98deallocate > legacy_run 17:22:08 lrc:/etc/rc3_d/S16boot_server > legacy_run 17:22:08 lrc:/etc/rc3_d/S50apache > legacy_run 17:22:09 lrc:/etc/rc3_d/S52imq > legacy_run 17:22:09 lrc:/etc/rc3_d/S80mipagent > legacy_run 17:22:09 lrc:/etc/rc3_d/S84appserv
The legacy_run type of service just means that a start script was found in /etc/rc?_d. It does not mean that there is any running service associated with the script. > online 17:16:27 svc:/system/svc/restarter:default > online 17:17:07 svc:/milestone/name-services:default milestones are not really services either, they are, for lack of a better word, milestones. > online 17:17:54 svc:/network/initial:default > online 17:17:55 svc:/network/loopback:default > online 17:17:56 svc:/network/physical:default > online 17:17:59 svc:/network/service:default > online 17:18:09 svc:/milestone/network:default > online 17:18:56 svc:/system/device/local:default > online 17:18:58 svc:/milestone/devices:default > online 17:18:59 svc:/system/filesystem/minimal:default > online 17:19:07 svc:/system/boot-archive:default > online 17:19:13 svc:/system/identity:node > online 17:19:18 svc:/system/rmtmpfiles:default > online 17:19:26 svc:/system/filesystem/usr:default > online 17:19:28 svc:/system/device/fc-fabric:default > online 17:19:28 svc:/system/sysevent:default > online 17:19:37 svc:/system/filesystem/root:default > online 17:19:45 svc:/system/resource-mgmt:default > online 17:19:50 svc:/system/installupdates:default > online 17:19:57 svc:/system/coreadm:default > online 17:19:57 svc:/system/identity:domain > online 17:19:58 svc:/system/cryptosvc:default > online 17:19:58 svc:/network/ipsec/ipsecalgs:default > online 17:19:58 svc:/system/scheduler:default > online 17:19:59 svc:/system/picl:default > online 17:19:59 svc:/system/name-service-cache:default > online 17:20:00 svc:/system/keymap:default > online 17:20:00 svc:/network/ipsec/policy:default > online 17:20:02 svc:/system/power:default > online 17:20:13 svc:/system/manifest-import:default > online 17:20:15 svc:/milestone/single-user:default > online 17:20:17 svc:/system/filesystem/local:default > online 17:20:18 svc:/system/boot-archive-update:default > online 17:20:18 svc:/system/cron:default > online 17:20:20 svc:/system/dbus:default > online 17:20:21 svc:/network/shares/group:default > online 17:20:22 svc:/network/shares/group:zfs > online 17:20:25 svc:/application/opengl/ogl-select:default > online 17:20:27 svc:/system/sysidtool:net > online 17:20:29 svc:/system/hal:default > online 17:20:31 svc:/network/routing-setup:default > online 17:20:31 svc:/system/filesystem/rmvolmgr:default > online 17:20:32 svc:/network/rpc/bind:default > online 17:20:35 svc:/network/routing/ndp:default > online 17:20:35 svc:/network/rpc/keyserv:default > online 17:20:35 svc:/network/nis/client:default NIS client is an example of a service which checks to see if there is a configuration file before doing anything. No config file, no action. If you really don't want it, don't install it. > online 17:20:37 svc:/system/filesystem/autofs:default > online 17:20:41 svc:/system/dumpadm:default > online 17:20:42 svc:/system/sysidtool:system > online 17:20:47 svc:/system/fmd:default > online 17:20:57 svc:/platform/i86pc/kdmconfig:default > online 17:20:58 svc:/milestone/sysconfig:default > online 17:20:59 svc:/system/sac:default > online 17:20:59 svc:/system/utmp:default > online 17:21:00 svc:/system/system-log:default > online 17:21:00 svc:/network/inetd:default > online 17:21:01 svc:/system/console-login:default > online 17:21:02 svc:/application/management/wbem:default > online 17:21:02 svc:/network/ssh:default > online 17:21:08 svc:/network/rpc/gss:default > online 17:21:08 svc:/network/rpc/smserver:default > online 17:21:08 svc:/network/security/ktkt_warn:default > online 17:21:08 svc:/network/rpc/cde-ttdbserver:tcp > online 17:21:08 svc:/network/rpc/cde-calendar-manager:default ok, I vote we kill CDE :-) > online 17:21:08 svc:/network/rpc-100235_1/rpc_ticotsord:default > online 17:21:50 svc:/application/font/fc-cache:default > online 17:21:53 svc:/network/smtp:sendmail > online 17:22:06 svc:/milestone/multi-user:default > online 17:22:07 svc:/system/intrd:default > online 17:22:09 svc:/milestone/multi-user-server:default > online 17:22:10 svc:/application/graphical-login/cde-login:default > online 17:22:12 svc:/system/zones:default > online 17:22:12 svc:/system/basicreg:default > online 17:22:21 svc:/application/cde-printinfo:default > online 17:23:45 svc:/system/webconsole:console > online 17:25:11 svc:/system/postrun:default There are also transient services, which can be quite useful during installation. Rather than going through a list of laundry items and deciding what not to wear, maybe a better approach is to look at your requirements. -- richard -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
