> I still suggest not using symbols at all, since I'd like to be able to
> quickly remove tempfiles by hand without worrying if I have to escape #
> or ^, etc.
Then disable globbing first. (csh et al) "set noglob" or (sh et al) "set -f
noglob".
John
To Unsubscribe: send mail to [EMAIL PROTECTE
> | >which is not believed to cause any problems with shells. The PID is also
> | Some shells parse # as a deletion character if memory serves me right.
> Also ^ is used for substitutions in many shells (as in ^faulty^ok).
Why would you care if some shell used the a character in some special way?
This is the same way that OS servers under Mach3 were developed and debugged!
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Had
> the file been split and a checksum computed for each piece, I could have
> grabbed only the affected portion of the ISO.
This is screaming for an FTP server mod similar to the wuftpd code that will
automatically run tar|gzip. That is, given a file "foo", serve "foo.aa" to be
the first (s
> o Is there a way to increase the number of lines of console output that are
> "remembered" when you hit Scroll-Lock. Is this the MSGBUF_SIZE parameter?
> What would be the consequences of increasing this slightly? e.
The value compiled into the kenrnel is set with SC_HISTORY_SIZE; see LINT o
> Again, lemmie get on my soap box, and ask have you looked at the man page,
> and compared the memory required when using -s to the memory required by
> gzip?
Actually, lemmie get on my soap box and ask have you measured the time that
bunzip2 takes to run? While it does give better compression
> Some people were afraid that it would end up like the Windows registry.
But it wouldn't, because that isn't the right thing.
A kernel config utility should end up functioning like XF86Setup. When was the
last time most people made an XF86Config file since that program came around?
> and we
