Lose 16 Pounds In 10 Days 31249
Hey there, If you're like me, you've tried EVERYTHING to lose weight. I know how you feel - the special diets, miracle pills, and fancy exercise equipment never helped me lose a pound either. It seemed like the harder I tried, the bigger I got, until I heard about a product called Extreme Power Plus. You're probably thinking to yourself, Oh geez, not another miracle diet pill! Like you, I was skeptical at first, but my sister swore it helped her lose 23 pounds in just two weeks, so I told her I'd give it a shot. I mean, there was nothing to lose except a lot of weight! Let me tell you, it was the best decision I've ever made. Period. Six months later, as I'm writing this message to you, I've gone from 355 pounds to 210 pounds, and I haven't changed my exercise routine or diet at all. Yes, I still eat pizza, and lots of it! I was so happy with the results that I contacted the manufacturer and got permission to resell it - at a BIG discount. I want to help other people lose weight like I did, because it does so much for your self-esteem, not to mention your health. I give you my personal pledge that Extreme Power Plus absolutely WILL WORK FOR YOU. If it doesn't, you can return it any time for a full refund. If you are frustrated with trying other products, not having any success, and just not getting the results you were promised, then I recommend the only product that worked for me - EXTREME POWER PLUS. You're probably asking yourself, Ok, so how does this stuff actually work? Extreme Power Plus contains Lipotropic fat burners and ephedra which is scientifically proven to increase metabolism and cause rapid weight loss. No hocus pocus in these pills - just RESULTS, RESULTS, RESULTS!! Here is the bottom line ... I can help you lose 10-15 pounds per week naturally, without exercising and without having to eat rice cakes all day. Just try it for one month - there's nothing to lose, and everything to gain. You will lose weight fast - GUARANTEED. That is my pledge to you. To order Extreme Power Plus on our secure server, just click on the link below: http://www.2002marketing.com/power/extreme.cfm If you have difficulty accessing the website above, please try our mirror site by clicking on the link below: http://www.2002marketing.com/power/extreme.cfm To see what some of our customers have said about this product, visit http://www.2002marketing.com/power/extreme.cfm To see a list of ingredients and for more information on test studies and how it will help you lose weight, visit http://www.2002marketing.com/power/extreme.cfm * If you do not wish to receive any more emails from me, please send an email to [EMAIL PROTECTED] requesting to be removed. * To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: jail man page
On Wed, May 29, 2002 at 11:44:12PM -0400, Michael R. Wayne wrote: Posted to -hackers in the hope that this can be tweaked in 4.6 RELEASE. 4.5-RELEASE-p4 % man jail D=/here/is/the/jail cd /usr/src make world DESTDIR=$D ^ | shouldn't that really be make installworld DESTDIR=$D Kinda difficult to installworld if you haven't built it yet... -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org msg34686/pgp0.pgp Description: PGP signature
Re: process hang in atprq state
Thanks for the speedy reply Søren :) Soeren Schmidt may have written: It seems Soeren Schmidt wrote: It seems Richard Nyberg wrote: Hi there. I seem to have some problems with my cd read program. I've attached a small prototype program that for some reason hangs in atprq, even though I use a timeout of 5 seconds. The program reads a cd in raw format using the MMC READ_CD command. It works fine :) except that it never manages to finish because of the hang. The hang doesn't seem to be linked to any specific place on the cd, but it might be linked to my ignorance ;) Uhm, you just need to set the blocksize on the CD device with the CDRIOCGETBLOCKSIZE and then just read the CD with dd if=/dev/acdX of=fil bs=2352 That will read the CD in RAW mode... Ok, I see! However, I also want to read the raw subchannel data, which I don't see any way of doing. In addition I also want to be able to handle flawed cd:s in a semi intelligent manner (examine the error instead of just stopping like dd). Oh, I forgot to tell you that it hangs because you have to stop reading at the last block, the drive will try to read anything you ask it to, but some drives newer return data for nonexistin blocks.. Unfortunately, this cannot be it :( The hangs occurs at different blocks on the same cd and often long before the last lba. I tried the dd approach and it worked much better, ie. no hang, so I must be doing something wrong. BTW, I noticed some stupid block count bugs in the source I posted, but they shouldn't matter since the hangs occured even when I just read one block at a time. -Richard To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: jail man page
On Thu, May 30, 2002 at 07:09:27AM -0400, Chris Faulhaber wrote: On Wed, May 29, 2002 at 11:44:12PM -0400, Michael R. Wayne wrote: Posted to -hackers in the hope that this can be tweaked in 4.6 RELEASE. 4.5-RELEASE-p4 % man jail D=/here/is/the/jail cd /usr/src make world DESTDIR=$D ^ | shouldn't that really be make installworld DESTDIR=$D Kinda difficult to installworld if you haven't built it yet... We are building from source here right? Not doing a binary install. So we should have recently followed the steps in UPDATING in order to get our host upgraded. So we use that. jail is confusing enough as it is. Having the man page tell people to rebuild the world for each jail they are going to install is not reasonable. So it's more than a one word fix: Prior to installing a jail, you should follow the instructions in /usr/src/UPDATING to build the world and install it on the host. Then, for each jail you wish to create, do the following /\/\ \/\/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
KLD mmap question
Hello, I have a question about implementing mmap functions in device drivers. Thinking it would be simple, I contigmalloc'd a buffer of PAGE_SIZE and returned it using atop like other mmap device implementations. However when my userland program mmaps the device with offset 0, when I try accessing the returned pointer, it returns me invalid memory address. Any help would be appreciated... - Tom -- Tom Tang tangj AT cs DOT ucdavis DOT edu To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: KLD mmap question
On Thu, 30 May 2002, Tom Tang wrote: I have a question about implementing mmap functions in device drivers. Thinking it would be simple, I contigmalloc'd a buffer of PAGE_SIZE and returned it using atop like other mmap device implementations. However when my userland program mmaps the device with offset 0, when I try accessing the returned pointer, it returns me invalid memory address. Any help would be appreciated... Generally, after the machine is started, memory gets too fragmented to use contigmalloc. If you preload the module and do the contigmalloc at attach time it should succeed. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: KLD mmap question
Doug, Thanks for the reply, I'll check it out. However if you'll notice in my prev mail, I stated that I was trying to contigmalloc 4K... Hard to believe that the system doesnt have 4K lying around. - Tom On Thu, 30 May 2002, Doug White wrote: On Thu, 30 May 2002, Tom Tang wrote: I have a question about implementing mmap functions in device drivers. Thinking it would be simple, I contigmalloc'd a buffer of PAGE_SIZE and returned it using atop like other mmap device implementations. However when my userland program mmaps the device with offset 0, when I try accessing the returned pointer, it returns me invalid memory address. Any help would be appreciated... Generally, after the machine is started, memory gets too fragmented to use contigmalloc. If you preload the module and do the contigmalloc at attach time it should succeed. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org -- Tom Tang [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
C ????
I am coding a scheduler. It is going to paste a msg to the screen after a certain time. How might i run this in the background? I tried just casting it into the background with the name but it did'nt work. I need it to asked the questions and then put it self into the background. If someone could give me some liks to some docs I woould be vary grateful.. Thanks Dan _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: C ????
echo dev writes: I am coding a scheduler. It is going to paste a msg to the screen after a certain time. How might i run this in the background? I tried just casting it into the background with the name but it did'nt work. I need it to asked the questions and then put it self into the background. If someone could give me some liks to some docs I woould be vary grateful.. If your backgrounded program stops when it tries to write to the terminal, you might want to unset tostop on the terminal via stty(1): tostop (-tostop) Send (do not send) SIGTTOU for background output. This causes background jobs to stop if they attempt terminal out put. --mkb To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Myson / if_my.c for FreeBSD
On Tue, 16 Apr 2002, Julian Elischer wrote: On Tue, 16 Apr 2002, Surfer wrote: Sir: Our latest driver is ready and tested. It's support our 3 network chips. MTD800Fast NIC MTD803Fast NIC with integrated PHY MTD891Gigabit NIC Should I release it at this time?? Or I can release it after the old driver checked into the current tree?? I don't check the old driver into the current tree yet. And the latest driver is NOT KNF. can you send me the files? also, can you make a very small man page that gives the cards that may be supported, and how to identify such cards.. the cards you sent me have chips identified as: BC001 0041afa3K1 with a logo of (circle)+ US there is no other identifying information on them so it would be good to have a document of how to identify cards that may be supported by this driver. I just checked in a KNF'd version of the 4.x drivers as well. (I may have a few small bits to clean up I just noticed...) Thanks for your help on our FreeBSD driver. This is my first time to write a FreeBSD driver. I have to learn a lot of thing about FreeBSD driver. Best Regards Yen Chien Wu HI, I'm back from vacation.. can yuou let me know where the latest drivers are so I can compare them and get them ready for freebsd? You said the driver did NOT support something but I do not know which it was.. julian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: C ????
* echo dev [EMAIL PROTECTED] [020530 13:17] wrote: I am coding a scheduler. It is going to paste a msg to the screen after a certain time. How might i run this in the background? I tried just casting it into the background with the name but it did'nt work. I need it to asked the questions and then put it self into the background. If someone could give me some liks to some docs I woould be vary grateful.. Have your program ask questions, then fork a child process, then have the parent exit, it will effectively detach. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: C ????
On 2002-05-30 23:01 +0200, Matthias Buelow wrote: echo dev writes: I am coding a scheduler. It is going to paste a msg to the screen after a certain time. How might i run this in the background? I tried just casting it into the background with the name but it did'nt work. I need it to asked the questions and then put it self into the background. If someone could give me some liks to some docs I woould be vary grateful.. Look at daemon(3). You can make your program do the equivalent of: % ./a.out [ ask questions check answers for validity ] [ call daemon(3) to become a background process ] - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: KLD mmap question
On Thu, 2002-05-30 at 13:14, Tom Tang wrote: Hello, I have a question about implementing mmap functions in device drivers. Thinking it would be simple, I contigmalloc'd a buffer of PAGE_SIZE and returned it using atop like other mmap device implementations. However when my userland program mmaps the device with offset 0, when I try accessing the returned pointer, it returns me invalid memory address. Any help would be appreciated... An associated question: while I was looking at the DRM's mmap for the shared memory area, I think I figured out that you didn't need memory that was going to be mmapped to be physically contiguous (since the device pager would get each page of it separately). Was I right? -- Eric Anholt [EMAIL PROTECTED] http://gladstone.uoregon.edu/~eanholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
On Thursday, May 30, 2002, at 08:31 , Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. Not necesarily. What video card did you have. Is it on the supported list for xfree? Is it on the well supported list or the take-your-chances list? Was your kernel and or xfree compiled with AMD optimizations turned on in gcc? Lots of questions can be asked. I have some servers running Athlon XP 1800+ processors and the kernel was compiled with -march=k6 since I specified a k7 processor in the make.conf. The machines would hang every few days. Once I recompiled the kernel with no -march flag (just straight x86) I have not had a problem (so far, knock on wood). I do not know where it was hanging up, since the machines are 4000km away from me right now, but they have not had a problem since I did that -- maybe you have a similar issue? best Chad To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. It's probably _not_ a FreeBSD issue. I'm running -stable on a dual AMD MP 1800+ system (Tyan 2466 motherboard), running XFree86 on a Radeon 8500 128MB card. No problems at all. And it screams. :-) -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
On Thu, 2002-05-30 at 19:31, Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. What video card/chip? Without this it's really hard to tell. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
I'll bet you wouldn't have any trouble running -stable on it. There was a problem with MTRR support which still needs a little fixing in order to shut down properly but that's nowhere near as bad as X not running. Fix should be in FreeBSD 4.6 as well. - Jordan On Thursday, May 30, 2002, at 17:31 US/Pacific, Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
On Friday, 31 May 2002 at 2:31:32 +0200, Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. This is rather simplistic logic. Firstly, it could be a hardware problem which Microsoft doesn't tickle. It could be any of a number of things. From this viewpoint, I'd say that the problem is you: you don't even say what happens. We can't debug like that. FWIW, I am running dual-headed X on an Athlon 1700+ based system. I've had no problems with X at all. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. There's a known problem with some of these processors; we discuss this every time someone with a lot of RAM uses an AGP card on one of these boxes, and doesn't use DISABLE_PSE. See the latest Linux release notes for details, if you aren't willing to run FreeBSD-STABLE, and install X from /usr/ports. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
At 10:26 2002/05/31 +0930, Greg 'groggy' Lehey wrote: On Friday, 31 May 2002 at 2:31:32 +0200, Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. Out of curiosity, is it an ASUS MB? There was a problem with some ASUS boards and X, which has been fixed--that is, if you do a cvsup, make world and recompile the kernel, X will work. If that was the problem well, then you could say the problem ~was~ with FreeBSD, but--it's been fixed. :) Scott Robbins To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
Jordan K Hubbard wrote: I'll bet you wouldn't have any trouble running -stable on it. There was a problem with MTRR support which still needs a little fixing in order to shut down properly but that's nowhere near as bad as X not running. Fix should be in FreeBSD 4.6 as well. The MTRR issue you're referring to, is this related to the one in the AMD errata docs about SMM TSEG and large page mappings? Which CPUs does this bug affect? Is it AMD specific at all? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sandboxing untrusted binaries
Hi Bjoern, On Thu, May 30, 2002 at 04:58:18AM +0200, Bjoern Fischer wrote: OpenBSD has a new interesting feature: systrace. It is a system call policy generator for sandboxing untrusted or semi-trusted binaries. The idea of sandboxing binaries is nice ofcourse but there is a conceptual drawback. I think you can divide the programs you run in two groups: the group of extra privileged programs which need that for changing passwords or for allowing users to log into their shell (ssh etc). the group of normal programs ran by a user interacting with the outside world like a browser. The problem is, a program needs privileges in order to perform its function. if this function is to change passwords, it needs privileges to actually change those passwords. The same thing goes for capabilities: you can finetune exactly what is allowed, but the main thing a program is supposed to do will still be allowed. If that program was ment to do something which requires root, and you disable everything else so the program can only do that little thing like changing passwords, an attacker gaining control of the process will still be able to do enough to hack the box. You can make it harder for him, but if the binary had to run with root privileges, and you disable all other privileges, an exploiter can still hack the box. If you could drop all privileges, the binary shouldn't be ran as root in the first place. This all goes for the first group of programs i just mentioned. The second group is more for trying to keep hackers from gaining local access. The examples provided by systrace are for this group of programs. But, the same concept applies: the binary needs to run local and access local files and even write to files. A webbrowser still needs to execute xpdf, the user still needs to be able to specify what program to run for pdf's. You can limit the possibilities, but, the minimal capabilities a program needs to function is always enough for a hacker. The whole idea looks interesting. The implementation details look relatively simple (read: not too complicated). Anyone interested in having a closer look and maybe porting it? I have coded similar things for linux, the main problem is the performance hit. For every system call, you will need to check against the policy and systrace even provides regular expression filters etc. This is a major performance hit for most daemons. Or I will try to port it myself if at least one core member says: Interesting technology, send a patch... I'm not sure if the performance hit will be worth the limiting of possibilities for hackers. They will still get in, it will only take a more specialized shellcode. Looking forward for others' views, Frank van Vliet [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
find(1) - peculiar behaviour
Hi, I'm writing a simple crontab script to automatically find and remove invalid symlinks. My initial ideas relied on readlink, etc., but looking more closely at find(1), I thought I saw a better/faster way to do it. I think my dilemma is best illustrated by example: [isometry@quadric:~/test]$ ls -l total 4 lrwxr-xr-x1 isometry isometry8 May 31 02:01 invalidlink1 - fakedir1 drwxr-xr-x2 isometry isometry 512 May 31 02:00 realdir1/ drwxr-xr-x2 isometry isometry 512 May 31 02:00 realdir2/ lrwxr-xr-x1 isometry isometry8 May 31 02:00 validlink1 - realdir1/ lrwxr-xr-x1 isometry isometry8 May 31 02:00 validlink2 - realdir2/ [isometry@quadric:~/test]$ find -L . -type l -print ./invalidlink1 [isometry@quadric:~/test]$ find -L . -type l -delete [isometry@quadric:~/test]$ ls -l total 4 drwxr-xr-x2 isometry isometry 512 May 31 02:00 realdir1/ drwxr-xr-x2 isometry isometry 512 May 31 02:00 realdir2/ [isometry@quadric:~/test]$ The problem is that `find -L . -type l -print` reports only the dud symlinks, but `find -L . -type l -delete` removes ALL symlinks... which is clearly not the desired behaviour. Obviously, I could just use `find -L . -type l -print | xargs rm` but that's two more execs, which being a scrooge isn't what I want ;) Can anyone see what I'm doing wrong, devise a superior solution or suggest a patch to fix this behaviour in find(1) ? Thanks in advance, - Robin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: find(1) - peculiar behaviour
I wrote:
The problem is that `find -L . -type l -print` reports only the dud
symlinks, but `find -L . -type l -delete` removes ALL symlinks...
which
is clearly not the desired behaviour.
I've just realised this is mentioned under BUGS in man 1 find, so my
query changes to: anyone fancy fixing it and/or giving me some
pointers on how to fix it, or maybe suggest a better way for me to do
this?
find -L . -type l -exec rm '{}' \; strikes me as likely to be the
fastest alternative... though it's not very pretty ;)
- Robin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: find(1) - peculiar behaviour
On Fri, May 31, 2002 at 03:33:18AM +0100, Robin Breathe wrote:
I've just realised this is mentioned under BUGS in man 1 find, so my
query changes to: anyone fancy fixing it and/or giving me some
pointers on how to fix it, or maybe suggest a better way for me to do
this?
find -L . -type l -exec rm '{}' \; strikes me as likely to be the
fastest alternative... though it's not very pretty ;)
That's likely to be more forks and execs than the xargs version,
O miserly one. :-)
--
Ben
An art scene of delight
I created this to be ... -- Sun Ra
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Improving GNU make compatibility in BSD make (+ patch)
The GNU make info file says:
`$^'
The names of all the prerequisites, with spaces between them. For
prerequisites which are archive members, only the member named is
used (*note Archives::). A target has only one prerequisite on
each other file it depends on, no matter how many times each file
is listed as a prerequisite. So if you list a prerequisite more
than once for a target, the value of `$^' contains just one copy
of the name.
`$+'
This is like `$^', but prerequisites listed more than once are
duplicated in the order they were listed in the makefile. This is
primarily useful for use in linking commands where it is
meaningful to repeat library file names in a particular order.
The make(1) manpage says:
.ALLSRC The list of all sources for this target; also known as
`'.
So BSD make interpreting either `$^' or `$+' as its own `$' would improve
compatibility with GNU make Makefiles. I am just not sure which of the two GNU
make variables maps better to our `$'. This patch implements the former:
--- var.c Sat Apr 13 03:16:56 2002
+++ var.c.new Thu May 30 19:32:01 2002
@@ -1489,6 +1489,8 @@
name[0] = str[1];
name[1] = '\0';
+ if (name[0] == '^')
+ name[0] = '';
v = VarFind (name, ctxt, FIND_ENV | FIND_GLOBAL | FIND_CMD);
if (v == (Var *)NULL) {
--
Jos Backus _/ _/_/_/Santa Clara, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
HSFLinModem: Anyone want to help teach me how?
Hello, I've just joined this list in the last few days, but was wondering if anyone out there wanted to help teach me how I/we could port the HSF LinModem code from LINUX to FreeBSD. I have one of the recognized PCI ID's in my Laptop, but don't even know where to start with interfacing with the FreeBSD kernel. I'm willing to do it, but I've never done Kernel programming before. I'm also very willing to help test. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
I haven't read the AMD errata docs so I can't comment on that, but it appears to be an issue with AMD CPUs and certain support chipsets, I believe the early VIAs. Reading the cvs logs for the MTRR support code will certainly yield more detailed information (and author attribution) than I've provided. In fact, here, I'll simply do it for you. :-) RCS file: /home/ncvs/src/sys/i386/i386/i686_mem.c,v Working file: i686_mem.c head: 1.14 revision 1.14 date: 2002/04/14 20:13:08; author: dwmalone; state: Exp; lines: +53 -32 Make the MTRR code a bit more defensive - this should help people trying to run X on some Athlon systems where the BIOS does odd things (mines an ASUS A7A266, but it seems to also help on other systems). Here's a description of the problem and my fix: The problem with the old MTRR code is that it only expects to find documented values in the bytes of MTRR registers. To convert the MTRR byte into a FreeBSD Memory Range Type (mrt) it uses the byte value and looks it up in an array. If the value is not in range then the mrt value ends up containing random junk. This isn't an immediate problem. The mrt value is only used later when rewriting the MTRR registers. When we finally go to write a value back again, the function i686_mtrrtype() searches for the junk value and returns -1 when it fails to find it. This is converted to a byte (0xff) and written back to the register, causing a GPF as 0xff is an illegal value for a MTRR byte. To work around this problem I've added a new mrt flag MDF_UNKNOWN. We set this when we read a MTRR byte which we do not understand. If we try to convert a MDF_UNKNOWN back into a MTRR value, then the new function, i686_mrt2mtrr, just returns the old value of the MTRR byte. This leaves the memory range type unchanged. I'd like to merge this before the 4.6 code freeze, so if people can test this with XFree 4 that would be very useful. PR: 28418, 25958 Tested by: jkh, Christopher Masto [EMAIL PROTECTED] MFC after: 2 weeks - Jordan On Thursday, May 30, 2002, at 06:41PM, Darren Pilgrim wrote: Jordan K Hubbard wrote: I'll bet you wouldn't have any trouble running -stable on it. There was a problem with MTRR support which still needs a little fixing in order to shut down properly but that's nowhere near as bad as X not running. Fix should be in FreeBSD 4.6 as well. The MTRR issue you're referring to, is this related to the one in the AMD errata docs about SMM TSEG and large page mappings? Which CPUs does this bug affect? Is it AMD specific at all? -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Does FreeBSD have a problem with some AMD processors?
Frank Mayhar writes: Morsal Rodbay wrote: I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt run XFree. Everything worked well besides X. Since a workstation without X is useless I was forced to switch to WinXP and it's very stable so there is nothing wrong with the hardware which means it's a FreeBSD issue. It's probably _not_ a FreeBSD issue. I'm running -stable on a dual AMD MP 1800+ system (Tyan 2466 motherboard), running XFree86 on a Radeon 8500 128MB card. No problems at all. And it screams. :-) ???!!! Please! I have a lot of troubles with Tyan 2466! Are you ising onboard ethernet? My system hangs immediatly when try ifconfig. Can you boot with SCSI controller? I change this mobo for a singleprocessor one but want to try more. I try UP STABLE kernels from 15-Feb-2002 to about 10-May-2002. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
broadcast packets not reaching sender on if_hwassist capable interfaces
Hi, I was chasing an interesting problem in our FreeBSD 4.3 codebase today. Broadcast IP datagrams were not being received by programs on the same system the IP datagrams were sent from. They were making it out the wire. The were being sent on a Broadcom GigE interface that has hardware checksumming. After a while we realized that what was happening was that the packets were being marked for hardware checksumming in ip_output (m-m_pkthdr.csum_flags), but the decision about looping a packet back to ourselves is made in ether_output, so the packet is never checksummed and is discarded in ip_input. Has this been fixed in a subsequent release? Also, why is the decision to loop the packet back made in ether_output rather than in ip_output? Off the top of my head I can't see any particular advantage, but perhaps there is. The disadvantage is that I will have to disable hardware assist for broadcast packets to make things work right. Regards - Richard Sharpe, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
