Quite a few steps were necessary to go from 3.1 to -CURRENT which I
think are not explained anywhere. Maybe it would be useful to add
this to /usr/src/UPGRADING?
* First, I ran a `make buildworld'. Nothing special here.
* Then I had to compile and install a -CURRENT kernel. For this, I
need
Sorry, this is not -current (FreeBSD 3.2) but
to file a bug report I think it's still too vague...
I ran ntop (/usr/ports/net/ntop) for a moment,
typed j inadvertently and ntop bailed out.
From then on I'm hearing beeps all the way. I restarted
ntop. Beeps went away. q in ntop. Beeps are t
It seems Wes Morgan wrote:
> Has there been any resolution to the known-broken-dma drives and the ata
> driver? I haven't seen any commits or LINT options to this effect, and it
> seems to me that since it is the new default driver that something should
> be in place before it goes to -release.
L
Please try out the newest patchset against CURRENT as of this night,
2000-02-08 02:00 GMT.
http://www.etla.net/~n_hibma/usb/patches/USB-patch-2208
It contains a working USB Zip 100 driver, based on state handling, that
provides >600kb/s at 64kb blocks(*). Working as in, you
Kai Großjohann wrote:
>
> I now think that I should have made a new kernel, first.
>
> Hm. The file /usr/src/UPDATING doesn't say that I should, so maybe I
> can be forgiven for not knowing, and there's nothing in Chapter 17 of
> the Handbook, either.
>
> Do you think making a kernel first wil
Yoshinobu Inoue wrote:
>
> > If IPv4 dotted-decimal forms are given, getaddrinfo() calls finally
> > inet_pton(). inet_pton() is defined in RFC2553 and it does not permit
> > non-standard IPv4 dotted-decimal, such as 10.10
>
> Do people have troubles with this change?
Not supporting 127.1 viola
Barry,
I think I know the problem you have.
When "device scbus0" changed to "device scbus" in LINT and I applied
that to my config file I found I could no longer wire down my disks
to scbus0 unless I changed the base SCSI code line back to "device
scbus0".
This is what I have:
device
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
> Kai Großjohann wrote:
> >
> > I now think that I should have made a new kernel, first.
> >
> > Hm. The file /usr/src/UPDATING doesn't say that I should,[...]
>
> UPDATING does say you need to do that.
Hm. Upon closer inspection, you're right.
[EMAIL PROTECTED] (Kai Großjohann) writes:
> * Then I had to compile and install a -CURRENT kernel. For this, I
> needed "cd /usr/src/usr.bin/genassym; make install" and "cd
> /usr/src/usr.sbin/config; make install".
Thanks to Daniel who pointed out that this (the fact that a kernel
needs t
On Tue, Feb 08, 2000 at 01:54:31PM +0100, Kai Gro?johann wrote:
> "Daniel C. Sobral" <[EMAIL PROTECTED]> writes:
>
> > Kai Gro?johann wrote:
> > >
> > > I now think that I should have made a new kernel, first.
> > >
> > > Hm. The file /usr/src/UPDATING doesn't say that I should,[...]
> >
> >
Kai Großjohann wrote:
>
> Quite a few steps were necessary to go from 3.1 to -CURRENT which I
> think are not explained anywhere. Maybe it would be useful to add
Because that's WAY too much trouble. Upgrade from latest -STABLE to
-CURRENT. Do not try to upgrade from anything else.
--
Daniel C.
Hi!
On a recent -current (don't know if this is a known problem),
when cursor is switched off on one virtual console, it is
turned off on *all* virtual consoles. Any patch to try?
--
Ruslan Ermilov Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECT
when trying to do
mdir z:
my current kernel immediately freezes!
here is dmesg (the ata devicee was attached to isa bus in the config
file, which is wrong but did not matter all the time):
The attached file "core" is the dmesg-output.
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniv
> Not supporting 127.1 violates POLA. Me, I hate 127.1. But some people
> expect it to work, and they have every right to.
Now there is some discussion about it on ietf/ipng list, but
not yet clear if future document allow it or not.
If it does not become clear in this 1 or 2 days,
I'll change ge
>On Tue, Feb 08, 2000 at 11:44:41PM +0900, Kazutaka YOKOTA wrote:
>> >On a recent -current (don't know if this is a known problem),
>> >when cursor is switched off on one virtual console, it is
>> >turned off on *all* virtual consoles. Any patch to try?
>>=20
>> Do you mean the "text" cursor, or
If memory serves me right, Ollivier Robert wrote:
> Please use consistent names like "mroute6d_flags" and "mroute6d_program".
Thanks...these changes will be reflected in the next version I post.
For your information, I didn't use different naming conventions just for
the hell of it...I just neg
On Wed, Feb 09, 2000 at 12:38:15AM +0900, Kazutaka YOKOTA wrote:
>
> >On Tue, Feb 08, 2000 at 11:44:41PM +0900, Kazutaka YOKOTA wrote:
> >> >On a recent -current (don't know if this is a known problem),
> >> >when cursor is switched off on one virtual console, it is
> >> >turned off on *all* virt
I am running the lastest -current (just did a cvsup followed by a make
world last night). I am getting these link errors when trying to compile
the developement version of kdesupport, which I obtained thru cvsup. (KDE
uses cvsup for its development versions.)
I get the following errors. I have
It seems F. Heinrichmeyer wrote:
> when trying to do
>
> mdir z:
>
> my current kernel immediately freezes!
Yeah, I used a bde patch verbatim, shouldn't have done that :)
Fixed.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
Forrest Aldrich wrote:
>
> Has anyone gotten the Megahertz pccards to work with the boot floppies? I don't
>believe the correct entry is there for them. I recall there being a discussion here,
>indicating that the modification wouldn't be difficult. Is there any way we can get
>this fixed?
Gerald Abshez wrote:
> I thought that I'd heard that the 3CCFE574BT (10/100) from
> 3com/Megahertz was supported, but it seems like it isn't. I've tried
Actually, it is. I'm running one in my laptop right now, in fact, and
it works fine. What problems are you seeing?
--
Frank Mayhar [EMAIL PRO
> shin> The 1st trial seems to be rejected at,
> shin> 500 Illegal PORT range rejected.
> shin> and 2nd trial seems to be accepted at,
> shin> 200 pcmd command successful.
>
> This problem was reported at [FreeBSD-users-jp 46521]. It is
> Japanese FreeBSD mailing list.
> In my experi
On Wed, 9 Feb 2000, Yoshinobu Inoue wrote:
> > Not supporting 127.1 violates POLA. Me, I hate 127.1. But some people
> > expect it to work, and they have every right to.
>
> Now there is some discussion about it on ietf/ipng list, but
> not yet clear if future document allow it or not.
> If it d
i have a problem with HP desktop which has onboard crystal
sound-chip.
i talked briefly with cameron yesterday on irc, and he pointed out
where i was wrong in my earlier attempts, but aven after that i
was only able to get the boot to initialize the chip, i still get
no sound.
=(
the machine i
Donn Miller wrote:
> I am running the lastest -current (just did a cvsup followed by a make
> world last night). I am getting these link errors when trying to compile
> the developement version of kdesupport, which I obtained thru cvsup. (KDE
> uses cvsup for its development versions.)
>
> I ge
I'm using the floppies from the 01/27 CURRENT (as that's all they provide
now, on current.freebsd.org)... and I can't get it to recognize the
cards. Period.When it goes to initialize, and time for installation,
nothing shows up for NICs... just ppp, lp0, etc.
Is very frustrating!
For wh
mika ruohotie stated:
>
> i have a problem with HP desktop which has onboard crystal
> sound-chip.
>
> i talked briefly with cameron yesterday on irc, and he pointed out
> where i was wrong in my earlier attempts, but aven after that i
> was only able to get the boot to initialize the chip, i st
In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: Look at the ata.4 manpage, there is a sysctl knob that can change the
: modes, if it gets too bad we can always make it boot in PIO mode, and
: then the user can change to known safe DMA modes in rc.something...
I know that I have one wdma dr
In message <[EMAIL PROTECTED]> Kai=?iso-8859-1?q?_Gro=DFjohann?=
writes:
: Hm. Upon closer inspection, you're right. The following entry has
: this:
I had thought to put something like
: /
: | 19990929:
: | The sigset_t datatype has been changed from an integral type
: | t
In message <[EMAIL PROTECTED]> Yoshinobu Inoue writes:
: If standard documents would be updated to disallow it in the
: future, then we need to think of changing getaddrinfo()
: behaviour at that time.
Agreed. I think in code freeze/feature freeze it is a bad time to
change this, reguardless of
In message <[EMAIL PROTECTED]> Gerald Abshez writes:
: FYI, Warner has stated that Cardbus isn't working, and there are known
: problems with some of the ethernet cards (interrupts don't seem to be
: working correctly).
As far as I know, the interrupt problems were fixed by Matt Dodd a
while ago.
According to Ruslan Ermilov:
> >From my recent experience upgrading from 3.3-S to 4.0-C:
> 1. You do not need a -current kernel for buildworld stage.
chown failed with a sig12 ("bad syscall" -- which I expected to get) so I
don't agree with you...
> 3. You will need to `make -DNOINFO installworl
In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
: I'm using the floppies from the 01/27 CURRENT (as that's all they provide
: now, on current.freebsd.org)... and I can't get it to recognize the
: cards. Period.When it goes to initialize, and time for installation,
: nothing shows up
With my Acer AW35/Pro (CS4236) and -current I can play sound just fine,
but I can't record. (Recording and full duplex worked fine with
3.4-stable.)
When I run
rec -c 1 -f s -r 44100 -s w test.wav
rec just sits, blocked in pcmrd, and rec can't be interrupted with
ctl-c. The output file
In article <[EMAIL PROTECTED]>,
Patrick M. Hausen <[EMAIL PROTECTED]> wrote:
>
> Yes, but now we have three different ways to update:
[...]
> 2. call cvsup from /usr/local/etc/periodic with supfiles for whatever you
>need ...
Not a good idea. Add a new crontab entry instead. If everybody u
In article <[EMAIL PROTECTED]>,
Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> Donn Miller wrote:
>
> > I am running the lastest -current (just did a cvsup followed by a make
> > world last night). I am getting these link errors when trying to compile
> > the developement version of kdesupport, whi
Frank Mayhar wrote:
>
> Gerald Abshez wrote:
> > I thought that I'd heard that the 3CCFE574BT (10/100) from
> > 3com/Megahertz was supported, but it seems like it isn't. I've tried
>
> Actually, it is. I'm running one in my laptop right now, in fact, and
> it works fine. What problems are you
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Forrest Aldrich writes:
> : 3CCFE574BT
That's mine...
> Boot -v and send me the output. You can get to the dmesg output from
> before the console switch by using the scroll lock key. After the
> switch, it is on vty2 or something like that
ps:
root@rodia> ps
PID TT STAT TIME COMMAND
311 p1 IN+0:00.05 su (M-@^A)
10030 p6 SN 0:00.13 su (M-@^A)
34398 p6 RNL+ 0:00.00 ps (M-@^A)
249 v0 INs+ 0:00.08 -bash (M-@^A)
250 v1 INLs+ 0:00.01 /usr/libexec/getty Pc ttyv1 (M-@^A)
251 v2 INLs+ 0:00.01 /usr
How do
[cc'd JKH: Assuming this passes review, can I put it in 4.0 and MFC? ]
passwd(1) normally enforces mixed case passwords -- or at least it forces
you to enter the lower case password several times before it will actually
let you use it.
This is a pain if you're using the Unix password fi
On Tue, 08 Feb 2000 14:22:25 EST, Gerald Abshez wrote:
>
>There is only the ethernet card plugged in. After the boot probe
>completes, I get:
>ep0: No irq?!
I also have one of these cards, and it's working fine under 4.0-CURRENT.
Seems like the default IRQs used by pccard are being used by somet
with the latest (ok, 2 days old) version of the kernel source, i've gotten
audio up on my poor little workstation. but, here's the problem: buffer
space.
mp3's play really slowly, other audio apps are fine, up untill you try to
stop them, then the buffer takes around 2 seconds to clear.
card i
Patel, you're a life saver!This is exactly what was needed, change the
IRQ. In my case, I chose option 2 and walla.
Amazing, so simple.
Note this is using the snapshot that is 02/08/2000, latest (floppies).
Thank you.
Forrest
At 11:56 AM 2/8/00 -0800, Parag Patel wrote:
>On Tue, 08 Fe
On Tue, Feb 08, 2000 at 08:25:15AM +0100, Ollivier Robert wrote:
> According to Ruslan Ermilov:
> > >From my recent experience upgrading from 3.3-S to 4.0-C:
> > 1. You do not need a -current kernel for buildworld stage.
>
> chown failed with a sig12 ("bad syscall" -- which I expected to get) so
On Tue, Feb 08, 2000 at 11:03:48AM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]>
>Kai=?iso-8859-1?q?_Gro=DFjohann?= writes:
> : Hm. Upon closer inspection, you're right. The following entry has
> : this:
>
> I had thought to put something like
>
> : /
> : | 19990929:
> : |
On Tue, Feb 08, 2000 at 01:16:14PM -0600, Raul Zighelboim wrote:
> ps:
> root@rodia> ps
> PID TT STAT TIME COMMAND
> 311 p1 IN+0:00.05 su (M-@^A)
I've seen ps(1) output similar to this when my kernel and `world'
versions were not compiled from the same sources. A build/installwo
Hi,
I've just installed a 4.0-20000208-SNAP on a test machine, sources
current as of 9am EST for the make world/make release.
The following command fails almost immediately:
cd /usr/src && make world
-
47 matches
Mail list logo
