Re: Cannot make buildworld
On Tue, Nov 21, 2000 at 08:58:14AM +0100, Jose Luis Arbona Orovay wrote:
Is this documented ?
If you kept up with this mailing list, you would have known this problem.
That is why I just gave the "what to do" rather than give an explanation.
Please review the recent archives when you have a problem.
Why should we do that ?
You must have CVSup'ed during a window of time when I was changing the
way we build crt{begin,end}.o. This caused the build problem you
experienced.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Cannot make buildworld
Hi David.
David O'Brien wrote:
If you kept up with this mailing list, you would have known this problem.
That is why I just gave the "what to do" rather than give an explanation.
Please review the recent archives when you have a problem.
You're right, next time I will review the mailing archives before asking.
You must have CVSup'ed during a window of time when I was changing the
way we build crt{begin,end}.o. This caused the build problem you
experienced.
Maybe it was a "microsoft window" of time ?
Thanks. (I never got an answer so fast :-)
Jose Luis.
__
José Luis Arbona
IBM GLOBAL SERVICES, S.A.
Avda. Aragón, 30 - 4 planta
46021 Valencia
mailto:[EMAIL PROTECTED]
tfno. 96 398 53 00
___
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Dangerously Dedicated
Hi Chad, good summary. Only one remark and two additions: To summarize the summary: The problem comes from the fact that a PC-BIOS is permitted to insist on an MBR on each drive, and that the slices in that MBR align on certain boundries whereas FreeBSD doesn't care about such sillyness but has to use the BIOS to get launched. I don´t think they do it for their fun and our work to be harder, but as a workaround for other problems the BIOS developers face. So it´s not silly, but a consequence of the PC architecture being defined in a suboptimal fashion. Simple solution? Don't use DD. Slightly less simple? Don't use DD on drives that are in any way involved with the boot process, but go ahead on data-only drives. As some stated here, the bogus data in a dd-MBR can break booting even on non-boot-disks (i.e. your data-only drives). The mere presence will be tested, detected as faulty and therefore the process stops before anything can be done on user side. For the IA64 no dd will work at all, as a valid MBR is a strict requirement. Ciao Siegbert To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.2-STABLE cd9660: Input/output error
Dear Sirs, I am using 4.2-STABLE: FreeBSD bofh.lasting.ro 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Nov 21 11:39:07 EET 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OOPS i386 cvsup'd last night. acd0: CDROM TOSHIBA CD-ROM XM-6702B at ata1-master using UDMA33 # mount /cdrom cd9660: Input/output error acd0: READ_BIG - HARDWARE ERROR asc=08 ascq=03 error=00 while trying to mount every cd-rom. It forked fine with 4.2-BETA, but had some problems with 4.1.1-STABLE. Best regards, Cristian Bradiceanu begin:vcard n:Bradiceanu;Cristian tel;fax:+40-56-201278 tel;work:+40-56-201278 x-mozilla-html:FALSE url:http://www.lasting.ro org:LASTING System;Internet version:2.1 email;internet:[EMAIL PROTECTED] adr;quoted-printable:;;Miron Costin 2=0D=0A;Timisoara;Timis;1900;Romania x-mozilla-cpt:;-12512 fn:Cristian Bradiceanu end:vcard
Java et al
Hello, Excuse this if it's off-topic... I couldn't think of the best place to ask this, and I am running STABLE on all production machines, so... We have a lot of proprietary code written in Java running on Wintel boxes. There's been talk of migrating to Linux, and our initial tests show performance equal to NT 4.0 under the JDK/JVM's we've tested. Is there anyone out there running a lot of mission-critical (read: updating Oracle queues responsible for 911 dispatching) Java code under FreeBSD? If so, I'd appreciate JDK/JVM reccomendations, OS tuning tips (or relevant FAQs), etc. If not... I guess I'll resign myself to letting penguins slowly infiltrate my network (ack!). Note: I've seen http://www.freebsd.org/java/. I'm asking for working knowledge, known bugs, stability, etc... and not just if a working JDK exists. Thanks, -Mike -- "IP assumes non-hostile, non-lazy, and non-clueless nodes." --Mark Mentovai To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Java et al
Mike Hoskins wrote: Hello, Excuse this if it's off-topic... I couldn't think of the best place to ask this, and I am running STABLE on all production machines, so... We have a lot of proprietary code written in Java running on Wintel boxes. There's been talk of migrating to Linux, and our initial tests show performance equal to NT 4.0 under the JDK/JVM's we've tested. Is there anyone out there running a lot of mission-critical (read: updating Oracle queues responsible for 911 dispatching) Java code under FreeBSD? If so, I'd appreciate JDK/JVM reccomendations, OS tuning tips (or relevant FAQs), etc. If not... I guess I'll resign myself to letting penguins slowly infiltrate my network (ack!). Note: I've seen http://www.freebsd.org/java/. I'm asking for working knowledge, known bugs, stability, etc... and not just if a working JDK exists. Thanks, -Mike There is a beta-source release of JDK 1.2.2 for FreeBSD. I have successfully compiled this and it does appear to work. However, no functional JIT means performance is a bit of a dog. (there are opensource JIT available but they don't always work right) I have the most success with running both IBM JDK1.3 and Sun JDK1.3 for Linux. Both require patches to the linux kld emulation in FreeBSD and both have "quirks". However, the Sun JDK can be coaxed into running large complex applications such as Borland JBuilder 4. The IBM JVM would frequently coredump on that but is perfectly acceptable at running more modest applications at speed - the IBM JVM has the advantage of correctly translating unicode characters and a whole host of other little things which the Sun JVM gets wrong. Both have a habit of "freezing" but I suspect this is due to the way how FreeBSD emulates Linux heavyweight threads. Personally, I would really want to see a native J2EE 1.3 JDK for FreeBSD which takes advantage of FreeBSD's lightweight threads... It should really fly! Using FreeBSD 4.1.1-STABLE (circa Oct 26) IBM Linux JVM: Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-2815 (JIT enabled: jitc) SUN Linux JVM: Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0rc1-b17) Java HotSpot(TM) Client VM (build 1.3.0rc1-b17, mixed mode) FreeBSD Native JVM: java version "1.2.2" Classic VM (build jdk1.2.2-FreeBSD:root:2000/10/26-09:55, green threads, nojit) -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 God did not create the world in seven days; he screwed around for six days and then pulled an all-nighter. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hmm..passwords.
Hello, Chris Byrnes! On Mon, Nov 20, 2000 at 06:33:21PM -0600, you wrote: I recently went 4.1.1-stable to 4.2-release and now lots of passwords...don't work. Any ideas? The same thing... Mabe the point is in DES/md5 passwords? -- Alexandr P. Kovalenko http://nevermind.kiev.ua/ NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hmm..passwords.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Nov 2000, Nevermind wrote: ... : The same thing... : Mabe the point is in DES/md5 passwords? FreeBSD has actually defaulted to MD5 passwords for quite a long time to those of us not within the US. However, installing the US crypto has always forced the usage of DES passwords by default. In order to switch your machine back to DES passwords from MD5 passwords, this is what you need to do: [ commands done one line at a time for clear reading ] # cd /usr/lib # rm libcrypt.a # rm libcrypt.so # rm libcrypt.so.2 # rm libcrypt_p.a # ln -s libdescrypt.a libcrypt.a # ln -s libdescrypt.so libcrypt.so # ln -s libdescrypt.so.2 libcrypt.so.2 # ln -s libdescrypt_p.a libcrypt_p.a That's it. Should you desire to switch BACK to MD5 passwords, just take those above steps and do a s/libdescrypt/libscrypt/g on it. Hope this if of help to you all. * Matt Heckaman - mailto:[EMAIL PROTECTED] http://www.lucida.qc.ca/ * * GPG fingerprint - A9BC F3A8 278E 22F2 9BDA BFCF 74C3 2D31 C035 5390 * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE6GmYXdMMtMcA1U5ARAtp6AJ995uDJnev8k6YaPt8WrP0laJuv+ACgkEAI DZE/qN+NUt8AkAZk2Mu+m/w= =VFbM -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Removal of Disklabel
Larry Rosenman [EMAIL PROTECTED] writes: * Chad R. Larson [EMAIL PROTECTED] [001120 23:44]: Our Pyramids, running DC/OSx 1.1 have 16 partitions per hard drive. DC/OSx is/was the reference port of SysVr4 to the MIPS chipset, done under contract by Pyramid for Unix System Labs. UnixWare V2.1+ and V7+ both support 16 slices per disk partition. They only support ONE active Unix partition per harddrive. also OpenBSD. don't remember about NetBSD. Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel breackage in machine/atomic.h
Cyrille Lefevre [EMAIL PROTECTED] writes: [snip] the symptom is : cc -c -fomit-frame-pointer -fno-builtin -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer ../../i386/i386/atomic.c In file included from ../../i386/i386/atomic.c:47: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:106: inconsistent operand constraints in an `asm' ... [snip] I've found the problem. cc need -O to compile this file (well, all files :) and my make.conf get rid of this. in fact, not really, since I use +=, but kernel's Makefile use ?= for COPTFLAGS. maybe it should use += also ? Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hmm..passwords.
Hello, Matt Heckaman! On Tue, Nov 21, 2000 at 07:09:57AM -0500, you wrote: FreeBSD has actually defaulted to MD5 passwords for quite a long time to those of us not within the US. However, installing the US crypto has always forced the usage of DES passwords by default. In order to switch your machine back to DES passwords from MD5 passwords, this is what you need to do: [ commands done one line at a time for clear reading ] # cd /usr/lib # rm libcrypt.a # rm libcrypt.so # rm libcrypt.so.2 # rm libcrypt_p.a # ln -s libdescrypt.a libcrypt.a # ln -s libdescrypt.so libcrypt.so # ln -s libdescrypt.so.2 libcrypt.so.2 # ln -s libdescrypt_p.a libcrypt_p.a That's it. Should you desire to switch BACK to MD5 passwords, just take those above steps and do a s/libdescrypt/libscrypt/g on it. Hope this if of help to you all. And if I wanna manage both -- DES MD5? For example I have about 200 users on one machine and I have no physical ability to make them change their passwords. It seems to me it worked fine somewhere between 3.4 and 4.0. -- Alexandr P. Kovalenko http://nevermind.kiev.ua/ NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hmm..passwords.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Nov 2000, Nevermind wrote: ... : And if I wanna manage both -- DES MD5? For example I have about 200 : users on one machine and I have no physical ability to make them : change their passwords. It seems to me it worked fine somewhere : between 3.4 and 4.0. Oh boy. To be honest Alexandr, I have no idea if this is even possible. It is my understanding that it is _not_ possible, but I've been known to be wrong before. I'll pass this question off to those on the list who are more knowledgeable than me in the area. :) * Matt Heckaman - mailto:[EMAIL PROTECTED] http://www.lucida.qc.ca/ * * GPG fingerprint - A9BC F3A8 278E 22F2 9BDA BFCF 74C3 2D31 C035 5390 * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE6Gm43dMMtMcA1U5ARAsc/AJ97bKM96lrJ0uKjfyTAz3X5tyn4ZQCg2xiX cnFcQVHNTdjLKGIBP/evP8k= =XXeU -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
pam_ssh problems
Sometime between 4.1.1-STABLE and 4.2-BETA we started having
difficulities with using pam_ssh and wdm. Here is a piece of our
/etc/pam.conf:
wdm authsufficient pam_ssh.so
wdm authrequiredpam_unix.so
wdm account requiredpam_unix.so try_first_pass
wdm session requiredpam_ssh.so
wdm password required pam_deny.so
This used to work just fine: It would authenticate against the user's
~/.ssh/identity, and when wdm started the session, it would
automatically startup ssh-agent and add the user's SSH key.
After a cvsup, wdm started dropping core. I've cvsup'ed a few times
since then also, hoping for a fix, but no luck yet. My latest cvsup
was yesterday.
So, I rebuilt wdm with debug symbols, and rebuilt world with -g too,
and here is the backtrace from gdb:
#0 0x283ed553 in ?? ()
#1 0x283ed72b in ?? ()
#2 0x283ea744 in ?? ()
#3 0x28321a10 in _pam_dispatch_aux (pamh=0x8069300, flags=0, h=0x8069900,
resumed=PAM_FALSE)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_dispatch.c:79
#4 0x28321e10 in _pam_dispatch (pamh=0x8069300, flags=0, choice=4)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_dispatch.c:270
#5 0x283200d6 in pam_open_session (pamh=0x8069300, flags=0)
at /usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_session.c:26
#6 0x8054b9d in StartClient (verify=0x805fbfc, d=0x8069000, pidp=0x805fbe0,
name=0x805f4e8 "user", passwd=0x805f500 "password")
at session.c:682
#7 0x8054009 in ManageSession (d=0x8069000) at session.c:308
#8 0x8050454 in StartDisplay (d=0x8069000) at dm.c:635
#9 0x805023b in CheckDisplayStatus (d=0x8069000) at dm.c:562
#10 0x8050a40 in ForEachDisplay (f=0x80501d4 CheckDisplayStatus)
at dpylist.c:55
#11 0x8050257 in StartDisplays () at dm.c:571
#12 0x804f638 in main (argc=2, argv=0xbfbff708) at dm.c:185
#13 0x804a5c8 in _start (arguments=0xbfbff818 "-:0 ")
at /usr/src/lib/csu/i386-elf/crt1.c:96
The code seems to be launching the module, but I can't figure out
which module it is having trouble with, although I expect it is
pam_ssh.so.
Here are a few more details from gdb:
(gdb) print *h
$8 = {must_fail = 0, func = 0x283ea1a0, actions = {-1, -3 repeats 11 times,
-1, -3 repeats 12 times, 0, -3, -3, -3, -3, -3, -3}, argc = 0,
argv = 0x0, next = 0x0}
(gdb) print *pamh
$9 = {authtok = 0x0, pam_conversation = 0x8065de0, oldauthtok = 0x0,
prompt = 0x0, service_name = 0x8065dc0 "wdm", user = 0x8065dd0 "user",
rhost = 0x0, ruser = 0x0, tty = 0x8065e00 ":0", pam_default_log = {
ident = 0x0, option = 0, facility = 0}, data = 0x8065f50, env = 0x8065df0,
fail_delay = {set = PAM_FALSE, delay = 0, begin = 974839469,
delay_fn_ptr = 0x0}, handlers = {module = 0x806a6c0,
modules_allocated = 4, modules_used = 3, handlers_loaded = 1, conf = {
authenticate = 0x8069400, setcred = 0x8069500, acct_mgmt = 0x8069800,
open_session = 0x8069900, close_session = 0x8069a00,
chauthtok = 0x8069b00}, other = {authenticate = 0x8069c00,
setcred = 0x8069d00, acct_mgmt = 0x8069e00, open_session = 0x0,
close_session = 0x0, chauthtok = 0x0}}, former = {choice = 0, depth = 0,
impression = 0, status = 0, want_user = 0, prompt = 0x0,
update = PAM_FALSE}}
I don't know if anybody else is having this problem, or know how to
fix it, but any assistance would be usefule.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-RC1 not (easily) bootable
On 20 Nov, Mike Smith wrote: "DO" == David O'Brien [EMAIL PROTECTED] writes: DO Why did you choose a "dangerously dedicated" install? "dangerously DO dedicated" might go away in the future (as it doesn't leave space enough DO space for boot0). Unless the normal slice configuration won't work for DO you, there really is no good reason to use "dangerously dedicated". I have two machines that wouldn't boot unless I installed them in DD mode. Am I to infer that at some date they will no longer run FreeBSD because DD mode goes away? Nope. You will just have to install them correctly, and you'll be fine. Why does this feel like the phone company talking? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Dangerously Dedicated
Chad R. Larson: I think earlier in this thread was a reference to a document somewhat later than the BIOS code shipped with an AT. Which probably makes some sense as FreeBSD won't run on a plain IBM AT box anyway... Do we want to start a new thread on what exactly =is= the authoritative documentation for PC architecture? The real issue is FreeBSD has to be able to boot on the hardware that's in the stores. Having abandoned my i486 Overdrive box just a week ago in favor of a decent 166 MHz (gee!) Pentium CPU, I'd like to claim that FreeBSD should be able to boot on hardware that's in the field rather than in the stores. That's definitely the bigger number of variants. Helge To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
subscribe freebsd-stable
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Removal of Disklabel
On Tue, Nov 21, 2000 at 12:33:11PM -0800, Cy Schubert - ITSD Open Systems Group wrote: I'm on tangent mode this afternoon, so this is not a direct reply. [excellent explanation that makes perfect sense snipped for brevity] Even if there's nothing else gained by this discussion, can this be put in the handbook? This is definitely a very good explanation of the whole situation wrt slices/partitions and FreeBSD/other OSes. --Stijn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Release Information
Hello All, When does the release information on the website usually get updated (http://www.freebsd.org/releases/index.html)? I've been slightly following the list, but I was just looking for a summary of changes and enhancements from 4.1.1 to 4.2. Jon * The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: The code freeze in RELENG_4 for src is now over.
On 20 Nov, Jordan Hubbard wrote: The 4.2 RELEASE has been rolled and you may now go back to your usual restrained hacking on -stable. That is all. Jordan, Sorry to bother, but when will the new Release be online. I'm not familiar with your procedure. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
perl locale not set
I installed 4.1-release from a .ISO from ftp.freebsd.org
I see that my locale is note set when ever I attempt to run my perl
scripts...
I keep getting ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_CTYPE = "en_US",
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
I looked thru the handbooke and mailing list to find out how to set my
locale, but no luck ...
If anyone can please let me know ... I would appreciate it.
thanks,
-mike
I am not currently subscribed to the list so please forward me a copy of
your reply as well ... thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Dangerously Dedicated
On 20 Nov, Chad R. Larson wrote: As I recall, Rodney W. Grimes wrote: The original IBM AT spec could give a rats ass about a partition table, all that it cares about is the boot block signature (magic 0xAA55). It is the MBR that knows what a partition table is and how to deal with it. The original spec says if there is a valid signature, load the code and jump to it passing the drive number in reg dl so that the boot code knows where it was loaded from. It was up to the MBR to decide what to do from then on. I think earlier in this thread was a reference to a document somewhat later than the BIOS code shipped with an AT. Do we want to start a new thread on what exactly =is= the authoritative documentation for PC architecture? The real issue is FreeBSD has to be able to boot on the hardware that's in the stores. Who's wrong, though interesting, doesn't matter. I trimmed the CC line. It was getting a bit long. As per the spec relating to this. There is definitive information out there, That is how HD Mfgs are able to draw up new ATA specs. Most of the issue regarding this, in your outline are correct. In addition, the partition table, as has been, suggested, was not important to the IBM spec. However, many aftermarket vendors, especially the people that wrote drivers for Seagate, required the table to be in place. So, the table is important for that reason. In addition, many WinX and DOS vendors expect that some sort of table will be there. The other missing item is the magic number and a correct cksum for the block. The checksum is part of the spec and is usually written in to many install tools. However, even on this point many BIOS Mfgs ignore the cksums and just boot the system. That is, the load the code in the MBR and pass the instruction pointer to that code. Hence, even in some (now) rare cases the cksum is important. If I've mis-stated some parts, someone will correct me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Dedicated disks (was: Dangerously Dedicated)
On 20 Nov, Mike Smith wrote: Let me state this one more time loudly for those calling themselves boot code experts. THE PARTITION TABLE IN THE MBR IS NOT DEALT WITH BY THE BIOS, BIOSES THAT TRY TO MAKE HEADS OR TALES OF PARTITION TABLES ARE TECHNICALLY BROKEN AND VIOLATE IBM AT COMPATIBILITY. If you doubt this go read about BIOS service 19H, IPL load. It doesn't matter how loudly you shout, or what exactly you stuff in your ears. The fact is that this code exists, is part of the de-facto platform standard, and has to be dealt with as such. You are welcome to continue to dual-boot FreeBSD and PC-DOS 2.0. In the meantime, the rest of us are living in the real world, and dealing with real-world problems. Please let us get on with what has to be done. Thankyou. Has it occured to you that perhaps there are people that really, really want DD? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RELEASE vs. Snapshot (BETA) question
Hello. What is ftp://releng4.freebsd.org/pub/FreeBSD/snapshots/i386/4.2-20001121-BETA (from Nov 21 13:49 GMT) related to ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.2-RELEASE (from Nov 20 17:49 GMT) The RELEASE seems older than the BETA. Liebe Grüße, Nora. -- [EMAIL PROTECTED]http://www.sappho-net.de/ Lesbian Computer Networks, Finland http://www.sappho.net/ Web for Women (von Frauen, für Frauen) http://www.w4w.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2
On Mon, Nov 20, 2000 at 18:52 -0600, Gerd Knops wrote: KVM users heads up: In order to support USB keyboards the generic kernel does not install an atkbd0 driver if no keyboard is detected. Some KVMs fail to sufficiently emulate a keyboard, causing the system to fail to detect a keyboard if the system is not currently selected on the KVM switch. This can be avoided by removing the 'flags 0x1' portion in the atkbd0 line of the kernel configuration file, then building and installing a new kernel. Is building and installing a new kernel necessary? Changing the flags in the USER_CONFIG menu or editing /boot/kernel.conf should suffice. So this could all be done at installation time and last for ever -- if I'm not overlooking some important point. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
