A freaking enlarger as a career. Wiped out by Xerox with the push of a (few) button(s).
From Webster's Revised Unabridged Dictionary (1913) [web1913]:
Engrosser \En*gross"er\, n.
1. One who copies a writing in large, fair characters.
Re:Broke support for Sun Ultra-2 with ISP SCSI
on
FreeBSD 5.1 Released
·
· Score: 1
Been posting it for months. Almost got Kirk Mckusic to work on it but he said he had not time since he was going out of the country on vacation. He forwarded it to two people who I never heard a peep out of.
I'm thinking that I could give access to the box to a developer. Maybe take it home from work and hook it to my network there where it can't be a problem for work.
Newsgroups: sol.lists.freebsd.current Date: 21 May 2003 19:00:59 +0000 Sender: news@ns.sol.net Approved: news@ns.sol.net Organization: sol.net Network Services - Milwaukee, WI References: X-To: stark@jeamland.ca X-Cc: freebsd-current@freebsd.org From: se@freebsd.org Subject: Re: Help with 5.1-beta snapshot Message-ID: Lines: 19
On 2003-05-21 11:14 -0400, stark wrote: > > I have the same mobo but I've never put extra NICs in it. > > Have you tried it with just the built-in bge? (I know it > > works fine for me.) > > It's failing for me:(
The Broadcom BCM550x Gigabit Ethernet chips are suppported, but the BCM4401 Fest Ethernet chip is not.
The ASUS A7V8X exists in many variants including some with either one of the above Ethernet chips. (I've got the 4401 on mine.)
Regards, STefan __________________________________________ _____ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fr eebsd- current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I use PPM/PNM/etc files all the time when I want to dump a JPEG from my camera out and then edit it without re-JPEG-ing it until the last step to prevent problems caused by re-JPEG-ing over and over.
Other file format are still in use just not by web sites because IE can't do them but IE can do PNG so you see it on the web and always will.
Along with the new features of FreeBSD 5.1 come some areas that can cause problems, or at least can lead to unexpected behavior. Generally, these come from the fact that a number of features are works-in-progress. A partial list of these areas of difficulty includes:
A number of features are not yet finished. Examples from the feature list above include SMPng and KSE. While suitable for testing and experimentation, these features may not be ready for production use.
Because of changes in kernel data structures and ABIs/APIs, third-party binary device drivers will require modifications to work correctly under FreeBSD 5.1. There is a possibility of more minor ABI/API changes before the 5-STABLE branch is created.
Several parts of FreeBSD's base system functionality have been moved to the Ports Collection. Notable examples include Perl, UUCP, and most (but not all) games. While these programs are still supported, their removal from the base system may cause some confusion.
Some parts of the FreeBSD base system have fallen into a state of disrepair due to a lack of users and maintainers. These have been removed. Specific examples include the generation of a.out-style executables, XNS networking support, and the X-10 controller driver.
A number of ports and packages do not build or do not run correctly under FreeBSD 5.0, whereas they did under FreeBSD 4-STABLE. Generally these problems are caused by compiler toolchain changes or cleanups of header files.
Many FreeBSD 5.1 features are seeing wide exposure for the first time. Many of these features (such as SMPng) have broad impacts on the kernel.
A certain amount of debugging and diagnostic code is still in place to help track down problems in FreeBSD 5.1's new features. This may cause FreeBSD 5.1 to perform more slowly than 4-STABLE.
Features are only added to the 4-STABLE development branch after a ``settling time'' in -CURRENT. FreeBSD 5.1 does not have the stabilizing influence of a -STABLE branch. (It is likely that the 5-STABLE development branch will be created sometime after 5.2-RELEASE.)
Documentation (such as the FreeBSD Handbook and FAQ) may not reflect changes recently made to FreeBSD 5.1.
Because a number of these drawbacks affect system stability, the release engineering team recommends that more conservative sites and users stick to releases based on the 4-STABLE branch until the 5.X series is more polished.
Ports worked out well until they broke during an upgrade.
Never use ports without using the portupgrade port to do it. This is a lesson I learned the hard way. The portupgrade tool includes pkgdb and "pkgdb -F" is like fsck for the ports database. You know you can't last without fsck.
Broke support for Sun Ultra-2 with ISP SCSI
on
FreeBSD 5.1 Released
·
· Score: 1
get:
Starting background file system checks.
Mon Jun 9 14:57:37 EDT 2003 panic: initiate_write_inodeblock_ufs1: already started cpuid = 1; Debugger("panic") Stopped at Debugger+0x1c: ta %xcc, 1 db> t panic() at panic+0x134 initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0x32c softdep_disk _io_initiation() at softdep_disk_io_initiation+0x80 spec_xstrategy() at spec_xstrategy+0x134 spec_specstrategy() at spec_specstrategy+0x8 spec_vnoperate() at spec_vnoperate+0x1c bwrite() at bwrite+0x3b8 vfs_bio_awrite() at vfs_bio_awrite+0x1a0 vop_stdfsync() at vop_stdfsync+0x120 spec_fsync() at spec_fsync+0x20 spec_vnoperate() at spec_vnoperate+0x1c ffs_sync() at ffs_sync+0x348 sync() at sync+0xcc syscall() at syscall+0x2a8 -- syscall (36, FreeBSD ELF64, sync) %o7=0x105e44 -- userland() at 0x10e4c8 user trace: trap %o7=0x105e44 pc 0x10e4c8, sp 0x7fdfffff311 pc 0x1001f0, sp 0x7fdfffff3e1 pc 0, sp 0x7fdfffff4a1 done db>
Wow, I had not heard. Near the end I was trying to help him as best one could over the Interenet. I sent him $200 and a copy of Pema Chodron's "When Things Fall Apart" but I guess it takes a lot more than that sometimes.
IBM, for its part, has said it doesn't intend to respond to SCO's threat. âoeWe believe our contact is perpetual and irrevocable,â an IBM spokeswoman said. âoeWe've already paid for it, and there is nothing else we need to do.â
Linux/usr/include/asm/errno.h and SCO 3.2.2/i386/usr/include/sys/errno.h both have:
#define EPERM 1/* Operation not permitted */ #define ENOENT 2/* No such file or directory */ #define ESRCH 3/* No such process */ #define EINTR 4/* Interrupted system call */ #define EIO 5/* I/O error */ #define ENXIO 6/* No such device or address */ #define E2BIG 7/* Arg list too long */
How hard is it to draw a license plate on cardboard and tape it over your real plate?
I have the UNIX code SCO found in Linux!
on
Today's SCO News
·
· Score: 1
#define EPERM 1/* Operation not permitted */ #define ENOENT 2/* No such file or directory */ #define ESRCH 3/* No such process */ #define EINTR 4/* Interrupted system call */
In the unlikely event that something actually breaks, even if it's at 2AM in the morning, a guy comes rushing in and repairs the machine.
Well you have to be there to let him in and he's only going to try to repair the unit. You might still have a down server the next day.
I can't think of many Linux binaries from 1997 that would work for me out-of-the-box on a modern distribution today.
Says more about Linux than about Solaris. I have some very old FreeBSD dynamically linked binaries like Veritas Netbackup that keep on plugging away. Linux developers love to break compatibility for no good reason. That's the number one reason we don't deploy it.
Slashdot Mirror
"gross" as in german meaning "large".
A freaking enlarger as a career. Wiped out by Xerox with the push of a (few) button(s).
From Webster's Revised Unabridged Dictionary (1913) [web1913]:
Engrosser \En*gross"er\, n.
1. One who copies a writing in large, fair characters.
Been posting it for months. Almost got Kirk Mckusic to work on it but he said he had not time since he was going out of the country on vacation. He forwarded it to two people who I never heard a peep out of.
I'm thinking that I could give access to the box to a developer. Maybe take it home from work and hook it to my network there where it can't be a problem for work.
You should ask here:
- current
http://lists.freebsd.org/mailman/listinfo/freebsd
What NIC does your A7V8X have?
:(
_ _____r eebsd- current
---
Newsgroups: sol.lists.freebsd.current
Date: 21 May 2003 19:00:59 +0000
Sender: news@ns.sol.net
Approved: news@ns.sol.net
Organization: sol.net Network Services - Milwaukee, WI
References:
X-To: stark@jeamland.ca
X-Cc: freebsd-current@freebsd.org
From: se@freebsd.org
Subject: Re: Help with 5.1-beta snapshot
Message-ID:
Lines: 19
On 2003-05-21 11:14 -0400, stark wrote:
> > I have the same mobo but I've never put extra NICs in it.
> > Have you tried it with just the built-in bge? (I know it
> > works fine for me.)
>
> It's failing for me
The Broadcom BCM550x Gigabit Ethernet chips are suppported,
but the BCM4401 Fest Ethernet chip is not.
The ASUS A7V8X exists in many variants including some with
either one of the above Ethernet chips. (I've got the 4401
on mine.)
Regards, STefan
_________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I use PPM/PNM/etc files all the time when I want to dump a JPEG from my camera out and then edit it without re-JPEG-ing it until the last step to prevent problems caused by re-JPEG-ing over and over.
Other file format are still in use just not by web sites because IE can't do them but IE can do PNG so you see it on the web and always will.
http://www.freebsd.org/releases/5.1R/early-adopte
Section 4 - Drawbacks to Early Adoption.
Along with the new features of FreeBSD 5.1 come some areas that can cause problems, or at least can lead to unexpected behavior. Generally, these come from the fact that a number of features are
works-in-progress. A partial list of these areas of difficulty includes:
feature list above include SMPng and KSE. While suitable for testing
and experimentation, these features may not be ready for production
use.
third-party binary device drivers will require modifications to work
correctly under FreeBSD 5.1. There is a possibility of more minor
ABI/API changes before the 5-STABLE branch is created.
moved to the Ports Collection. Notable examples include Perl,
UUCP, and most (but not all) games. While these programs are
still supported, their removal from the base system may cause some
confusion.
disrepair due to a lack of users and maintainers. These have been
removed. Specific examples include the generation of a.out-style
executables, XNS networking support, and the X-10 controller
driver.
correctly under FreeBSD 5.0, whereas they did under FreeBSD
4-STABLE. Generally these problems are caused by compiler toolchain
changes or cleanups of header files.
time. Many of these features (such as SMPng) have broad impacts on
the kernel.
place to help track down problems in FreeBSD 5.1's new features. This
may cause FreeBSD 5.1 to perform more slowly than 4-STABLE.
a ``settling time'' in -CURRENT. FreeBSD 5.1 does not have the
stabilizing influence of a -STABLE branch. (It is likely that the
5-STABLE development branch will be created sometime after
5.2-RELEASE.)
FreeBSD 5.1.
Because a number of these drawbacks affect system stability, the release engineering team recommends that more conservative sites and users stick to releases based on the 4-STABLE branch until the 5.X series is more polished.
get:
k _io_initiation() at softdep_disk_io_initiation+0x80
Starting background file system checks.
Mon Jun 9 14:57:37 EDT 2003
panic: initiate_write_inodeblock_ufs1: already started
cpuid = 1;
Debugger("panic")
Stopped at Debugger+0x1c: ta %xcc, 1
db> t
panic() at panic+0x134
initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0x32c
softdep_dis
spec_xstrategy() at spec_xstrategy+0x134
spec_specstrategy() at spec_specstrategy+0x8
spec_vnoperate() at spec_vnoperate+0x1c
bwrite() at bwrite+0x3b8
vfs_bio_awrite() at vfs_bio_awrite+0x1a0
vop_stdfsync() at vop_stdfsync+0x120
spec_fsync() at spec_fsync+0x20
spec_vnoperate() at spec_vnoperate+0x1c
ffs_sync() at ffs_sync+0x348
sync() at sync+0xcc
syscall() at syscall+0x2a8
-- syscall (36, FreeBSD ELF64, sync) %o7=0x105e44 --
userland() at 0x10e4c8
user trace: trap %o7=0x105e44
pc 0x10e4c8, sp 0x7fdfffff311
pc 0x1001f0, sp 0x7fdfffff3e1
pc 0, sp 0x7fdfffff4a1
done
db>
FreeBSD 5.0-RELEASE-p7 works OK though.
Wow, I had not heard. Near the end I was trying to help him as best one could over the Interenet. I sent him $200 and a copy of Pema Chodron's "When Things Fall Apart" but I guess it takes a lot more than that sometimes.
http://www.eetimes.com/sys/news/OEG20030606S0039
You can't get rid of a graphics file format once it's out there.
http://www.fpgacpu.org/links.html
http://www.aracnet.com/~healyzh/pdp_fpga.html
Michael Sokolov is rumored to be working on a FPGA VAX-inspired CPU with intent to fab eventually.
Linux
http://www.ovmj.org/GNUnet/namespace.php3?xlang=E
documents the planned GNUnet approach to namespaces and directories.
http://mail.gnu.org/archive/html/help-gnunet/
How hard is it to draw a license plate on cardboard and tape it over your real plate?
#define EPERM 1
#define ENOENT 2
#define ESRCH 3
#define EINTR 4
We Await Silent Tristero's Empire
http://tinyurl.com/cy1z
Well you have to be there to let him in and he's only going to try to repair the unit. You might still have a down server the next day.
Says more about Linux than about Solaris. I have some very old FreeBSD dynamically linked binaries like Veritas Netbackup that keep on plugging away. Linux developers love to break compatibility for no good reason. That's the number one reason we don't deploy it.
AOL: Is it all you know is is it all you know?
Want certified Java in FreeBSD?
Here's where to donate money:
http://www.freebsdfoundation.org/