Hi
Has the svn-cvs exporter died? Or have the cvsup/csup servers
been retired as threatened in a previous thread (I might have missed
the headsup)?
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
On 15 November 2012 13:47, Ian FREISLICH i...@clue.co.za wrote:
Hi
Has the svn-cvs exporter died? Or have the cvsup/csup servers
been retired as threatened in a previous thread (I might have missed
the headsup)?
The FreeBSD cluster is undergoing maintenance. In particular the main
machines
On 11/15/2012 12:58 PM, Eitan Adler wrote:
On 15 November 2012 13:47, Ian FREISLICH i...@clue.co.za wrote:
Hi
Has the svn-cvs exporter died? Or have the cvsup/csup servers
been retired as threatened in a previous thread (I might have missed
the headsup)?
The FreeBSD cluster is undergoing
Good luck with employing full discombobulation!
I think this is the main requirement for _cloud computing_.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/cvsup-csup-servers-stale-tp5761290p5761389.html
Sent from the freebsd-current mailing list archive at Nabble.com
. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup config
file, however in system installed from 9.0 snapshot (maybe two
weeks old) this file points to version 8 files, so I need
to csup
*default release=cvs tag=RELENG_8
which is incorrect, I think. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup config
file, however in system installed
updated via csup. In both example files there is line specifying
what to csup
*default release=cvs tag=RELENG_8
which is incorrect, I think. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without
/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup config
file, however in system installed from 9.0 snapshot (maybe two
weeks old) this file points to version 8 files, so I need to
correct it for 9.0-PRERELEASE to not accidentally download older
. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup config file,
however in system installed from 9.0 snapshot (maybe two weeks old)
this file points to version 8 files, so I need to correct
csup. In both example files there is line specifying what to csup
*default release=cvs tag=RELENG_8
which is incorrect, I think. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup
*default release=cvs tag=RELENG_8
which is incorrect, I think. It is convenient for me to issue just
csup -h cvsup.freebsd.sk /usr/share/examples/cvsup/stable-supfile
to update full sources without need to create any cvsup config file,
however in system installed from 9.0 snapshot (maybe two
/cvsup/stable-supfile
to update full sources without need to create any cvsup config file,
however in system installed from 9.0 snapshot (maybe two weeks old)
this file points to version 8 files, so I need to correct it for
9.0-PRERELEASE to not accidentally download older version sources.
The same
cvsup is a port, so you would need to install that to have cvsup. csup
and cvsup are totally different code bases in different languages.
(csup is C and cvsup is Modula-3.) You probably want to install cvsup
as a package as installing the port also requires building all of the
Modula-3
On Wed, Oct 05, 2011 at 03:21:45PM -0700, David O'Brien wrote:
On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote:
--- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig2011-09-09
17:58:12.867431639 +0300
+++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-09
On 10/06/2011 01:41, Thomas Mueller wrote:
Anyway, from what I read, csup is better, and I think I can use the same
supfile and same server that I would use for cvsup?
Yes.
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth
amd64 and looking to update via source.
There is /usr/bin/csup but no cvsup. Can I safely use csup on tag RELENG_9 to
update, or is that broken?
Does this csup come under the cvsup bug in this thread?
Tom
___
freebsd-current@freebsd.org mailing list
without a
whole lot of testing. :)
Thanks,
Adrian
I am now in 9.0-BETA2 amd64 and looking to update via source.
There is /usr/bin/csup but no cvsup. Can I safely use csup on tag RELENG_9
to update, or is that broken?
Does this csup come under the cvsup bug in this thread?
cvsup is a port
On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote:
--- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig 2011-09-09
17:58:12.867431639 +0300
+++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-09
17:58:30.380428486 +0300
@@ -180,7 +180,7 @@
pausedThreads : T;
On Tue, Oct 4, 2011 at 2:19 AM, Adrian Chadd adr...@freebsd.org wrote:
On 4 October 2011 05:53, Maxime Henrion m...@freebsd.org wrote:
Great, that's a relief. I knew the pthread library was free to wake a
thread up even if it hadn't been signaled, which is why one always has
to call
Hi all,
I've committed this to -head.
I'd appreciate it if csup users would give this a thorough testing and
report back to the list with results.
I won't submit this as a merge candidate this to stable/9 without a
whole lot of testing. :)
Thanks,
Adrian
of the
CVSup protocol is a lot more twisted than it would seem, plus a
comment of mine was definitely misleading (it should say that the
detailer thread will hang, not the lister one). Here are some
explanations that should help clarify things.
When the updater thread encountered a problem in updating
On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote:
Knowing all that, what's happening seems quite clear. If
fixups_close() is called while there was still fixup requests pending,
those should be processed by the detailer thread before it returns.
Subsequent fixups_get() call
On Mon, Oct 3, 2011 at 11:30 PM, Jilles Tjoelker jil...@stack.nl wrote:
On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote:
Knowing all that, what's happening seems quite clear. If
fixups_close() is called while there was still fixup requests pending,
those should be processed by
On 4 October 2011 05:53, Maxime Henrion m...@freebsd.org wrote:
Great, that's a relief. I knew the pthread library was free to wake a
thread up even if it hadn't been signaled, which is why one always has
to call pthread_cond_wait() inside of a while() loop checking for the
condition, but
2011/9/19 Alexander Zagrebin al...@visp.ru:
I've tried this patch. Now csup hangs before handling fixups.
So there is no message Applying fixups... at all.
Wow. Hm. Where's the author when one needs them..
Adrian
___
freebsd-current@freebsd.org
Hi,
So I've taken a look at the csup source.
The problem here is the updater thread setting the closed state
(fixups_closed()) before calling updater_batch() again to handle
fixups.
Checking for size != 0 at that point may not be valid at the list size
may actually be 0 for a short period of
Adrian Chadd adr...@freebsd.org wrote:
So I've taken a look at the csup source.
[...]
What about this patch:
[...]
Oliver, would you please try that?
I have a problem with cvsup, not csup - Alexander mentioned a csup problem.
___
freebsd
On Sun, Sep 18, 2011 at 12:22:53PM +0200, Oliver Lehmann wrote:
Adrian Chadd adr...@freebsd.org wrote:
So I've taken a look at the csup source.
[...]
What about this patch:
[...]
Oliver, would you please try that?
I have a problem with cvsup, not csup - Alexander mentioned
Ah, you're the one with the csup problem.
Would you mind trying csup again, and if it doesn't work, try this patch:
Index: updater.c
===
--- updater.c (revision 224905)
+++ updater.c (working copy)
@@ -240,9 +240,9 @@
*
Kostik Belousov kostik...@gmail.com wrote:
Did you saw the message with the patch for tzcode I mailed to you ?
Mmmh... no didn't reached my mailbox - can you resend it please?
___
freebsd-current@freebsd.org mailing list
On Sun, Sep 18, 2011 at 02:46:24PM +0200, Oliver Lehmann wrote:
Kostik Belousov kostik...@gmail.com wrote:
Did you saw the message with the patch for tzcode I mailed to you ?
Mmmh... no didn't reached my mailbox - can you resend it please?
See the Segfault in libthr.so on 9.0-BETA2
Hi!
So I've taken a look at the csup source.
The problem here is the updater thread setting the closed state
(fixups_closed()) before calling updater_batch() again to handle
fixups.
Checking for size != 0 at that point may not be valid at the list size
may actually be 0 for a short
Pester the maintainer?
Adrian
2011/9/15 Alexander Zagrebin al...@visp.ru:
I'm also using cvsup again, due to a problem I had with csup
back in February
2011
http://www.mail-archive.com/freebsd-stable@freebsd.org/msg114
813.html .
I didn't open a PR; I was under some time pressure
On Wed, Sep 14, 2011 at 11:19 PM, Adrian Chadd adr...@freebsd.org wrote:
Pester the maintainer?
The maintainer is alumni.
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
Pester the maintainer?
I've thought that if an opened PR exists, then it have to be
reviewed sooner or later...
--
Alexander Zagrebin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
on 15/09/2011 12:16 Alexander Zagrebin said the following:
Pester the maintainer?
I've thought that if an opened PR exists, then it have to be
reviewed sooner or later...
Usually rather quite later than sooner.
There are about 5000 non-ports PRs and there are only a few dozen active
Usually rather quite later than sooner.
A perfect opportunity for src committers to dive in and make a
difference :-)
mcl
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
On 15 September 2011 18:05, Mark Linimon lini...@lonesome.com wrote:
Usually rather quite later than sooner.
A perfect opportunity for src committers to dive in and make a
difference :-)
I hate you. :)
Ok. Some third person test/verify that this patch (a) does what it's
supposed to do, and
the issue seen by the end-user before applying the patch though
:).
Thanks,
-Garrett
supdir=$(mktemp -d /tmp/sup.XX)
# Supfile follows. Change cvsup host as necessary..
cat $supdir/supfile EOF
*default host=cvsup10.FreeBSD.org
*default base=$supdir
*default prefix=$supdir/checkout
*default release
procedure for verifying the patch. Please verify that the case below
repros the issue seen by the end-user before applying the patch though
:).
Thanks,
-Garrett
supdir=$(mktemp -d /tmp/sup.XX)
# Supfile follows. Change cvsup host as necessary..
cat $supdir/supfile EOF
*default host=cvsup10
I'm also using cvsup again, due to a problem I had with csup
back in February
2011
http://www.mail-archive.com/freebsd-stable@freebsd.org/msg114
813.html .
I didn't open a PR; I was under some time pressure and cvsup worked.
There is a solution of the csup problem:
http
the fault.
Ok, I'm trying. I recompiled cvsup for purpose with -DSTATIC
How do I continue from the gdb output below to help?
nudel# gdb
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome
Mike Tancsa m...@sentex.net wrote:
Just curious as to why you need cvsup and not instead use csup that is
in the base ?
I got used to it in the past 12 years? But this is not realy the question.
If it is BROKEN it should be marked as BROKEN or there should be a
statement
On 9 September 2011 06:33, Oliver Lehmann lehm...@ans-netz.de wrote:
Mike Tancsa m...@sentex.net wrote:
Just curious as to why you need cvsup and not instead use csup that is
in the base ?
I got used to it in the past 12 years? But this is not realy the question.
If it is BROKEN it should
on at least amd64 or we
will have other users complaining about the same at least when
9.0 RELEASE is out - right?
The cvsup port is normally used now only for cvsupd, for which there
is no csupd analog. As far as I know, and perhaps mux (CC'd) could
confirm every feature present in cvsup
or there should be a
statement that it will not work with FreeBSD 9 on at least amd64 or we
will have other users complaining about the same at least when
9.0 RELEASE is out - right?
The cvsup port is normally used now only for cvsupd, for which there
is no csupd analog. As far as I know
Kostik Belousov kostik...@gmail.com wrote:
For start, you should provide the information what exactly is the
instruction that caused the fault. Show the disassembly from gdb
for the function that caused the fault.
Ok, I'm trying. I recompiled cvsup for purpose with -DSTATIC
How do I
trying. I recompiled cvsup for purpose with -DSTATIC
How do I continue from the gdb output below to help?
I do not know, I was curious about 'illegal instruction' signal,
which would indicate a problem in the compilation environment.
Now you get segmentation violation, that is usually caused
On 09/09/11 01:33, Oliver Lehmann wrote:
Mike Tancsam...@sentex.net wrote:
Just curious as to why you need cvsup and not instead use csup that is
in the base ?
I got used to it in the past 12 years? But this is not realy the question.
If it is BROKEN it should be marked as BROKEN
results in an 'illegal instruction' error.
Why it gets to segmentation violation inside gdb I just don't know.
nudel# ./client/FBSD_AMD64/cvsup -g /usr/share/examples/cvsup/9-supfile
Connected to cvsup.de.FreeBSD.org
Updating collection src-all/cvs
Edit src/crypto/openssl/ssl/s3_lib.c
Illegal
caused by a bug in
the program itself.
running it outside gdb still results in an 'illegal instruction' error.
Why it gets to segmentation violation inside gdb I just don't know.
nudel# ./client/FBSD_AMD64/cvsup -g /usr/share/examples/cvsup/9-supfile
Connected to cvsup.de.FreeBSD.org
Updating
Kostik Belousov kostik...@gmail.com wrote:
On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote:
(gdb) bt
#0 0x004d24c6 in tzload ()
Try to do disas 0x4d24c6 0x4d24c6+30 from gdb prompt with the loaded core.
(gdb) disas 0x4d24c6 0x4d24c6+30
Dump of assembler code from
,%bpl
End of assembler dump.
Ok, please do the following:
run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do:
1. info registers $rsp
2. info program
This should print you the pid of the process, then do
3. shell procstat -v pid
I suspect that modula 3 system uses
+112:movzbl (%rbx),%ebp
0x004d24e3 tzload+115:cmp$0x2f,%bpl
End of assembler dump.
Ok, please do the following:
run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do:
1. info registers $rsp
2. info program
This should print you the pid
Kostik Belousov kostik...@gmail.com wrote:
On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote:
Ok, please do the following:
run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do:
1. info registers $rsp
2. info program
This should print you the pid
On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote:
Kostik Belousov kostik...@gmail.com wrote:
On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote:
Ok, please do the following:
run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do:
1. info
Kostik Belousov kostik...@gmail.com wrote:
On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote:
(gdb) run
Starting program:
/usr/obj/amd64/usr/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/client/FBSD_AMD64/cvsup
-g
/usr/share/examples/cvsup/9-supfile
Connected
On 09/08/11 14:52, b. f. wrote:
I have an Atom 330 with 9.0-BETA2/amd64 installed.
I did a pkg_add -r cvsup-without-gui at first after installation.
Using cvsup, resulted in a core dump (illegal instruction).
I then removed all ports, and installed cvsup-without-gui from source.
Started cvsup
Hi,
I have an Atom 330 with 9.0-BETA2/amd64 installed.
I did a pkg_add -r cvsup-without-gui at first after installation.
Using cvsup, resulted in a core dump (illegal instruction).
I then removed all ports, and installed cvsup-without-gui from source.
Started cvsup... core dump again.
I
I have an Atom 330 with 9.0-BETA2/amd64 installed.
I did a pkg_add -r cvsup-without-gui at first after installation.
Using cvsup, resulted in a core dump (illegal instruction).
I then removed all ports, and installed cvsup-without-gui from source.
Started cvsup... core dump again.
I
On 07/03/2011 03:51 PM, Stephen Montgomery-Smith wrote:
On 07/02/2011 10:25 PM, jhell wrote:
Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for
much longer than it really needed to be and should probably be removed
from use as a client entirely and links generated
Gavin Atkinson wrote:
On Sat, 2 Jul 2011, Ian FREISLICH wrote:
Matt wrote:
On 07/01/11 09:34, Ian FREISLICH wrote:
It looks like the server is just exiting. I've tested cvsup4 and
cvsup5 as well. Is cvsup deprecated these days or has something
else broken it?
Try csup
On 02/07/2011 17:07, Garrett Cooper wrote:
On Sat, Jul 2, 2011 at 8:33 AM, Vassilis Laganakos
vassilis.lagana...@yahoo.com wrote:
Hello,
I am facing the same problems as Holger here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html
although CVSup dies in gmtime_r
On 02/07/2011 17:54, Kurt Jaeger wrote:
Hi!
Any quick ideas on how to correct this, or if someone else is seeing
this issue?
Does csup work ?
Yeah! That works!
I see that csups is part of the build system. So is this to replace the
cvsup port?
Thanks,
Vassilis L
On 03/07/2011 04:25, jhell wrote:
On Sat, Jul 02, 2011 at 04:33:39PM +0100, Vassilis Laganakos wrote:
Hello,
I am facing the same problems as Holger here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html
although CVSup dies in gmtime_r in libc.so.7
On 07/02/2011 10:25 PM, jhell wrote:
Use csup(1) in base. This is in 7, 8 9. cvsup has been deprecated for
much longer than it really needed to be and should probably be removed
from use as a client entirely and links generated for installation of
cvsup - csup.
Only drawback for you may
Matt wrote:
On 07/01/11 09:34, Ian FREISLICH wrote:
It looks like the server is just exiting. I've tested cvsup4 and
cvsup5 as well. Is cvsup deprecated these days or has something
else broken it?
Try csup instead of cvsup...I've found it works better. Any possibility
of network
Hello,
I am facing the same problems as Holger here:
http://lists.freebsd.org/pipermail/freebsd-current/2011-June/025205.html
although CVSup dies in gmtime_r in libc.so.7:
...
Updating collection src-all/cvs
Edit src/UPDATING
Program received signal SIGSEGV, Segmentation
On Sat, 2 Jul 2011, Ian FREISLICH wrote:
Matt wrote:
On 07/01/11 09:34, Ian FREISLICH wrote:
It looks like the server is just exiting. I've tested cvsup4 and
cvsup5 as well. Is cvsup deprecated these days or has something
else broken it?
Try csup instead of cvsup...I've found
Hi
I've been seeing this all day:
# cvsup -L2 /root/supfile-cvs
Parsing supfile /root/supfile-cvs
Connecting to cvsup6.freebsd.org
Connected to cvsup6.freebsd.org
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed
On 07/01/11 09:34, Ian FREISLICH wrote:
Hi
I've been seeing this all day:
# cvsup -L2 /root/supfile-cvs
Parsing supfile /root/supfile-cvs
Connecting to cvsup6.freebsd.org
Connected to cvsup6.freebsd.org
Server software version: SNAP_16_1h
Negotiating file attribute support
Exchanging
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled port /usr/ports/net/cvsup-without-gui without
W dniu 2011-06-15 14:23, Holger Kipp pisze:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled
W dniu 2011-06-15 14:23, Holger Kipp pisze:
Have now used csup instead of cvsup (which seems to have worked fine), and started cvsup
once again (seems cvsup only gives Illegal Instruction when a file needs to
be changed...).
Any ideas?
Whoops, I read your message too fast, apologize. Please
On 6/15/11 8:23 AM, Holger Kipp wrote:
Dear all,
I had installed FreeBSD 9 amd64 from snapshot (ISO-image) located here:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201101/FreeBSD-9.0-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled
wanted to cvsup to a later date to upgrade to ZFS v28
and compiled port /usr/ports/net/cvsup-without-gui without problems.
Starting freshly compiled cvsup then gives me
Illegal Instruction
This error seems to be identical to
http://lists.freebsd.org/pipermail/freebsd-current/2010
On 6/15/11 10:46 AM, Holger Kipp wrote:
Ah, ok.
Do we have a compiler switch to force stack alignment to 16-Byte-boundaries?
Otherwise I am really concerned that we might have similar wrong pieces of code
lurking unnoticed in other binaries as well :-/
My cvsup binary is:
# file /usr/local
-CURRENT-201101-amd64-dvd1.iso
Today I wanted to cvsup to a later date to upgrade to ZFS v28
and compiled port /usr/ports/net/cvsup-without-gui without problems.
Starting freshly compiled cvsup then gives me
Illegal Instruction
This error seems to be identical to
http://lists.freebsd.org/pipermail
Tinderbox
/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
error: initializer element is not constant
Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
the additional error message
/usr/src/lib/libfetch/common.c:58: error:
On Fri, Oct 24, 2003 at 10:47:22AM -0500, Michael L. Squires wrote:
Tinderbox
/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
error: initializer element is not constant
Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
the
Il Ven, 2003-10-24 alle 17:47, Michael L. Squires ha scritto:
Tinderbox
/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
error: initializer element is not constant
Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
the additional
. This happens on my old pentium router
box, however on another box (well, not a real one, it's VMware ;) this
does NOT occur, with precisely the same cvsup...
pgp0.pgp
Description: PGP signature
'spinner' goes away, before the
initial copyright message even. This happens on my old pentium router
box, however on another box (well, not a real one, it's VMware ;) this
does NOT occur, with precisely the same cvsup...
I'm going to bet that both your machines have an odd amount of
memory in about
the same cvsup...
I'm going to bet that both your machines have an odd amount of
memory in about the same ballpark.
my fujitsu lifebook p2120 has 384mb of ram with 8mb shared video.
i'm going to start checking past days' kernels and see exactly what day
it stopped working.
In my experience
and pciconf attached.
- --
Anish Mistry
The problem was in a commit to /src/sys/i386/i386/machdep.c which what just
fixed last night it should work now if you CVSup.
- --
Anish Mistry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 12 Oct 2003, Anish Mistry wrote:
I finally recvsupped today as some problems with my ata stuff was
fixed. Went through the normal buildworld/kernel progress and on
reboot of loading the new kernel, it loads the kernel and modules and
then
machines
and it is able to boot just fine. looks like this is a tm crusoe
issue.
maybe something with the acpi or longrun stuff.
i'm not too proficient with freebsd kernel hacking, so hopefully
someone
else will be able to tackle this.
When was the last good cvsup that you did? I think we
On 12 Oct, Anish Mistry wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally recvsupped today as some problems with my ata stuff was
fixed. Went through the normal buildworld/kernel progress and on
reboot of loading the new kernel, it loads the kernel and modules and
then as
this.
When was the last good cvsup that you did? I think we will have to
track down ourselves which commit broke since no one else is having
this problem. I don't remember when I did mine since I let a friend
borrow it for a couple of weeks. I hope that someone with more
knowledge can point
On Tue, Oct 14, 2003 at 09:19:10PM -0400, Brian J. Creasy wrote:
the last good cvsup i did was quite a while ago. july 13th. i got a
little hung up with the semester starting back up. there isn't a way to
tell cvsup a specific date to roll back to, is there?
There is... please to be RTFMing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 14 Oct 2003, Don Lewis wrote:
On 12 Oct, Anish Mistry wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally recvsupped today as some problems with my ata stuff was
fixed. Went through the normal buildworld/kernel progress
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there. Is everyone and
their brother doing a make world today
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote:
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out
In the last episode (Sep 16), Andrew Lankford said:
I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and
each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out there.
Is everyone
On Tue, Sep 16, 2003 at 05:11:02PM -0500, Dan Nelson wrote:
In the last episode (Sep 16), Andrew Lankford said:
I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and
each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote:
I've tried various cvsup sites (normally cvsup2 or cvsup16 )
and each site returns this message:
Rejected by server: Access limit exceeded; try again later
I've gotten that before but never with all of the hosts out
I spoke too soon. Suddenly it all works.
It never got above 10 clients before today. How about a few
people switch to my server for regular updates? Thanks. :)
Regards,
--
wca
Oh, alright!
Andrew Lankford
___
[EMAIL
Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
-Al
___
[EMAIL PROTECTED] mailing list
It seems Alastair G. Hogge wrote:
Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
I'm working on it...
-Søren
Hi...
Sorry to do a me too, but I have a similar problem after a cvsup midday
on the 13th September. The previous kernel was pre-ATAng.
The machine panic'd after inserting a friends wireless PCMCIA card
(but that's probably another unrelated issue), rebooted and left
me in single user after
1 - 100 of 617 matches
Mail list logo
