To my mind, its about time!
The question I have is 3rd party software. Candidates that seem to be
likely to be used by ISVs:
autopush
fstyp
install
mknod
mount
rmt (this one may have implications for interop with BSD systems)
tar
uadmin
volcopy
The remainder seem unlikely to be used by ISVs.
Looking at the above list:
All of these seem like they should be obtained by $PATH. The impact to
ISV software seems like it would mostly be exceptional cases, such as
stuff related to STREAMs modules, unusual kernel software, or stuff
ported from BSD. I think we can probably live with the fall out.
One possible exception to that concern is rmt. I worry that "/etc/rmt"
may be hard coded into software that would be using remote tape
facilities. While I doubt there is much concern about SunOS 4.x and
earlier accessing rmt in this way (over rsh), I am not convinced that
there are no other places this is hard coded (such as in other tape
management systems.)
Has any investigative work been done to try to ensure that
removing /etc/rmt won't cause heartache to such subsystems? Do all the
common tape management systems now in use either use something other
than rmt or at least don't use "/etc/rmt" hardcoded?
I'll give a +1 to the case for all these except rmt; I'll withhold the
overall +1 including rmt until I hear that at least some work to ensure
that the impact is not severe for rmt has been done.
- Garrett
On Fri, 2010-07-23 at 08:55 -0700, Peter Dennis wrote:
> Required release binding:
> Patch binding for the announcement and marking as Obsolete.
> Minor binding for the removal.
>
> Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI
> This information is Copyright (c) 2010, Oracle and/or its affiliates. All
> rights reserved.
> 1. Introduction
> 1.1. Project/Component Working Name:
> Remove binary symlinks from /etc
> 1.2. Name of Document Author/Supplier:
> Author: Venky Tv
> 1.3 Date of This Document:
> 23 July, 2010
> 4. Technical Description
>
> 4.1. Details:
>
> This project aims to remove binary symlinks from /etc. These
> compatibility links were introduced along with /sbin.
>
> The telinit(1M) utility which is symlink to /sbin/init will be
> moved from /etc to /sbin. Though there is no difference
> between init(1M) and telinit(1M) in Solaris anymore, telinit is
> still supposed to be the interface to use to signal init to
> change the runlevel or re-examine the /etc/inittab file.
>
> The changes have been tested to make sure they do not introduce any
> standards conformance issues.
>
> 4.2. Bug/RFE Number(s):
>
> 4856275 /etc needs a cleanup
>
> 4.5. Interfaces:
>
> The following interfaces in /etc will be deleted:
>
> autopush -> ../sbin/autopush
> cfgadm -> ../usr/sbin/cfgadm
> clri -> ../usr/sbin/clri
> cron -> ../usr/sbin/cron
> dcopy -> ../usr/sbin/dcopy
> ff -> ../usr/sbin/ff
> fmthard -> ../usr/sbin/fmthard
> format -> ../usr/sbin/format
> fsck -> ../usr/sbin/fsck
> fsdb -> ../usr/sbin/fsdb
> fstyp -> ../usr/sbin/fstyp
> getty -> ../usr/lib/saf/ttymon
> grpck -> ../usr/sbin/grpck
> halt -> ../usr/sbin/halt
> init -> ../sbin/init
> install -> ../usr/sbin/install
> killall -> ../usr/sbin/killall
> labelit -> ../usr/sbin/labelit
> mkfs -> ../usr/sbin/mkfs
> mknod -> ../usr/sbin/mknod
> mount -> ../sbin/mount
> mountall -> ../sbin/mountall
> ncheck -> ../usr/sbin/ncheck
> prtconf -> ../usr/sbin/prtconf
> prtvtoc -> ../usr/sbin/prtvtoc
> reboot -> ../usr/sbin/halt
> rmt -> ../usr/sbin/rmt
> setmnt -> ../usr/sbin/setmnt
> shutdown -> ../usr/sbin/shutdown
> sulogin -> ../sbin/sulogin
> swap -> ../usr/sbin/swap
> swapadd -> ../sbin/swapadd
> sysdef -> ../usr/sbin/sysdef
> tar -> ../usr/sbin/tar
> telinit -> ../sbin/init
> uadmin -> ../sbin/uadmin
> umount -> ../sbin/umount
> umountall -> ../sbin/umountall
> volcopy -> ../usr/sbin/volcopy
> wall -> ../usr/sbin/wall
> whodo -> ../usr/sbin/whodo
>
> This interface will be introduced:
>
> /sbin/telinit -> /sbin/init
>
> 4.6. Doc Impact:
>
> The telinit(1M) manpage needs to be modified to indicate the
> new location of the telinit executable.
>
> 4.10. Packaging & Delivery:
>
> All these are part of the SUNWcs package. There is no impact
> on install/upgrade.
>
>
> 6. Resources and Schedule
> 6.4. Steering Committee requested information
> 6.4.1. Consolidation C-team Name:
> ON
> 6.5. ARC review type: FastTrack
> 6.6. ARC Exposure: open
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
