On Dec 14, 2006, at 11:03 AM, Stephen Potter wrote: > Narendra Kumar S.S wrote: >> I think we need to brainstorm on this. >> What are the other ways that we can handle this? >> What are the implications , if we put a size limit on the contents >> file and when it reaches the max_size, open a second file. >> How does other OSes handle this? > > I think you need to go a little lower first. A size limit isn't > useful if the contents need to be sorted. So, an easy first > question is, does the file need to be sorted? If not, then does > the file need to be ASCII or would a DB file be better? > > -spp > > -- > Stephen Potter <spp at unixsa.net> <http:// > www.lopsa.org> > Director, LOPSA Executive Board > > "I have come to the conclusion that one useless man is a disgrace, two > useless men are a law firm, and three are a congress." - John Adams > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/install-discuss
Would it be practical to break the contents file into an index of the packages, and a for each package name? The index could then be small and quick to use, and each package would then have to write/update only the file for that package. ----- Gregory Shaw, IT Architect Phone: (303) 673-8273 Fax: (303) 673-2773 ITCTO Group, Sun Microsystems Inc. 500 Eldorado Blvd, UBRM02-157 greg.shaw at sun.com (work) Broomfield, CO 80021 shaw at fmsoft.com (home) "When Microsoft writes an application for Linux, I've Won." - Linus Torvalds -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20061214/386332dc/attachment.html>
