Re: -current kernel problems (spec_getpages vm_fault)
On Friday, 27 August 1999 at 8:55:04 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Greg Lehey writes: On Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote: int devminor; /* minor number */ devminor = minor(dev); +dev-si_bsize_phys = DEV_BSIZE; +dev-si_bsize_best = BLKDEV_IOSIZE; +dev-si_bsize_max = MAXBSIZE; Bingo! Thank you. Cool, I expect grog will commit it soon. So did I until I read this message. The patch for ccd is not quite right. Here is the patch from my big fat patch at http://www.backplane.com/FreeBSD4/ The problem is that you cannot simply set the physical sector size to DEV_BSIZE if the underlying device has a larger sector size. If you do, specfs's blocksize alignment (another fix in my big fat patch) will be incorrect and result in an I/O error on the physical media. For example, swap-backed VN devices have a sector size of one page, i.e. 4K. Vinum currently doesn't track the sector size of the drives. I'll have to put some code in there to DTRT. In the meantime, I'll set si_bsize_best to 4K in the hope that this will be OK. Are there any larger block sizes in current use? 4K is probably too conservative, it only applies if you have a swap-backed vn device at the bottom, which would be a truly weird thing to do with vinum. I think I've heard of people doing things like this. Cybernet were thinking of it a long time ago, but I think I've talked them out of it. Don't spend too much time on tracking the sector size yet. I think the si_bsize stuff needs some thinking before we do more with it. OK, I'll set it to 4 kB at the moment and make a note to myself to fix it when dev_t stops changing. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Fri 1999-08-27 (10:25), Nick Hibma wrote: I seriously doubt they'll win this lawsuit. You can sue someone for anything and everything, including having a hair color which ^ in the States Or if you're a US company. Wasn't it (the Irish?) McMuffin which Mcdonalds sued for name infringment? Neil -- Neil Blakey-Milner [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
I seriously doubt they'll win this lawsuit. You can sue someone for anything and everything, including having a hair color which ^ in the States Sorry, I've lived in Europe, you can't pull that one on me. :) In Germany, for example, it's possible to sue someone simply for sticking their finger against their forehead. The myth that only the U.S. is litigious is just that, a myth. Europeans sue the crap out of one another all the time, and for issues just as silly. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
In message 8062.935743977@localhost, "Jordan K. Hubbard" writes: I seriously doubt they'll win this lawsuit. You can sue someone for anything and everything, including having a hair color which ^ in the States Sorry, I've lived in Europe, you can't pull that one on me. :) In Germany, for example, it's possible to sue someone simply for sticking their finger against their forehead. The myth that only the U.S. is litigious is just that, a myth. Europeans sue the crap out of one another all the time, and for issues just as silly. :) Jordan, I've lived in the US, Luxembourg, Italy and Denmark. While it is true that anyone can sue anybody else for anything they feel like all over the planet, the likely (lack of) outcome in europe makes it far less likely that they will do so in the first place. The main difference as far as I can tell, is that European courts apply some kind of "common sense" criteria before they award huge compensations to people who burn themselves on coffee, cut their fingers off with chain saws and so on: "Should this person not be realizing that coffee could be hot ? She has been drinking coffee for the last 50+ years ?" "If you use a chainsaw, shouldn't you be smart enough to realize that you cannot stop the chain with your hand ?" etc etc. The secondary difference is that in all the countries I know, they lawyer has to state his fee before the verdict, and it may not depend on the outcome of the verdict. The third difference is that we only use jurys in murder cases, we fully realize the ability of a showman-laywer to sway a jury, therefore we don't use them, unless the issue is the gravest crime we know off. Fourth, "puntative damages" fall to the state over here, so the potential for getting rich that way is simply not present. So while you're technically correct reality looks far different. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VESA_800x600 mode on CT65554 based videocard.
I'm trying to get VESA_800x600 mode to work on my notebook (Toshiba SatellitePro 445, CT65554 videocard, 2MB, 800x600 LCD), and unfortunately found that it is impossible. Any ideas of what is wrong? Following is relevant pieces from dmesg, vidcontrol, kernel debug (VESA_DEBUG=1 in my kernel config), and trace of syscalls made by vidcontrol: Output of vidcontrol -i mode: mode# flags typesize font window linear buffer -- 258 (0x102) 0x000b G 800x600x4 4 8x16 0xa 64k 64k 0x 2048k 259 (0x103) 0x000f G 800x600x8 1 8x16 0xa 64k 64k 0xfe00 2048k 275 (0x113) 0x000f G 800x600x15 18x16 0xa 64k 64k 0xfe00 2048k 276 (0x114) 0x000f G 800x600x16 18x16 0xa 64k 64k 0xfe00 2048k 277 (0x115) 0x000f G 800x600x24 18x16 0xa 64k 64k 0xfe00 2048k Output of dmesg: VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 40 00 00 01 20 00 00 01 16 01 00 01 31 01 00 01 4a 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 20 mode(s) found VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc0265fa0 (140) VESA: CHIPS 6x554 Super VGA VESA: Chips Technologies, Inc. 6x554 Display Controller 2 vga-pci0: Chips Technologies model 00e4 VGA-compatible display device at device 4.0 on pci0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 06 40 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sc0: fb0 kbd0 Output of vidcontrol VESA_800x600: vidcontrol: cannot activate raster display: Inappropriate ioctl for device Kernel debug msgs when doing vidcontrol VESA_800x600 VESA: set_mode(): 24(18) - 258(102) VESA: about to set a VESA mode... VESA: mode set! vesa_set_mode(): vi_width:800, len:100, line_width:100 VESA: set_mode(): 258(102) - 24(18) Trace of syscalls (truss vidcontrol VESA_800x600): syscall ioctl(0,CONS_GETINFO,0x804bc1c) returns 0 (0x0) syscall ioctl(0,CONS_GET,0xbfbfd904) returns 0 (0x0) syscall ioctl(0,VSIOABORT,0x0) returns 0 (0x0) syscall ioctl(0,KDRASTER,0xbfbfd908) errno 25 'Inappropriate ioctl for device' syscall ioctl(0,SW_VGA_C80x25,0x0) returns 0 (0x0) syscall write(2,0xbfbfd1c4,12) returns 12 (0xc) syscall write(2,0xbfbfd1dc,30) returns 30 (0x1e) syscall write(2,0xbfbfd1bc,2) returns 2 (0x2) syscall write(2,0xbfbfd1c0,31) returns 31 (0x1f) syscall exit(0x0) process exit, rval = 0 -- "We believe in the Power and the Might!" (Manowar, 1996) Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: [EMAIL PROTECTED] ICQ: #42290709 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VESA_800x600 mode on CT65554 based videocard.
I'm trying to get VESA_800x600 mode to work on my notebook (Toshiba SatellitePro 445, CT65554 videocard, 2MB, 800x600 LCD), and unfortunately found that it is impossible. Any ideas of what is wrong? You need to add options SC_PIXEL_MODE to your kernel configuration file. There is a note in http://www.freebsd.org/~yokota/sc_update-June.txt, which is referenced by /usr/src/UPDATING, about this option. - options SC_PIXEL_MODE Syscons has supported the raster console mode (VESA 800x600) by default. This is now an optional feature, and must be explicitly enabled by SC_PIXEL_MODE. If you have been using this mode, add the above option. - Please also refer to the man page syscons(4). Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current-APM causes panic on SMP-System
Hello, since the apm-code was changed to use the generic bios-call interface (dated around 1999/07/28) my FreeBSD-4.0-current system panics when I do an "apmconf -e". This has not changed since then. I reproduced it with a very current System (1999/08/25) today. The system is a Dual-Proc GigaByte 6BXDS-MB with 2x350Mhz PII and 256MB-RAM. For further information I have added the Config-File and dmesg-output. When calling apmconf -e i am getting the following panic: (written down by hand, so there might be some typos) --- Fatal trap 12: page fault while in kernel mode mp_lock=0102; cpuid=1; lapic.id=0100 fault virtual address = 0x8380 fault code = supervisor read, page not present ip = 0x50:0x8380 stack = 0x10:0xff80df24 frame = 0x10:0xc02bde80 code= base 0xc00f, limit 0x, type 0x1b = DPL 0, pres 1, def32 1, gran 0 proc flags = intr enabled, resume, iopl=0 current proc= idle interrupt mask = -- SMP: XXX --- The Adress 0x8380 seems to be the one from the APM-BIOS-Call. What can I do to track this further down? Michael - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - # # SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration - # Configuring the FreeBSD Kernel - The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # URL:http://www.FreeBSD.ORG/ # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: SMP-GENERIC,v 1.20 1998/10/22 13:49:51 bde Exp $ machine i386 cpu I686_CPU ident MCSMP maxusers64 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: #optionsNCPU=2 # number of CPUs #optionsNBUS=4 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs # Lets always enable the kernel debugger for SMP. options DDB # SMP shouldn't need x87 emulation, disable by default. #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT#MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options KERNFS options COMPAT_LINUX options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1#Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console #optionsFAILSAFE#Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # Enable the following (IPFIREWALL_VERBOSE optional) to enable the IP firewall # code. This is used in conjunction with the ipfw(1) command. See the # man page for more details. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable xparent proxy support #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow
Re: The Matrix screensaver, v.0.2
Poul-Henning Kamp [EMAIL PROTECTED] writes: The third difference is that we only use jurys in murder cases, we fully realize the ability of a showman-laywer to sway a jury, therefore we don't use them, unless the issue is the gravest crime we know off. That doesn't seem quite valid, it shouldn't be considered a good thing if a "showman-lawyer" (on either side) is permitted to sway a jury for a murder-trial. Of course this is getting off topic, or have there been any FreeBSD-current related homicides that I haven't heard about? ;--) Have there even been any actual trials directly related to FreeBSD? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdates reliability?
Doesn't Asus make an AT formfactor Super 7 motherboard w/ a 100mhz bus? Yes, but it is shy on card slots. The Tyan s1590 Trinity-AT100 is the has the most card slots of any of today's AT formfactor Super7 boards I am aware of. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
In message [EMAIL PROTECTED], Ville-Pertti Keinonen writes: Poul-Henning Kamp [EMAIL PROTECTED] writes: The third difference is that we only use jurys in murder cases, we fully realize the ability of a showman-laywer to sway a jury, therefore we don't use them, unless the issue is the gravest crime we know off. That doesn't seem quite valid, it shouldn't be considered a good thing if a "showman-lawyer" (on either side) is permitted to sway a jury for a murder-trial. I didn't say I agreed, I merely pointed out that we had limited the problem significantly. In Denmark a couple of interesting cases over the last five years have putj the use of a jury for even murder cases in the limelight. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
Hi, On Mon, 23 Aug 1999, Peter Wemm wrote: Maybe we *should* go approach the producers? I have gone to that movie several times, and I keep on enjoying it, so this is GOOD PR for them. Tell them there will be a reference to the movie web site or something. ;-) Actually the FreeBSD site already has a reference to them (they used an CG Render Farm of 32 Dual processor FreeBSD systems): http://www.freebsd.ady.ro/news/press-rel-1.html Read all about it ! ;-) Cheers, -Peter Take care, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
Hi again, http://www.freebsd.ady.ro/news/press-rel-1.html Whoops, that should have been http://www.freebsd.org/news/press-rel-1.html for all you fellows out there (the former is my local mirror)... Ady (@freebsd.ady.ro) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel problems (spec_getpages vm_fault)
:Greg, : :4K is probably too conservative, it only applies if you have a :swap-backed vn device at the bottom, which would be a truly :weird thing to do with vinum. : :Don't spend too much time on tracking the sector size yet. I think :the si_bsize stuff needs some thinking before we do more with it. : :Poul-Henning There's nothing wrong with the si_bsize stuff, but it got broken temporarily with all the dev_t work. All that really needs to be done is to reset the block sizes to their defaults when the last reference to the device goes away. This way reconfigurable devices do not have to reload the defaults prior to making adjustments based on the actual sector size of the device. There is no better way to do it. specfs and physio need to know how to realign byte-aligned I/O requests for physical devices. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel problems (spec_getpages vm_fault)
In message [EMAIL PROTECTED], Matthew Dillon writes: :Greg, : :4K is probably too conservative, it only applies if you have a :swap-backed vn device at the bottom, which would be a truly :weird thing to do with vinum. : :Don't spend too much time on tracking the sector size yet. I think :the si_bsize stuff needs some thinking before we do more with it. : :Poul-Henning There's nothing wrong with the si_bsize stuff, but it got broken temporarily with all the dev_t work. Well, it was obviously broken both in ccd and vinum before too, just not the same way. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On 27 Aug 1999, Ville-Pertti Keinonen wrote: Of course this is getting off topic, or have there been any FreeBSD-current related homicides that I haven't heard about? ;--) Have there even been any actual trials directly related to FreeBSD? There was a signup sheet going around at the last 'Brucified Anonymous' meeting, but I guess that never materialized. :- -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On Wed, 25 Aug 1999, Jordan K. Hubbard wrote: I'm sorry you got so beaten up over this one. All due respect to the contributors aside, I think we have too many old women around here, all shrieking and holding up their skirts at the rumor of a mouse somewhere in the building. :) As I said, I'm done with the subject. it's on my web page on freefall. Anyone wishing to do something with it can grab it and do whatever he wants (within terms of BSD license). Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re[2]: The Matrix screensaver, v.0.2
On 27.08.1999, 10:52, Jordan K. Hubbard wrote: Sorry, I've lived in Europe, you can't pull that one on me. :) In Germany, for example, it's possible to sue someone simply for sticking their finger against their forehead. The myth that only the U.S. is litigious is just that, a myth. Europeans sue the crap out of one another all the time, and for issues just as silly. :) True. A well known german lawyer is currently about to sue a few webhosters for using the name "Webspace" in their ads. (Yes, some silly - or maybe not-so-silly - dude has registered the word "Webspace" as a trademark). In this case, the problem are not the lawyers, but the fact that you can actually register trademarks like this one. Others have been threatened with lawsuits for using the word "Triton" in mainboard advertisments a few years ago, because "Triton" sounds very similar to the registered trademark "Tricon". -- # My PGP public key (ID=7A2AFB8F): http://darkstar.psa.at/aspgp.txt# # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make buildworld failed...
After cvsup my -current sources, i try to make build world... ld -N -e start -Ttext 0x10 -o btxldr.out btxldr.o objcopy -S -O binary btxldr.out btxldr === sys/boot/i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o === sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- What can i do? Rgdz, Osokin Sergey aka oZZ, [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld failed...
According to Sergey A. Osokin: After cvsup my -current sources, i try to make build world... === sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o I get a different error: dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null (cd /src/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o *** Error code 1 cc -elf -I/src/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -I/usr/obj/src/src/tmp/usr/include -c /src/src/sys/boot/i386/boot2/boot2.c (cd /src/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o 1 error *** Error code 2 CVSup from two hours ago. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld failed...
"Sergey A. Osokin" wrote: After cvsup my -current sources, i try to make build world... ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o === sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2.-- What can i do? Probably it consequences of recent dd changes... -Max To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld failed...
dd if=/dev/zero of=boot2.ldr bs=512 count=1 2/dev/null *** Error code 1 Probably it consequences of recent dd changes... So I'm not entirely alone, then. I actually kernel panic quite reliably every time I try to dd onto a floppy. I can dd from one file to another without a problem, and floppy access in general works as always. What debugging information would be relevant? -adam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mucho Bandwith
The claim of this arcticle is that the researchers are at a lost of what to do with their CA*Net3 network (80 giga bits /second ). http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) I am sure that some on the list can figure out other creative uses like clustering. Enjoy -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mucho Bandwith
http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) Significantly less than what its doing now. What the article fails to mention, is that (last I heard) CA*Net3 is *not* connected to the Internet at large. Currently, it only connects universities and research institutions within Canada. AFAIK, there aren't any real plans to patch it into the global 'net. josh -- C'est-ci n'est pas un .sig To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
