My Config:
PIIIx2 TYAN S1836 board with dual 10k rpm Connor SCSI, 384Mb ram,
and Maxtrox G200 16Meg SD ram.
Ftp'd kern.flp and mfsroot.flp from current.freebsd.org
(4.0-2000-03-08_Snap)...
Did a clean install ...
Things I noticed were:
During the install, couldn't get the Crypt distribution o
It seems Hans Ottevanger wrote:
> Hi folks,
>
> I just tried to boot the RC3 install floppies on my Pentium 66 testbox.
> It gets through the config stage without trouble, but then panics
> immediately with:
>
> ...
> pcib0: on motherboard
> pci0: on pcib0
> atapci0: possible> port 0
> x3f4-0
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I try to
On Fri, 10 Mar 2000, Peter Jeremy wrote:
> On 2000-Mar-10 12:06:18 +1100, Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> >Will the -current version of FreeBSD run on a multi-CPU axp machine and
> >use all of the CPUs?
>
> Not yet, but Real Soon Now.
>
> > Would that be a reliable box (assumin
On Thu, 9 Mar 2000, Bush Doctor wrote:
> Again my libRSAglue libraries before the above were:
> bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR*
> -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a
> lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglu
>> Original Message <<
On 3/10/00, 9:51:06 AM, R Joseph Wright <[EMAIL PROTECTED]> wrote
regarding single user mode problem:
> This has been going on for awhile, and I've looked everywhere for a
> solution. When I boot single user, the / filesystem gets mounted
> > Work on this driver is stalled owing to the fact that nobody that can
and
> > wants to work on it has access to the Compaq hardware required. You
> > can't use these controllers except in Compaq systems, which makes things
> > very difficult.
> that's true :-(
Again I would like to point out
Hi,
I need to use a quite big NFS server, serving ~120GB for ~200
clients, all OS's mixed (*BSD, Linux, HP-UX, IRIX, Solaris, Xterminals).
Is it worth it to use the -current branch (-release on next monday
perhaps?) for this important server, or should I rather use the
3.4-STABLE NFS im
Hi,
I installed a -current snap from internat.freebsd.org that was built
with crypto source from internat. I answered yes when sysinstall asked
me if I want the crypto stuff, but then found that it marked me as an
USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I
want to install
> >Very unfortunately, 6to4 is not yet supported in FreeBSD/KAME.
> >So now available options will be,
> > -Use freenet6 (for one hosts).
> > -Get IPv6 address block and connect to 6bone using gif tunnel.
>
> We hope to add 6to4 support for KAME/FreeBSD very soon (next week is a
> goo
> And here is the patches.
The last patches should work but I found a improvement related
to coexistence with gif, so this is the updated patches.
Thanks,
Yoshinobu Inoue
Index: net/if_gif.c
===
RCS file: /home/ncvs/src/sys/net/if_
[EMAIL PROTECTED] (FreeBSD mailing list) writes:
> You know people, it's quite sad that those with knowledge simply
> refuse to answer simple questions without "RTFM" attitudes and
> indirect (and more frequently direct) insults to intelligence and
> sensibilities.
The answer `run mergemaster' w
John Reynolds wrote:
> 1) There is a typo (spelling error) in one of the dialogs I was presented. I
> was trying to force pilot error into the situation :) and got a dialog that
> contained the following line:
>
> "You can also chose "No" at the next prompt and go back into the
>
On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote:
> 6to4 support seems to be very important for initial IPv6
> deployment on FreeBSD4.0, so I tried small additinal patches
> to make it available. And It seems to work.
>
> Could some FreeBSD4.0 user with direct internet connectivit
Kris Kennaway wrote:
>
> On Fri, 10 Mar 2000, Paul Richards wrote:
>
> > Non-root users can use the pw command to get information from the
> > master.passwd file e.g.
> >
> > ps showuser paul
> > paul:*:1000:1000::0:0:& Richards:/home/paul:/usr/local/bin/bash
>
> % pw showuser kkenn
>
> kkenn:
We use A Mylex DAC960PD RAID 5 controller, attached to 7
harddrives. One of the drives have had permanent failures, so
we changed it. Well, as I understand RAID 5, rebuilding the defective
drive should not involve the system, but On console (it ttyv0) I get
a message like "mlx0: error reading mes
In article you
write:
>> > Work on this driver is stalled owing to the fact that nobody that can
>and
>> > wants to work on it has access to the Compaq hardware required. You
>> > can't use these controllers except in Compaq systems, which makes things
>> > very difficult.
>> that's true :-(
>
A couple of comments on the RC3 CD image.
1) I tried to install by moving things out od the way:
cd /;mkdir save;mv * save;cd /usr;mkdir save;mv * save
and then boot from CD. Because I did not newfs /, it assumed /dev was
built and failed.
2) When I tried to install CRYPTO from the CD I
It appears inetd is broken if you don't have INET6 defined. This is
the case for picoBSD, for example:
> make -DRELEASE_CRUNCH
cc -O -pipe -Wall -DLOGIN_CAP -c /usr/source/src/usr.sbin/inetd/inetd.c
/usr/source/src/usr.sbin/inetd/inetd.c: In function `getconfigent':
/usr/source/src/usr.sbin/ine
On Fri, Mar 10, 2000 at 07:35:08AM -0600, Richard Seaman, Jr. wrote:
> On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote:
>
> > 6to4 support seems to be very important for initial IPv6
> > deployment on FreeBSD4.0, so I tried small additinal patches
> > to make it available. And It
Well, Iposted prior a message here because of the failure of our Mylex
DAC960PD based RAID 5.
After changing the faulty drive, the Mylex controller started rebuilding
the defective drive (hot-swapped the drive). On console I got (and still get!)
the message
mlx0: error reading message lo
On Fri, 10 Mar 2000, Paul Richards wrote:
> So what I'm puzzled about now is how come yours is different and do we
> think its correct that pwd.db and /etc/passwd have different information
> in them?
Oops, that was a cut-n-paste-o. I didn't notice the extra two fields the
second time :-)
It's
>
> > This has been going on for awhile, and I've looked everywhere for a
> > solution. When I boot single user, the / filesystem gets mounted on
> > wd0s4a even though /dev does not even have such an entry nor does
> > /etc/fstab, since these have all been updated.
> > This is not really such a
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said:
> On Thu, 9 Mar 2000, Bush Doctor wrote:
>
> > Again my libRSAglue libraries before the above were:
> > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR*
> > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a
> > lr
Kris Kennaway wrote:
>
> On Thu, 9 Mar 2000, Bush Doctor wrote:
>
> > Again my libRSAglue libraries before the above were:
> > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR*
> > -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a
> > lrwxr-xr-x 1 root wheel
Jim Bloom wrote:
>
> The
> following makefiles need to have the references to RSAglue removed:
>
> usr.sbin/ppp/Makefile
> usr.sbin/pppd/Makefile
> secure/libexec/sshd/Makefile
> kerberosIV/Makefile.inc
>
Ignore secure/libexec/sshd/Makefile. That was left over from when I was
trying to integr
Hi Jonathan,
> Note that I just committed some more changes to the IDA driver to
> 4.0-RC yesterday. The changes are:
>
> - support for EISA controllers (untested)
> - support for newer S2400 controllers (untested)
> - addition of IDA to the GENERIC kernel
> - support for installing directly ont
Out of da blue Jim Bloom aka ([EMAIL PROTECTED]) said:
> Kris Kennaway wrote:
> >
> > On Thu, 9 Mar 2000, Bush Doctor wrote:
> >
> > > Again my libRSAglue libraries before the above were:
> > > bantu.cl.msu.edu:dervish> ls -l /usr/lib/libR*
> > > -r--r--r-- 1 root wheel 810 Feb 28
> > > 6to4 support seems to be very important for initial IPv6
> > > deployment on FreeBSD4.0, so I tried small additinal patches
> > > to make it available. And It seems to work.
> > >
> > > Could some FreeBSD4.0 user with direct internet connectivity
> > > please try this patches and try to pin
> It appears inetd is broken if you don't have INET6 defined. This is
> the case for picoBSD, for example:
Woops, sorry.
I'll reflect it.
Thanks for the patches.
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> This has been going on for awhile, and I've looked everywhere for a
> solution. When I boot single user, the / filesystem gets mounted on
> wd0s4a even though /dev does not even have such an entry nor does
> /etc/fstab, since these have all been updated.
> This is not really such a problem unti
On Fri, Mar 10, 2000 at 11:45:19AM -0600, Alejandro Ramirez wrote:
> Hi Jonathan,
>
> > Note that I just committed some more changes to the IDA driver to
> > 4.0-RC yesterday. The changes are:
> >
> > - support for EISA controllers (untested)
> > - support for newer S2400 controllers (untested)
Well ... more confused!
I posted some messages here before ... after I though the RAID has been
rebuilt I tried to shutdown the server. On console I still got massive dumps
of the same message, as I posted before.
Shutdown was blocked, but I don't know by what, only thing to bring back the
server
On Tue, 7 Mar 2000, Doug Barton wrote:
> I've been meaning to post this for a while. I recently upgraded two way
> old 4.0 systems to post-signal changes -current. It's not quite a 3.x ->
> 4.0-Current upgrade, but it's close. I had to do a few things
> differently than what's in Updating,
> Hi Jonathan,
>
> > Note that I just committed some more changes to the IDA driver to
> > 4.0-RC yesterday. The changes are:
> >
> > - support for EISA controllers (untested)
> > - support for newer S2400 controllers (untested)
> > - addition of IDA to the GENERIC kernel
> > - support for insta
> We use A Mylex DAC960PD RAID 5 controller, attached to 7
> harddrives. One of the drives have had permanent failures, so
> we changed it. Well, as I understand RAID 5, rebuilding the defective
> drive should not involve the system, but On console (it ttyv0) I get
> a message like "mlx0: error r
On Fri, 10 Mar 2000, Alejandro Ramirez wrote:
> > Note that I just committed some more changes to the IDA driver to
> > 4.0-RC yesterday. The changes are:
> >
> > - support for EISA controllers (untested)
> > - support for newer S2400 controllers (untested)
> > - addition of IDA to the GENERIC ke
Hi,
I've managed to install RC3 without a hitch. The only problem I have is that
I can't get the XFree86 setup to configure X to run on my graphics hardware:
pci0: at 1.0 irq 11
My Compaq desktop using the Intel 810e motherboard.
Any pointers?
Daniel.
>
> Regardless, this is typically syptomatic of either a very old
> /boot/loader, non-use of the loader eg. through a /boot.config file, or
> an error in the entry for / in /etc/fstab.
>
Isn't /boot/loader updated upon making a new world? If so, it ought to be
current. I don't know any way o
On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote:
> By the way, I'm now very much interested in next round of
> test, that non 6to4 IPv6 prefix routing via 6to4 cloud.
>
> Could you please assign some non 6to4 prefix inside your
> environment?
Ok. c000::/64
> route add -inet6
> > By the way, I'm now very much interested in next round of
> > test, that non 6to4 IPv6 prefix routing via 6to4 cloud.
> >
> > Could you please assign some non 6to4 prefix inside your
> > environment?
>
> Ok. c000::/64
>
> > route add -inet6 3ffe:501:4819:2000:: -prefixlen 64 2002:cbb2:8d
> I installed a -current snap from internat.freebsd.org that was built
> with crypto source from internat. I answered yes when sysinstall asked
> me if I want the crypto stuff, but then found that it marked me as an
> USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I
> want to ins
I have 4 different Mylex DAC960 controllers that I cannot install Current
onto. (Tried from Late December to 2307). Sysinstall seems to get the
geometry wrong, and even telling sysinstall the "correct" geometry, it gives
a "tied to write beyond end of drive" error. Booting from a running -curr
On Sat, Mar 11, 2000 at 05:22:09AM +0900, Yoshinobu Inoue wrote:
> > I tried deleting the 6to4 address from an interface on the
> > interior node and did a ping6, but I get no replies (I think
> > you have to configure the route on your end first?).
>
> Yes, I have configured it, so it should w
On Fri, Mar 10, 2000 at 09:26:12PM +0200, Daniel Mpolokoso wrote:
> I've managed to install RC3 without a hitch. The only problem I have is that
> I can't get the XFree86 setup to configure X to run on my graphics hardware:
>
> pci0: at 1.0 irq 11
>
> My Compaq desktop using the Intel 810e m
On Sat, Mar 11, 2000 at 02:50:28AM +0900, Yoshinobu Inoue wrote:
> > I also had to adjust my ipv4 firewall rules to allow protocol
> > ipv6 through. Strange that I didn't have to do that when
> > doing a gif tunnel to freenet6.net. Also, what do I have to
> > do to enable ip6fw?
>
> Wmmm, it i
Hi all,
I've tried hard to get my PCI internal modem work with current.
I've tried editing /sys/isa/sio.c with the all possible byte
and word swaps of the vendor/dev printouts from the kernel
probe. The documentation for this USR modem says it's *not*
a winmodem, but a "standalone" modem.
The 3
> > > I tried deleting the 6to4 address from an interface on the
> > > interior node and did a ping6, but I get no replies (I think
> > > you have to configure the route on your end first?).
> >
> > Yes, I have configured it, so it should work now.
>
> Yes, it does. It all looks good.
>
> PING
Hi, I was looking around the internet to see how the opensource people
were getting along with all the suits against them, and I found a site
with a freebsd css-auth patch and nist archive tared; I was wondering how
well dvd playback was at this point?
all those wondering, the site is linked from
Hi all...
Maybe there is a valid reason for this, but when I attempt to boot the 4.0
kern.flp without a keyboard attached (I share one keyboard between four
systems, here), it displays keyboard: no and the BTX loader message, and
ceases to display ANY output on the attached monitor (though it doe
In article <[EMAIL PROTECTED]>, Jim Bloom <[EMAIL PROTECTED]> wrote:
[when dllockinit() should be called]
> It should be called somewhere between the starting of the process
> and the creation of the second thread. There is no problem if there
> is only one thread.
>
> THREAD Create would be f
On Fri, Mar 10, 2000 at 11:21:15AM -0800, R Joseph Wright wrote:
> >
> > Regardless, this is typically syptomatic of either a very old
> > /boot/loader, non-use of the loader eg. through a /boot.config file, or
> > an error in the entry for / in /etc/fstab.
> >
>
> Isn't /boot/loader updated u
* From: Edwin Kremer <[EMAIL PROTECTED]>
* On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote:
*
* : Your system is too old to use this bsd.port.mk.
*
* According to the mail headers, your system clock is about one year
* behind actual time. That might have screwed up the `make'..
> >
> > Regardless, this is typically syptomatic of either a very old
> > /boot/loader, non-use of the loader eg. through a /boot.config file, or
> > an error in the entry for / in /etc/fstab.
> >
>
> Isn't /boot/loader updated upon making a new world? If so, it ought to be
> current. I don'
On Fri, 10 Mar 2000, Lawrence Farr wrote:
> I have 4 different Mylex DAC960 controllers that I cannot install Current
> onto. (Tried from Late December to 2307). Sysinstall seems to get the
> geometry wrong, and even telling sysinstall the "correct" geometry, it gives
> a "tied to write beyon
$BEbFM$J%a!<%k$*5v$72<$5$$!#(J
$B4?Aw7^2q$d7k:'<0$N%7!<%:%s$G$9!#(J
$B$=$3$G!"1c2q44;vMM$K$*CN$i$;$G$9!#(J
$B$46=L#$N$J$$J}$K$O?4$+$i$*OM$S?=$7>e$2$^$9$H$H$b$K!"(J
$B:o=|$N$*4j$$$r?=$7>e$2$^$9!#(J
$B!|!|!|4{B8$N%S!<%k$,$"$J$?MM$@$1$N%S!<%k$K%o%s%?%C%A$GJQ?H!#!|!|!|(J
$B!Je$K!"%7!<%k$
In message <[EMAIL PROTECTED]> Kent Hauser writes:
: I've tried hard to get my PCI internal modem work with current.
Well, there's no support for that yet.
: I've tried editing /sys/isa/sio.c with the all possible byte
: and word swaps of the vendor/dev printouts from the kernel
: probe. The doc
Soren Schmidt wrote:
>
[...]
> Hmm, seems to be a resource conflict problem, question is what is
> causing this. Could you do a verbose boot both with the old
> working kernel, and the new failing one ?
>
Attached are two files. Both kernels used are built from the same config
file, which is m
BTW, my latest patches can be found at
http://people.freebsd.org/~imp/sio-current-pci-patch
and it works for me on my 3com model 5610 and actiontek pci controller
based modem. If your 3com modem isn't a 5610, then it is almost
certianly a winmodem, despite what you've been told.
For a long time I have noticed that when I build kdm from the kdebase
port, it works.
But if I used packages off either the CDs or ftp sites, it doesn't work.
Specifically if I
do a 'strings' on the binary and grep for /, some of the paths I see
have XBINDIR
rather than explicit references to /usr
> I have 4 different Mylex DAC960 controllers that I cannot install Current
> onto. (Tried from Late December to 2307). Sysinstall seems to get the
> geometry wrong, and even telling sysinstall the "correct" geometry, it gives
> a "tied to write beyond end of drive" error. Booting from a runni
> And here is the patches.
The last patches should work but I found a improvement related
to coexistence with gif, so this is the updated patches.
Thanks,
Yoshinobu Inoue
I applied a variant of your patch to my NetBSD/i386 -currentish box that
also uses the KAME stack and was a
I've been playing with it using the original sources and the patches that
were posted a long time ago on this list. On my DVD drive (Sony DDU220E),
the software fails on gettitlekey. I've chatted with Soren and he left me
with something to try that I never did (can you say, busy busy busy :(
Fo
I am currently experiencing problems with the 0307 -CURRENT snapshot, and
the dc driver. I previously have had no problems with the pn driver I had
been using in 3.4-STABLE. I installed current on this machine because as
of now, the wd driver in stable doesn't like my larger IDE drive very
much.
On Thu, 2 Mar 2000, Theo van Klaveren wrote:
> stereofftscope.cpp:~80: sorry, not implemented. (something about symbol
> to big for symbol table). Recompile all your sources with -fhuge-objects.
>
> I finished the build with make -k, but I have no arts :( I suspect this to
> be a FreeBSD problem
>Maybe there is a valid reason for this, but when I attempt to boot the 4.0
>kern.flp without a keyboard attached (I share one keyboard between four
>systems, here), it displays keyboard: no and the BTX loader message, and
>ceases to display ANY output on the attached monitor (though it does
>cont
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Shaun (UNIX) wrote:
> Hello,
>
> You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob
> problems like alot of us are. What is your system config?
>
> Yes it is FAST! and I love itI see that the 64MB memor
Kazutaka YOKOTA wrote to Ryan Thompson:
> >Maybe there is a valid reason for this, but when I attempt to boot the 4.0
> >kern.flp without a keyboard attached (I share one keyboard between four
> >systems, here), it displays keyboard: no and the BTX loader message, and
> >ceases to display ANY out
On Fri, 10 Mar 2000, Walter Brameld wrote:
> I wonder about other nit-picky things, like why is sound.doc (to
> which I've seen numorous RTFM references) still written for
> configurations under FreeBSD 2.1 ?
Because no-one has rewritten it?
Kris
In God we Trust -- all others must submit
> > >Isn't there a better way to identify a serial console?
> >
> > I don't understand. What do you expect the boot loader to do?
>
> I'm not sure, that's why I asked the list :-) Really, what I was asking
> is if there is a better way to detect a serial console.. Rather than the
> current l
Why does it seem like I'm posting a lot of messages about keyboards,
today? :-)
I seem to remember hearing a similar problem a month or two ago, and do
not remember if it was resolved. I couldn't remember enough about it to
find it in the list archives. In any case, I at least want to say "me
t
On Fri, 10 Mar 2000, Brian Beattie wrote:
> 2) When I tried to install CRYPTO from the CD I got errors for a number of
> them, something about not being able to read a script of something (it was
> 2am so I do not have the exact error message), so i installed from FTP.
...
> 3) First time i dec
On Fri, 10 Mar 2000, Jim Bloom wrote:
> I believe it is a build order and dependency problem that shouldn't
> exist. libkrb is built before libRSAglue and then the shared library is
> built with -LRSAglue which is only found in /usr/lib.
> kerberosIV/Makefile.inc has a line "LDADD+= -LRSAglue".
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Kris Kennaway wrote:
> On Fri, 10 Mar 2000, Walter Brameld wrote:
>
> > I wonder about other nit-picky things, like why is sound.doc (to
> > which I've seen numorous RTFM references) still written for
> > configurations under FreeBS
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Walter Brameld wrote:
> On Fri, 10 Mar 2000, in a never-ending search for enlightenment, Kris Kennaway wrote:
> > On Fri, 10 Mar 2000, Walter Brameld wrote:
> >
> > > I wonder about other nit-picky things, like why is sound.doc (to
>On my -current system, after rebooting, the keyboard was in a funny state
>(all 4 LEDs were turned on. My keyboard also has an internal click
>mechanism, which was no longer functional) I plugged the keyboard into
>another machine at that point, and it reset itself and worked fine on that
>mac
In article <[EMAIL PROTECTED]>,
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Sun, 5 Mar 2000, Brian Dean wrote:
>
> > The perl script h2ph does not exit immediately on des.h, it sets it's
> > $Exit value to 1, but continues processing. If the original poster
> > would check further back in his
Mike Smith wrote to Ryan Thompson:
> > > >Isn't there a better way to identify a serial console?
> > >
> > > I don't understand. What do you expect the boot loader to do?
> >
> > I'm not sure, that's why I asked the list :-) Really, what I was asking
> > is if there is a better way to detec
On Fri, 10 Mar 2000, John Polstra wrote:
> This is still broken. I ran into it when upgrading a Feb. 29 -current
> system to today's -current. I didn't use make -j and I didn't take
> any shortcuts.
Both were compiled with the same options (i.e. you didn't do the first one
NO_OPENSSL or someth
On Fri, 10 Mar 2000, Walter Brameld wrote:
> Yeah, I'll buy that. Now I gather it was not written by the commiters
> and it's not their responsibility (?) to rewrite it. But is there any
> point in keeing it?
This is FreeBSD, no-one has any resposibilities whatsoever :-)
It should probably ei
On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright wrote:
> >
> > Regardless, this is typically syptomatic of either a very old
> > /boot/loader, non-use of the loader eg. through a /boot.config file, or
> > an error in the entry for / in /etc/fstab.
> >
>
> Isn't
In article <[EMAIL PROTECTED]>,
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Fri, 10 Mar 2000, John Polstra wrote:
>
> > This is still broken. I ran into it when upgrading a Feb. 29 -current
> > system to today's -current. I didn't use make -j and I didn't take
> > any shortcuts.
>
> Both we
At 05:35 PM 3/8/00 +, Kris Kennaway wrote:
>On Wed, 8 Mar 2000, Jeffrey J. Mountin wrote:
>
> > What I did not check is removing RSAref after a buildworld and checking for
> > breakage, but that smacks of shooting one's self in the foot.
>
>That should just revert to the previous case of compl
At 05:06 PM 3/10/00 -0800, Mike Smith wrote:
>Note also that the probe-for-keyboard feature is only used on the
>installation media; it's not the default for system behaviour (yet).
Hopefully that "yet" will be "never" so one can boot sans keyboard and
later hook one up if need be.
Jeff Mounti
> At 05:06 PM 3/10/00 -0800, Mike Smith wrote:
> >Note also that the probe-for-keyboard feature is only used on the
> >installation media; it's not the default for system behaviour (yet).
>
> Hopefully that "yet" will be "never" so one can boot sans keyboard and
> later hook one up if need be.
> > > > >Isn't there a better way to identify a serial console?
> > > >
> > > > I don't understand. What do you expect the boot loader to do?
> > >
> > > I'm not sure, that's why I asked the list :-) Really, what I was asking
> > > is if there is a better way to detect a serial console.. Rat
>> >And, if not, could
>> >the loader at least not display a message on the local monitor like
>> >"Switching output to serial console...", or better yet, "Switching output
>> >to serial console in 10 seconds.. press any key to abort"?
>>
>> Which key do you mean? The system has found no keyboa
Kazutaka YOKOTA wrote to Ryan Thompson:
> It sounds like the keyboard interface of your motherboard has somewhat
> become flaky; it may even be broken.
>
> It is NOT recommended that you attach or detach the keyboard while the
> power is on. The keyboard interface of the PC motherboard is not
>
At 12:23 PM 3/10/00 -0800, Jordan K. Hubbard wrote:
> > I installed a -current snap from internat.freebsd.org that was built
> > with crypto source from internat. I answered yes when sysinstall asked
> > me if I want the crypto stuff, but then found that it marked me as an
> > USA_RESIDENT=YES in
> It's indeed inconvenient that you cannot safely hot-plug the keyboard.
> And the world is heading for the USB standard... :-)
This actually opens another entire can of worms; detecting a USB keyboard
at the bootstrap level is _not_ easy. It looks like at least some
systems aren't setting the
John Polstra wrote:
> I don't believe I've ever used any special options, and my make.conf
> file is "normal" except that it has "USA_RESIDENT=YES" in it.
I know for certain that when I ran into this that I did not do
anything other than a "make world" on a standard -current system,
i.e., nothing
Mike Smith wrote to Ryan Thompson:
> > "Don't have a keyboard" != "No keyboard detected" != "Serial Console".
>
> No keyboard detected -> local console won't be used -> use serial console
Yes, that would seem to sum up the current behavior quite well. :-)
> > Ok, so they can't be probed. H
>I don't make a habit of keyboard swapping, and I HAVE experienced some
>minor glitches before (such as weird scan codes being sent, or the state
>of caps lock changing).
You have been lucky that you didn't broke the motherboard when swapping
the keyboard.
The fact that you only had minor prob
>> It's indeed inconvenient that you cannot safely hot-plug the keyboard.
>> And the world is heading for the USB standard... :-)
>
>This actually opens another entire can of worms; detecting a USB keyboard
>at the bootstrap level is _not_ easy. It looks like at least some
>systems aren't sett
At 05:54 PM 3/10/00 -0800, Mike Smith wrote:
>Since you can't safely hot-plug the PC keyboard, that wouldn't be very
>smart. The only way to auto-detect the use of a serial console is to
>look for a keyboard; if one isn't plugged in, there's no local console,
>end of story.
Can't safely? Why th
Ryan Thompson wrote:
> Thanks for the info. When I have another $500 burning a hole in my
> checkbook, I will probably order another keyboard, just so I have
> another one, if nothing else. :-)
Why not just get a decent monitor/keyboard switch? Belkin makes a
nice 4-port in the $200 range that
Brian Dean wrote to Ryan Thompson:
> Ryan Thompson wrote:
> > Thanks for the info. When I have another $500 burning a hole in my
> > checkbook, I will probably order another keyboard, just so I have
> > another one, if nothing else. :-)
>
> Why not just get a decent monitor/keyboard switch? Be
Jeffrey J. Mountin wrote to Mike Smith:
> At 05:54 PM 3/10/00 -0800, Mike Smith wrote:
> >Since you can't safely hot-plug the PC keyboard, that wouldn't be very
> >smart. The only way to auto-detect the use of a serial console is to
> >look for a keyboard; if one isn't plugged in, there's no loc
In message <[EMAIL PROTECTED]> "Jeffrey J. Mountin" writes:
: Can't safely? Why the hell not?
The spec doesn't allow for it. And most mobo mfg don't properly
ground things so that you won't accidentally introduce a large static
zap into the system.
: Been hot-swapping keyboards for many years
On Fri, 10 Mar 2000, Walter Brameld wrote:
> On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright
>wrote:
> > >
> > > Regardless, this is typically syptomatic of either a very old
> > > /boot/loader, non-use of the loader eg. through a /boot.config file, or
> > > an
1 - 100 of 103 matches
Mail list logo
