So you obviously never came up against trying to talk to somebody on a SunOS box, which used otalk against the rest of the world, which used ntalk. Unless they were really l33t and had installed ytalk.
Really. Talk never worked that well. I believe that it also had byte order dependency problems.
That's entirely missing the point. It's as if asked "I wish perl had a unified database handling module", somebody had answered: "well, you've got the oracle module, the sybase module and the mysql module. They don't have the same API, but they all allow you to connect to the database you're using.".
A GUI abstraction layer would be a much, much harder thing to achieve, simply because the API to guis can vary so much. OTOH, Python has an "anygui" module available, so maybe it's not as hard as I think...
# cd/usr/src # patch </path/to/sshd.patch # cd/usr/src/secure/lib/libssh # make depend && make all # cd/usr/src/secure/usr.sbin/sshd # make depend && make all install # cd/usr/src/secure/usr.bin/ssh # make depend && make all install
If you've got the ssh port installed, check out the advisory for details on what to do:
In FreeBSD, CVSup is used to keep source trees in sync. It's a very efficient way of keeping several hundred megs of source code up to date.
I realise that CVSup is oriented towards CVS trees, which the Linux kernel isn't, but even an rsync server would be better than continuously downloading the patch.
The reason I mention this is because of the support infrastructure available in FreeBSD:
Everybody so far seems to be saying that netscape 5/mozilla was a complete rewrite. Which is true, but its missing the point that netscape 4 was a complete rewrite of version 3. And that's where things started to go badly wrong...
softupdates were first invented as theory by Ganger & Patt and the idea was published as a paper. Kirk McKusick then took their idea, and coded it for *BSD.
Hello, what planet are you on? The csh looks nothing like C. The syntax is clumsy and inflexible. See Csh Programming Considered Harmful.
Not only that, but csh is actually older than the bourne shell!!! It was derived from 6th Edition Unix, the bourne shell was new in 7th Edition. Talk about being slow to catch up...
Seriously, there is very little (most would say none) incentive to use csh anymore. Even in its tcsh incarnation, it's almost completely been superceded by zsh. You should check it out for your own sanity.
Should you desire, you can even turn on the god-awful insane history mechanism that all those weird-ass csh users seem to have gotten ingrained with...
Well, it's easy to get paren-matching emacs as well. I think it's turned on by default. But one more useful hint is to make the % key behave the same as in vi. This bit of elisp code does the trick.
(defun match-paren (arg)
"Go to the matching parenthesis if on parenthesis otherwise insert %."
(interactive "p")
(cond ((looking-at "\\s\(") (forward-list 1) (backward-char 1))
((looking-at "\\s\)") (forward-char 1) (backward-list 1))
(t (self-insert-command (or arg 1)))))
(global-set-key "%" 'match-paren)
I'm not sure which number it is (5 or 7), but the enable secret passwords are encrypted using the FreeBSD password algorithm, which is to say, MD5. It was implemented by Poul Henning-Kamp ( http://people.freebsd.org/~phk/ , look at the "beerware" bit). The algorithm is a lot stronger than the the old DES based unix scheme. And a lot harder to brute force.
-Dom
Re:Time for environment integration
on
GNU Emacs 21
·
· Score: 1
Well, Gee. XEmacs had support for this *years* ago. It was one of the things that JWZ ensured was in place. Of course, it only works with Xt widget sets like Motif and Athena, but there you are. That's Gnome and Kde's fault for not following existing standards and pissing everybody off.
They already do this; but rather, they anaylze the structure of the HTML rather than doing a solely textual comparison. This gives better results where all that has changed is the domain name in the title or something like that.
Have a look in some of the back issues of the survey for a discussion of it.
BSD doesn't have runlevels. You've got single-user mode and multi-user mode. FWIW, I have yet to see a Linux distribution with a usable single-user mode.
Although BSD doesn't have run-levels, it does have per-service (init.d style) scripts available as an option if you want to use them. See/usr/local/etc/rc.d for example.
BSD has rc.conf which is a huge list of shell variables (effectively; some are defaults), which is sourced by the individual script that uses it.
If you want more details about the BSD rc system, take a peek at the FreeBSD CVS Web.
Although I feel that the new NetBSD system with per-script dependencies is probably a better system.
Ksh will expand environment variables when it diplays, so you can do:
PS1='$PWD$ '
(Note the single quotes)
-Dom
Re:Does Postfix support Maildir like Exim or Qmail
on
Postfix
·
· Score: 1
Actually, postfix only really supports Maildirs in your home directory (unless you use a.forward file). However, I have a patch to postfix which will allow you to send to Maildir's in the spool much more easily.
Slashdot Mirror
-Dom
Didn't think so. Back to vi.
-Dom
That will fail nicely when you have too many java files lying around. You're much better off using xargs:
find src -name '*.java' | xargs javac -d classes
-Dom
Test First is a godsend!
I've started doing test first for all my programming now and I've found that it helps in several areas:
* Forces you to think upfront about what you're doing and helps catch stupid errors right there.
* Tends you towards a better, more separated design. This is a natural consequence of testing.
-Dom
Really. Talk never worked that well. I believe that it also had byte order dependency problems.
-Dom
-Dom
Yes, but you can happily replace the (IMHO) awful bash with zsh. And Linux will still carry on working just fine.
-Dom
If you don't like it, you don't have to port it.
There are still people using emacs 18 to edit their files because it's small and it works.
There are still people running Windows 98 to run their games because it works.
Nobody's forcing you to move to Perl 6. That's the beauty of Open Source. Perl 5 is going to be developed for a long time to come. Don't give up hope.
-Dom
And rightly criticized if I might add. Too many comments obscure the code and duplicate what it says a lot of the time. Good comments are an art form.
-Dom
That's entirely missing the point. It's as if asked "I wish perl had a unified database handling module", somebody had answered: "well, you've got the oracle module, the sybase module and the mysql module. They don't have the same API, but they all allow you to connect to the database you're using.".
A GUI abstraction layer would be a much, much harder thing to achieve, simply because the API to guis can vary so much. OTOH, Python has an "anygui" module available, so maybe it's not as hard as I think...
-Dom
Unfortunately, I can't post the advisory here due to the lame lameness filter. But here are the patches:
S A- 02:13/openssh.patche eBSD/CERT/patches/SA- 02:13/openssh.patch.asc
/usr/src /path/to/sshd.patch /usr/src/secure/lib/libssh /usr/src/secure/usr.sbin/sshd /usr/src/secure/usr.bin/ssh
0 +c urrent/freebsd-announce
ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/patches/
ftp://ftp.FreeBSD.org/pub/Fr
Execute the following commands as root:
# cd
# patch <
# cd
# make depend && make all
# cd
# make depend && make all install
# cd
# make depend && make all install
If you've got the ssh port installed, check out the advisory for details on what to do:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+
In FreeBSD, CVSup is used to keep source trees in sync. It's a very efficient way of keeping several hundred megs of source code up to date.
/etc/make.conf (once)
/usr/src && make update
I realise that CVSup is oriented towards CVS trees, which the Linux kernel isn't, but even an rsync server would be better than continuously downloading the patch.
The reason I mention this is because of the support infrastructure available in FreeBSD:
1. Install cvsup (once)
2. edit
3. cd
CVSup is available at http://www.polstra.com/projects/freeware/CVSup/
Finally, FreeBSD will get a native Java for 4.5. This is a very positive outcome of Sun's!
-Dom
Everybody so far seems to be saying that netscape 5/mozilla was a complete rewrite. Which is true, but its missing the point that netscape 4 was a complete rewrite of version 3. And that's where things started to go badly wrong...
-Dom
softupdates were first invented as theory by Ganger & Patt and the idea was published as a paper. Kirk McKusick then took their idea, and coded it for *BSD.
Hello, what planet are you on? The csh looks nothing like C. The syntax is clumsy and inflexible. See Csh Programming Considered Harmful.
Not only that, but csh is actually older than the bourne shell!!! It was derived from 6th Edition Unix, the bourne shell was new in 7th Edition. Talk about being slow to catch up...
Seriously, there is very little (most would say none) incentive to use csh anymore. Even in its tcsh incarnation, it's almost completely been superceded by zsh. You should check it out for your own sanity.
Should you desire, you can even turn on the god-awful insane history mechanism that all those weird-ass csh users seem to have gotten ingrained with...
Well, it's easy to get paren-matching emacs as well. I think it's turned on by default. But one more useful hint is to make the % key behave the same as in vi. This bit of elisp code does the trick.
(defun match-paren (arg)
"Go to the matching parenthesis if on parenthesis otherwise insert %."
(interactive "p")
(cond ((looking-at "\\s\(") (forward-list 1) (backward-char 1))
((looking-at "\\s\)") (forward-char 1) (backward-list 1))
(t (self-insert-command (or arg 1)))))
(global-set-key "%" 'match-paren)
I'm not sure which number it is (5 or 7), but the enable secret passwords are encrypted using the FreeBSD password algorithm, which is to say, MD5. It was implemented by Poul Henning-Kamp ( http://people.freebsd.org/~phk/ , look at the "beerware" bit). The algorithm is a lot stronger than the the old DES based unix scheme. And a lot harder to brute force.
-Dom
Well, Gee. XEmacs had support for this *years* ago. It was one of the things that JWZ ensured was in place. Of course, it only works with Xt widget sets like Motif and Athena, but there you are. That's Gnome and Kde's fault for not following existing standards and pissing everybody off.
-Dom
They already do this; but rather, they anaylze the structure of the HTML rather than doing a solely textual comparison. This gives better results where all that has changed is the domain name in the title or something like that.
Have a look in some of the back issues of the survey for a discussion of it.
-Dom
- BSD doesn't have runlevels. You've got single-user mode and multi-user mode. FWIW, I have yet to see a Linux distribution with a usable single-user mode.
- Although BSD doesn't have run-levels, it does have per-service (init.d style) scripts available as an option if you want to use them. See
/usr/local/etc/rc.d for example.
- BSD has rc.conf which is a huge list of shell variables (effectively; some are defaults), which is sourced by the individual script that uses it.
If you want more details about the BSD rc system, take a peek at the FreeBSD CVS Web. Although I feel that the new NetBSD system with per-script dependencies is probably a better system.-Dom
Sounds precisely like FreeBSD's Linux mode (which it's had for years). :-)
-Dom
Ksh will expand environment variables when it diplays, so you can do:
PS1='$PWD$ '
(Note the single quotes)
-Dom
Actually, postfix only really supports Maildirs in your home directory (unless you use a .forward file). However, I have a patch to postfix which will allow you to send to Maildir's in the spool much more easily.
Mail me if you want it.
-Dom
I think you need to look at AxKit instead!
AxKit.org
It's like cocoon but written in mod_perl (using Apache) and is much easier to get along with if you're not familiar with Java.
-Dom