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
On 11/15/2012 12:58 PM, Eitan Adler wrote:
On 15 November 2012 13:47, Ian FREISLICH 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.
On 15 November 2012 13:47, Ian FREISLICH 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
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/mail
;> >>>
>> >> >>> I am playing a bit with 9.0-PRERELEASE compiling it from source
>> >> >>> updated via csup. In both example files there is line specifying
>> >> >>> what to csup
>> >> >>>
>> &g
it from source
> >> >>> updated via csup. In both example files there is line specifying
> >> >>> what to csup
> >> >>>
> >> >>> *default release=cvs tag=RELENG_8
> >> >>>
> >> >>> which is in
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-
> >>> 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
> >>>
;>
>> *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
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/exampl
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
/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
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.
-- O
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-
> 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 th
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
merge candidate this to stable/9 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
anks,
> 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?
Tom
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
___
On Tue, Oct 4, 2011 at 2:19 AM, Adrian Chadd wrote:
> On 4 October 2011 05:53, Maxime Henrion 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 whil
On 4 October 2011 05:53, Maxime Henrion 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 wasn't sure abou
On Mon, Oct 3, 2011 at 11:30 PM, Jilles Tjoelker 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 the detail
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 sh
hor when one needs them..
Well that's quite a strange coincidence. I haven't read current@ in
ages and now I just stumble upon this. :-)
It's been a long time since I've been looking at this code but the
patch from the original PR seems /nearly/ correct, while the one from
adrian@
2011/9/19 Alexander Zagrebin :
> 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 mailing lis
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 s
On Sun, Sep 18, 2011 at 02:46:24PM +0200, Oliver Lehmann wrote:
>
> Kostik Belousov 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 (with stunnel FW
Kostik Belousov 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
http://lists.freebsd.org/mailman/listinfo/free
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 @@
*
On Sun, Sep 18, 2011 at 12:22:53PM +0200, Oliver Lehmann wrote:
>
> Adrian Chadd wrote:
>
> >So I've taken a look at the csup source.
> >
> >[...]
> >
> >What about this patch:
> >
> >[...]
> >
> >Oliver, would you ple
Adrian Chadd 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-current@freebs
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 t
for..)
>
> Based on the ticket and the patch, I think this is the right
> 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 /t
lease 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 < $i
done
# This should fail, requi
On 15 September 2011 18:05, Mark Linimon 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 (b) is correct, a
> 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 m
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
> 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 unsubsc
On Wed, Sep 14, 2011 at 11:19 PM, Adrian Chadd 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, send any mail to "fr
Pester the maintainer?
Adrian
2011/9/15 Alexander Zagrebin :
>> 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
> 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
ult.
>
> 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 Genera
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
Kostik Belousov 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 to cvsup.de.FreeBSD.org
Updating
On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote:
>
> Kostik Belousov 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,
Kostik Belousov 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 of the process, then
ne0x4d24e3
> > 0x004d24dc :add$0x1,%rbx
> > 0x004d24e0 :movzbl (%rbx),%ebp
> > 0x004d24e3 :cmp$0x2f,%bpl
> > End of assembler dump.
>
> Ok, please do the following:
> run cvsup under the gdb. When SIGSEGV
d25e0
> 0x004d24d3 : movzbl (%rbx),%ebp
> 0x004d24d6 :cmp$0x3a,%bpl
> 0x004d24da :jne0x4d24e3
> 0x004d24dc :add$0x1,%rbx
> 0x004d24e0 :movzbl (%rbx),%ebp
> 0x0000004d24e3 :cmp$0x2f,
Kostik Belousov 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 0x4d24c6 to 0x4d2
iolation, that is usually 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_AMD
ults 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
On 09/09/11 01:33, Oliver Lehmann wrote:
Mike Tancsa 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 s
ult.
>
> Ok, I'm 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 segm
Kostik Belousov 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 continue from th
ld be marked as BROKEN 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 onl
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 is present in csup--
On 9 September 2011 06:33, Oliver Lehmann wrote:
>
> Mike Tancsa 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 "BROKE
Mike Tancsa 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 that it will not
> 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 cvs
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 then
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
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
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 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 02/07/2011 17:07, Garrett Cooper wrote:
On Sat, Jul 2, 2011 at 8:33 AM, 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
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 the
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
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
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 foun
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 sup
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
Establish
-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.f
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/bin/cvsup
/usr/local/bin/cvsup: ELF 64-bit
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
RRENT-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
> >
> >"Illega
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
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, apologi
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
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
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 additio
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 a
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: 'EAINON
rnel, so i can get debug info that
> > way if needed. Old dmesg 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 Mist
owever 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 ballpark.
my fujitsu lifebook p2120 has 384mb of ram with 8mb sh
just after the boot loader's '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 go
e boot loader's '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...
pgp0.pgp
Description: PGP signature
-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/kerne
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..
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 will have to
> track down ourselves which commit broke since no one else is having
> this problem. I don&#
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
> th
ernel) on one of my desktop
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.
&
-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
> t
-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 it starts booting it just causes my mac
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
___
[EMAI
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 nev
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
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 o
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 nev
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
imon Brown wrote:
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
1 - 100 of 664 matches
Mail list logo
