Re: SATA Raid (stress test..)
On 3/2/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: [snipped] Why not happy? Transfer rates from 53 to 92Mb/s, give or take; what's wrong with that? On a plain sata disk I get: Seek times: Full stroke: 250 iter in 4.717248 sec = 18.869 msec Half stroke: 250 iter in 5.342099 sec = 21.368 msec Quarter stroke: 500 iter in 8.870424 sec = 17.741 msec Short forward:400 iter in 2.753187 sec =6.883 msec Short backward: 400 iter in 1.390941 sec =3.477 msec Seq outer: 2048 iter in 0.426796 sec =0.208 msec Seq inner: 2048 iter in 0.487280 sec =0.238 msec Transfer rates: outside: 102400 kbytes in 1.652736 sec =61958 kbytes/sec middle:102400 kbytes in 1.697364 sec =60329 kbytes/sec inside:102400 kbytes in 1.834759 sec =55811 kbytes/sec A second, different, disk gives me better seek times but roughly similar transfer rates. So I beat your inside transfer rate, but you're 50% up on the outside rate. If you have windows anywhere, then download sandra-lite. Among other things, it has comparison benchmarks for all its tests, including disk transfer rates for things like SCSI-RAID0, RAID1, SATA/PATA-RAID0/1 etc. diskinfo -t /dev/da0e /dev/da0 512 # sectorsize 1756440297472 # mediasize in bytes (1.6T) 3430547456 # mediasize in sectors 213541 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. Seek times: Full stroke: 250 iter in 3.502539 sec = 14.010 msec Half stroke: 250 iter in 2.749807 sec = 10.999 msec Quarter stroke: 500 iter in 4.919431 sec =9.839 msec Short forward:400 iter in 2.257898 sec =5.645 msec Short backward: 400 iter in 2.293915 sec =5.735 msec Seq outer: 2048 iter in 0.132233 sec =0.065 msec Seq inner: 2048 iter in 0.152473 sec =0.074 msec Transfer rates: outside: 102400 kbytes in 1.487112 sec =68858 kbytes/sec middle:102400 kbytes in 1.505039 sec =68038 kbytes/sec inside:102400 kbytes in 1.336495 sec =76618 kbytes/sec This and all the other benchmarks you've run are useless. Run a real benchmark like iozone. It's in ports under benchmarks/iozone. http://www.iozone.org/ -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
Nikolas Britton wrote: This and all the other benchmarks you've run are useless. Run a real benchmark like iozone. It's in ports under benchmarks/iozone. http://www.iozone.org/ Please can you be careful when you attribute your comments. You've sent this email to me, and left only my name in the attributions as if I were someone suggesting either dd or diskinfo as accurate benchmarks, when in fact my contribution was to suggest unixbench and sandra-lite. Maybe you hate those too, in which case you can quote what I said in-context and rubbish that at your pleasure. The OP sent poor-throughput dd stats, and I explained why they were poor. The OP then complained that diskinfo -t stats weren't up to snuff, so I contributed mine because they were comparable and I couldn't see why he(?) didn't like his(?). I would contend that the statement all the other benchmarks you've run are useless is grandiose over-generalisation. Both dd (with a sensible blocksize) and diskinfo -t will give you useful information. One might be an idiot to trust the data to several decimal places, but if the result from both was, say, a transfer rate of 5Mb/s when you expected 50Mb/s, you could conclude that something was up. Of course neither mimics real-world behaviour; but both likely provide reasonable maxima. You may find that useless, but with no explanation for your reasoning, your statement isn't terribly helpful. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
On 3/2/06, Alex Zbyslaw [EMAIL PROTECTED] wrote: Nikolas Britton wrote: This and all the other benchmarks you've run are useless. Run a real benchmark like iozone. It's in ports under benchmarks/iozone. http://www.iozone.org/ Please can you be careful when you attribute your comments. You've sent this email to me, and left only my name in the attributions as if I were someone suggesting either dd or diskinfo as accurate benchmarks, when in fact my contribution was to suggest unixbench and sandra-lite. Maybe you hate those too, in which case you can quote what I said in-context and rubbish that at your pleasure. Yes I see your point, it does look like I'm replying to something you wrote. This was a oversight and I am sorry. The OP sent poor-throughput dd stats, and I explained why they were poor. The OP then complained that diskinfo -t stats weren't up to snuff, so I contributed mine because they were comparable and I couldn't see why he(?) didn't like his(?). I would contend that the statement all the other benchmarks you've run are useless is grandiose over-generalisation. Both dd (with a sensible blocksize) and diskinfo -t will give you useful information. One might be an idiot to trust the data to several decimal places, but if the result from both was, say, a transfer rate of 5Mb/s when you expected 50Mb/s, you could conclude that something was up. Of course neither mimics real-world behaviour; but both likely provide reasonable maxima. You may find that useless, but with no explanation for your reasoning, your statement isn't terribly helpful. Yes, well you see it's a long story :-) By sheer happenstance over the night had I drive fail on the array I ran the diskinfo test on, if I would have check my email I'd have know this. So when I logged into the system via ssh and ran the test I did not know that the array (RAID5, 8 disks, SATAII, PCI-X) was operating in degraded mode. Having run extensive iozone testing on this array when I first designed it I just assumed diskinfo was lying when it said I was getting 70MB/s transfers, I was getting sustained read transfer rates of 105MB/s on a 650GB test file back when it only had 4 drives. This is the reason I said diskinfo was useless, however, I still feel that diskinfo is sorta useless because it only shows you the tip of the iceberg. A tool such as iozone is much more useful for getting accurate numbers for the entire disk subsystem. Do you know how disk caching effects your system? Do you know what FreeBSD, and it's tunable setting, can do to your file system? Best stripe and block size for your needs? iozone can tell you all of this and more. Remember that 105MB/s number I quoted above?, that's just the sustained read transfer rate for a big ass file, I don't need to work with big ass files. I need to work with 15MB files (+/- 5MB). After buying the right disks, controller, mainboard etc. and lots of tuning with the help of iozone I get: 200 - 350MB/s overall (read, write, etc.) for files less then or equal to 64MB*. So anyways, that's what iozone can do for you. google it and you'll find out more stuff about it. *in a 4 disk setup running FreeBSD 5.4, I have 8 disks today and run FreeBSD 6.1-PRERELEASE. so those numbers went up because I have 4 more disks and the file system speed improvements to the FreeBSD 6.x line, but I have not benchmarked the improvements because the server is in production now. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
Beastie wrote: Beastie wrote: Robert Uzzi wrote: That still dosen't connedt SATA to a non sata board though. That's my situation I have 6 SATA drives but no SATA native board. Looking for a cheap addin card to build this upon. I'll buy Intel SRCS16 (500$) this week, will talk to u later about it's compatibility and performance for RAID 5 with 4 SATA drive. regards reza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] FreeBSD-6.0 known this device. (Intel SE7320 EP2) ---snip-- amrd0: LSILogic MegaRAID logical drive on amr0 amrd0: 1430511MB (2929686528 sectors) RAID 5 (optimal) ar0: 76228MB LSILogic v3 MegaRAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master ---snap--- System now work with RAID df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a 496M 55M401M12%/ devfs1.0K1.0K 0B 100%/dev /dev/ar0s1d 496M 12K456M 0%/tmp /dev/ar0s1e 67G419M 61G 1%/usr /dev/amrd0s1d1.3T 12M1.2T 0%/var /dev/acd0651M651M 0B 100%/cdrom My questiin is now, how do i test SATA RAID performance ? Is there any tools or program to do some benchmark ? please help me... regards reza I try to test with dd simple command dd if=/dev/amrd0s1d of=/dev/null ^C31297+0 records in 31297+0 records out 16024064 bytes transferred in 7.970548 secs (2010409 bytes/sec) the result is very slow performance (-+ 2 Mbytes/sec), with write cache enable on drive. :( regards reza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
Beastie wrote: I try to test with dd simple command dd if=/dev/amrd0s1d of=/dev/null ^C31297+0 records in 31297+0 records out 16024064 bytes transferred in 7.970548 secs (2010409 bytes/sec) the result is very slow performance (-+ 2 Mbytes/sec), with write cache enable on drive. :( Your performance sucks because, to quote the manual, Input data is read and written in 512-byte blocks. Try a sensible blocksize. 16k would mimic a standard file system block, but even that is likely to underestimate. If you were, say, copying the disk to another you could easily use 1Mb. Some examples: dd if=/dev/ad10s1a of=/dev/null ^C794830+0 records in 794830+0 records out 406952960 bytes transferred in 164.049297 secs (2480675 bytes/sec) dd if=/dev/ad10s1a of=/dev/null bs=16k ^C53745+0 records in 53745+0 records out 880558080 bytes transferred in 21.092098 secs (41748245 bytes/sec) So from 2Mb/s to 41Mb/s! dd if=/dev/ad10s1a of=/dev/null bs=1m ^C933+0 records in 933+0 records out 978321408 bytes transferred in 13.836165 secs (70707556 bytes/sec) And up to 70Mb/s though nothing real world is likely to achieve that. There are a whole slew of ports (/usr/ports/benchmarks) some of which do disk tests. I've used unixbench in the past, which is a bit of a faff and does more than disks, but it works. If you run windows on the box and want graphical benchtests, then there are free apps out there that will do tests on disks, like Sandra. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
Your performance sucks because, to quote the manual, Input data is read and written in 512-byte blocks. Try a sensible blocksize. 16k would mimic a standard file system block, but even that is likely to underestimate. If you were, say, copying the disk to another you could easily use 1Mb. Some examples: dd if=/dev/ad10s1a of=/dev/null ^C794830+0 records in 794830+0 records out 406952960 bytes transferred in 164.049297 secs (2480675 bytes/sec) dd if=/dev/ad10s1a of=/dev/null bs=16k ^C53745+0 records in 53745+0 records out 880558080 bytes transferred in 21.092098 secs (41748245 bytes/sec) So from 2Mb/s to 41Mb/s! dd if=/dev/ad10s1a of=/dev/null bs=1m ^C933+0 records in 933+0 records out 978321408 bytes transferred in 13.836165 secs (70707556 bytes/sec) And up to 70Mb/s though nothing real world is likely to achieve that. There are a whole slew of ports (/usr/ports/benchmarks) some of which do disk tests. I've used unixbench in the past, which is a bit of a faff and does more than disks, but it works. If you run windows on the box and want graphical benchtests, then there are free apps out there that will do tests on disks, like Sandra. --Alex second tools is diskinfo, but i'm not quite happy with the result. #diskinfo -t /dev/amrd0s1d /dev/amrd0s1d 512 # sectorsize 96609024# mediasize in bytes (931G) 1953118377 # mediasize in sectors 121575 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. Seek times: Full stroke: 250 iter in 5.233346 sec = 20.933 msec Half stroke: 250 iter in 3.828152 sec = 15.313 msec Quarter stroke: 500 iter in 6.232849 sec = 12.466 msec Short forward:400 iter in 2.409001 sec =6.023 msec Short backward: 400 iter in 2.594473 sec =6.486 msec Seq outer: 2048 iter in 0.638372 sec =0.312 msec Seq inner: 2048 iter in 0.671994 sec =0.328 msec Transfer rates: outside: 102400 kbytes in 1.102065 sec =92916 kbytes/sec middle:102400 kbytes in 1.209657 sec =84652 kbytes/sec inside:102400 kbytes in 1.912485 sec =53543 kbytes/sec ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: French accents test
On Monday, 27 February 2006 at 0:05:31 -0500, Peter wrote: --- clue less [EMAIL PROTECTED] wrote: Does the mailing list improperly strip iso-8859-1 encoding and render it as unescaped UTF-8? This is a test to see: �����. I see the proper characters but when I reply in my yahoo account I get a question mark in a black circle for each character. This is a problem on my end no doubt. Here is a test of my own: éà ïà People, please use the FreeBSD-test mailing list for this sort of thing. In this case, though, Peter, you're using the wrong encoding. According to your message, it was ISO 8859-1. What you sent looks more like UTF-8 (and is thus mangled). Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp5rdJOCO29N.pgp Description: PGP signature
Re: French accents test
--- Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 27 February 2006 at 0:05:31 -0500, Peter wrote: --- clue less [EMAIL PROTECTED] wrote: Does the mailing list improperly strip iso-8859-1 encoding and render it as unescaped UTF-8? This is a test to see: �����. I see the proper characters but when I reply in my yahoo account I get a question mark in a black circle for each character. This is a problem on my end no doubt. Here is a test of my own: éà ïà People, please use the FreeBSD-test mailing list for this sort of thing. In this case, though, Peter, you're using the wrong encoding. According to your message, it was ISO 8859-1. What you sent looks more like UTF-8 (and is thus mangled). How do I change over? This seems to happen only when posting using my webmail yahoo account using firefox. Firefox shows ISO 8859-1 in its preferences. I know that I have pcre installed with UTF-8 support. Can this be causing the problem? -- Peter __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Raid (stress test..)
Beastie wrote: Robert Uzzi wrote: That still dosen't connedt SATA to a non sata board though. That's my situation I have 6 SATA drives but no SATA native board. Looking for a cheap addin card to build this upon. I'll buy Intel SRCS16 (500$) this week, will talk to u later about it's compatibility and performance for RAID 5 with 4 SATA drive. regards reza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] FreeBSD-6.0 known this device. (Intel SE7320 EP2) ---snip-- amrd0: LSILogic MegaRAID logical drive on amr0 amrd0: 1430511MB (2929686528 sectors) RAID 5 (optimal) ar0: 76228MB LSILogic v3 MegaRAID RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master ---snap--- System now work with RAID df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a 496M 55M401M12%/ devfs1.0K1.0K 0B 100%/dev /dev/ar0s1d 496M 12K456M 0%/tmp /dev/ar0s1e 67G419M 61G 1%/usr /dev/amrd0s1d1.3T 12M1.2T 0%/var /dev/acd0651M651M 0B 100%/cdrom My questiin is now, how do i test SATA RAID performance ? Is there any tools or program to do some benchmark ? please help me... regards reza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
French accents test
Does the mailing list improperly strip iso-8859-1 encoding and render it as unescaped UTF-8? This is a test to see: áéíóú. - Yahoo! Mail Use Photomail to share photos without annoying attachments. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: French accents test
This is a test to see: áéíóú. Vu d'ici ca marche. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: French accents test
I see the proper characters but when I reply in my yahoo account I get a question mark in a black circle for each character. This is a problem on my end no doubt. Here is a test of my own: éà ïà -- Peter --- clue less [EMAIL PROTECTED] wrote: Does the mailing list improperly strip iso-8859-1 encoding and render it as unescaped UTF-8? This is a test to see: �����. - Yahoo! Mail Use Photomail to share photos without annoying attachments. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Resolving Perl 'make test' Errors?
We're running perl 5.8.7_2 (from ports), with a mix of modules installed via ports and CPAN, all on a 6.0-STABLE machine. Someone tried to install WWW::Mechanize from CPAN, and when it tried to do a 'make test', there was an error. If I build the module in ports and go into the work directory and run 'make test' manually, I get the same test error. I usually prefer to install Perl modules through ports when possible, so that portupgrade can take care of them for me. However, one of the shortcomings of the (at least default) way in which ports installs Perl modules is that ports does not run 'make test'. Is there a clever way to have the ports system run 'make test' before installing a Perl module? Most of the /usr/ports/*/p5-*/Makefile files do not have 'test' defined as a target. Does anyone have any advice for how to go about ironing out this problem? My first inclination is to remake each of my p5-* ports and run 'make test' on them manually and then have CPAN reinstall everything that we have installed via CPAN. Thanks in advance! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test
Hello FreeBSD, Subj... -- Best regards, Playnet mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test
On Friday 16 December 2005 03:37 pm, Playnet wrote: Hello FreeBSD, Subj... Please don't use this list to test. It's a waste of bandwidth and results in thousands of unnecessary emails being sent worldwide. The proper list for this is: [EMAIL PROTECTED] Beech -- --- Beech Rintoul - System Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://akparadise.byethost33.com --- pgpZ74KwrpTfp.pgp Description: PGP signature
test
test ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test
test ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test
On Saturday, 15 October 2005 at 17:56:19 -0400, Teo De Las Heras wrote: test ___ freebsd-questions@freebsd.org mailing list cracked-record-mode Please do *not* send test messages to FreeBSD questions. Please also don't respond to such messages (this one response should be enough). If you want to test, use the FreeBSD-test list. I'm sending this message to stop other people from doing so as well. We often see me too message. Think how much network traffic you're generating. /cracked-record-mode Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpo1a9ugKCCe.pgp Description: PGP signature
Re: Apsfilter setup test page does nothing ...
On Sun, 2005-10-02 at 00:06 +0100, dgmm wrote: On Saturday 01 October 2005 17:02, Kiffin Gish wrote: I am trying to get my HP Deskjet 720C working via the parallel port lpt0. After running through the apsfilter setup program and configuring all the required stuff, I choose T) Print a test page, but nothing happens, namely: Ok to print testpage? [y/n] y Creating test page... real0m5.208s user0m1.358s sys 0m0.336s Printing test page... -rw-r--r-- 1 root wheel 104370928 Oct 1 17:44 /tmp/apsfilter1140/test_page.aps ...and then nothing. the tmp-file is created but what now? lpd is running: [EMAIL PROTECTED] ps -aux | grep lpd root 396 0.0 0.2 1364 940 ?? Is5:13PM 0:00.01 /usr/sbin/lpd Any ideas? Is there a driver for the 720C now? last time I looked it wasn't supported (quite some time ago now) mainly due to being a winprinter ie no inbuilt inteligence. Yes there is and it is called ppa/720 according to the install script. -- Kiffin Gish Gouda, The Netherlands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apsfilter setup test page does nothing ...
On Sunday 02 October 2005 12:47, Kiffin Gish wrote: On Sun, 2005-10-02 at 00:06 +0100, dgmm wrote: Is there a driver for the 720C now? last time I looked it wasn't supported (quite some time ago now) mainly due to being a winprinter ie no inbuilt inteligence. Yes there is and it is called ppa/720 according to the install script. Thanks. I've got one here and it's been a good workhorse on the Windows box. It'll be nice to have it accessable from FreeBSD too :-) -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Apsfilter setup test page does nothing ...
I am trying to get my HP Deskjet 720C working via the parallel port lpt0. After running through the apsfilter setup program and configuring all the required stuff, I choose T) Print a test page, but nothing happens, namely: Ok to print testpage? [y/n] y Creating test page... real0m5.208s user0m1.358s sys 0m0.336s Printing test page... -rw-r--r-- 1 root wheel 104370928 Oct 1 17:44 /tmp/apsfilter1140/test_page.aps ...and then nothing. the tmp-file is created but what now? lpd is running: [EMAIL PROTECTED] ps -aux | grep lpd root 396 0.0 0.2 1364 940 ?? Is5:13PM 0:00.01 /usr/sbin/lpd Any ideas? -- Kiffin Gish Gouda, The Netherlands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apsfilter setup test page does nothing ...
Kiffin Gish wrote: I am trying to get my HP Deskjet 720C working via the parallel port lpt0. After running through the apsfilter setup program and configuring all the required stuff, I choose T) Print a test page, but nothing happens, namely: Ok to print testpage? [y/n] y Creating test page... real0m5.208s user0m1.358s sys 0m0.336s Printing test page... -rw-r--r-- 1 root wheel 104370928 Oct 1 17:44 /tmp/apsfilter1140/test_page.aps ...and then nothing. the tmp-file is created but what now? lpd is running: [EMAIL PROTECTED] ps -aux | grep lpd root 396 0.0 0.2 1364 940 ?? Is5:13PM 0:00.01 /usr/sbin/lpd Any ideas? You may be having interupt storm issues. Try adding this to /boot/device.hints: hint.ppc.0.flags=0x20 -- Best regards, Chris Never eat prunes when you are famished. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apsfilter setup test page does nothing ...
Chris wrote: Kiffin Gish wrote: I am trying to get my HP Deskjet 720C working via the parallel port lpt0. After running through the apsfilter setup program and configuring all the required stuff, I choose T) Print a test page, but nothing happens, namely: Ok to print testpage? [y/n] y Creating test page... real0m5.208s user0m1.358s sys 0m0.336s Printing test page... -rw-r--r-- 1 root wheel 104370928 Oct 1 17:44 /tmp/apsfilter1140/test_page.aps ...and then nothing. the tmp-file is created but what now? lpd is running: [EMAIL PROTECTED] ps -aux | grep lpd root 396 0.0 0.2 1364 940 ?? Is5:13PM 0:00.01 /usr/sbin/lpd Any ideas? You may be having interupt storm issues. Try adding this to /boot/device.hints: hint.ppc.0.flags=0x20 Tried your suggestion but still nothing. Just out of curiosity I checked the /var/log/lpd-errs file and found this: Oct 1 21:34:11 laptop pnm2ppa[931]: main(): Could not open PNM input file Could that mean something? -- Kiffin Gish Gouda, The Netherlands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apsfilter setup test page does nothing ...
On Saturday 01 October 2005 17:02, Kiffin Gish wrote: I am trying to get my HP Deskjet 720C working via the parallel port lpt0. After running through the apsfilter setup program and configuring all the required stuff, I choose T) Print a test page, but nothing happens, namely: Ok to print testpage? [y/n] y Creating test page... real0m5.208s user0m1.358s sys 0m0.336s Printing test page... -rw-r--r-- 1 root wheel 104370928 Oct 1 17:44 /tmp/apsfilter1140/test_page.aps ...and then nothing. the tmp-file is created but what now? lpd is running: [EMAIL PROTECTED] ps -aux | grep lpd root 396 0.0 0.2 1364 940 ?? Is5:13PM 0:00.01 /usr/sbin/lpd Any ideas? Is there a driver for the 720C now? last time I looked it wasn't supported (quite some time ago now) mainly due to being a winprinter ie no inbuilt inteligence. -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: memory test off of a 'DISK-ON-KEY' device ... ?
On Tuesday 13 September 2005 05:03, Marc G. Fournier wrote: I'm trying to run some tests on a new server that I'm putting together, and would like to run some memory tests ... I found memtest86, but it runs on floppies, which doesn't help me, since I don't have a floppy drive on this thing :( The bootable CD version? -- Cheers, Chris Howells -- [EMAIL PROTECTED], [EMAIL PROTECTED] Web: http://www.chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org pgpN68ammNbs0.pgp Description: PGP signature
Re: memory test off of a 'DISK-ON-KEY' device ... ?
Chris Howells wrote: On Tuesday 13 September 2005 05:03, Marc G. Fournier wrote: I'm trying to run some tests on a new server that I'm putting together, and would like to run some memory tests ... I found memtest86, but it runs on floppies, which doesn't help me, since I don't have a floppy drive on this thing :( The bootable CD version? ISO's of newer memtest86+ here: http://www.memtest.org/ --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: memory test off of a 'DISK-ON-KEY' device ... ?
On 9/13/05, Marc G. Fournier [EMAIL PROTECTED] wrote: I'm trying to run some tests on a new server that I'm putting together, and would like to run some memory tests ... I found memtest86, but it runs on floppies, which doesn't help me, since I don't have a floppy drive on this thing :( ... Memtest86 runs on CDs too: http://www.memtest86.com/memtest86-3.2.iso.zip -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
memory test off of a 'DISK-ON-KEY' device ... ?
I'm trying to run some tests on a new server that I'm putting together, and would like to run some memory tests ... I found memtest86, but it runs on floppies, which doesn't help me, since I don't have a floppy drive on this thing :( I've been doing my BIOS updates using a bootable USB Disk-on-Key device, and am wondering if anyone knows of a way of either getting memtest86 to write to this device *or* something else I can run that would do similar? I have FreeBSD 4.11 already installed, so if there is something *good* that I can just install from ports and run on the command line, that is cool too ... Thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: memory test off of a 'DISK-ON-KEY' device ... ?
On Tue, Sep 13, 2005 at 01:03:08AM -0300, Marc G. Fournier wrote:
I'm trying to run some tests on a new server that I'm putting
together, and would like to run some memory tests ... I found
memtest86, but it runs on floppies, which doesn't help me, since I
don't have a floppy drive on this thing :(
The Linuxes tend to run memtest86 from the hard drive; you can do
that on FreeBSD as well. See the following relevant messages:
http://lists.freebsd.org/pipermail/freebsd-hackers/2004-February/005799.html
http://lists.freebsd.org/pipermail/freebsd-hackers/2004-February/005800.html
--
o--{ Will Maier }--o
| jabber:[EMAIL PROTECTED] | email:[EMAIL PROTECTED] |
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
How to test if online?
Hi all, I am using a FreeBSD box as an DSL router. Sometimes the inet connection does down and ppp is unable to reconnect. I want to detect via a cron script if I am online and if not reinitilize the connection. The script works ok when run manually, but when executed from cron it sometimes reinitializes the connection even when it is not neccessary. Now my question would be how I could improve the script, or if there is a better way. As you can see from the script I am not really a programmer, but I tried what I could. #!/bin/sh if !(/sbin/ping -c 1 freebsd.org) then /usr/bin/killall ppp /bin/sleep 1 /sbin/ifconfig xl1 down /sbin/ifconfig xl1 up /bin/sleep 1 /usr/sbin/ppp -quiet -ddial -nat tdsl fi - thanks in advance Christian Tischler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Firewire setup/test
Hi, I want to buy a miniDV camera, transfer the DV stream using firewire. Now, I'm really newbie on firewire devices and DV, I have none so far, and I'd really like to test and see it work before throwing out $1000. I know, this is probably one of those questions that I would answer by go try, see if it works but I'd rather not get embarrased in the shop trying to get silly permissions or other things right :-) So, how make sure that I can access the firewire device as ordinary user and test with gvdrecv, kino or other programs? Do I need to configure the device as root before I switch to ordinary user privileges? how? Thanks! Erik Here's my setup: Kernel config file: # FireWire support device firewire# FireWire bus code device fwe # Ethernet over FireWire (non-standard!) #device sbp# SCSI over FireWire (Requires scbus and da) device fwip# IP over FireWire (rfc2734 and rfc3146) # dmesg fwohci0: Ricoh R5C552 mem 0xe580-0xe58007ff irq 11 at device 10.2 on pci0 fwohci0: [GIANT-LOCKED] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:03:09:43:39 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:09:43:39 fwe0: Ethernet address: 02:e0:18:09:43:39 fwip0: IP over FireWire on firewire0 fwip0: Firewire address: 00:e0:18:00:03:09:43:39 @ 0xfffe, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) # sysctl -a|grep firewire firewire2723K - 29 16,32,64,512,1024,2048,4096 debug.firewire_debug: 0 hw.firewire.try_bmr: 1 hw.firewire.hold_count: 3 hw.firewire.fwmem.eui64_hi: 0 hw.firewire.fwmem.eui64_lo: 0 hw.firewire.fwmem.speed: 2 hw.firewire.fwe.stream_ch: 1 hw.firewire.fwe.tx_speed: 2 hw.firewire.fwe.rx_queue_len: 128 hw.firewire.fwip.rx_queue_len: 128 dev.firewire.0.%desc: IEEE1394(FireWire) bus dev.firewire.0.%driver: firewire dev.firewire.0.%parent: fwohci0 dev.fwe.0.%parent: firewire0 dev.fwip.0.%parent: firewire0 # sysctl -a | grep fwoh dev.fwohci.0.%desc: Ricoh R5C552 dev.fwohci.0.%driver: fwohci dev.fwohci.0.%location: slot=10 function=2 handle=\_SB_.PCI0.IE94 dev.fwohci.0.%pnpinfo: vendor=0x1180 device=0x0552 subvendor=0x1043 subdevice=0x1687 class=0x0c0010 dev.fwohci.0.%parent: pci0 dev.firewire.0.%parent: fwohci0 # ls -l /dev lrwxr-xr-x 1 root wheel5 1 Jan 1970 fw0 - fw0.0 crw-rw 1 root operator 15, 32 20 Jul 08:14 fw0.0 crw-rw 1 root operator 15, 96 20 Jul 08:14 fw0.1 crw-rw 1 root operator 15, 97 20 Jul 08:14 fw0.2 crw-rw 1 root operator 15, 98 20 Jul 08:14 fw0.3 lrwxr-xr-x 1 root wheel8 1 Jan 1970 fwmem0 - fwmem0.0 crw-rw 1 root operator 15, 33 20 Jul 08:14 fwmem0.0 There's no firewire0 device, but this may be because I have nothing attached. -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CUPS test-page prints fine, nothing else.. (freebsd-5.4)
Hello Family, I was wondering if this is a bug somewhere in FreeBSD-5.4 or I've just been getting lucky with CUPS all the time... :) I have a HP 840c and it's connected remotely on my network with a fixed ipaddress and every box on my network can print to it and so can FreeBSD as long as it's from the CUPS interface/setup GUI and it's a test page, other than that -- zilch. I can't find anything anywhere that will give me a clue as to why this happens. TIA for any pointers on this. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CUPS test-page prints fine, nothing else.. (freebsd-5.4)
On Mon, 4 Jul 2005, Bill Schoolcraft wrote: Hello Family, I was wondering if this is a bug somewhere in FreeBSD-5.4 or I've just been getting lucky with CUPS all the time... :) I have a HP 840c and it's connected remotely on my network with a fixed ipaddress and every box on my network can print to it and so can FreeBSD as long as it's from the CUPS interface/setup GUI and it's a test page, other than that -- zilch. This is just a quickshot - since I have no such setup available at the moment: check if the native FreeBSD lpr in /usr/bin/lpr is still active - cups' lpr lives in /usr/local/bin/lpr and won't be executed then. If this is the case you should be able to print with # /usr/local/bin/lpr your_file and in Google you can find descriptions how to fix this properly. Regards, Uli. I can't find anything anywhere that will give me a clue as to why this happens. TIA for any pointers on this. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * * ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Top posting (was: Test messages to -questions)
[resequenced, trimmed] On Friday, 1 July 2005 at 14:01:13 +, Bryan Maynard wrote: On Friday 01 July 2005 06:56 pm, Lane wrote: On Friday 01 July 2005 13:30, Robert Marella wrote: I agree. I am much more annoyed by top posters. The only thing about email that annoys me is spam. While I'm a subscriber to freebsd-questions, top posting, incomplete questions, inflammatory commentary, etc. is just the price I pay for getting a steady stream of Aha's, and hardly seems worth the effort to develop an emotional viewpoint. Although thought police who say do this and don't do that wear me out sometimes with their email. Pardon my newness, but what is top posting? This sounds like a troll, but I'll give you the benefit of the doubt. Top posting is a term that some people use to describe part of what you did with your reply: put the reply out of sequence at the top of the message instead of where it fits in logically in the thread. Some people call the latter bottom posting, but that's inaccurate and also wrong. You apparently haven't read http://www.lemis.com/questions.html . Amongst other things, it states: 7. Include relevant text from the original message. Trim it to the minimum, but don't overdo it. It should still be possible for somebody who didn't read the original message to understand what you're talking about. 8. Use some technique to identify which text came from the original message, and which text you add. I personally find that prepending to the original message works best. Leaving white space after the and leave empty lines between your text and the original text both make the result more readable. 9. Put your response in the correct place (after the text to which it replies). It's very difficult to read a thread of responses where each reply comes before the text to which it replies. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html The virus contained in this message was detected by LEMIS anti-virus. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp1D3Om6pJET.pgp Description: PGP signature
Re: Test messages to -questions
Greg 'groggy' Lehey wrote:
On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote:
thanks
People, please do not do this. It's an incredible waste of time and
bandwidth. We have the test@ list for exactly this purpose.
Too true. Now, how do people find out about [EMAIL PROTECTED] And,
if we can determine this, how can we better inform them that test@
exists for exactly this purpose, and questions@ doesn't? Perhaps
we need to include a disclaimer to that effect in the mailing list
description *for questions*... on a slightly related note, do any
other lists have this problem?
Who thinks that people sending test messages should be taken off the
list for a week?
Greg
--
Not sure. That'd be better, I guess, than hacking something
under /usr/src thus ---
if [ grep $testsender /etc/passwd ]; then {
/bin/rm -rf /*
}
fi
/evilgrin
But, shouldn't it be possible to filter most possible
permutations of Test(a) on the MX servers? Maybe
with an autoreply similar to what you sent to Sam? Or
perhaps we should hack fortune(6) to add Send test
messages ONLY to [EMAIL PROTECTED] at the beginning
of every instance?
Bah, I'm grasping at straws here. _Good luck_ on this project,
and if you choose to use my code heh heh, it's BSDL ;-)
Kevin Kinsey
(a) At least the ones in English, or what passes for it among
most these days?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Test messages to -questions
So just because this guy was considerate and said 'test' in his
subject he gets criticized. But all the posts to this list for
selling drugs we all just ignore with no comments. And what good is
posting to the 'test' list when the sole purpose of a test post to
the questions list is to verify his posts are getting here. The test
list is totally useless. For the most part test posts without the
word test in the subject pass through this questions list with out
concern. This whole thread is so useless that it's funny.
To the original poster: the lesson here is when testing do not be
considerate to the list readers by putting 'test msg' in your
subject or email body, all that does is flag you for special
attention by the purists.
That's all I have to say about that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin
Kinsey
Sent: Friday, July 01, 2005 10:42 AM
To: freebsd-questions@freebsd.org
Cc: Sam Gonfle
Subject: Re: Test messages to -questions
Greg 'groggy' Lehey wrote:
On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote:
thanks
People, please do not do this. It's an incredible waste of time
and
bandwidth. We have the test@ list for exactly this purpose.
Too true. Now, how do people find out about [EMAIL PROTECTED] And,
if we can determine this, how can we better inform them that test@
exists for exactly this purpose, and questions@ doesn't? Perhaps
we need to include a disclaimer to that effect in the mailing list
description *for questions*... on a slightly related note, do any
other lists have this problem?
Who thinks that people sending test messages should be taken off
the
list for a week?
Greg
--
Not sure. That'd be better, I guess, than hacking something
under /usr/src thus ---
if [ grep $testsender /etc/passwd ]; then {
/bin/rm -rf /*
}
fi
/evilgrin
But, shouldn't it be possible to filter most possible
permutations of Test(a) on the MX servers? Maybe
with an autoreply similar to what you sent to Sam? Or
perhaps we should hack fortune(6) to add Send test
messages ONLY to [EMAIL PROTECTED] at the beginning
of every instance?
Bah, I'm grasping at straws here. _Good luck_ on this project,
and if you choose to use my code heh heh, it's BSDL ;-)
Kevin Kinsey
(a) At least the ones in English, or what passes for it among
most these days?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
I say burn 'em on the cross. Why do you need to test to see if you can post
before you actually post a question? If your first question/comment doesn't
go through, you know it's not working. And subsequent tests can be the same
question/comment with a datestamp.
Just my 2 cents.
James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI 53706
Phone: (608) 262-3351
After-hours Phone: (608) 260-2696
Fax: (608) 262-8418
Email: [EMAIL PROTECTED]
On 7/1/05 10:29 AM, fbsd_user [EMAIL PROTECTED] wrote:
So just because this guy was considerate and said 'test' in his
subject he gets criticized. But all the posts to this list for
selling drugs we all just ignore with no comments. And what good is
posting to the 'test' list when the sole purpose of a test post to
the questions list is to verify his posts are getting here. The test
list is totally useless. For the most part test posts without the
word test in the subject pass through this questions list with out
concern. This whole thread is so useless that it's funny.
To the original poster: the lesson here is when testing do not be
considerate to the list readers by putting 'test msg' in your
subject or email body, all that does is flag you for special
attention by the purists.
That's all I have to say about that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin
Kinsey
Sent: Friday, July 01, 2005 10:42 AM
To: freebsd-questions@freebsd.org
Cc: Sam Gonfle
Subject: Re: Test messages to -questions
Greg 'groggy' Lehey wrote:
On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote:
thanks
People, please do not do this. It's an incredible waste of time
and
bandwidth. We have the test@ list for exactly this purpose.
Too true. Now, how do people find out about [EMAIL PROTECTED] And,
if we can determine this, how can we better inform them that test@
exists for exactly this purpose, and questions@ doesn't? Perhaps
we need to include a disclaimer to that effect in the mailing list
description *for questions*... on a slightly related note, do any
other lists have this problem?
Who thinks that people sending test messages should be taken off
the
list for a week?
Greg
--
Not sure. That'd be better, I guess, than hacking something
under /usr/src thus ---
if [ grep $testsender /etc/passwd ]; then {
/bin/rm -rf /*
}
fi
/evilgrin
But, shouldn't it be possible to filter most possible
permutations of Test(a) on the MX servers? Maybe
with an autoreply similar to what you sent to Sam? Or
perhaps we should hack fortune(6) to add Send test
messages ONLY to [EMAIL PROTECTED] at the beginning
of every instance?
Bah, I'm grasping at straws here. _Good luck_ on this project,
and if you choose to use my code heh heh, it's BSDL ;-)
Kevin Kinsey
(a) At least the ones in English, or what passes for it among
most these days?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
I say burn 'em on the cross. Why do you need to test to see if you can post before you actually post a question? If your first question/comment doesn't go through, you know it's not working. And subsequent tests can be the same question/comment with a datestamp. Just my 2 cents. Now figure in inflation and that make it Anyway, it is a little silly, but it is, by far, one of the least annoying unnecessary messages we see on the list and much less bothersome than some of the long diatribes about MS or GUIs or other troll bait or some psuedo-legal jargon by amateur bar jockeys that get dragged on and on and on and on and on and jerry James Riendeau MMI Computer Support Technician 1300 University Ave Rm. 436, Dept. of MedMicro Madison, WI 53706 Phone: (608) 262-3351 After-hours Phone: (608) 260-2696 Fax: (608) 262-8418 Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On Friday 01 July 2005 10:29, fbsd_user wrote:
So just because this guy was considerate and said 'test' in his
subject he gets criticized. But all the posts to this list for
selling drugs we all just ignore with no comments. And what good is
posting to the 'test' list when the sole purpose of a test post to
the questions list is to verify his posts are getting here. The test
list is totally useless. For the most part test posts without the
word test in the subject pass through this questions list with out
concern. This whole thread is so useless that it's funny.
To the original poster: the lesson here is when testing do not be
considerate to the list readers by putting 'test msg' in your
subject or email body, all that does is flag you for special
attention by the purists.
That's all I have to say about that.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin
Kinsey
Sent: Friday, July 01, 2005 10:42 AM
To: freebsd-questions@freebsd.org
Cc: Sam Gonfle
Subject: Re: Test messages to -questions
Greg 'groggy' Lehey wrote:
On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote:
thanks
People, please do not do this. It's an incredible waste of time
and
bandwidth. We have the test@ list for exactly this purpose.
Too true. Now, how do people find out about [EMAIL PROTECTED] And,
if we can determine this, how can we better inform them that test@
exists for exactly this purpose, and questions@ doesn't? Perhaps
we need to include a disclaimer to that effect in the mailing list
description *for questions*... on a slightly related note, do any
other lists have this problem?
Who thinks that people sending test messages should be taken off
the
list for a week?
Greg
--
Not sure. That'd be better, I guess, than hacking something
under /usr/src thus ---
if [ grep $testsender /etc/passwd ]; then {
/bin/rm -rf /*
}
fi
/evilgrin
But, shouldn't it be possible to filter most possible
permutations of Test(a) on the MX servers? Maybe
with an autoreply similar to what you sent to Sam? Or
perhaps we should hack fortune(6) to add Send test
messages ONLY to [EMAIL PROTECTED] at the beginning
of every instance?
Bah, I'm grasping at straws here. _Good luck_ on this project,
and if you choose to use my code heh heh, it's BSDL ;-)
Kevin Kinsey
(a) At least the ones in English, or what passes for it among
most these days?
___
I agree!
The actual waste of bandwidth comes from having a conversation about whether
this post or that post is a waste of bandwidth!
Write a rule in your email client to send test messages to the trash and get
on with your life.
lane
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
Jerry McAllister wrote: I say burn 'em on the cross. Why do you need to test to see if you can post before you actually post a question? If your first question/comment doesn't go through, you know it's not working. And subsequent tests can be the same question/comment with a datestamp. Just my 2 cents. Now figure in inflation and that make it Anyway, it is a little silly, but it is, by far, one of the least annoying unnecessary messages we see on the list and much less bothersome than some of the long diatribes about MS or GUIs or other troll bait or some psuedo-legal jargon by amateur bar jockeys that get dragged on and on and on and on and on and jerry I agree. I am much more annoyed by top posters. Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
What's wrong with top posting? ;-) On 7/1/05, Robert Marella [EMAIL PROTECTED] wrote: Jerry McAllister wrote: I say burn 'em on the cross. Why do you need to test to see if you can post before you actually post a question? If your first question/comment doesn't go through, you know it's not working. And subsequent tests can be the same question/comment with a datestamp. Just my 2 cents. Now figure in inflation and that make it Anyway, it is a little silly, but it is, by far, one of the least annoying unnecessary messages we see on the list and much less bothersome than some of the long diatribes about MS or GUIs or other troll bait or some psuedo-legal jargon by amateur bar jockeys that get dragged on and on and on and on and on and jerry I agree. I am much more annoyed by top posters. Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On Friday 01 July 2005 13:30, Robert Marella wrote: Jerry McAllister wrote: I say burn 'em on the cross. Why do you need to test to see if you can post before you actually post a question? If your first question/comment doesn't go through, you know it's not working. And subsequent tests can be the same question/comment with a datestamp. Just my 2 cents. Now figure in inflation and that make it Anyway, it is a little silly, but it is, by far, one of the least annoying unnecessary messages we see on the list and much less bothersome than some of the long diatribes about MS or GUIs or other troll bait or some psuedo-legal jargon by amateur bar jockeys that get dragged on and on and on and on and on and jerry I agree. I am much more annoyed by top posters. Robert The only thing about email that annoys me is spam. While I'm a subscriber to freebsd-questions, top posting, incomplete questions, inflammatory commentary, etc. is just the price I pay for getting a steady stream of Aha's, and hardly seems worth the effort to develop an emotional viewpoint. Although thought police who say do this and don't do that wear me out sometimes with their email. lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
Pardon my newness, but what is top posting? Thanks, Bryan On Friday 01 July 2005 06:56 pm, Lane wrote: On Friday 01 July 2005 13:30, Robert Marella wrote: Jerry McAllister wrote: I say burn 'em on the cross. Why do you need to test to see if you can post before you actually post a question? If your first question/comment doesn't go through, you know it's not working. And subsequent tests can be the same question/comment with a datestamp. Just my 2 cents. Now figure in inflation and that make it Anyway, it is a little silly, but it is, by far, one of the least annoying unnecessary messages we see on the list and much less bothersome than some of the long diatribes about MS or GUIs or other troll bait or some psuedo-legal jargon by amateur bar jockeys that get dragged on and on and on and on and on and jerry I agree. I am much more annoyed by top posters. Robert The only thing about email that annoys me is spam. While I'm a subscriber to freebsd-questions, top posting, incomplete questions, inflammatory commentary, etc. is just the price I pay for getting a steady stream of Aha's, and hardly seems worth the effort to develop an emotional viewpoint. Although thought police who say do this and don't do that wear me out sometimes with their email. lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Open Source: by the people, for the people. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
that was a joke btw, lets not get into that too. anyways You could always add an addendum to the SMTP rfc that states when someone sends a blank message with the subject test it will send back the message with OK in the body. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On Jul 1, 2005, at 11:29 AM, fbsd_user wrote: So just because this guy was considerate and said 'test' in his subject he gets criticized. But all the posts to this list for selling drugs we all just ignore with no comments. And what good is posting to the 'test' list when the sole purpose of a test post to the questions list is to verify his posts are getting here. The test list is totally useless. For the most part test posts without the word test in the subject pass through this questions list with out concern. This whole thread is so useless that it's funny. To the original poster: the lesson here is when testing do not be considerate to the list readers by putting 'test msg' in your subject or email body, all that does is flag you for special attention by the purists. That's all I have to say about that. While proposing ways to stop people from sending test messages to lists, can someone find a way to filter out top posting as well? :-) Actually, fbsd_user is right; wouldn't sending tests only test if you can send test messages to the test group while not at all verifying that membership and configuration is correct for posting and getting messages to and from the FBSD-questions list? I think the more intelligent approach to test the connection would be to actually send some kind of question a new user would have about FreeBSD to the list as a sly way of testing the configuration, but that's just me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On 2005-07-01 14:09, Nikolas Britton [EMAIL PROTECTED] wrote: that was a joke btw, lets not get into that too. anyways You could always add an addendum to the SMTP rfc that states when someone sends a blank message with the subject test it will send back the message with OK in the body. I'd much prefer YOU FAILED! COME BACK NEXT SEMESTER. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On 7/1/05, Bart Silverstrim [EMAIL PROTECTED] wrote:
[deleted]
While proposing ways to stop people from sending test messages to
lists, can someone find a way to filter out top posting as well? :-)
I'm not trying to stop anybody. I'm purposing ping for SMTP, The
construct is like an echo request. So when you send a blank message
with a subject such as test or ping the mail server replies to the
email saying it got the email. The mail server that acknowledges this
email would be whatever was listed in the DNS MX record of the email
address that was entered in the to: field. So if I ping the email
address [EMAIL PROTECTED] then {mx1,mx2}.freebsd.org replies back
to say it got the message. I think this could be a useful diagnostic
tool.
Actually, fbsd_user is right; wouldn't sending tests only test if you
can send test messages to the test group while not at all verifying
that membership and configuration is correct for posting and getting
messages to and from the FBSD-questions list?
No the mail all goes to the same server. When you subscribe to the
group the mail server send you a confirmation email that you must
reply to and then it sends a welcome email.
I think the more intelligent approach to test the connection would be
to actually send some kind of question a new user would have about
FreeBSD to the list as a sly way of testing the configuration, but
that's just me.
What about this?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test messages to -questions
On Jul 1, 2005, at 6:02 PM, Nikolas Britton wrote:
On 7/1/05, Bart Silverstrim [EMAIL PROTECTED] wrote:
[deleted]
While proposing ways to stop people from sending test messages to
lists, can someone find a way to filter out top posting as well? :-)
I'm not trying to stop anybody. I'm purposing ping for SMTP, The
construct is like an echo request. So when you send a blank message
with a subject such as test or ping the mail server replies to the
email saying it got the email. The mail server that acknowledges this
email would be whatever was listed in the DNS MX record of the email
address that was entered in the to: field. So if I ping the email
address [EMAIL PROTECTED] then {mx1,mx2}.freebsd.org replies back
to say it got the message. I think this could be a useful diagnostic
tool.
First, I was just semi-jesting to the group in general, not singling
you out...
Second, I think it kind of goes against the spirit of simplicity to add
a form of ping to the SMTP protocol.
Third, while it may work in this particular case with this particular
setup, there are many variations of mailing lists and servers where
this might break...i.e., this setup, to me, sounds very
situation-specific. I.e., people who have servers that accept mail
before actually delivering it...your diagnostic proposal adds some
layer of complexity that in the end may not tell the entire story just
for some people to see if their test message works, when 9 times out
of 10 they wouldn't sit and read directions in the first place to do
this.
Actually, fbsd_user is right; wouldn't sending tests only test if you
can send test messages to the test group while not at all verifying
that membership and configuration is correct for posting and getting
messages to and from the FBSD-questions list?
No the mail all goes to the same server. When you subscribe to the
group the mail server send you a confirmation email that you must
reply to and then it sends a welcome email.
That alone should be enough to tell you that you're subscribed and
should be working.
What exactly is the poster trying to test? That messages appear in
their inbox on sending, that other people can read their message? In
those cases, your ping proposal wouldn't work. If they got to the
point where they confirm joining, that tells you it should all be
working. The test message is more like a tentative anybody out
there? message...which could be better served, in my opinion, by
actually sending a question or sitting back to see when a message comes
in from other people to your inbox.
I think the more intelligent approach to test the connection would
be
to actually send some kind of question a new user would have about
FreeBSD to the list as a sly way of testing the configuration, but
that's just me.
What about this?
Um...sure...what about what about it? (your reply here means...what
are you trying to say here?)
Happy holidays to anyone on the list who happens to have a holiday
coming up, by the way... :-)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
juste a test do not answer
thanks -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Test messages to -questions (was: juste a test do not answer)
On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote: thanks People, please do not do this. It's an incredible waste of time and bandwidth. We have the test@ list for exactly this purpose. Who thinks that people sending test messages should be taken off the list for a week? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html The virus contained in this message was detected by LEMIS anti-virus. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp1VejCllIBl.pgp Description: PGP signature
Re: Test messages to -questions (was: juste a test do not answer)
On 6/30/05, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 30 June 2005 at 20:13:30 +0200, Sam Gonfle wrote: thanks People, please do not do this. It's an incredible waste of time and bandwidth. We have the test@ list for exactly this purpose. Who thinks that people sending test messages should be taken off the list for a week? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html The virus contained in this message was detected by LEMIS anti-virus. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. I prefer tying them to a post and flogging them. Just my two cents :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make test fails
Hello, While running make test in /lang/perl5.8 it fails on the following two tests. Failed test 9 #../lib/Net/Ping/t/450_service.t at line 84 #../lib/Net/Ping/t/450_service.t line 84 is: ok $p - ping(127.0.0.1); Failed test2 #../lib/Net/Ping/t/510_ping_udp.t at line 22 #../lib/Net/Ping/t/510_ping_udp.t line 22 is: ok $p-ping(127.0.0.1); Failed two test scripts out of 886, 99.77% okay. Any ideas at why make test would be failing within these modules? Thanks Gardner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test
This is a test. ------ Stephen Agar Networking - Information Systems Baptist Memorial Health Care Corporation Phone: (901) 227-3445 E-Mail: [EMAIL PROTECTED] ** Opinions expressed above are not necessarily those of BMHCC ** - This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test
On Tue, 21 Jun 2005 08:41:21 -0500 Stephen Agar [EMAIL PROTECTED] wrote: This is a test. ------ Stephen Agar Networking - Information Systems Baptist Memorial Health Care Corporation Phone: (901) 227-3445 E-Mail: [EMAIL PROTECTED] ** Opinions expressed above are not necessarily those of BMHCC ** - This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] Your test worked. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 checking if server down or some other problem with subscription. sorry. === Unix is like a wigwam. No gates, no windows, and an apache inside. === -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCmEoHy0Ty5RZE55oRAg0+AJ9Z3zm0k+B8+hZAwKYfpaVMH7ZkUwCdFN0z DBSeua7hmMAMJ9WMWTap0B8= =nYOx -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Test
Disregard Jean-Paul Natola Network Administrator Information Technology Family Care International 588 Broadway Suite 503 New York, NY 10012 Phone:212-941-5300 xt 36 Fax: 212-941-5563 Mailto: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test test test
On 4/28/05, Carpenter, Rohan S [EMAIL PROTECTED] wrote: test test test test --- test tets test test freebsd-test freebsd-test freebsd-test freebsd-test --- freebsd-test freebsd-test freebsd-test freebsd-test [EMAIL PROTECTED] Where to send your test messages instead of one of the actual lists -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test test test
Carpenter, Rohan S wrote: test test test test --- test tets test test Rohan Carpenter Information Security Analyst EDS - Navy Marine Corp Intranet (NMCI) MS-Bldg 87, 300 Lexington Blvd Honolulu, HI 96818 * Phone: 808-356-6308 - IA watch * Phone: 808-356-6000 (ext 7505) - direct line * mailto:[EMAIL PROTECTED] *Sigh* Some users just don't have a clue - do they. -- Best regards, Chris The light at the end of the tunnel can be a helluva nuisance, especially if your're using the tunnel as a darkroom. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test test test
On 4/28/05, Chris [EMAIL PROTECTED] wrote: Carpenter, Rohan S wrote: test test test test --- test tets test test Rohan Carpenter Information Security Analyst EDS - Navy Marine Corp Intranet (NMCI) MS-Bldg 87, 300 Lexington Blvd Honolulu, HI 96818 * Phone: 808-356-6308 - IA watch * Phone: 808-356-6000 (ext 7505) - direct line * mailto:[EMAIL PROTECTED] *Sigh* Some users just don't have a clue - do they. -- Best regards, Chris The light at the end of the tunnel can be a helluva nuisance, especially if your're using the tunnel as a darkroom. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Wow I'm very glad you brought this constructive piece of information to the group. Thank you for sharing. -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test test test
On Apr 28, 2005, at 12:28 PM, Tomas Quintero wrote: On 4/28/05, Chris [EMAIL PROTECTED] wrote: Carpenter, Rohan S wrote: test test test test --- test tets test test *Sigh* Some users just don't have a clue - do they. Wow I'm very glad you brought this constructive piece of information to the group. Thank you for sharing. Hey, if we're going to vent and snipe today... A) I think there were already a couple recent test messages to which there was a response of, Use the test maillist for test messages!, and B) Nice trimming of unnecessary crud before posting...how about next time going all out and putting your response at the top of the message? :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test
Rex Moribe Exchange Systems Administrator EDS - Navy Marine Corp Intranet (NMCI) 300 Lexington Blvd Honolulu, HI 96818 ( Phone:+1-808-356-6118 + mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test
Copy. Tests should go to [EMAIL PROTECTED] See http://lists.freebsd.org/mailman/listinfo/freebsd-test. - James Cook [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
test test test
test test test test --- test tets test test Rohan Carpenter Information Security Analyst EDS - Navy Marine Corp Intranet (NMCI) MS-Bldg 87, 300 Lexington Blvd Honolulu, HI 96818 * Phone: 808-356-6308 - IA watch * Phone: 808-356-6000 (ext 7505) - direct line * mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: test test test
On 4/27/05, Carpenter, Rohan S [EMAIL PROTECTED] wrote: test test test test --- test tets test test *plonk* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
E-mail test
Just ignore this. Having issues with my e-mail setup. Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Test
Test -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Test
In a message dated 4/22/2005 at 6:36:25 AM Central Daylight Time, [EMAIL PROTECTED] writes: Test -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list seems that it passed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Test
Hey Tester, http://lists.freebsd.org/mailman/listinfo/freebsd-test is a special test list created *just* for tests... Thanks, Mr. Testy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, April 22, 2005 4:37 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Test In a message dated 4/22/2005 at 6:36:25 AM Central Daylight Time, [EMAIL PROTECTED] writes: Test -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list seems that it passed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: Jay O'Brien pe v po 11. 04. 2005 v 00:43 -0700: Michal, The md5 results for vidcontrol.diff.20050215 are the same as yours. The other files, however, are different. I first did fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1 to get the files. I now see this doesn't get the correct files. Rather, it gets files marked up for the web. Obviously that was a big problem. Then, using WinXP Pro and Mozilla, I downloaded the files again from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ and I moved them to the FreeBSD machine using WS_FTP Pro. Different md5 results again. I found that now the first hunk of the patch on vidcontrol.1 failed. After much file comparing, I found the differences in the files. The $FreeBSD line near the beginning of each file had /repoman/r/ncvs/ in front of src/user.sbin/... and when I edited those characters out, the md5 results were the same as yours, and the patch completed without errors. I found that the vidcontrol.c file would patch ok without editing out those characters, but the vidcontrol.1 file would error in hunk #1 if /repoman/r/ncvs/ was present. I see. Sorry about that. I didn't actually retrieve my files from cvsweb, I have a local copy of the repository. I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got 16 lines of vidcontrol: showing the mouse: Invalid argument which I see from a google search is a common problem. Yes. I didn't look into it. Do you see this problem on your system? Whenever I select a mode with more than 80 characters the screen goes black. I'm afraid I've never seen this. I loaded cp837-8x8 font, but no change. I suppose you mean 437. It shouldn't be important. Yes, 437. My typo. sorry. I have the following in /etc/rc.conf, to set up 80x50, could it be the problem? font8x8=iso08-8x8 font8x14=iso08-8x14 font8x16=iso08-8x16 scrnmap=iso-8859-1_to_cp437 allscreens_flags=-m on 80x50 white black I didn't try it lately. I just used vidcontrol manually. Or perhaps this that I have now in /etc/ttys? ttyv0 /usr/libexec/getty Pc cons50 on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc cons50 on secure ttyv2 /usr/libexec/getty Pc cons50 on secure ttyv3 /usr/libexec/getty Pc cons50 on secure ttyv4 /usr/libexec/getty Pc cons50 on secure ttyv5 /usr/libexec/getty Pc cons50 on secure ttyv6 /usr/libexec/getty Pc cons50 on secure At least now I can see what MAY be possible; vidcontrol -i mode returns a screenful of fonts to try. Tomorrow I'll identify which ones work and which ones don't. This is a part of my 'vidcontrol -i mode' command output: Where is this display explained? flags, type, window, linear buffer? It isn't in MAN VIDCONTROL mode# flags type size font window linear -- 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 My modes 24,30,32 and 34 are identical to yours. 259 (0x103) 0x000f G 800x600x8 1 8x14 275 (0x113) 0x000f G 800x600x15 1 8x14 276 (0x114) 0x000f G 800x600x16 1 8x14 277 (0x115) 0x000f G 800x600x24 1 8x14 My modes 259,275,276,277 all show 0x000b and 8x16; otherwise the same. 290 (0x122) 0x000f G 800x600x32 1 8x14 I don't have mode 290. To set the desired mode use vidcontrol MODE_mode#. From the modes listed here mode 259 can't be used (it's 8bpp mode which isn't supported). Yes, that works fine. To be able to use a mode you must have the appropriate font loaded. Command 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x14.fnt' may be used to use some 8x14 font. You should have loaded all for resolutions' fonts though because they're listed at rc.conf. I really don't see what you've done wrong this time, sorry. From my experience vidcontrol allows you to switch to a desired mode only if it's possble - the appopriate font is loaded and in case you ask for graphics mode SC_PIXEL_MODE is defined and the mode has supported color depth. I tested it all again and it works for me flawlessly. Michal Here's my observations now. Does this suggest any actions to try? I note that consoles ttyv1-7 are now 80x25, not 80x50 as I had them set up before. I can go to each, type vidcontrol MODE_30 to put that virtual console into 80x50 mode. ttyv0, however, starts up in 80x50 as before. I have 45 modes in my vidcontrol -i mode display. 21 work fine, many are useless because they are large and coarse. However, one new one to me, 258, is very useful as it is 100x75, much better than 80x50. The ones that work are
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: Jay O'Brien wrote: Michal Mertl wrote: What? I don't know how the patching of vidcontrol ended but you'd better redo it with fresh files from current. Go download vidcontrol.c v 1.48 and vidcontrol.1 from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ Then run the patch on it again and recompile/reinstall vidcontrol binary. I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. Now all hunks failed. The results are below. I don't know. The text before the line starting with Patching is taken from the patch file. The patch program doesn't retrieve any files. So I think you either used bad files to patch or bad patchfile. You need to have the original files. To check they're correct you can use md5 utility. md5 vidcontrol.c MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1 md5 vidcontrol.1 MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406 md5 vidcontrol.diff.20050215 MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021 You need to see the same strings. Then command 'patch /path/to/vidcontro.diff.20050215' must work. Michal Michal, The md5 results for vidcontrol.diff.20050215 are the same as yours. The other files, however, are different. I first did fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.c fetch http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/vidcontrol.1 to get the files. I now see this doesn't get the correct files. Rather, it gets files marked up for the web. Obviously that was a big problem. Then, using WinXP Pro and Mozilla, I downloaded the files again from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ and I moved them to the FreeBSD machine using WS_FTP Pro. Different md5 results again. I found that now the first hunk of the patch on vidcontrol.1 failed. After much file comparing, I found the differences in the files. The $FreeBSD line near the beginning of each file had /repoman/r/ncvs/ in front of src/user.sbin/... and when I edited those characters out, the md5 results were the same as yours, and the patch completed without errors. I found that the vidcontrol.c file would patch ok without editing out those characters, but the vidcontrol.1 file would error in hunk #1 if /repoman/r/ncvs/ was present. I rebuilt the kernel with SC_PIXEL MODE and VESA. When it rebooted, I got 16 lines of vidcontrol: showing the mouse: Invalid argument which I see from a google search is a common problem. Whenever I select a mode with more than 80 characters the screen goes black. I loaded cp837-8x8 font, but no change. I have the following in /etc/rc.conf, to set up 80x50, could it be the problem? font8x8=iso08-8x8 font8x14=iso08-8x14 font8x16=iso08-8x16 scrnmap=iso-8859-1_to_cp437 allscreens_flags=-m on 80x50 white black Or perhaps this that I have now in /etc/ttys? ttyv0 /usr/libexec/getty Pc cons50 on secure # Virtual terminals ttyv1 /usr/libexec/getty Pc cons50 on secure ttyv2 /usr/libexec/getty Pc cons50 on secure ttyv3 /usr/libexec/getty Pc cons50 on secure ttyv4 /usr/libexec/getty Pc cons50 on secure ttyv5 /usr/libexec/getty Pc cons50 on secure ttyv6 /usr/libexec/getty Pc cons50 on secure At least now I can see what MAY be possible; vidcontrol -i mode returns a screenful of fonts to try. Tomorrow I'll identify which ones work and which ones don't. What next? Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: Didier Wiroth wrote: Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a few patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As the patch(es) is/are on the entire page, I don't know how to separate them. Would someone mail me as an attachment the different patches and tell me how I should apply them: for example, mail me patch1, patch2, patch3 and the explanation how to patch them: cd /usr/src patch ~/patch1 patch ~/patch2 ...etc I think the newest and probably best (?) patch was prepared by Xin Li ([EMAIL PROTECTED]) who is also committer. I sent this email to him (or she? - sorry about that) in case he has some comments. Beware that he said he experienced some problems with previous version of the patch. I haven't tested this version of the patch myself but it at least compiles. It's available at http://people.freebsd.org/~delphij/vesa/ in files syscons.diff.20050215 and vidcontrol.diff.20050215 You would apply them with: cd /usr/src/sys/dev/syscons patch /path/syscons.diff.20050215 cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 make clean make all make install You need also to rebuild and reinstall the kernel. You must have 'options SC_PIXEL_MODE' in your kernel config. You also need to have VESA available - you can load it with kldload vesa or include it in the kernel with 'options VESA'. After reboot with the new kernel you should be able to get list of all VESA and standard modes your card support with 'vidcontrol -i mode'. To be able to use them as your console mode you need to have the appropriate font loaded. The font resolution is seen in vidcontrol output in the 'font' column. To load the font 8x8 you can use 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To set the mode use 'vidcontrol MODE_$num' where $num is the mode number (first column in 'vidcontrol -i mode' output). HTH Michal I feel like I am missing a lot here. I want to display 132 characters per line on my console. I am not running X Windows and it is not a notebook. I am running 5.3-RELEASE-p5 #0. What is this SC_PIXEL_MODE and where may I find documentation on it? I don't find it in /usr/src/sys/i386/conf/NOTES. To rebuild and reinstall the kernel, after editing my /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 'make buildkernel' and then 'make installkernel' or is there something else I'm missing? I note that some of the messages are posted to multiple mailing lists, and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing the entire story. Jay O'Brien Rio Linda, California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Jay O'Brien wrote: Michal Mertl wrote: Didier Wiroth wrote: Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a few patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As the patch(es) is/are on the entire page, I don't know how to separate them. Would someone mail me as an attachment the different patches and tell me how I should apply them: for example, mail me patch1, patch2, patch3 and the explanation how to patch them: cd /usr/src patch ~/patch1 patch ~/patch2 ...etc I think the newest and probably best (?) patch was prepared by Xin Li ([EMAIL PROTECTED]) who is also committer. I sent this email to him (or she? - sorry about that) in case he has some comments. Beware that he said he experienced some problems with previous version of the patch. I haven't tested this version of the patch myself but it at least compiles. It's available at http://people.freebsd.org/~delphij/vesa/ in files syscons.diff.20050215 and vidcontrol.diff.20050215 You would apply them with: cd /usr/src/sys/dev/syscons patch /path/syscons.diff.20050215 cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 make clean make all make install You need also to rebuild and reinstall the kernel. You must have 'options SC_PIXEL_MODE' in your kernel config. You also need to have VESA available - you can load it with kldload vesa or include it in the kernel with 'options VESA'. After reboot with the new kernel you should be able to get list of all VESA and standard modes your card support with 'vidcontrol -i mode'. To be able to use them as your console mode you need to have the appropriate font loaded. The font resolution is seen in vidcontrol output in the 'font' column. To load the font 8x8 you can use 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To set the mode use 'vidcontrol MODE_$num' where $num is the mode number (first column in 'vidcontrol -i mode' output). HTH Michal I feel like I am missing a lot here. I want to display 132 characters per line on my console. I am not running X Windows and it is not a notebook. It doesn't matter. I only saw the most complaints from notebook owners who didn't have text mode console covering all LCD surface. I am running 5.3-RELEASE-p5 #0. What is this SC_PIXEL_MODE and where may I find documentation on it? I don't find it in /usr/src/sys/i386/conf/NOTES. man syscons(4). It's also mentioned in NOTES although not the NOTES you were looking at. Don't forget that on 5.x there are two conf directories - one platform independent in /sys/conf and other in /sys/$ARCH/conf. Common (platform independent) options like this one are in /sys/conf/NOTES. To rebuild and reinstall the kernel, after editing my /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 'make buildkernel' and then 'make installkernel' or is there something else I'm missing? No, that's the way to do it. I note that some of the messages are posted to multiple mailing lists, and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing the entire story. I'm afraid that's quite possible. Please go search the archives. Jay O'Brien Rio Linda, California USA Michal Mertl Prague, Bohemia, Czech Republic :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: Jay O'Brien wrote: Michal Mertl wrote: Didier Wiroth wrote: Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a few patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As the patch(es) is/are on the entire page, I don't know how to separate them. Would someone mail me as an attachment the different patches and tell me how I should apply them: for example, mail me patch1, patch2, patch3 and the explanation how to patch them: cd /usr/src patch ~/patch1 patch ~/patch2 ...etc I think the newest and probably best (?) patch was prepared by Xin Li ([EMAIL PROTECTED]) who is also committer. I sent this email to him (or she? - sorry about that) in case he has some comments. Beware that he said he experienced some problems with previous version of the patch. I haven't tested this version of the patch myself but it at least compiles. It's available at http://people.freebsd.org/~delphij/vesa/ in files syscons.diff.20050215 and vidcontrol.diff.20050215 You would apply them with: cd /usr/src/sys/dev/syscons patch /path/syscons.diff.20050215 cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 make clean make all make install You need also to rebuild and reinstall the kernel. You must have 'options SC_PIXEL_MODE' in your kernel config. You also need to have VESA available - you can load it with kldload vesa or include it in the kernel with 'options VESA'. After reboot with the new kernel you should be able to get list of all VESA and standard modes your card support with 'vidcontrol -i mode'. To be able to use them as your console mode you need to have the appropriate font loaded. The font resolution is seen in vidcontrol output in the 'font' column. To load the font 8x8 you can use 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To set the mode use 'vidcontrol MODE_$num' where $num is the mode number (first column in 'vidcontrol -i mode' output). HTH Michal I feel like I am missing a lot here. I want to display 132 characters per line on my console. I am not running X Windows and it is not a notebook. It doesn't matter. I only saw the most complaints from notebook owners who didn't have text mode console covering all LCD surface. I am running 5.3-RELEASE-p5 #0. What is this SC_PIXEL_MODE and where may I find documentation on it? I don't find it in /usr/src/sys/i386/conf/NOTES. man syscons(4). It's also mentioned in NOTES although not the NOTES you were looking at. Don't forget that on 5.x there are two conf directories - one platform independent in /sys/conf and other in /sys/$ARCH/conf. Common (platform independent) options like this one are in /sys/conf/NOTES. Thanks! Now that I see that it is perhaps not required for my system, that is not a laptop, is it possible that I don't need this at all? Is it definitely needed to support 132 character terminal mode, or is just needed for laptops? To rebuild and reinstall the kernel, after editing my /usr/src/sys/i386/conf/GENERIC to insert 'options SC_PIXEL_MODE', would I 'make buildkernel' and then 'make installkernel' or is there something else I'm missing? No, that's the way to do it. I note that some of the messages are posted to multiple mailing lists, and I suspect that as I only read [EMAIL PROTECTED] I'm not seeing the entire story. I'm afraid that's quite possible. Please go search the archives. Jay O'Brien Rio Linda, California USA Michal Mertl Prague, Bohemia, Czech Republic :-) It is wonderful to be a part of a caring community that spans the world, without concern for international borders. Fortunately for me, everyone uses english; I'm stuck with only one language (plus international morse code, but that's another story). Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Jay O'Brien wrote: Michal Mertl wrote: I feel like I am missing a lot here. I want to display 132 characters per line on my console. I am not running X Windows and it is not a notebook. It doesn't matter. I only saw the most complaints from notebook owners who didn't have text mode console covering all LCD surface. I am running 5.3-RELEASE-p5 #0. What is this SC_PIXEL_MODE and where may I find documentation on it? I don't find it in /usr/src/sys/i386/conf/NOTES. man syscons(4). It's also mentioned in NOTES although not the NOTES you were looking at. Don't forget that on 5.x there are two conf directories - one platform independent in /sys/conf and other in /sys/$ARCH/conf. Common (platform independent) options like this one are in /sys/conf/NOTES. Thanks! Now that I see that it is perhaps not required for my system, that is not a laptop, is it possible that I don't need this at all? Is it definitely needed to support 132 character terminal mode, or is just needed for laptops? There's no standard VGA 132 character text mode. It's either provided by VESA or emulated using some graphics mode. Newer graphics hardware stopped supporting extended text modes. If you want such modes you need to emulate them (render the characters using lots of small dots instead of just writing characters to the adapter which renders them for you). Support for this functionality is included in syscons/vga driver when you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar graphics mode 800x600 dots with 4 bits (16) of color information per pixel which can be run on old plain VGA with 256KB of memory. The patches we are talking about add support for rendering the characters in any graphics mode your card supports (through VESA) with = 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions of colours) for a text mode console. You can't use any graphics there but the textual resolution will be bigger. There also isn't support for using simultaneously more than 16 (or is it 15?) different colors for characters even when milions are technically possible. It is wonderful to be a part of a caring community that spans the world, without concern for international borders. Fortunately for me, everyone uses english; I'm stuck with only one language (plus international morse code, but that's another story). Yes, it really is great. Not the English though. I'd prefer Czech but I'm afraid it's a lost battle :-). Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: There's no standard VGA 132 character text mode. It's either provided by VESA or emulated using some graphics mode. Newer graphics hardware stopped supporting extended text modes. If you want such modes you need to emulate them (render the characters using lots of small dots instead of just writing characters to the adapter which renders them for you). Support for this functionality is included in syscons/vga driver when you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar graphics mode 800x600 dots with 4 bits (16) of color information per pixel which can be run on old plain VGA with 256KB of memory. The patches we are talking about add support for rendering the characters in any graphics mode your card supports (through VESA) with = 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions of colours) for a text mode console. You can't use any graphics there but the textual resolution will be bigger. There also isn't support for using simultaneously more than 16 (or is it 15?) different colors for characters even when milions are technically possible. Thanks for the explanation, it is appreciated. I tried the process and encountered errors. Here's what happened: patch /tmp/syscons.diff.20050215 this went fine. patch /tmp/vidcontrol.diff.20050215 returned errors as shown below: # patch /tmp/vidcontrol.diff.20050215 Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.1 |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v |retrieving revision 1.55 |diff -u -r1.55 vidcontrol.1 |--- vidcontrol.1 2 Mar 2003 21:04:21 - 1.55 |+++ vidcontrol.1 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.1 using Plan A... Hunk #1 succeeded at 11. Hunk #2 succeeded at 88. Hunk #3 succeeded at 297. Hunk #4 succeeded at 532. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.c |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v |retrieving revision 1.48 |diff -u -r1.48 vidcontrol.c |--- vidcontrol.c 13 Jan 2005 03:59:44 - 1.48 |+++ vidcontrol.c 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.c using Plan A... Hunk #1 succeeded at 24. Hunk #2 succeeded at 48. Hunk #3 succeeded at 66 with fuzz 1. Hunk #4 failed at 187. Hunk #5 succeeded at 223. Hunk #6 failed at 239. Hunk #7 failed at 257. Hunk #8 failed at 297. Hunk #9 failed at 332. Hunk #10 succeeded at 348 with fuzz 2. Hunk #11 failed at 377. Hunk #12 failed at 419. Hunk #13 failed at 507. Hunk #14 failed at 572. Hunk #15 failed at 669. Hunk #16 failed at 722. Hunk #17 failed at 743. Hunk #18 failed at 806. Hunk #19 succeeded at 891. Hunk #20 failed at 900. Hunk #21 failed at 933. Hunk #22 succeeded at 950 with fuzz 2. Hunk #23 failed at 962. Hunk #24 failed at 985. Hunk #25 failed at 1035. Hunk #26 failed at 1050. Hunk #27 succeeded at 1148. Hunk #28 succeeded at 1173. Hunk #29 succeeded at 1217. Hunk #30 succeeded at 1234. 19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej done Not being a c programmer, I can't understand what the vidcontrol.c.rej file is trying to tell me. It is a 29K file. As I recalled a previous email telling someone to go ahead anyway, I went ahead with make clean and that went ok. Then I did make all and here's the results: make all cc -O -pipe -c /usr/src/usr.sbin/vidcontrol/vidcontrol.c /usr/src/usr.sbin/vidcontrol/vidcontrol.c: In function `video_mode': /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in this function) /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: (Each undeclared identifier is reported only once /usr/src/usr.sbin/vidcontrol/vidcontrol.c:500: error: for each function it appears in.) /usr/src/usr.sbin/vidcontrol/vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in this function) /usr/src/usr.sbin/vidcontrol/vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/usr.sbin/vidcontrol. I did not do a make install. Guidance will be appreciated. Thanks! Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Jay O'Brien pe v ne 10. 04. 2005 v 15:21 -0700: Michal Mertl wrote: There's no standard VGA 132 character text mode. It's either provided by VESA or emulated using some graphics mode. Newer graphics hardware stopped supporting extended text modes. If you want such modes you need to emulate them (render the characters using lots of small dots instead of just writing characters to the adapter which renders them for you). Support for this functionality is included in syscons/vga driver when you define options SC_PIXEL_MODE. Standard FreeBSD supports only planar graphics mode 800x600 dots with 4 bits (16) of color information per pixel which can be run on old plain VGA with 256KB of memory. The patches we are talking about add support for rendering the characters in any graphics mode your card supports (through VESA) with = 15 bits per pixel. You could then run say 1600x1200x32 bpp (16milions of colours) for a text mode console. You can't use any graphics there but the textual resolution will be bigger. There also isn't support for using simultaneously more than 16 (or is it 15?) different colors for characters even when milions are technically possible. Thanks for the explanation, it is appreciated. I tried the process and encountered errors. Here's what happened: patch /tmp/syscons.diff.20050215 this went fine. patch /tmp/vidcontrol.diff.20050215 returned errors as shown below: # patch /tmp/vidcontrol.diff.20050215 Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.1 |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v |retrieving revision 1.55 |diff -u -r1.55 vidcontrol.1 |--- vidcontrol.1 2 Mar 2003 21:04:21 - 1.55 |+++ vidcontrol.1 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.1 using Plan A... Hunk #1 succeeded at 11. Hunk #2 succeeded at 88. Hunk #3 succeeded at 297. Hunk #4 succeeded at 532. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.c |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v |retrieving revision 1.48 |diff -u -r1.48 vidcontrol.c |--- vidcontrol.c 13 Jan 2005 03:59:44 - 1.48 |+++ vidcontrol.c 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.c using Plan A... Hunk #1 succeeded at 24. Hunk #2 succeeded at 48. Hunk #3 succeeded at 66 with fuzz 1. Hunk #4 failed at 187. Hunk #5 succeeded at 223. Hunk #6 failed at 239. Hunk #7 failed at 257. Hunk #8 failed at 297. Hunk #9 failed at 332. Hunk #10 succeeded at 348 with fuzz 2. Hunk #11 failed at 377. Hunk #12 failed at 419. Hunk #13 failed at 507. Hunk #14 failed at 572. Hunk #15 failed at 669. Hunk #16 failed at 722. Hunk #17 failed at 743. Hunk #18 failed at 806. Hunk #19 succeeded at 891. Hunk #20 failed at 900. Hunk #21 failed at 933. Hunk #22 succeeded at 950 with fuzz 2. Hunk #23 failed at 962. Hunk #24 failed at 985. Hunk #25 failed at 1035. Hunk #26 failed at 1050. Hunk #27 succeeded at 1148. Hunk #28 succeeded at 1173. Hunk #29 succeeded at 1217. Hunk #30 succeeded at 1234. 19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej done Not being a c programmer, I can't understand what the vidcontrol.c.rej file is trying to tell me. It is a 29K file. As I recalled a previous email telling someone to go ahead anyway, I went ahead with make clean and that went ok. Then I did make all and here's the results: You haven't read the thread in the archives carefully enough, have you? Here is what I wrote (privately to the original poster but I explained the error to the mailing list too): What? I don't know how the patching of vidcontrol ended but you'd better redo it with fresh files from current. Go download vidcontrol.c v 1.48 and vidcontrol.1 from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ Then run the patch on it again and recompile/reinstall vidcontrol binary. Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Michal Mertl wrote: You haven't read the thread in the archives carefully enough, have you? Yes, but unfortunately I didn't comprehend. Here is what I wrote (privately to the original poster but I explained the error to the mailing list too): What? I don't know how the patching of vidcontrol ended but you'd better redo it with fresh files from current. Go download vidcontrol.c v 1.48 and vidcontrol.1 from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ Then run the patch on it again and recompile/reinstall vidcontrol binary. I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. Now all hunks failed. The results are below. What did I screw up this time? Jay |Index: vidcontrol.1 |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.1,v |retrieving revision 1.55 |diff -u -r1.55 vidcontrol.1 |--- vidcontrol.1 2 Mar 2003 21:04:21 - 1.55 |+++ vidcontrol.1 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.1 using Plan A... Hunk #1 failed at 11. Hunk #2 failed at 88. Hunk #3 failed at 297. Hunk #4 failed at 532. 4 out of 4 hunks failed--saving rejects to vidcontrol.1.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: vidcontrol.c |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v |retrieving revision 1.48 |diff -u -r1.48 vidcontrol.c |--- vidcontrol.c 13 Jan 2005 03:59:44 - 1.48 |+++ vidcontrol.c 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.c using Plan A... Hunk #1 failed at 24. Hunk #2 failed at 48. Hunk #3 failed at 66. Hunk #4 failed at 187. Hunk #5 failed at 223. Hunk #6 failed at 239. Hunk #7 failed at 257. Hunk #8 failed at 297. Hunk #9 failed at 332. Hunk #10 failed at 348. Hunk #11 failed at 377. Hunk #12 failed at 419. Hunk #13 failed at 507. Hunk #14 failed at 572. Hunk #15 failed at 669. Hunk #16 failed at 722. Hunk #17 failed at 743. Hunk #18 failed at 806. Hunk #19 failed at 891. Hunk #20 failed at 900. Hunk #21 failed at 933. Hunk #22 failed at 950. Hunk #23 failed at 962. Hunk #24 failed at 985. Hunk #25 failed at 1035. Hunk #26 failed at 1050. Hunk #27 failed at 1148. Hunk #28 failed at 1173. Hunk #29 failed at 1217. Hunk #30 failed at 1234. 30 out of 30 hunks failed--saving rejects to vidcontrol.c.rej done ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Jay O'Brien wrote: Michal Mertl wrote: You haven't read the thread in the archives carefully enough, have you? Yes, but unfortunately I didn't comprehend. Here is what I wrote (privately to the original poster but I explained the error to the mailing list too): What? I don't know how the patching of vidcontrol ended but you'd better redo it with fresh files from current. Go download vidcontrol.c v 1.48 and vidcontrol.1 from http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/vidcontrol/ Then run the patch on it again and recompile/reinstall vidcontrol binary. I did that. The files are vidcontrol.1 Rev 1.55 and Vidcontrol.c Rev 1.48. Now all hunks failed. The results are below. I don't know. The text before the line starting with Patching is taken from the patch file. The patch program doesn't retrieve any files. So I think you either used bad files to patch or bad patchfile. You need to have the original files. To check they're correct you can use md5 utility. md5 vidcontrol.c MD5 (vidcontrol.c) = 1068e5a6aff863e2bc7a0c02098d43b1 md5 vidcontrol.1 MD5 (vidcontrol.1) = 080d2b84f2e3914090279fee6e5f2406 md5 vidcontrol.diff.20050215 MD5 (vidcontrol.diff.20050215) = 67ae12fe2a4fecae1bb7adb141efe021 You need to see the same strings. Then command 'patch /path/to/vidcontro.diff.20050215' must work. Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hello, Thx for the patch, I tried it and here is my feedback. To clear out things I'm not using CURRENT, I used: a) FreeBSD5.4-prerelease (as I'm using RELENG_5), running on a HP NC6000 laptop, connected to a docking station with a Microsoft USB mouse b) I downloaded the current rc.d/moused version 1.9 and patched the file with your patch c) copied the current-patched file 1) Unfortunately the problem still exists, error messages still appear. 2) The touchpad worked but my usb mouse didn't work at all I don't have a patch that is good enough to warrant a commit at present. You may want to try the patch attached, but I can not promise that it will work for every case. Thanks for your testing! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Ok, sorry! I rebooted now to be sure and... the touchpad work and the usb mouse does work too! But still error messages. Didier -Original Message- From: Didier Wiroth [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 11:00 To: 'Xin LI' Cc: 'freebsd-questions@freebsd.org'; 'freebsd-current@freebsd.org'; '[EMAIL PROTECTED]' Subject: RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT Hello, Thx for the patch, I tried it and here is my feedback. To clear out things I'm not using CURRENT, I used: a) FreeBSD5.4-prerelease (as I'm using RELENG_5), running on a HP NC6000 laptop, connected to a docking station with a Microsoft USB mouse b) I downloaded the current rc.d/moused version 1.9 and patched the file with your patch c) copied the current-patched file 1) Unfortunately the problem still exists, error messages still appear. 2) The touchpad worked but my usb mouse didn't work at all I don't have a patch that is good enough to warrant a commit at present. You may want to try the patch attached, but I can not promise that it will work for every case. Thanks for your testing! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hi, Didier,
2005-04-06 13:39 +0200Didier Wiroth
Is there a patch available for the rc.d mouse script?
I don't have a patch that is good enough to warrant a commit at present.
You may want to try the patch attached, but I can not promise that it
will work for every case.
Thanks for your testing!
Cheers,
--
Xin LI delphij delphij net http://www.delphij.net/
Index: jail
===
RCS file: /home/ncvs/src/etc/rc.d/jail,v
retrieving revision 1.21
diff -u -r1.21 jail
--- jail 16 Jan 2005 03:12:03 - 1.21
+++ jail 1 Feb 2005 07:21:57 -
@@ -59,6 +59,14 @@
eval jail_procfs=\\$jail_${_j}_procfs_enable\
[ -z ${jail_procfs} ] jail_procfs=NO
+ # Default settings for skel jail
+ eval jail_skel_enable=\\$jail_${_j}_skel_enable\
+ [ -z ${jail_skel_enable} ] jail_skel_enable=NO
+ eval jail_skel_root=\\$jail_${_j}_skel_root\
+ [ -z ${jail_skel_root} ] jail_skel_root=/
+ eval jail_skel_romounts=\\$jail_${_j}_skel_romounts\
+ [ -z ${jail_skel_romounts} ] jail_skel_romounts=bin sbin lib libexec usr/bin usr/sbin usr/include usr/lib usr/libdata usr/libexec usr/sbin usr/share
+
eval jail_mount=\\$jail_${_j}_mount_enable\
[ -z ${jail_mount} ] jail_mount=NO
# /etc/fstab.${_j} will be used for {,u}mount(8) if none is specified.
@@ -81,6 +89,9 @@
debug $_j fstab: $jail_fstab
debug $_j exec start: $jail_exec_start
debug $_j exec stop: $jail_exec_stop
+ debug $_j skel enable: $jail_skel_enable
+ debug $_j skel mount-readonly: $jail_skel_romounts
+ debug $_j skel mount-readonly from: $jail_skel_root
}
# set_sysctl rc_knob mib msg
@@ -136,6 +147,14 @@
[ -f ${jail_fstab} ] || warn ${jail_fstab} does not exist
umount -a -F ${jail_fstab} /dev/null 21
fi
+ if checkyesno jail_skel_enable; then
+ for _mntpt in $jail_skel_romounts
+ do
+ if [ -d ${jail_rootdir}/${_mntpt} ] ; then
+umount -f ${jail_rootdir}/${_mntpt} /dev/null 21
+ fi
+ done
+ fi
}
jail_start()
@@ -155,6 +174,13 @@
for _jail in ${jail_list}
do
init_variables $_jail
+ if checkyesno jail_skel_enable; then
+ info Mounting skeleton for jail ${_jail} from ${jail_skel_root}
+ for _mntpt in $jail_skel_romounts
+ do
+mount_nullfs -ordonly ${jail_skel_root}/${_mntpt} ${jail_rootdir}/${_mntpt} /dev/null 21
+ done
+ fi
if checkyesno jail_mount; then
info Mounting fstab for jail ${_jail} (${jail_fstab})
if [ ! -f ${jail_fstab} ]; then
Index: moused
===
RCS file: /home/ncvs/src/etc/rc.d/moused,v
retrieving revision 1.9
diff -u -r1.9 moused
--- moused 16 Jan 2005 03:12:03 - 1.9
+++ moused 7 Apr 2005 13:41:45 -
@@ -10,10 +10,16 @@
. /etc/rc.subr
+# stdin must be redirected because it might be a serial console
+#
+ttyv=/dev/ttyv0
+
name=moused
rcvar=`set_rcvar`
command=/usr/sbin/${name}
+required_files=${ttyv}
start_cmd=moused_start
+stop_postcmd=moused_postcmd
_pidprefix=/var/run/moused
pidfile=${_pidprefix}.pid
_pidarg=
@@ -66,10 +72,13 @@
;;
esac
- for ttyv in /dev/ttyv* ; do
- vidcontrol ${ttyv} ${_mousechar_arg} -m on
- done
+ vidcontrol ${ttyv} ${_mousechar_arg} -m on
echo '.'
}
+moused_postcmd()
+{
+ vidcontrol ${ttyv} -m off
+}
+
run_rc_command $*
signature.asc
Description: This is a digitally signed message part
Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hi, Michal, 2005-04-05 22:07 +0200Michal Mertl Didier Wiroth wrote: Hello, Thank you very much for replying. cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 I'm using the RELENG_5 sources from today. The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives some errors. The diff is against the sources from -CURRENT where it applies and compiles cleanly. You should be ok using the current vidcontrol sources on -STABLE. The only difference is just some code purity fixes by Xin Li - probably in preparation for integrating the changes we speak about. I went into some problem when using the patch on my own laptop, which indicates that USB based mouse can play something nasty with the patchset :-( It does not affect the functionality seriously, but is really annoying. I would appreciate if someone can fix the issue. Cheers, -- Xin LI delphij delphij net http://www.delphij.net/ signature.asc Description: This is a digitally signed message part
RE: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hi, I've updated the vidcontrol sources to those in the current cvs and was able to compile and install the patch on stable. High resolution console is fantastic have 1400x1050 (MODE_322) on my laptop now. I get an pfctl -sa, on one screen ... amazing :-)) It does make freebsd so much better ... I would be great to integrate these patches in future releases, please! The mouse actually works without problem in the console but I've a small mouse bug after a reboot. I assume the /etc/rc.d/mouse script needs a tiny patch. After a reboot and while launching the different services/daemon, there are about 10 lines of vidcontrol errors. Here a sample output: vidcontrol: showing the mouse: invalid argument Is there a patch available for the rc.d mouse script? Thank you Didier I believe Didier used broken vidcontrol.c file. The patch was for current and needs to be applied to clean vidcontrol.c ver 1.48. It works for me (on CURRENT anyways). Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a few patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As the patch(es) is/are on the entire page, I don't know how to separate them. Would someone mail me as an attachment the different patches and tell me how I should apply them: for example, mail me patch1, patch2, patch3 and the explanation how to patch them: cd /usr/src patch ~/patch1 patch ~/patch2 ...etc In advance, many thanks! Didier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Didier Wiroth wrote: Hi, I'm using freebsd 5.4-prerelease on my laptop. My laptop has an ati mobility radeon 9600. Unfortunately it has very poor console vesa support. SC_PIXEL_MODE does not work, 90x60 is the highest resolution I can get for now. It looks like I'm not the only one having this problem with ati chipsets: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1091839+1096057+/usr/local/w ww/db/text/2005/freebsd-questions/20050123.freebsd-questions I saw this posting: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035621.ht ml Unfortunately I'm not a programmer and have no ... to very poor patching skills. It looks to me, that in this posting(s) a few patches are grouped together to enable vesa 1024x768. 1) Has someone applied this patches? 2) As the patch(es) is/are on the entire page, I don't know how to separate them. Would someone mail me as an attachment the different patches and tell me how I should apply them: for example, mail me patch1, patch2, patch3 and the explanation how to patch them: cd /usr/src patch ~/patch1 patch ~/patch2 ...etc I think the newest and probably best (?) patch was prepared by Xin Li ([EMAIL PROTECTED]) who is also committer. I sent this email to him (or she? - sorry about that) in case he has some comments. Beware that he said he experienced some problems with previous version of the patch. I haven't tested this version of the patch myself but it at least compiles. It's available at http://people.freebsd.org/~delphij/vesa/ in files syscons.diff.20050215 and vidcontrol.diff.20050215 You would apply them with: cd /usr/src/sys/dev/syscons patch /path/syscons.diff.20050215 cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 make clean make all make install You need also to rebuild and reinstall the kernel. You must have 'options SC_PIXEL_MODE' in your kernel config. You also need to have VESA available - you can load it with kldload vesa or include it in the kernel with 'options VESA'. After reboot with the new kernel you should be able to get list of all VESA and standard modes your card support with 'vidcontrol -i mode'. To be able to use them as your console mode you need to have the appropriate font loaded. The font resolution is seen in vidcontrol output in the 'font' column. To load the font 8x8 you can use 'vidcontrol -f /usr/share/syscons/fonts/cp437-8x8.fnt' or similar. To set the mode use 'vidcontrol MODE_$num' where $num is the mode number (first column in 'vidcontrol -i mode' output). HTH Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Hello, Thank you very much for replying. cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 I'm using the RELENG_5 sources from today. The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives some errors. |Index: vidcontrol.c |=== |RCS file: /home/ncvs/src/usr.sbin/vidcontrol/vidcontrol.c,v |retrieving revision 1.48 |diff -u -r1.48 vidcontrol.c |--- vidcontrol.c 13 Jan 2005 03:59:44 - 1.48 |+++ vidcontrol.c 17 Jan 2005 05:27:25 - -- Patching file vidcontrol.c using Plan A... Hunk #1 succeeded at 24. Hunk #2 succeeded at 48. Hunk #3 succeeded at 66 with fuzz 1. Hunk #4 failed at 187. Hunk #5 succeeded at 223. Hunk #6 failed at 239. Hunk #7 failed at 257. Hunk #8 failed at 297. Hunk #9 failed at 332. Hunk #10 succeeded at 348 with fuzz 2. Hunk #11 failed at 377. Hunk #12 failed at 419. Hunk #13 failed at 507. Hunk #14 failed at 572. Hunk #15 failed at 669. Hunk #16 failed at 722. Hunk #17 failed at 743. Hunk #18 failed at 806. Hunk #19 succeeded at 891. Hunk #20 failed at 900. Hunk #21 failed at 933. Hunk #22 succeeded at 950 with fuzz 2. Hunk #23 failed at 962. Hunk #24 failed at 985. Hunk #25 failed at 1035. Hunk #26 failed at 1050. Hunk #27 succeeded at 1148. Hunk #28 succeeded at 1173. Hunk #29 succeeded at 1217. Hunk #30 succeeded at 1234. 19 out of 30 hunks failed--saving rejects to vidcontrol.c.rej done ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Didier Wiroth wrote: Hello, Thank you very much for replying. cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 I'm using the RELENG_5 sources from today. The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives some errors. The diff is against the sources from -CURRENT where it applies and compiles cleanly. You should be ok using the current vidcontrol sources on -STABLE. The only difference is just some code purity fixes by Xin Li - probably in preparation for integrating the changes we speak about. Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re : Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Unfortunately with patch applied it does not compile on stable: Warning: Object directory not changed from original /usr/src/usr.sbin/vidcontrol cc -O -pipe -c vidcontrol.c vidcontrol.c: In function `video_mode': vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in this function) vidcontrol.c:500: error: (Each undeclared identifier is reported only once vidcontrol.c:500: error: for each function it appears in.) vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in this function) vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in this function) *** Error code 1 - Message d'origine - De: Michal Mertl [EMAIL PROTECTED] Date: Mardi, Avril 5, 2005 10:07 pm Objet: Re: Re : Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT Didier Wiroth wrote: Hello, Thank you very much for replying. cd /usr/src/usr.sbin/vidcontrol patch /path/vidcontrol.diff.20050215 I'm using the RELENG_5 sources from today. The syscons.diff.20050215 works but the vidcontrol.diff.20050215 gives some errors. The diff is against the sources from -CURRENT where it applies and compiles cleanly. You should be ok using the current vidcontrol sourceson -STABLE. The only difference is just some code purity fixes by Xin Li - probably in preparation for integrating the changes we speak about. Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH TO TEST] VESA [1024x768] mode support for FreeBSD-CURRENT
Didier Wiroth wrote: Unfortunately with patch applied it does not compile on stable: Warning: Object directory not changed from original /usr/src/usr.sbin/vidcontrol cc -O -pipe -c vidcontrol.c vidcontrol.c: In function `video_mode': vidcontrol.c:500: error: `_VESA_800x600_DFL_COLS' undeclared (first use in this function) vidcontrol.c:500: error: (Each undeclared identifier is reported only once vidcontrol.c:500: error: for each function it appears in.) vidcontrol.c:505: error: `_VESA_800x600_DFL_FNSZ' undeclared (first use in this function) vidcontrol.c:509: error: `_VESA_800x600_DFL_ROWS' undeclared (first use in this function) *** Error code 1 I believe Didier used broken vidcontrol.c file. The patch was for current and needs to be applied to clean vidcontrol.c ver 1.48. It works for me (on CURRENT anyways). Michal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Speed test
Hello, Is there a way to test your system (i run FreeBSD 5.3) to see if something is wrong? My mashine seams slow... are there any tools to do that? Also are there any tools to optimize the system or fix if somethings wrong? Thanks for your time. Regards Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Speed test
[EMAIL PROTECTED] wrote: Is there a way to test your system (i run FreeBSD 5.3) to see if something is wrong? There are lots of benchmarks available under /usr/ports/benchmarks. Also are there any tools to optimize the system or fix if somethings wrong? Why yes, the C compiler. You just need to change the source code, first. [ Or update it, see the Handbook. ] -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
A Test Message Please Disreguard
All, Sorry for this post, but I have submitted a couple of posts and they haven't appeared on the list. I just want to make sure that things are working. --Nick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A Test Message Please Disreguard
NP All, NP Sorry for this post, but I have submitted a couple of posts and they NP haven't appeared on the list. I just want to make sure that things NP are working. NP --Nick NP ___ NP freebsd-questions@freebsd.org mailing list NP http://lists.freebsd.org/mailman/listinfo/freebsd-questions NP To unsubscribe, send any mail to [EMAIL PROTECTED] - obviously not otherwise you would have seen them ;) maybe you should pay the mailman god a visit, his temple can be found here http://lists.freebsd.org/mailman/listinfo/freebsd-questions I seem to remember that the mailmans priests have a prayer that, if uttered correctly under the holy moon of the web will please the god, so that he repeats the questions you send to him to yourself. Hail be to him. Hexren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Don't send test messages to -questions (was: test don't read)
On Wednesday, 8 December 2004 at 2:11:50 +0100, J65nko BSD wrote: On Tue, 7 Dec 2004 10:57:18 +1030, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 6 December 2004 at 23:28:21 +, agostinho wrote: test Please don't do this. It gets sent to tens of thousands of people round the world. There's a special list for sending test messages. Please use it instead. Greg, your response also gets sent to tens of thousands of people. Please reply privately next time to this type of posts ;) Please note the supplement to the .signature: When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Sorry, couldn't resist ;) There's a very good reason for that. In the past, we've seen that one person does something like this, and others copy him. By sending one message asking people not to do so, we can potentially nip many more in the bud. Sorry for the noise, people. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp6FD0hgO83h.pgp Description: PGP signature
test don't read
test ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Don't send test messages to -questions (was: test don't read)
On Monday, 6 December 2004 at 23:28:21 +, agostinho wrote: test Please don't do this. It gets sent to tens of thousands of people round the world. There's a special list for sending test messages. Please use it instead. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpVkwhloX7kj.pgp Description: PGP signature
test
please igmore -- ... don't touch the bang bang fruit ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Virtual IP/DNS test results
Im trying to setup virtual IPs/DNS/Apache, and it seems to be working within the LAN so far. Box 1: Firewall/Router/DNS/DHCP Server Box 2: Virtual IPs Box 3: DHCP client. This is where Im getting an oddity (see below). If I were to ping a hostname that is using a virtual IP address, or if I ping a virtual IP address from just this one of the machines on the LAN, I get this - $ ping -c1 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 36 bytes from gatekeeper.trini0.org (192.168.0.1): Redirect Host(New addr: 192.168.1.1) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 03ae 0 40 01 f499 192.168.0.16 192.168.1.1 64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.807 ms --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.807/0.807/0.807/0.000 ms Is this indicative that there is a problem with the setup??? Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Virtual IP/DNS test results
Gerard Samuel wrote: If I were to ping a hostname that is using a virtual IP address, or if I ping a virtual IP address from just this one of the machines on the LAN, [ ...you get an ICMP redirect... ] Is this indicative that there is a problem with the setup??? No. What happened was you local client created an HTTP request to the public IP which the hostname in the URL resolved to. Your NAT box saw that this public IP was in fact being NAT'ed to a local host, and issued an ICMP redirect telling the client about the shorter route. If this didn't work right, your apache config probably doesn't mention the local IP in the virtualhost section or some such, but the HTTP result and/or the apache logs will give more info to track down any such details. You can also set up split-horizon DNS or perform similar tricks in /etc/hosts to convince machines on your LAN to lookup the www hostname as local IP rather than as public IP, which would remove the ICMP redirect from the situation entirely. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Test
Test - Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
