Re: "J" type log in newsyslog
h did look through the man page first, but eyes must have skipped over it... sorry I wasn't thorough enough... thanks for the expanation though. At 05:53 PM 2.13.2002 +, Simon Dick wrote: >On Wed, Feb 13, 2002 at 11:45:35AM -0600, [EMAIL PROTECTED] wrote: >> Upgraded to 4.5-STABLE from 4.4 >> >> I must have missed the change notice, but was wondering what the new >> "J"-type log is in "newsyslog.conf". Used to be just (ZB), now (ZJB)...?? > >J means bzip2 the logs, have a look through newsyslog(8) :) > >-- >Simon Dick [EMAIL PROTECTED] >"Why do I get this urge to go bowling everytime I see Tux?" > > Best regards, Jack L. Stone, Server Admin === Sage-American http://www.sage-american.com [EMAIL PROTECTED] "My center is giving way, my right is in retreat; situation excellent! I shall attack!" === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
"J" type log in newsyslog
Upgraded to 4.5-STABLE from 4.4 I must have missed the change notice, but was wondering what the new "J"-type log is in "newsyslog.conf". Used to be just (ZB), now (ZJB)...?? Best regards, Jack L. Stone, Server Admin === Sage-American http://www.sage-american.com [EMAIL PROTECTED] "My center is giving way, my right is in retreat; situation excellent! I shall attack!" === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Great OS FBSD 4.5-STABLE!
I always use source At 06:01 PM 2.9.2002 +, Nuno Teixeira wrote: >On Fri, Feb 08, 2002 at 09:55:46AM -0600, [EMAIL PROTECTED] wrote: >| Although, I waited as long as I could stand it, I finally upgraded a number >| of boxes, including the main server from 4.4 to 4.5-STABLE. I make it a >| practice of using an "expendable" test box for initial upgrades to see what >| problems if any to expect. Then, if okay I move to the other boxes and >| finally the main server. >| >| Once again, the experience was a totally pleaseant one with not a single >| installation problem. While still going through "shake down" as the daily >| routines are done, I have not seen any probalems at all and in fact quite >| pleased with many subtle enhances that surface. >| >| Once again... GREAT JOB TEAM-4.5..!!! >| >| Best regards, >| Jack L. Stone, >| Server Admin >| >| === >| Sage-American >| http://www.sage-american.com >| [EMAIL PROTECTED] >| >| "My center is giving way, my right is in retreat; >| situation excellent! I shall attack!" >| === > > Hi, > > I'm about to upgrade a server from 4.4 RELEASE to 4.5 RELEASE from source. > > I'd like to know if you use a binary upgrade or source upgrade. > > Thnaks, > >-- >Nuno Teixeira >pt-quorum.com > >/* >PGP Public Key: >http://www.pt-quorum.com/pgp/nunoteixeira.asc >Key fingerprint: >8C2C B364 D4DC 0C92 56F5 CE6F 8F07 720A 63A0 4FC7 >*/ > > Best regards, Jack L. Stone, Server Admin === Sage-American http://www.sage-american.com [EMAIL PROTECTED] "My center is giving way, my right is in retreat; situation excellent! I shall attack!" === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ATA driver feature request
Yes, I always see this same thing if I place an older CD-ROM slave on the same cable. It drops to UDMA33. If I remove the CD-ROM, then the systme sees the cable fine as ATA100. If I then put my new CD-ROM on the cable, it likes that too. At 12:04 AM 1.22.2002 -0600, [EMAIL PROTECTED] wrote: > >On Sun, 20 Jan 2002, Dmitry Valdov wrote: >> >> On Sun, 20 Jan 2002, Bill Moran wrote: >> > > FreeBSD limits both >> > > drives on the bus because there is 'non-ATA66 compliant cable'. >> > >> > Are you sure you have an 80 conductor cable and that it isn't too long? >> >> Yes. When I disconnect secondary (non ATA-66/100 compliant) drive from this >> cable, FreeBSD use ATA-100 on primary. >> > >FWIW, I'm seeing the exact same symptom. I just added to 80gb Western >Digital (IDE) drives to the system. I used the 80-wire cables that came >with the drives, and I see the following messages: > >atapci0: port 0xd000-0xd00f at device 7.1 on pci0 >ata0: at 0x1f0 irq 14 on atapci0 >ata1: at 0x170 irq 15 on atapci0 >. . . >ad0: 19458MB [39535/16/63] at ata0-master UDMA66 >ad1: 76319MB [155061/16/63] at ata0-slave UDMA66 >ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable >ad2: 76319MB [155061/16/63] at ata1-master UDMA33 >ad3: 2503MB [5086/16/63] at ata1-slave UDMA33 > >They are the exact same drives using the exact same cable. My controller >only supports UDMA66, not 100... but the reason that the 2nd controller >seems to print out "non-ATA66 compiant cable" appears to simply be that >ad3 is only ATA33 capable. > >Just thought I'd pipe up, since the subject came up :) > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin === Sage-American http://www.sage-american.com [EMAIL PROTECTED] "My center is giving way, my right is in retreat; situation excellent! I shall attack!" === To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Trying NT Hacks
I put up a brand new server with a brand new IP and the attacks were immediate so, I figured they are just running loose in swarms... At 07:02 PM 12.27.2001 -0800, Peter Ong wrote: >Really... I just wonder how they figure out the IPs, other than randomly >guessing. Someone did mention that, and I guess there really aren't that >many IP addresses that a computer could randomly generate in a short amount >of time without covering the whole spectrum. > >Peter >- Original Message - >From: "Julien B." <[EMAIL PROTECTED]> >To: "Peter Ong" <[EMAIL PROTECTED]> >Cc: <[EMAIL PROTECTED]> >Sent: Thursday, December 27, 2001 6:57 PM >Subject: Re: Trying NT Hacks > > >> On Thu, Dec 27, 2001 at 06:39:58PM -0800, Peter Ong wrote: >> > I don't know what it is with some people. I post my site here today >because >> > I was wondering about why the initial page was gibberrish, and then I >get >> > crackers. I finally get home, and I'm reviewing my log files, and I'm >> > seeing some folks trying to use IIS/NT exploits on my FreeBSD machine. >It's >> > infuriating. >> > >> >> My logs are full of these too, and getting bigger and bigger everyday. >Most of >> these "attacks" comes from some Windows worms. I'm totally amazed through, >as >> i get one such connection every 10 minuts, and my web server is not even >> public. >> >> Regards >> >> Julien B >> >> >> > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: slightly bumpy ride ahead
I didn't say it was every night. It is weekly & Friday night is the night... AND, the time is very short by doing it weekly rather than scheduling at a longer span of time to play "catchup" I want to keep the sources up to date, then make world once/month. works for me and seems the fair way to allocate short loads on the mirror's server so, I don't understand the "load" concern. ...and I always read UPDATING... At 02:57 PM 12.15.2001 +0200, Domas Mituzas wrote: >On Fri, 14 Dec 2001 [EMAIL PROTECTED] wrote: > >> I will need to abort cron tonight... please advise when done... thanks! > >It is considered unwise to have cron job each night, unless you: >a) are cvsup mirror >b) do src/ tree builds each day (sounds masochistic) >c) also reboot after each build :) >d) really wish to hog cvsup server resources (it's really i/o intensive >on serveris-side) > >If you want to track changes, you can read cvs commitlogs, use webcvs, >read UPDATING file, stable@ mailing list. > >-- >Regards, >Domas Mituzas >DELFI Internet, UAB > > > Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cvsup server warnings; /usr/local/etc/cvsup/prefixes/FreeBSD.cvs
Try another mirror
At 01:03 PM 12.1.2001 -0500, Jason Hunt wrote:
>I don't know if it's just something I missed, or if this has been answered
>before, but when I try cvsup'ing my ports I get numerous messages about
>not being able to write
>/usr/local/etc/cvsup/prefixes/FreeBSD.cvs/{port-section}/{port-name}/files/
patch-*,v
>and
>/usr/local/etc/cvsup/freebsd/FreeBSD.cvs/{port-section}/{port-name}/pkg-*
>
>I am using cvsup 16.1e and cvsup2.ca.freebsd.org
>
>My supfile is as follows:
>
>*default host=cvsup2.ca.FreeBSD.org
>*default base=/usr
>*default prefix=/usr
>*default release=cvs tag=.
>*default delete use-rel-suffix
>*default compress
>
>ports-all
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-stable" in the body of the message
>
>
Best regards,
Jack L. Stone,
Server Admin
Sage-American
http://www.sage-american.com
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: kernel compile error on latest cvsup of stable
... several messages ago have mentioned the buildkernel has a bug that crept in during the past few days... something to do with stale dependencies... I just had a similar problem (October update worked fine) tonight. This fixed mine #rm -rf /usr/obj/usr Then recompile the kernel... should be fine. At 11:32 PM 11.13.2001 -0500, Ilya wrote: >I just cvsuped 4.4 stable and kernel build fails with these: > >cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr >ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma >t-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpre >ferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-pr >ototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fforma >t-extensions -ansi -c linux_sysent.c >In file included from linux_sysent.c:14: >linux_proto.h:57: syntax error before `linux_time_t' >linux_proto.h:57: `linux_time_t' undeclared here (not in a function) >linux_proto.h:57: syntax error before `)' >linux_proto.h:57: `linux_time_t' undeclared here (not in a function) >linux_proto.h:57: syntax error before `)' >linux_proto.h:156: syntax error before `linux_handler_t' >linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) >linux_proto.h:156: `linux_handler_t' undeclared here (not in a function) >linux_proto.h:184: syntax error before `linux_dev_t' >linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) >linux_proto.h:184: `linux_dev_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `linux_osigaction_t' >linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `)' >linux_proto.h:189: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:189: syntax error before `)' >linux_proto.h:190: syntax error before `linux_osigaction_t' >linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:190: syntax error before `)' >linux_proto.h:190: `linux_osigaction_t' undeclared here (not in a function) >linux_proto.h:190: syntax error before `)' >linux_proto.h:196: syntax error before `linux_osigset_t' >linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:196: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:200: syntax error before `linux_osigset_t' >linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:200: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:201: syntax error before `linux_osigset_t' >linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:201: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `linux_osigset_t' >linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `)' >linux_proto.h:204: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:204: syntax error before `)' >linux_proto.h:216: syntax error before `linux_gid_t' >linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:216: syntax error before `)' >linux_proto.h:216: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:216: syntax error before `)' >linux_proto.h:220: syntax error before `linux_gid_t' >linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:220: syntax error before `)' >linux_proto.h:220: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:220: syntax error before `)' >linux_proto.h:344: syntax error before `linux_osigset_t' >linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:344: syntax error before `)' >linux_proto.h:344: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:344: syntax error before `)' >linux_proto.h:345: syntax error before `linux_osigset_t' >linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:345: syntax error before `)' >linux_proto.h:345: `linux_osigset_t' undeclared here (not in a function) >linux_proto.h:345: syntax error before `)' >linux_proto.h:380: syntax error before `linux_uid_t' >linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:380: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:383: syntax error before `linux_gid_t' >linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:383: `linux_gid_t' undeclared here (not in a function) >linux_proto.h:410: syntax error before `linux_pid_t' >linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) >linux_proto.h:410: `linux_pid_t' undeclared here (not in a function) >linux_proto.h:439: syntax error before `linux_uid_t' >linux_proto.h:439: `linux_uid_t' undeclared here (not in a function) >linux_proto.h:439: syntax error before `)' >linux_proto.h:439:
Re: mount madness
Perhaps go into Win2K and convert the HD from Fat32 to NTFS under Disk Management tools. then maybe FreeBSD can see it At 04:04 PM 9.6.2001 -0400, Robin P. Blanchard wrote: >after much wailing and gnashing of teeth i've figured out >what the problem is. i wasn't doing anything wrong. >the command was fine. > >the damn harddisk that i've been assigned to retrieve data >from is apparently fat32x. i can't mount the bastard period. >no freebsd. no linux. nothing. > >windows 2000 can't even speak fat32x. > >ridiculous. > >any ideas on how to get this thing working? >(other than building up a windwos98 box) > >thanks in advance. > > > >> root@quattro [~]# mount -t msdos /dev/ad1s1 /mnt/fat32 >> msdos: /dev/ad1s1: Invalid argument >> >> >> what the hell am i doing wrong here? > > > > >-- > >Robin P. Blanchard >IT Program Specialist >Georgia Center for Continuing Ed. >fon: 706.542.2404 fax: 706.542.6546 >email: [EMAIL PROTECTED] > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message > > Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CVSUP
Yeah, there are about 17 sites in the USA. Best to run traceroute on each to find the fastest site. Sometimes closer is not better many are more than 20 hops while another is only 11 hops (from here) but depends on your location too. At 10:34 PM 8.19.2001 -0700, Kris Kennaway wrote: >On Mon, Aug 20, 2001 at 11:00:35AM +0700, Maxim M. Kazachek wrote: >> What is happened with cvsup.internat.freebsd.org... Looks like >> CVS service is downed for some time. I've got following error message >>Cannot connect to cvsup.internat.freebsd.org: Connection refused >> about a week. > >Just use another cvsup server in the meantime...there are probably >several which are closer to you anyway. > >Kris > >Attachment Converted: "c:\eudora\attach\Re CVSUP1" > Best regards, Jack L. Stone, Server Admin Sage-American http://www.sage-american.com [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
