Re: etcupdate -B, /.cshrc and /.profile

2023-08-22 Thread Jamie Landeg-Jones
Sulev-Madis Silber wrote: > on why removing those, i for example only use /etc/csh.cshrc so i don't need > others Exactly the same here!

Re: etcupdate -B, /.cshrc and /.profile

2023-08-22 Thread Sulev-Madis Silber
on why removing those, i for example only use /etc/csh.cshrc so i don't need others

Re: etcupdate -B, /.cshrc and /.profile

2023-08-22 Thread Jamie Landeg-Jones
Mike Karels wrote: > Both sets have been present since 4.3-Reno in 1990, although they were > apparently not links. Well before my time! > > > Removing them both is one of the first things I do when I install a new > > system from install-media. > > Why? Because I don't use them > > If etcupda

Re: etcupdate -B, /.cshrc and /.profile

2023-08-22 Thread Jamie Landeg-Jones
Graham Perrin wrote: > If I recall correctly, a few hours ago etcupdate -B resulted in removal > of two files: > > /.cshrc > /.profile > > Is this degree of checking/removal a novelty? > > (I can't recall the files' contents, or when I created them. I guess

Re: etcupdate -B, /.cshrc and /.profile

2023-08-17 Thread Steve Rikli
On Thu, Aug 17, 2023 at 07:17:20PM +0100, Graham Perrin wrote: > If I recall correctly, a few hours ago etcupdate -B resulted in removal of > two files: > > /.cshrc > /.profile > > Is this degree of checking/removal a novelty? > > (I can't recall the files'

etcupdate -B, /.cshrc and /.profile

2023-08-17 Thread Graham Perrin
If I recall correctly, a few hours ago etcupdate -B resulted in removal of two files: /.cshrc /.profile Is this degree of checking/removal a novelty? (I can't recall the files' contents, or when I created them. I guess that I carelessly created them as dot files months ago without

Pine64+2GB unable to boot after attempted update, failure very early: efipart_readwrite: rw=1,  blk=... size=32 status=7; RPi3 has no problem

2020-07-17 Thread Mark Millard
s read in 33 ms (20.1 MiB/s) Consoles: EFI console    |/-\|/-\|    Reading loader env vars from /efi/freebsd/loader.env  Setting currd

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

2019-11-26 Thread Ruslan Garipov
On 11/26/2019 12:09 AM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 19:26: > > [...] > >>> I didn't tried this with current but I am using it with stable (11.3 at >>> this time). Building on Xeon E3-1240v3 and installing on many different >>> machines. Some of them are 10+ years

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

2019-11-25 Thread Miroslav Lachman
Ruslan Garipov wrote on 2019/11/25 19:26: [...] I didn't tried this with current but I am using it with stable (11.3 at this time). Building on Xeon E3-1240v3 and installing on many different machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, some 10 years old Intel Pentium.

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

2019-11-25 Thread Ruslan Garipov
On 11/25/2019 10:30 PM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 15:06: >> Hello. >> >> I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast >> virtual machine for other ones (all the virtual machines are hosted on >> VMware EXSi hypervisors, which have different

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

2019-11-25 Thread Miroslav Lachman
Ruslan Garipov wrote on 2019/11/25 15:06: Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished su

buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

2019-11-25 Thread Ruslan Garipov
Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished successfully on the build machine, I get there

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-26 Thread Mark Millard
ang/lldb .ERROR_TARGET='lldb.full' .ERROR_META_FILE='/usr/obj/armv7_clang/arm.armv6/usr/src/usr.bin/clang/lldb/lldb.full.meta' .MAKE.LEVEL='5' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='c++

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-24 Thread Warner Losh
On Mon, Jul 24, 2017 at 1:33 AM, Mark Millard wrote: > [I forgot that linking lldb historically failed on armv6 > (cortex-a7) based on the historical system binutils.] > > On 2017-Jul-23, at 8:51 PM, Mark Millard wrote: > > > [Using WITH_LLDB= had no problem for amd64 -> TARGET_ARCH=aarch64 > >

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-24 Thread Mark Millard
[I forgot that linking lldb historically failed on armv6 (cortex-a7) based on the historical system binutils.] On 2017-Jul-23, at 8:51 PM, Mark Millard wrote: > [Using WITH_LLDB= had no problem for amd64 -> TARGET_ARCH=aarch64 > buildworld buildkernel .] > > On 2017-Jul-23, at 3:44 PM, Mark Mil

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[Using WITH_LLDB= had no problem for amd64 -> TARGET_ARCH=aarch64 buildworld buildkernel .] On 2017-Jul-23, at 3:44 PM, Mark Millard wrote: > [WITH_LLD= WITHOUT_LLDB= did a buildworld buildkernel > just fine for TARGET_ARCH=powerpc64 .] > > On 2017-Jul-23, at 2:46 PM, Mark Millard wrote: > >>

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[WITH_LLD= WITHOUT_LLDB= did a buildworld buildkernel just fine for TARGET_ARCH=powerpc64 .] On 2017-Jul-23, at 2:46 PM, Mark Millard wrote: > [Shawn Webb's logfile shows an error similar to what I > report: lldb_private::AppleObjCRuntime::GetFoundationVersion() > is a problem. But his report sh

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[Shawn Webb's logfile shows an error similar to what I report: lldb_private::AppleObjCRuntime::GetFoundationVersion() is a problem. But his report shows other errors as well, ones that I did not get.] On 2017-Jul-23, at 1:04 PM, Mark Millard wrote: > [The lldb problem is a: > > lldb_private::Ap

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
[The lldb problem is a: lldb_private::AppleObjCRuntime::GetFoundationVersion() reference via Cocoa.o in liblldb.a . See below. Sorry that sometimes I'm having to go back and later find and report more details because of other things going on here. But this likely will continue for some of my prel

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Dimitry Andric
On 23 Jul 2017, at 11:17, Mark Millard wrote: > > [Linking lldb.full via 2.28 of /usr/local/powerpc64-freebsd/bin/ld > also fails with "exit code 1" (using WIHTOUT_LLD so it gets that > far). I'll continue via WITHOUT_LLDB.] ... > > Here is the lldb.full failure text: > > --- all_subdir_usr.bin

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
PENDFILE=.depend.test_01 NO_SUBDIR=1 >> make -f /usr/src/lib/libxo/tests/Makefile _RECURSING_PROGS=t PROG=test_01 ) >> Building >> /usr/obj/powerpc64vtsc_clang_altbinutils/powerpc.powerpc64/usr/src/lib/libxo/tests/test_01.o >> --- all_subdir_usr.bin --- >> --

Re: -r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
dir_usr.bin/clang/lldb --- > c++: error: linker command failed with exit code 1 (use -v to see invocation) > --- all_subdir_lib --- > Building > /usr/obj/powerpc64vtsc_clang_altbinutils/powerpc.powerpc64/usr/src/lib/libxo/tests/test_01.full > --- all_subdir_usr.bin --- > *** [lldb.full] E

-r321371 amd64 -> powerpc64 cross build: lldb.full link fails with: c++: error: linker command failed with exit code 1, -B/usr/local/powerpc64-freebsd/bin/ in use

2017-07-23 Thread Mark Millard
MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='c++ -target powerpc64-unknown-freebsd12.0 --sysroot=/usr/obj/powerpc64vtsc_clang_altbinutils/powerpc.powerpc64/usr/src/tmp -B/usr/local/powerpc64-freebsd/bin/ -O2 -pipe -I/usr/src/contrib/llvm/tool

Re: rpi-b leds

2016-08-23 Thread Andrey Fesenko
On Tue, Aug 23, 2016 at 1:00 AM, Luiz Otavio O Souza wrote: > On 22 August 2016 at 08:55, Andrey Fesenko wrote: >> On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: >>> Hi, >>> I see that now both leds on the rpi-2 are operational, >>> any chance it can

Re: rpi-b leds

2016-08-22 Thread Daniel Braniss
Hi, >>>> I see that now both leds on the rpi-2 are operational, >>>> any chance it can happen on the rpi-b too? >>>> >>> >>> A year or two ago, rpi-b had operational leds, it's make not working >>> after rework fdt/std layer >> >&

Re: rpi-b leds

2016-08-22 Thread Daniel Braniss
> On 23 Aug 2016, at 01:00, Luiz Otavio O Souza wrote: > > On 22 August 2016 at 08:55, Andrey Fesenko wrote: >> On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: >>> Hi, >>> I see that now both leds on the rpi-2 are operational, >>> any chance it

Re: rpi-b leds

2016-08-22 Thread Luiz Otavio O Souza
On 22 August 2016 at 08:55, Andrey Fesenko wrote: > On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: >> Hi, >> I see that now both leds on the rpi-2 are operational, >> any chance it can happen on the rpi-b too? >> > > A year or two ago, rpi-b had operat

Re: rpi-b leds

2016-08-22 Thread Andrey Fesenko
On Mon, Aug 22, 2016 at 1:29 PM, Daniel Braniss wrote: > Hi, > I see that now both leds on the rpi-2 are operational, > any chance it can happen on the rpi-b too? > A year or two ago, rpi-b had operational leds, it's make not working after rew

Re: [Bug 210953] 11.0 -r302412 via powerpc64-xtoolchain-gcc fails to build: dev/ahci/ahci.c:288:22: error: unknown conversion type character 'b' in format; too many arguments for format

2016-07-10 Thread Ngie Cooper
> On Jul 9, 2016, at 23:03, Mark Millard wrote: > > On 2016-Jul-9, at 8:53 PM, Ngie Cooper wrote: > >>> On Jul 9, 2016, at 18:52, bugzilla-nore...@freebsd.org wrote: >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210953 >>> >>> Mark Millard changed: >> >> I accidentally committe

Re: [Bug 210953] 11.0 -r302412 via powerpc64-xtoolchain-gcc fails to build: dev/ahci/ahci.c:288:22: error: unknown conversion type character 'b' in format; too many arguments for format

2016-07-09 Thread Mark Millard
On 2016-Jul-9, at 8:53 PM, Ngie Cooper wrote: >> On Jul 9, 2016, at 18:52, bugzilla-nore...@freebsd.org wrote: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210953 >> >> Mark Millard changed: > > I accidentally committed this regression to kern.mk. I don't have bugzilla > login rig

Re: [Bug 210953] 11.0 -r302412 via powerpc64-xtoolchain-gcc fails to build: dev/ahci/ahci.c:288:22: error: unknown conversion type character 'b' in format; too many arguments for format

2016-07-09 Thread Mark Millard
ld: dev/ahci/ahci.c:288:22: error: unknown > conversion type character 'b' in format; too many >arguments for format > Product: Base System > Version: 11.0-BETA1 > Hardware: ppc >OS: Any

[Bug 210953] 11.0 -r302412 via powerpc64-xtoolchain-gcc fails to build: dev/ahci/ahci.c:288:22: error: unknown conversion type character 'b' in format; too many arguments for format

2016-07-09 Thread Mark Millard
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210953 > > > Bug ID: 210953 >Summary: 11.0 -r302412 via powerpc64-xtoolchain-gcc fails to > build: dev/ahci/ahci.c:288:22: error: unknown > conversion type ch

Re: Compiling 11 on a Raspberry B+ 2 failes [not in my experience for -r301975]

2016-06-19 Thread Mark Millard
On 2016-Jun-19, at 7:41 PM, Mark Millard wrote: > Quoting Erich Dollansky erichsfreebsdlist at alogt.com Sun Jun 19 23:38:56 > UTC 2016 : > >> I am trying to compile HEAD on a Raspberry and get always the following >> error. >> >> Of course, compiling revision 302017 on amd64 works. >> >> Eri

RE: Compiling 11 on a Raspberry B+ 2 failes [not in my experience for -r301975]

2016-06-19 Thread Mark Millard
Quoting Erich Dollansky erichsfreebsdlist at alogt.com Sun Jun 19 23:38:56 UTC 2016 : > I am trying to compile HEAD on a Raspberry and get always the following > error. > > Of course, compiling revision 302017 on amd64 works. > > Erich > > Last Changed Rev: 301974 > > /usr/src/lib/csu/arm/cr

Compiling 11 on a Raspberry B+ 2 failes

2016-06-19 Thread Erich Dollansky
Hi, I am trying to compile HEAD on a Raspberry and get always the following error. Of course, compiling revision 302017 on amd64 works. Erich Last Changed Rev: 301974 /usr/src/lib/csu/arm/crt1.c:(.text+0xb4): relocation truncated to fit: R_ARM_CALL against symbol `atexit' defined in .text sec

Re: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Keith White
On Fri, 17 Jun 2016, Adrian Chadd wrote: Just disable 11n for now. ifconfig wlan0 -ht (and reassociate.) See if it's that. -adrian ... Apparently not. I have the same panic even with 11n disabled. ...keith ___ freebsd-current@freebsd.org mailin

Re: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Ian Lepore
fo lists the nearby symbol as > > $a.17+0x38, > > which doesn't help find the actual code. A stack backtrace might > > help. > > > > -- Ian > > ... > > What do I need to type at the "db> " prompt that would be useful? > I should be able to

Re: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Keith White
+0x38, which doesn't help find the actual code. A stack backtrace might help. -- Ian ... What do I need to type at the "db> " prompt that would be useful? I should be able to access the RPI-B in 5 hours. Here's the result of a "where" taken from an earlier lo

Re: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Ian Lepore
> > > https://lists.freebsd.org/pipermail/freebsd-current/2016-June/0 > > > > 61904.html > > > > reports an RPI-B alignment fault for -r301815 (the snapshot) > > > > "when > > > > connecting via WiFi". > > > > > > > &

Re: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Adrian Chadd
ermail/freebsd-current/2016-June/061904.html >>> reports an RPI-B alignment fault for -r301815 (the snapshot) "when >>> connecting via WiFi". >>> >>> -r301872 ( >>> https://lists.freebsd.org/pipermail/svn-src-head/2016-June/088339.html

RE: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-17 Thread Keith White
On Thu, 16 Jun 2016, Keith White wrote: On Wed, 15 Jun 2016, Mark Millard wrote: https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061904.html reports an RPI-B alignment fault for -r301815 (the snapshot) "when connecting via WiFi". -r301872 ( https://lists.f

RE: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-16 Thread Keith White
On Wed, 15 Jun 2016, Mark Millard wrote: https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061904.html reports an RPI-B alignment fault for -r301815 (the snapshot) "when connecting via WiFi". -r301872 ( https://lists.freebsd.org/pipermail/svn-src-head/2016-June/088339.

Re: RPI-B 11.0-ALPHA3 r301815 panic

2016-06-16 Thread Keith White
On Thu, 16 Jun 2016, Svatopluk Kraus wrote: There was a fix committed in r301872 which should help. Svatopluk Kraus ... Thanks! I'd tried r301932 with the same panic. I'll try again with r301872 and a pristine /usr/obj ...keith ___ freebsd-curren

Re: RPI-B 11.0-ALPHA3 r301815 panic

2016-06-16 Thread Svatopluk Kraus
There was a fix committed in r301872 which should help. Svatopluk Kraus On Thu, Jun 16, 2016 at 3:48 AM, Keith White wrote: > I get the following panic when connecting via WiFi to an RPI-B > running the r301815 snapshot: > > Fatal kernel mode data abort: 'Alignment Fault

RE: RPI-B 11.0-ALPHA3 r301815 panic ["when connecting via WiFi"]

2016-06-15 Thread Mark Millard
https://lists.freebsd.org/pipermail/freebsd-current/2016-June/061904.html reports an RPI-B alignment fault for -r301815 (the snapshot) "when connecting via WiFi". -r301872 ( https://lists.freebsd.org/pipermail/svn-src-head/2016-June/088339.html ) has a fix for networking vs.

RPI-B 11.0-ALPHA3 r301815 panic

2016-06-15 Thread Keith White
I get the following panic when connecting via WiFi to an RPI-B running the r301815 snapshot: Fatal kernel mode data abort: 'Alignment Fault' on read trapframe: 0xc18f28c0 FSR=0001, FAR=c21a287a, spsr=6013 r0 =c07a6548, r1 =0004, r2 =c060513d, r3 =07b6 r4 =c18f2a28, r5

x11/nvidia-driver: make -B clean all ===> Cleaning for nvidia-driver-331.38 *** [all] Stopped -- signal 22

2014-02-04 Thread O. Hartmann
this happens with the version nvidia-driver-331.38 as well as with nvidia-driver-331.20. See error below. It allways ends with WRKDIRPREFIX=/usr/obj/usr/src/sys/THOR make -B clean all ===> Cleaning for nvidia-driver-331.38 *** [all] Stopped -- signal 22 The SIGNAL 22 ( SIGTTOU) sounds stran

Re: CLANG reports an error with %b in printf(9)

2013-10-01 Thread Dimitry Andric
On Oct 1, 2013, at 21:30, Luigi Rizzo wrote: > This is on HEAD -- while compiling the kernel with CLANG and slightly > higher warns level, i get errors of this kind (in multiple places): > > /usr/home/luigi/FreeBSD/head/sys/cam/cam_xpt.c:1069:27: error: invalid > conversion spec

CLANG reports an error with %b in printf(9)

2013-10-01 Thread Luigi Rizzo
This is on HEAD -- while compiling the kernel with CLANG and slightly higher warns level, i get errors of this kind (in multiple places): /usr/home/luigi/FreeBSD/head/sys/cam/cam_xpt.c:1069:27: error: invalid conversion specifier 'b' [-Werror,-Wformat-invalid

Re: [RFC] support -b when starting gdb

2013-01-16 Thread John Baldwin
On Wednesday, January 16, 2013 1:30:37 am Adrian Chadd wrote: > Also, I found 'set remotebaud' and 'set debug remote 1' to do this. > > I'd like to add the code just to support the same -b flag as gdb (so > -r can also be used with a non-standard ser

Re: [RFC] support -b when starting gdb

2013-01-16 Thread Adrian Chadd
d yes, it'd be nice to have -b so I can use -b and -r to instantly open up a remote gdb session. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "

Re: [RFC] support -b when starting gdb

2013-01-16 Thread Warner Losh
t; Hi, >>> >>> There doesn't seem to be a blessed way to set the baudrate from inside >>> gdb/kgdb. It seems to be set from '-b' on the command line. >>> >>> However kgdb doesn't have this support. >>> >>> This pat

Re: [RFC] support -b when starting gdb

2013-01-16 Thread Garrett Cooper
On Jan 16, 2013, at 7:35 AM, Warner Losh wrote: > How does 'set remotebaud' not do what you want? > > Warner > > On Jan 15, 2013, at 10:15 PM, Adrian Chadd wrote: > >> Hi, >> >> There doesn't seem to be a blessed way to set the baudrate f

Re: [RFC] support -b when starting gdb

2013-01-16 Thread Warner Losh
How does 'set remotebaud' not do what you want? Warner On Jan 15, 2013, at 10:15 PM, Adrian Chadd wrote: > Hi, > > There doesn't seem to be a blessed way to set the baudrate from inside > gdb/kgdb. It seems to be set from '-b' on the command line. >

Re: [RFC] support -b when starting gdb

2013-01-15 Thread Adrian Chadd
Also, I found 'set remotebaud' and 'set debug remote 1' to do this. I'd like to add the code just to support the same -b flag as gdb (so -r can also be used with a non-standard serial port.) Thanks, Adrian On 15 January 2013 21:15, Adrian Chadd wrote: > Hi, &g

[RFC] support -b when starting gdb

2013-01-15 Thread Adrian Chadd
Hi, There doesn't seem to be a blessed way to set the baudrate from inside gdb/kgdb. It seems to be set from '-b' on the command line. However kgdb doesn't have this support. This patch adds -b support so kgdb so I can override the default speed (9600 it seems) to speak k

Re: r232623 breaks buildworld (or a recent commit...)B

2012-03-06 Thread matt
On 03/06/12 14:01, Dimitry Andric wrote: > On 2012-03-06 22:21, Larry Rosenman wrote: >> buildworld broken by r232623. >> >> -fpic -DPIC -O2 -pipe -fno-omit-frame-pointer >> -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include >> -I/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVA

Re: r232623 breaks buildworld (or a recent commit...)B

2012-03-06 Thread matt
On 03/06/12 13:21, Larry Rosenman wrote: > buildworld broken by r232623. > > -fpic -DPIC -O2 -pipe -fno-omit-frame-pointer > -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include > -I/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVATE > -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6

Re: r232623 breaks buildworld (or a recent commit...)B

2012-03-06 Thread Dimitry Andric
On 2012-03-06 22:21, Larry Rosenman wrote: > buildworld broken by r232623. > > -fpic -DPIC -O2 -pipe -fno-omit-frame-pointer -I/usr/src/lib/libc/include > -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS > -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DIN

r232623 breaks buildworld (or a recent commit...)B

2012-03-06 Thread Larry Rosenman
buildworld broken by r232623. -fpic -DPIC -O2 -pipe -fno-omit-frame-pointer -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/

Re: HELP: ServerWorks data corruption after 350 MB with BerkeleyD B 4.0?

2003-11-04 Thread Soren Schmidt
It seems Anshuman Kanwar wrote: Ehem, this machine is NOT ServerWorks based, its Intel... > rack2-102.nyc# pciconf -l > [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x254c8086 rev=0x01 > hdr=0x00 > [EMAIL PROTECTED]:2:0: class=0x060400 card=0x chip=0x25438086 rev=0x01 > hdr=

Re: fsck_ufs -B lockup any writes on filesystem

2003-10-15 Thread Vladimir B. Grebenschikov
В ср, 15.10.2003, в 17:31, Robert Watson пишет: > On Wed, 15 Oct 2003, Vladimir B. Grebenschikov wrote: > > > After unclean shutdown, system boots and work properly. After some time > > any processes triing to write was blocked in suspfs state. fsck_ufs > > process was

Re: fsck_ufs -B lockup any writes on filesystem

2003-10-15 Thread Robert Watson
On Wed, 15 Oct 2003, Vladimir B. Grebenschikov wrote: > After unclean shutdown, system boots and work properly. After some time > any processes triing to write was blocked in suspfs state. fsck_ufs > process was blocked in suspwt state. I reported an identical set of symptoms over th

fsck_ufs -B lockup any writes on filesystem

2003-10-15 Thread Vladimir B. Grebenschikov
suspwt D ??0:00.91 fsck_ufs -p -B /dev/ad0s3f # strace -p 917 mount(0x80af3d3, 0x80cb44c, 0x1211000, 0xbfbffcc0^C ^C # ps alx | fgrep suspfs 0 559 1 0 75 0 7076 1588 suspfs Is??0:01.92 /usr/local/sbin/cupsd 207 611 609 0 75 0 8832 2396 suspfs I ??0

Re: Fun with 'fdisk -B -b /boot/boot0 ad0'

2003-07-25 Thread Craig Boston
On Wednesday 23 July 2003 04:26 pm, Ryan T. Dean wrote: > [...] The FreeBSD boot program came back, > however, when I attempt to load FreeBSD, it merely beeps at me. It will, > however, boot into W2k. I've tried supping, rebuilding the boot blocks (cd > src/sys/boot; make ins

Fun with 'fdisk -B -b /boot/boot0 ad0'

2003-07-23 Thread Andrew Lankford
eebsd slice. This is done with the -B option of bsdlabel (formerly disklabel). For all I know something to the effect of typing "bsdlabel -e -B ad0s2_or_whateveryourfbsdsliceis" and then exiting without making any changes to the displayed table of fbsd partitions may do the trick. Hopeful

Fun with 'fdisk -B -b /boot/boot0 ad0'

2003-07-23 Thread Ryan T. Dean
ludgy. Checking the handbook, I found the entry on how to reinstall the MBR. So, I did a 'fdisk -B -b /boot/boot0 ad0'. The FreeBSD boot program came back, however, when I attempt to load FreeBSD, it merely beeps at me. It will, however, boot into W2k. I've tried supping, rebuilding

Re: BCM5703 GigE ifs on Supermicro X5DL8-GG m/b not detectedon5.1-BETA2 or 4.8 (resolved)

2003-05-29 Thread John Dhmioyrgos
Just to bring the list up to date, I went onsite, popped the case open, and guess what I saw.. SUPER X5DP8-G2 REV 1.2 rather than X5DL8-GG, so it looks like the vendor pulled a fast one. spec sheet on that lists onboard Intel 82546EB dual port GigE, but note that I've already got one single port Pr

Re: BCM5703 GigE ifs on Supermicro X5DL8-GG m/b not detectedon5.1-BETA2 or 4.8

2003-05-28 Thread Doug White
On Fri, 23 May 2003, Tom Samplonius wrote: > I don't know about Supermicro, but ASUS uses Broadcom chips with an > Intel chipset on at least one workstation board: > > http://usa.asus.com/prog/spec.asp?langs=09&m=P4G8X%20Deluxe Okay so the crack pipe is being passed around :) And what happened

Re: Is netstat b?rked?

2003-01-30 Thread Juli Mallett
* De: "Scott R." <[EMAIL PROTECTED]> [ Data: 2003-01-30 ] [ Subjecte: Re: Is netstat b?rked? ] > On Thu, Jan 30, 2003 at 12:30:44AM -0800, Juli Mallett wrote: > > * De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ] > > [ Subjecte: Re: Is n

Re: Is netstat b?rked?

2003-01-30 Thread Scott R.
On Thu, Jan 30, 2003 at 12:30:44AM -0800, Juli Mallett wrote: > * De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ] > [ Subjecte: Re: Is netstat b?rked? ] > > On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote: > > > ref5% ne

Re: Is netstat b?rked?

2003-01-30 Thread Juli Mallett
* De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ] [ Subjecte: Re: Is netstat b?rked? ] > On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote: > > ref5% netstat -na -p tcp > > ref5% > > > > dalek# netstat -an -p tcp > > dalek#

Re: Is netstat b?rked?

2003-01-30 Thread Ruslan Ermilov
On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote: > ref5% netstat -na -p tcp > ref5% > > dalek# netstat -an -p tcp > dalek# > Both beast and ref5 are from Jan 4 and exhibit this problem; builder, which is from Jan 28, doesn't. Perhaps, someone updated the kernel and forgot to updat

Re: boot0cfg -B

2002-11-18 Thread Dan Lukes
[EMAIL PROTECTED] wrote, On 11/18/02 07:52: Any reason why this doesn't work ? sheel>sudo boot0cfg -B ad0 boot0cfg: /dev/ad0: Operation not permitted securelevel too high ? Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webma

Re: boot0cfg -B

2002-11-17 Thread Marcel Moolenaar
On Mon, Nov 18, 2002 at 05:07:08PM +1030, Wilkinson,Alex wrote: > Howdy crew, > > Any reason why this doesn't work ? > > sheel>sudo boot0cfg -B ad0 > boot0cfg: /dev/ad0: Operation not permitted > > running: FreeBSD 5.0-CURRENT #0: Fri Nov 8 15:07:18 CST 2002 GE

boot0cfg -B

2002-11-17 Thread Wilkinson,Alex
Howdy crew, Any reason why this doesn't work ? sheel>sudo boot0cfg -B ad0 boot0cfg: /dev/ad0: Operation not permitted running: FreeBSD 5.0-CURRENT #0: Fri Nov 8 15:07:18 CST 2002 Thanks - aW To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current&qu

$B!y$?$^$2$?%K%e!<%9!y(J

2002-10-04 Thread watanabe@bb.knet.ne.jp
EBEKEBEKEBEKEBEKEBEKEBEKEBEKEB @@ @@@@@@@@@@@™@‚½‚Ü‚°‚½ƒjƒ…[ƒX@™ @@@@— ƒrƒfƒI”Ì”„E“ÁŽêƒ_ƒbƒ`ƒƒCƒtE‚r‚lƒNƒ‰ƒu @@‚`‚u’j—D•åWE‰‡•ŒðÛE‚Žû“üŠmŽÀuo’£ƒzƒXƒgv•åW @@@@@@@@¦¦¦@‚»‚Ì‘¼— î•ñ–žÚ@¦¦¦ @EBEKEBE

$B"#E9F,HNGd$G$-$J$$$*?M7A$5$s"#(J

2002-09-28 Thread pplpp@fb.freeserve.ne.jp
•ø‚«‚µ‚ß‚½‚­‚È‚é‚æ‚¤‚È‚¨lŒ`‚³‚ñ‚ðì‚è‚Ü‚µ‚½I‚»‚ê‚à“™g‘åI ”š”­“Iƒqƒbƒg¤•iI ”‚ɐ§ŒÀ‚ª‚ ‚邽‚ß‚¨\‚µž‚݂͂¨‘‚߂ɁI ‚‚¢‚ɐV»•i“oê! ¬Ž­‚̂悤‚ȉ˜‚ê‚È‚«—öl ™‹Ç•”‚܂Ŗ{•¨‚»‚Á‚­‚è‚ɐ§ì‚µ‚½‚½‚߁A“X“ª”Ì”„‚Å‚«‚Ü‚¹‚ñB http://211.120.47.186/~cutepower/dattii.co.jp/dollcompany124.jp/ ƒƒfƒBƒJ

SEX$B%U%l%s%IJg=8(J

2002-09-27 Thread pplpp@fb.freeserve.ne.jp
^Œ•‚ÉSEXƒtƒŒƒ“ƒh‚ð’T‚µ‚Ä‚¢‚él‚¾‚¯W‡I ‘S‘‚Ç‚±‚Å‚à‹ß‚­‚̐l‚ðƒvƒƒtƒB[ƒ‹•t‚Å‚·‚®Ð‰îB Žá‚¢l‚©‚çn”N‚܂ł¢‚Á‚Ï‚¢‚¢‚邿! ƒ_ƒ“ƒi‚É“à‚ÌH‚ðŠy‚µ‚à‚¤I http://k-server.org/banana33/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

$B"#5.IX?M%/%i%V"#(J

2002-09-27 Thread sonoda12@po4.nsk.ne.jp
‘f“G‚È’j«‚ðÐ‰î‚µ‚Ü‚· ƒ}ƒbƒT[ƒWƒR[ƒX‚àŠJÝ ‘f“G‚È–é‚ð–ñ‘©‚µ‚Ü‚· i’j«•åWj ‚ ‚È‚½‚Ì–²‚ªâ‘΂©‚È‚¤ ƒŠƒbƒ`‚ȍ‚‹‰•wl‚Ƃ̌ðÛ‚Å–²‚ðŽÀŒ» ŽáŽÒ‚©‚ç’†‚”N‚܂Ō’N‚È’j«‹à–¬El–¬‚̂قµ‚¢’j«‚ɍœK —«‚ÍŒoÏ“I‚ÉŒb‚܂ꂽŽÐ’·•wlEŽÀ‹Æ‰ÆE‘½” http://red.ribbon.to/~mania/ To Unsubscribe: send

$B$7$8$_$H$b$b$N%3%i%\%l!<%7%g%s(J

2002-09-09 Thread sous1@aa.alles.or.jp
‚à‚à‚ª‚Í‚¶‚¯‚ĂԂǂ¤‚ª‚ä‚ê‚é ‚µ‚¶‚݂Ƃà‚à‚̃Rƒ‰ƒ{ƒŒ[ƒVƒ‡ƒ“ ƒƒŠ[ƒ^ƒrƒfƒIi‚c‚u‚cjê–å ‚¢‚‚܂ʼnc‹Æ‚Å‚«‚é‚©‚í‚©‚è‚Ü‚¹‚ñ ‚²’•¶‚Í‚¨‘‚߂ɁI http://book-i.net/mutou ì•i—á ­—“`à@–¼ŒÃ‰®’c’n9@­—‚Ì“¹‘ ‚ȂǂȂÇ132ì•iBD•]”­”„’†I (^-^)/~ƒƒŠ˜F—˜ƒ€ƒg[ To Unsubscribe: send mail to [EMAIL

=?windows-874?b?cGFydC10aW1lIDUsMDAwLTEwLDAwMCCk2LOh57fT5LTpICEhIQ==?=

2002-06-25 Thread mont
Ãкº¡Ò÷ӧҹ¢Í§¸ØÃ¡Ô¨ã¹Í¹Ò¤µ·Óä´é§èÒ áÅÐÊÃéÒ§ÃÒÂä´é§ÒÁ¨Ò¡¡Ò÷ӧҹ¼èÒ¹Ãкº¼ÁÁÕÃÒÂä´éÁÒ¡¡ÇèÒ 30,000 / à´×͹ ¨Ò¡¡Ò÷ӧҹà¾Õ§ÇѹÅÐ 2-3 ªÑèÇâÁ§à·èÒ¹Ñé¹âÍ¡ÒÊÁÒ¶Ö§¤Ø³áÅéÇ !à

=?windows-874?b?cGFydC10aW1lIDUsMDAwLTEwLDAwMCCk2LOh57fT5LTpICEhIQ==?=

2002-06-25 Thread mont
Ãкº¡Ò÷ӧҹ¢Í§¸ØÃ¡Ô¨ã¹Í¹Ò¤µ·Óä´é§èÒ áÅÐÊÃéÒ§ÃÒÂä´é§ÒÁ¨Ò¡¡Ò÷ӧҹ¼èÒ¹Ãкº¼ÁÁÕÃÒÂä´éÁÒ¡¡ÇèÒ 30,000 / à´×͹ ¨Ò¡¡Ò÷ӧҹà¾Õ§ÇѹÅÐ 2-3 ªÑèÇâÁ§à·èÒ¹Ñé¹âÍ¡ÒÊÁÒ¶Ö§¤Ø³áÅéÇ !à

(J!$B9-9p(J!$B!!=P2q$$%S%8%M(B$B%9#3E@%;%C%H$GBgLY$1!*(B

2002-06-14 Thread umeda
$BCK=w=P2q$$%S%8%M%9$K$D$$$F$N$*CN$i$;$G$9!#%a!<%k$NITMW$NJ}$O(B $B$3$N$^$^JV?.$7$F$*CN$i$;$/$@$5$$!#(B $BCK=w=P2q$$%S%8%M%9$GBgLY$1$7$^$;$s$+!)=P2q$$7O%5%$%H$O@$$NCf(B $B$K#3K|7o$[$I$"$k$H8@$o$l$F$$$^$9$,!"6%9g$,B?$9$.$FBgLY$1$7$F(B $B$$$k%5%$%H$O$4$/0lIt!#:#2s$4Ds0F$9$k!VC

$B=wM%!&%"%J$rJz$/%k!<%H(B

2002-05-18 Thread $B=wM%%k!<%H(B
$B2?$H$7$F$bJz$$$F$_$?$$$H??7u$K$*9M$($N=wM%!"%"%J%&%s%5!<$r(B $B#5L>0J>e#7L>?M$*J9$+$;$/$@$5$$!#!J(B18$B:P0J2<%?%l%s%H!"El5~0J(B $B30$N%?%l%s%H!"%"%J$O=|$/!K(B $B$=$NCf$G$4AjCL2DG=$JL>A0$,$"$C$?>l9g$N$_$*JV;v$$$?$7$^$9!#(B $B>

Re: cross-buildworld from i386 to alpha b rked...

2002-05-04 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: > >I tried "make buildworld TARGET_ARCH=alpha" and it croaked. Is this >expected breakage for a cross-build or genuine breakage ? >/flat/src/usr.sbin/pstat/pstat.c:546: `NLOCKED' undeclared (first use in this >fu >nction) It's genuine b

$B!*9-9p!*!!3FpJsDs6!$N$40FFb(B

2002-04-10 Thread $B%o%s%@!<%i%$%U(B
$B!!FMA3$N%a!<%k$NG[?.?<$/$*OM$S?=$7>e$2$^$9!#(B $B!!$3$l$O(BWEB$B>e$K%"%I%l%9$r8x3+$5$l$F$$$kJ}$rBP>]$KG[?.$7$F$$$k9-9p(B $B!!%a!<%k$G$9!#:#8e0l@Z$N%a!<%kG[?.ITMW$NJ}$O$3$N%a!<%k$r$=$N$^$^(B $B!!$4JV?.$/$@$5$$!#(B $B!!7G<(HD$KEj9F$9$k$h$j8z2LE*$G$9!*

(J!$B9-9p(J!$B!!(J500$B1_(B$B$+$i9b<}1W$J=P2q$$7O%5%$%H$,(B$B1?1D2DG=!*(B

2002-04-04 Thread tarou
$B=P2q$$7O%5%$%H$NI{6H$K4X$9$k$*CN$i$;$G$9!#(B $BITMW$NJ}$O%j%9%H$+$i:o=|$7$^$9$N$G!"$3$N$^$^JV?.$7$F$*CN$i$;$/$@$5$$!#(B $B@$$NCf$K#3K|7o0J>e$"$k$H8@$o$l$F$$$k=P2q$$7O%5%$%H!#(B $B#3K|7o$b$"$k$H$$$&$3$H$O!"%*%$%7%$;T>l$@$+$i$3$=;2F~$9$k;v6H.8/$$$r2T$.$?$$$

$B7HBS5a?M>pJs%5!<%S%9!!(B

2002-03-18 Thread $B7HBS5a?M>pJs%5!<%S%9(B
$B7HBS5a?M>pJs%5!<%S%9!!L5NA%-%c%s%Z!<%s$N$*CN$i$;(B $B$46=L#$N$J$$>pJs$G$7$?$i@?$K$*!W$K!!G[?.ITMW!!$H=q$-$4JV?.2<$5$$!#(B ML$B$+$i:o=|$5$l$^$9!#$b$7$b%a!<%k$,=EJ#$7$?(B $B>l9g$O$4MFpJs$rC5$;$^$9!#(B $BJXMx$5$r0lEYhttp://www.kkjs.com/i-mode.htm $BH/?.85(B $B7H

$B7HBS5a?M>pJs%5!<%S%9!!(B

2002-03-16 Thread $B7HBS5a?M>pJs%5!<%S%9(B
$B7HBS5a?M>pJs%5!<%S%9!!L5NA%-%c%s%Z!<%s$N$*CN$i$;(B $B$46=L#$N$J$$>pJs$G$7$?$i@?$K$*!W$K!!G[?.ITMW!!$H=q$-$4JV?.2<$5$$!#(B ML$B$+$i:o=|$5$l$^$9!#$b$7$b%a!<%k$,=EJ#$7$?(B $B>l9g$O$4MFpJs$rC5$;$^$9!#(B $BJXMx$5$r0lEYhttp://www.kkjs.com/i-mode.htm $BH/?.85(B $B7H

$B7HBS5a?M>pJs%5!<%S%9(B

2002-03-12 Thread kkjs
$B7HBS5a?M>pJs%5!<%S%9!!L5NA%-%c%s%Z!<%s$N$*CN$i$;(B $B$46=L#$N$J$$>pJs$G$7$?$i@?$K$*!W$K!!G[?.ITMW!!$H=q$-$4JV?.2<$5$$!#(B ML$B$+$i:o=|$5$l$^$9!#$b$7$b%a!<%k$,=EJ#$7$?(B $B>l9g$O$4MFpJs$rC5$;$^$9!#(B $BJXMx$5$r0lEYhttp://www.kkjs.com/i-mode.htm $BH/?.85(B $B7H

$B!*9-9p!*!!!!?7$7$$!!JXMx$JJ!;c(B$B$N!!

2002-02-05 Thread tesrix
*** $B!*9-9p!*?7$7$$!!JXMx$JJ!;c$N!!pJs$H;W$$$*Aw$j?=$7>e$2$^$7$?!#(B *** $B$3$N%a!<%k$rITMW$H$5$l$kJ}$O62$lF~$j$^$9$,(B $B$3$N$^$^JVAw$/$@$5$$!#%a!<%k$NAw?.$r$R$+$($5$;$F$$$

$B"#$G$"$$$N7hDjHG"#$"$($^$9$M$C(B$B$H"#(B

2002-01-24 Thread $B$"$($^$9$M$C$H(B
$B$44uK>$KE:$o$:$3$N%a!<%k$,FO$$$F$7$^$$$^$7$?$i$*http://www.aemasu.net/ === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

!$B9-9p(B! $B%Q%=%3%s!&(BOA$B$N$M$C$HDLHN!V$K$3$K$3F;!W%*!<%W%s$N$40FFb(B

2002-01-23 Thread 2525do
$B$*5RMM3F0L(B $B!|J8>O$NJ8;zG[Ns$,Mp$l$k>l9g$O%5%$%:$rD4@0$7$F$4Mw2<$5$$!|(B $B$*$9$9$a>&IJ$rK~:\CW$7$^$7$?%[!<%`%Z!<%8$,$3$NEY3+@_CW$7$^$7$?$N$G(B $B$40FFbCW$7$^$9!#I,MW$J$$J}$KFO$$$F$7$^$C$?>l9g$O@?$K?=$7Lu$4$6$$$^$;$s!#(B

$B%a%kM'$K$J$C$F$M!#(B

2002-01-04 Thread $BH~Jf(B
$B$3$s$K$A$O!"%W%i%$%Y!<%H(BH$B%S%G%*;#$j$^$7$?!#Gc$C$F$/$l$??M$K$OD>%"%I65$($k$N$G%a%kM'$K$J$j$^$;$s$+!)Gc$C$F$/$l$k?M$O!"#H#P$r8+$F$M!#%W%m%U$H$+$"$k$h!#(B http://www.d-mix.net/ $B$@$h!#(B To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubsc

$B%a!<%k%^%,%8%s9XFI$N$*4j$$(B

2001-12-19 Thread $B#E!u#C!]#U(B
$BFMA3$N%a!<%k$r:9$7>e$2$?$3$H!"$4MF$BM-1W$J>&IJ$r$40FFb$7$^$9%a!<%k%^%,%8%s$rH/4)CW$7$F$*$j$^$9!#(B$B>&IJ>pJs$K6=L#$r$*;}$A$G$7$?$i!"@'Hs9XFI!JL5NA!K$r$*4j$$CW$7$^$9!#(B$BITI,MW$G$7$?$i!"$*$B>!   $B9XFIEPO?!!(Bhttp://www.ec-inte

$B$*@$OC$K$J$j$^$9(B

2001-12-04 Thread $B%i%Y%s%@!<;(B
$BLLGr$$$h!"C/$K$bCN$i$l$:0B?4!"=w@-$O40A4(B $BL5NA%-%c%C%7%e%P%C%/$,$"$k$h!*CK@-$*;n$7(B $BIU$-0lEY;n$7$F$_$F$M!*!*(B To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

$B:#$N@83h!"JQ$($F$_$^$;$s$+!)(B

2001-07-24 Thread ts-net
“Ë‘R‚̃[ƒ‹Ž¸—ç’v‚µ‚Ü‚·B ‚±‚̃[ƒ‹‚ÍDMNŽÐ‚É‚æ‚è”zM‚³‚ê‚Ä‚¨‚è‚Ü‚·B ”zM‰ðœ‚Í‚±‚±‚©‚炨Šè‚¢’v‚µ‚Ü‚·B http://dmn.tripod.com/?[EMAIL PROTECTED] ‚±‚̃[ƒ‹‚ÉŠÖ‚·‚é‹êî“™‚́A‚±‚̃[ƒ‹‚ɕԐM‚¹‚¸A [EMAIL PROTECTED] ‚܂ł¨Šè‚¢’v‚µ‚Ü‚·B

y“]EŽx‰‡ƒTƒCƒgzƒWƒ‡ƒuƒŒƒbƒNƒX

2001-06-17 Thread job-rex.com
y“]EŽx‰‡ƒTƒCƒgzƒWƒ‡ƒuƒŒƒbƒNƒX http://www.job-rex.com/ ‚Í‚¶‚߂܂µ‚āAƒWƒ‡ƒuƒŒƒbƒNƒX‚Å‚·B “Ë‘R‚Å‚·‚ª ¡“­‚¢‚Ä‚¢‚é‰ïŽÐ‚Ì•]‰¿‚É–ž‘«‚µ‚Ä‚¢‚Ü‚·‚©H ƒWƒ‡ƒuƒŒƒbƒNƒX‚ÍŒ»ÝƒLƒƒƒŠƒAƒAƒbƒvŠˆ“®’†‚̐lA •s–ž‚Í‚ ‚邯‚ǁdddA‚Æ‚¢‚¤l‚ÌŠˆ“®‚ðŽx‰‡‚·‚é ƒLƒƒƒŠƒAƒAƒbƒvŽx‰‡ƒTƒCƒg‚Å‚·B ¡‚܂œ]EŠˆ“®‚Ő¬‰Ê‚ðã

$B!JL5NA%3%s%F%s%D!K(BFREE JAPANESE TOONS UPDATED DAILY!

2001-06-14 Thread info
To cancel your subscription please click on the link : http://64.23.86.178/rejectmail.html XXX FREE-ASIAN DAYLY PICTURE ARCHIVE! Japanese 10 pics updated daily! Point your browser at: http://www.free-asia.com/free/okazu/ JAPANESE SCHOOL GIRL'S GOLDEN ARCHIVES! Our favorite now with o

  1   2   >