On Sun, Jul 26, 1998 at 12:41:06AM -0400, Raul Miller wrote: > > a: the gui system for install should probably be based on w96 (a > > small 2 color windowing system) > > b: a port of apt to w96 or whatever gui chosen should be looked > > into. > > *shrug* I believe this should wait. GGI is coming along nicely and will probably make this a lot easier to do. > > c: the console install should be completly rewriten to include > > better error handleing and faster base install suport... mabye move from a > > tar archive to a cpio, or ar, or even zip archive... > > Er... this would be faster? I was not aware of any significant speed > difference. > > We do need some good docs on failure modes though, so we can do more > about them. Maybe you could help compile such docs? Problem with zip---it's faster on extremely large archives, but it's got a failing: permissions? zip is based on pkzip, a dos tool. pkware has extended the format to include long filenames, but I don't recall ever seeing anything about permissions. FYI: gzip uses the zip deflate compression method. > > Of the above, on the part about useing zip could even remotly be > > considered a compromise to techincal quality. (and even then only > > becuase I don't know that zips licens is. > > Er.. before we switch, how about verifying that the switch buys us > something significant? indeed, zip costs us permissions and adds one more program to base. zip cannot be used in batch and neither can unzip. base includes essentially zcat and star.. If base wants to open a tarball, it zcat file | star's it. iirc, it's not called zcat on the floppy, but that's what it is. > > debian should also have a firm and well known and loved logo. a contest > > should be held for this ... possibly debian should do as gimp does and > > offer a reward. ... > > I think some people are working on logo stuff. I dunno where they're > at on it. A logo contest sounds like a Good Thing. > > debian should also work to switch from the archaic man page format, by > > provideing as standard packages, the packages that will allow man pages to > > be served as html pages. useing lynx or kfm, netscape... ect. > > Er.. there's a massive project that is doing even better than this > (integrating multiple document formats, and indexing documentation). > > > I fail to see how this could be a compromise either... > > Check out the mailing list archives, this one has been discussed. Problem I hit, I installed apache on a machine (sinclair) which has no domain. The default installation doesn't say how to deal with this, but it seems that in this case putting sinclair.localnet in hosts will let apache run. This matters because dwww now works thanks to a number of NMU's of the package by joost I believe. dwww makes almost docs available at http://localhost/dwww. dwww is a cgi-bin and as such won't work with ANY server. It works with apache quite well. > > as for error loging and handle ing all errors should be writen to a file > > and then tailed on a empty vt for console isntalls and to the root window > > for the gui/newbie install. > > Hmm... I dunno who's working on this. ? Syslog ------ What syslog does and why you might want to be able to see the last few lines of it quickly here. You can change ttys with the alt and fkeys, so this reminds you of how you'd use it. It also points out why it can be unsafe. Do you want a syslog on tty12? [y/N] _ The install scripts could ask questions that haven't been answered yet. This leaves the option to have a response file which can be found and read (similar to kernel .config really) making life installing several machines easier. This could in theory work with a graphics install too, but I don't see why you'd want graphics if you're not going to be prompted for anything.
Attachment:
pgp5AF3_3Npxg.pgp
Description: PGP signature