Date: Wed, 22 Feb 1995 12:43:16 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: mark@grondar.za (Mark Murray) Cc: bugs@FreeBSD.org, current@FreeBSD.org Subject: Re: Lots of crud... Message-ID: <199502222043.MAA25124@gndrsh.aac.dev.com> In-Reply-To: <199502222025.WAA22507@grunt.grondar.za> from "Mark Murray" at Feb 22, 95 10:25:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I see no MAKEDEV.Local in src/release, MAKEDEV files are machine depenedent, > > so they need to be in the etc.i386 directory. MAKEDEV.local is machine > > independent so it belongs where it is. > > I meant move MAKEDEV _with_ MAKEDEV.local. MAKEDEV is in etc.i386, and > MAKEDEV.local is in etc. Should they at least not be together? Please read again what I said ``MAKEDEV is machine dependent, MAKEDEV.local is machine INdependent''. No, they should not be togeather. ... > > > AFAICSee, these are all for the 1.1.5.1 install floppies. > > > > And are still in use by some folks who prefer the 1.x method of installing > > things. I am still using these, expect a revamp some time real soon now. > > OK - I'll buy that. Why would anyone still want the 1.x method ;-) Fixit functionality, running a system from cdrom and floppy, etc... there are things that can be done with these tools that can not be done with the new ones. :-( > > > - 5178 Feb 20 1994 disktab > > > This, I believe, could comfortably live in src/etc > > > > Think multiplatform, but maybe this could safely be moved. This is the > > traditional BSD location for this source file. > > I'll go for tradition. It needs some updating tho'. There are a few hard disks > out there... And with the new or old install tools we create entries for the disk that is installed to, no need to really create a huge /etc/disktab file. Perhaps the parts of the scripts that create /etc/disktab entries could be pulled out and made a seperate script and installed as /usr/sbin/mkdisktab for those that want an easier way to create one. The things that really need to stay in this file are the floppy disks, as far as I can see we could nuke the rest of the file. ... > > There is no such thing as a non-customizable file in /etc :-(. > > Bummer. It is much better, now that most of the customising can be > done _without_ messing with rc*. This idea should be taken as far as > possible with other /etc files, leaving as clear as possible a distinction > between files that one _should_ modify, _may_ modify and should preferably > _not_ modify. I was Helping someone upgrade his production 1.1 box to > 1.1.5.1 today, and the /etc area was a nightmare to do. Having been installing and upgrading unix systems for 15 years I have never seen a clean way to handle /etc, atleast now all the files in /etc are text files, and diff can be used to see what was customized (if you keep the original files around). I don't think your classing of ``should, may, and may not'' would work, I can label every file in /etc as ``should''. Can you point to one that a user under some circumstances would not modify. If you can I will make the argument that the file no longer belongs in /etc. :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502222043.MAA25124>