As an American, I am very confused about the patent issues. OpenSSH provides support for both SSH1 and SSH2 protocols. SSH1 protocol uses the RSA algorithm, which was under patent till September 21, 2000 inside the USA. Outside the USA, none of these issues ever applied. The SSH2 protocol uses DH and DSA, two other algorithms which have no nasty patent issues. If you avoid use of the SSH1 protocol, and use only the SSH2 protocol, you have nothing to worry about. However, you will need to find SSH2-compatible clients and servers for your other machines. For some users, this can be a small problem, since at this point in time we know of no free SSH2 Windows clients. Since the RSA patent has expired, there are no restrictions on the use of RSA algorithm using software, including OpenBSD.
>>75 それで三台ほど運用してますが問題無しです。(BIND は ISP ですが) ただし、cache server とそれ以外(zone transfer or external DNS) を同アドレスでサービスすることはできませんので、cache server の アドレスを容易に変更できない場合は申請時に注意してください。
There are 3 managers from Debian JP in Debian's "New Maintainer Team". And Ukai is nominated as "One of the best top 4 managers" in the mail from the "Developer Account Manager (The Delegate, i.e. the authority for membership, the position is defined in the Debian Constitution).
Sections titled "[debian-devel:10087] ASCII24" and "[debian-devel:10269] Re: ASCII24]" is the reviews, but due to list server problem, the links are not correct.
When the disk is formatted, superformat automatically invokes mformat in order to put an MS-DOS filesystem on it. You may ignore this filesystem, if you don't need it.
So you can use "dd if=/dev/zero of=/dev/fd0 bs=1024 count=1440" after using superformat. OK ?
146 名前: 名無しさん@お腹いっぱい。 投稿日: 2000/12/07(木) 19:54
ログイン時のメッセージがウザくて鬱になりそうです。
Most of the programs included with the Debian GNU/Linux system are freely redistributable; the exact distribution terms for each program are described in the individual files in /usr/doc/*/copyright
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail.
But you should take care of /etc/init.d/bootmisc.sh and /etc/default/rcS, because /etc/motd is automatically generated by default via these setup/script.
Maybe you need to change EDITMOTD="no" in /etc/default/rcS then you can edit /etc/motd as you like.
149 名前: 名無しさん@お腹いっぱい。 投稿日: 2000/12/08(金) 13:29
文語調で擬古趣味気取ってますか? ギコギコ
150 名前: 名無しさん@お腹いっぱい。 投稿日: 2000/12/08(金) 15:16
X を woody のものにして dexter で設定したのですが X が立ちあがりません。 しかし何故か root では立ちあがります。
X: user not authorized to run the X server, aborting.
Well, maybe most of users need to call mformat automatically.
I checked the code in superformat.c, and made it sure that this command line option does not call mformat:
% superformat -D "" /dev/fd0
Note the two continuated doble quotes as an argument of "-D" option. This sets the "dosdrive" variable to zero, and the superformat does not call the mformat command in this case only.
But you got a warning message even in this case, as:
"warning: mformat not called because DOS drive unknown"
To suppress this, you have to redirect the stderr to some place such as /dev/null.
I think it is easy to implement the option not to call mformat in superformat. I don't know the answer since I'm not the developer of fdutils, but I suppose that they just don't reallize such needs.
If you wish to have it strongly, you can report your wishlist on the Debian BTS for fdutils package.
Ah,,, already there is. Bug#51368 shows the need from a user. Maybe you can add your voice on this report.
I suspect #74587 and #78915 are related to this issue, but I am not sure on these reports.
The unstable is now "sid". If you wish to use the "Cutting-Edge" version, you should point your apt's sources.list to "unstable".
"woody" is now "testing", which is effectively "parmanent semi-frozen" though new upstream version will be added on testing if that package does not have significant bug and can be available all architecture which is to be released. (build failure on unreleased-architecture such as hurd-i386, superh, or hppa, are not considered to be the cause to stop the addition to testing)
So, glibc 2.2 and XFree86 v4 was retracted from the woody ("testing") because glibc2.2 could not be built up well on some (m68k ? arm ?) "architecture to be released".
XFree86 v4 just depends glibc2.2 (not Build-Depends, but binary depends since the developer uses unstable) and it could not be added on to the woody until glibc2.2 was added recently.
Now woody has already glibc2.2, so new packages which depend it will be added lately. But it takes some duration (about 2 weeks) after the new package is registered into unstable before it in turn will be registered into "testing".
This whole thing (creation of "testing") is implemented in order to make more frequent release of the official Debian (stable).
This file should be marked as "conffile", and package upgrade should keep the modification on "conffile" by user.
So, if you add, for example, "exit 0" at the start of that command (just after the head line "#!/bin/sh" and the following comment lines if there are), then that package would not start up automatically after the upgrade unless you explicitly order to replace that file with the corresponding one in the newer package.
If you say "NO" to replase the conffile, then newer file will be saved as <filename>.dpkg-new
If you say "YES" to replace the confffile, then old file will be saved as <filename>.dpkg-old
Files in /etc/rc<runlevel>.d/ (or /etc/rcS.d/) are just symlinks to the one under /etc/init.d/ and they are automatically created by the "postinst" script of the package.
Of course, the best solution to kill the server software, is not to install them at all. If you have CD-ROMs or fast network access, you can install them whenever you need it, so you don't have to keep the un-needed software on your harddisk just to hog up your space.
And, maybe Japanese translation of "Debian FAQ" will work for you. If you don't read it, let's try it.