Re: OT: Domain Registration
On Tuesday 25 April 2006 12:44, [EMAIL PROTECTED] wrote: > Hi All, > >I know this is off topic, but I can't think of a good place to ask this > where knowledgable people will answer, and this list usually has a high > tolerence of ot but technical questions (plus I will be using a FreeBSD > server, so it is not _entirely_ OT :) > >I'm looking to setup my server as a domain name server. I already have > it setup for internal use, but last time when I tried to have the > internet at large using it, I had real trouble explaining to my ISP > that I wanted my server as the main domain controller, the best they > could do was pointing www.domain to my server. They wern't even > able/willing to point the mx record directly to my server, it goes > through their relay first. > >It has done the job so far, and there is really no reason why I can't > manage with this, but I am getting a new domain and would like to get > it all sorted out the way I would like (my main justification for > hosting it myself is the flexibility to add on sub-domains and such, > but the real reason is that I am a control freak and like to tinker). > > I assume what should happen is > > - I buy a domain from registrar X > - X sets that domain to point to my dns server as the master server > - X hosts a secondary dns server > - I can then add subdomains to my domain which will directly > propagate on the internet, set the various MX and ilk to whatever I > want etc. without having to contact a 3rd party > > My further assumptions are > - The secondary server will either update from my server directly OR > I will need to contact X to add anything new for me. > > My questions are - > a) Are my assumptions correct? > b) What would be the best way to explain this to a phone drone? > c) Can anyone recommend a good registrar that will be able to set > this up with minimum fuss (and cost)? > d) Are there any good reasons not to do it this way (remember, this > is not a mission critical setup, and its main purpose is to tinker) > > > Regards, > Martin McCann > Thanks for all the input - I decided to go with the suggested registrar gandi.net, I picked my domain, and paid the 14 euros fee. It set up automatically with its own dns servers and pointing to its own hosting address. After that, it was a very simple process of logging in, entering my server as the primary dns server, plus its suggested secondary, and after a period of time (less than 8 hours) voila, it is all working. I now have everything working the way I want and it took very little effort. I need to do a few more checks to make sure I havn't overlooked anything, but it all looks grand atm - if you are looking for a no nonsence, just give me what I want type of setup, I would highly recommend them. I'm now going to transfer my origional domain over to them and get that setup to my tastes too. I think I may also consider taking a backup of my server setup ... :) Thanks again, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nss_ldap/pam_ldap: problems binding
Hi, I've been trying to get my ldap authentication working, something I have done before with little issue, but this time around it is causing real pain. Pretty much the same problems Jan HREHO was having back in Febuary - http://lists.freebsd.org/pipermail/freebsd-questions/2006-February/112066.html I tried the suggested solution to that - moving the slapd startup script into /etc/rc.d, but that didn't help, same problem just further up in the boot process. Another possibility I came across was putting the line 'bind_policy soft' in /etc/ldap.conf (symlinked to /usr/local/etc/ldap.conf & /usr/local/etc/nss_ldap.conf). This seemed to do the job, until I then tried to ssh onto localhost using an ldap user account. It failed with Apr 19 22:48:10 svr1 sshd[660]: nss_ldap: could not search LDAP server - Server is unavailable Apr 19 22:48:10 svr1 sshd[660]: fatal: login_get_lastlog: Cannot find account for uid 2000 Removing the bind_policy from the file then retrying, it worked fine. The second solution I tried was to change the slapd.sh file to just launch the deamon i.e. '/usr/local/libexec/slapd'. This seems to work, but it is very unelegent, and it may have knock on effects I am unaware of at this time. I'm more interested in getting the process right to set it up at this stage, rather than hacking away to get a working system (I'm working on a series of documents). I'm doing this on a virgin 6.0 installation, cvsuped with the latest ports, fresh install of openldap22, pam_ldap and nss_ldap. So the question is, is this a common problem, if not then what I am doing wrong to create it, if so then is there a more elequent solutions than hacking away at the startup script? The thread that suggests the bind_policy also mentions 'nss_reconnect_* parameters', which certainly sounds like it could be the answer, but I havn't been able to google anything about them. Cheers, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Creating bootable DOS floppy w/FreeBSD
On Wednesday 16 November 2005 18:32, Doug Poland wrote: > Hello, > > I'm stuck... I need a bootable DOS floppy (for BIOS upgrade) to fix a > broken Windows box. > > I have no problem formatting and putting an msdosfs on a floppy but it > appears I cannot make it bootable with native tools. > > I tried emulators/mtools mformat, but it doesn't create bootable media. > I even installed emulators/qemu and installed Win98 into it but format > fails trying to format the host's floppy. > > I'm in a bit of a time crunch here, does anyone know how do create a > bootable DOS floppy using just FreeBSD and/or it's ports? do a google on bootable floppy images, there are quite a few about, then dd the image you download onto your floppy disk Cheers, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ASUS A8N-SLI raid Question
Hi all, I've recently updated to 64 bit (spending way to much money in the process!) and want to get freebsd 6.0 64 bit installed. I am running windows 64 on it (the main reason for the upgrade was games) so it will be dual boot. I have freebsd on a 32 bit system on a kvm switch, so it is not essential to get it on the 64 bit system, but I would like to give it a go. My specific question is, the install doesn't seem to pick up the raid, it comes up with ad12 and ad14, reporting both as 80 gig drives, as opposed to the 160 gig raid-0 it should see. Any suggestions on that? My other question is just feedback in generally, anyone out there with experience installing 64 bit 6.0 version on an nforce 4 mobo, and any problems I might encounter? I am assuming there are no drivers for SLI mode, is this right, and any sign of them on the horizon? Cheers, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: command question..
On Thursday 08 September 2005 22:12, Eric Murphy wrote:
> Hey guys heres a quick question for you...
>
> I am trying to ping a certain website with the following command . ping
> yahoo.com
>
> I would like to log all requests that come back higher then 100 or any #
> i specify.
>
> I figured I could use the script command but im not sure how to go from
> there?
>
> Reason for this is to prove to my ISP that there is something wrong with
> my connection :)
>
> Would it also be possible to log the date and time of each requets?
>
> So inconclusion I'd like to log all icmp requests that come back higher
> then 100 by date and time into a log file.
date > pings.txt ; ping -c 10 www.yahoo.com | awk '{ print $7 ; }' | sort >>
pings.txt
this will give you a file with the date then the pings sorted from quickest to
slowest. Plenty of scope to make it nicer, but it gets you the info you want.
(You will probably want to increase the count, but I would also add a delay,
-i, it will give you a better range and also it is not nice to fire a lot of
pings to a public server).
Martin
>
> Thanks
>
>
> ___
> 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: Anthony's drive issues.Re: ssh password delay
In a final effort to resolve this issue - It is widely agreed that anthony's issue lies in a custom chipset for his hardware. It is widely agreed that anthony is not willing to put any effort into trying to verify this. If is widely belivied that the person who could answer these queries conculsively is not on this list. It is widely belived that anthony is more interested in arguing his point (in fact, any point) than he is in resolving his issues. Therefore, in order to keep this list a sane and useful resource, I would suggest that if anyone feels like answering anthonys queries, they do it to his personal email address, so the rest of us might get on with other issues, and not scare new comers away with this bad blood (I am aware I have sent a fair few comments on this threat, and the more I did, the more I realised the futility of it). I'm here to learn about FreeBSD, not to hear about how many decades of experience Anthony has, nor what he thinks of others on this list, and certainly not an endless stream of his rants about his crappy hardware. Hoping to get back to a sane list soon, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 23:25 +0200, Anthony Atkielski wrote: > Bart Silverstrim writes: > > > Um...because it took an adapter that generically had worked, but after > > modifying it didn't? > > It was referenced by an OS that generically worked, but then did not > after the modification of the adapter. So what are you saying? Origional, it worked with NT, but then didn't with FreeBSD. NOW you are saying, it working with 'OS' before update, now doesn't work with 'OS', after update. So, I have to assume you had the same OS at this point, which makes your whole arguement a lie. > > I have an old 68k mac laying here...think I can install > > AmigaDOS on it? > > I don't believe so, but it has been a long time. Conjecutre? I thought we didn't do conjecture Why the hell do you not know? what the fuck are you doing on this list if you do not know You must know everything!!! I have a problem and I demand that you solve it! Right fucking know, or I will take up every thread in you goddamn list with my tantrum until you do! > Note that it has not been established that any particularity of the > adapter firmware is at the root of this problem. The meaning and cause > of the messages and behavior I'm seeing remain unknown. > > > I and others on the list have suggested numerous times things like > > self-contained Live-CD's of Linux/FreeBSD, or USB-bootable versions, > > or talking to the actual developers instead of a USER MAILING LIST > > (Not DEVELOPER), or swapping the controller out and get matching > > drives to test against, or even paying someone to fix it with your > > hardware to test on, or just going back to windows so you can ignore > > the problem in the first place ... > > The one thing you have not done is explain the meaning of the messages > I've seen. > > > As far as this list is concerned, it's not gonna happen. > > I'm not optimistic, but one never knows. > Aren't you the same person that said MS changed features specifically > > at your request, but you didn't remember what they were? > > Yes. Convienient. > > > If so, you never did answer me on how you could have forgotten what > > that feature was. > > It was quite some time ago. Much water has passed beneath the bridge. I doubt many people here would request a feature for MS, have it granted, then forget what that feature was. Smackes of a lie if you ask me. > > You couldn't figure out why someone would suggest testing a problem on > > another bit of identical hardware to isolate if it was a hardware > > problem or a software problem? > > Someone might suggest that in order to seem knowledgeable, rather than > admit that he has no clue as to the source of the problem. Or it could to try to be helpful, rather than saying, don't know, go away. But no, you have to take the cynical route, and believe it is a fault, rather than a virtue, which makes them do this. Says more about you than it does them. > > > How long have you been a sysadmin? > > Overall I have a fair number of years of experience in that capacity. > Currently I only administer my own systems. Well, you are showing many user traits, and not many sys admin traits. User = "I don't like this, you must fix this". Sys admin = "This is crap, how can we fix this". > > > Get the multithousand dollar support contract with them, run exactly > > what they tell you to run, and you'll be happy with the support they > > would give. > > I don't think they'd approve of FreeBSD. Then don't use it, don't whine to this list about it. > > > how long have you been doing this, anyway? > > A couple of decades. Maybe past your prime? > > > I heard a similar type of argument from a five year old. > > Small children have a way of getting straight to the point that their > elders might sometimes do well to emulate. Ah, so all those comments about this list being full of children was a compliment. Why thank-you. > > > I've had several machines where distro X wouldn't work but Distro Y > > did. But by your logic, this isn't possible, right? > > I haven't tried any other distributions. I don't know the source of the > boot problem, so it's hard to say. Perhaps some flaming is in need then? > > > You're right. You're getting much farther by insulting people and > > being obstinate when given suggestions. > > Apply that same logic consistently, and you'll see the source of my > frustration. Hah! You claim logic. Read back on your past posts. > > > What a dichotomy to your insults of FreeBSD developers. > > Dichotomy? Why does a man of your decades of experience have to ask a FreeBSD mailing list the meaning of a common english word? http://dictionary.reference.com/search?q=dichotomy > > > You mean, it could be buggy or have problems that are "ignored", but it > > still "works" anyway and gets the MS stamp? > > Yes. > > > But, how could this be? > > The certification tests are not exhaustive. > ___
Re: Anthony's drive issues.Re: ssh password delay
> No, I was referring to the additional modularity and stability made > possible by the additional abstraction of a HAL. > Please explain this to me - I have had a lot of experience in OS design, and would like you, who obviously from you remarks, have extensive OS design knowledge, point out to me how a HAL makes an OS inherintly more stable than a system that writes its drivers for a particular peice of hardware, without pretence it will cope with differetn pieces of hardware? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 23:13 +0200, Anthony Atkielski wrote: > Bart Silverstrim writes: > > > That's nice. I wasn't talking about NT there. I was talking about > > DOS. > > I'm not running anything named DOS. > > > Command line, popular before Windows but after CP/M...maybe > > you've heard of it? > > I used to run a few operating systems by that name. > > > They're trying to help troubleshoot over the list. > > Why don't they just suggest that I move to another city, in case there's > RF interference in my neighborhood. That's troubleshooting, too, but > like swapping hardware, it's not very practical, and you don't start > with the impractical methods if you have no idea what's wrong. So, you start by demanding your individual problem is resoloved by a list who has no responsibility to the upkeep of the software that has given you issue? > > > Did you pass science class? This would show if it's reproducible as a > > bug. > > Nobody even knows what the messages mean. Without knowing that, what > use is it to try to reproduce it on another machine? You have repeated this time and time again. No-one is argueing with you. I think it is safe to assume no-one knows excactly what the message is about. Many people have tried to help by applying their high level of knowledge to the situation, which you have lambasted. Accept that no-one on this list knows, and move on. > > > Slap it on the same damn hardware, *right down to the firmware* > > (remember you have modified firmware?). If it isn't running on two > > machines that are exactly the same, that shows an increased chance that > > that is indeed a bug in some driver, and you should contact the driver > > maintainer. > > What if the messages don't represent an error? As you have said, no-one here knows, move on. > > > It's troubleshooting by eliminating variables. > > It's rolling dice unless you first determine what the messages mean. As you have said, no-one here knows, move on. > > > Bzzt. Wrong. Not if the hardware is going bad or has a problem. > > There's no reason to believe that the hardware is going bad. There is reason to belive it. It doesn't mean that it is going bad, but it shows that there is reaseon to suspect that it could be going bad. > > > See, in our magical and mystical world, we need to be able to > > reproduce the problem in order to help. > > How do you know it's a problem? You don't know what the messages mean. > > > Otherwise we have to troubleshoot and speculate. > > All anyone has done thus far is guess. Yes, tried their best. No-one knows, if people trying to help you to the best of their knowledge isn't good enough for you, pay someone, then you can shout at them as much as you like. > > > You know, the things you insist we don't need to do. On > > top of that, you never even commented on the possibility of someone > > being able to FIX your problem *IF IT IS* a FreeBSD software problem > > WITHOUT THE DAMN HARDWARE on which to test the fix. Sheeyit! How can > > I fix something on a configuration that I don't even have? > > By examining and modifying the code. Developers do it all the time. > > > Wow, how long have you worked in the field as a troubleshooter? > > I spent a number of years in that capacity. Sad to say you are probably right. Most people I work with in the I.T. field know the score, that not everything works as documented all the time. Some though, will waste weeks and months lamenting the fact that it doesn't rather than moving on. Consider if you will the impression you might give to a future employer who does a google search on your name. > > > So...unless everything is handled exactly as you wish it, unrealistic > > or not, by volunteers no less, it is a waste of your time. > > No, unless people follow a logical course of action to isolate the > problem, if there is one, then they waste my time. Hah. You are following a logical caouse of action? You have spend more time critising this list, and boasting about your own merits, that you have trying to resolve this issue. > > > And here I thought it was because it uses a PPC. > > My computer uses Intel hardware, but FreeBSD seems to have a problem > with it. So it is now intel hardware causing the problem? Pleas repeat what the error is coming from. > > > Your turn. Pull out that shit controller and set of drives, put in new > > drives and a new controller that's generic instead of modified, and > > see if FreeBSD works. > > Tell me what the messages mean, first. As you have said, no-one here knows, move on. > > > Then fix it. Or pay someone to. > > I don't have the time to examine the source. Then move on, and stop throwing a tantrum. > > > In the length of time you've spend insulting people on this list you > > could have swapped out the drives and controller and probably have > > things working already. > > Hmm. Exactly. > > > It did, it used an IR interface to do the transfer
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 23:03 +0200, Anthony Atkielski wrote: > Bart Silverstrim writes: > > > It's deduction. > > It can't be. There's nothing to deduct from. Exactly, because you have time and time again refused to put any effort into deducing anything. It, as you have said, is the fault of the people who subscribe to this list. You seem to disregard the fact that you, as a subscriber to this list, are as much as part of it as anyone else. Every derogatory comment you make to this list, you aim towards yourself, you are no more or less a part of this list than anyone else. > > Tell me again what those messages said, exactly? > > > Really? I have a free program running on my NT machines, ntpdate I > > believe is the name, that just hammers the registry with requests > > constantly. I'd never have known it was querying it so much if it > > wasn't for regmon. *Contant* hits. dunno why, doesn't seem to hurt > > anything...thus I ignore it. NT doesn't seem to care. Only gets in > > the way when I'm troubleshooting registry errors. > > So where's the problem? > > > I've already told you I had a scsi bus reset problem what showed up > > under Linux but not NT several years ago. But you probably ignored > > that. > > Did someone fix Linux? > > > I've had power supply fans that have lasted for years despite making > > odd noises that are indicative of impending failure. It's not unheard > > of. > > Years without a failure is not impending failure, no matter what noises > you hear. > > Some fans are inherently noisy. > > > That's nice. Some hardware is being a pain. People here either ignore > > you at this point or tell you to replace that controller and/or disks > > and see what it takes from there. > > Yes. But I'm still hoping that someone might provide a truly useful > answer sooner or later. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 23:00 +0200, Anthony Atkielski wrote: > Bart Silverstrim writes: > > > From the way you were complaining, I had the impression that MS was > > bending backwards to help in issues while the FreeBSD people were > > immature children. > > They do a much better job than the FreeBSD project does, no doubt about > that. then stop complaining to a list of 'kiddies', and use that. > > > Is this evidence to the contrary, that MS isn't the > > pinnacle of perfection in dealing with every software issue? > > No, it's evidence that you never talk to developers when you call the > support line. > > > http://en.wikipedia.org/wiki/FLOSS > > Thanks. Just today I was hoping for some new acronyms, it's been hours > since I last encountered one. If you have never encountered the term FLOSS, you are not the open source user you claim to be, it is a common term. > > > Especially in projects driven by money and politics in a workplace, and > > with looming deadlines. > > Yes, but also in projects with no profit motive at all. Many developers > love to write code, but hate to design and test. So they bloat what > they write just for their own enjoyment. > > > You can do the job to get it shoved out the door or do the job right. > > Doing it right often means doing it at a loss. And what open source developer does anything but 'doing it at a loss'?. > > > B) The "More popular thus more exploited" is a crap argument. > > The statistics seem to support it. Statistics will prove whatever you want it to prove, most people with intelligence look beyond the given conclusion, and make their own. > > > Windows was "designed" for single user non-network desktops. > > Not Windows NT and its successors. They were designed as network-aware > multiuser desktops. They originally had a strong server emphasis, > although that has gradually shifted back towards the more profitable > desktop, to the detriment of server environments. > > > That "30 year old UNIX" was better designed for network sharing and > > multiple users in scant resources. > > Yes. Unfortunately it's a poor desktop. Depends on what you want as a desktop - desktop != WIMP. > > > If apologists would get their heads out of their butts they'd see that > > it isn't always "There's more Windows, thus easier to exploit!", it's > > "Windows' design is inherently less secure, so it's easier to target!", > > as well as a healthy dose of "the average Windows user is more clueless > > than the average Linux user!" thrown in to boot. > > It's a bit of all of these, but mostly the number of installed seats and > the fact that it's a desktop used by unsophisticated users. > > > Many of the features in the recent "The Road to Windows "Longhorn" > > 2005" article on Paul Thurrott's Supersite for Windows seems oddly to > > match many of the features already available on OS X... > > Many features of OS X seem oddly to match many of the features > already available on Windows. Alternatively, many of the features of windows seem to match those of already available software. > > > Hmm, wonder why...could it be because of the security imposed by > > "UNIX" under OS X that makes that kind of model a decent tradeoff of > > usability and security in the first place? > > I have to smile when I hear UNIX held up as an example of a secure > system. In the land of the blind, the one-eyed man is king, I suppose. > > Current Windows systems have a much stronger security model than UNIX; > it just isn't used, because users wouldn't be happy if they had to deal > with it. So what defines a secure system, if not the fact it is less prone breakens? > > > If it wasn't such a pain in the butt for Joe Sixpack to use, ideas in > > EROS would help a helluva lot more on the desktop for security. > > Security is an inconvenience. Users want mindless interactions. > > Somewhere it meets in the middle in order to be usable. > > Yes. But this isn't a problem with the OS. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hyper threading.
On Tue, 2005-03-29 at 22:20 +0200, Anthony Atkielski wrote: > [EMAIL PROTECTED] writes: > > > Thats because you seem unable to grasp modern concepts. > > None were under discussion. As far as you can see, which shows the limit of your percption. > > > If you think that performance criteria > > of modern controllers and processors are the same > > as 30 years ago, then you are incapable of commenting > > on anything modern. > > The principles of "modern" controllers are surprisingly similar to those > of "old" controllers. The biggest change is that the PC world is only > now discovering what mainframe designers knew 40 years ago. Bollocks. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
> I'm not that interested in running Linux. Linux is for kids. > This pretty much sums up your attitute. Most people on this list use the right tool for the right job, they are not interested in labeling a piece of code for 'adults' or for 'children'. I am sure IBM, SUN, and plently of other highly profitable companies would disagree with your assertion, but they are probably wrong too, hmmm? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 22:16 +0200, Anthony Atkielski wrote: > Martin McCann writes: > > > And how do you write software that will be able to communicate with > > hardware, irrelevent of what changes have been made to that hardware? > > The hardware and software must agree on a minimum set of standards. > That is how standards work, and when a piece of hardware goes beyond those standards either through design or mis-implementation, who is to blame? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
> > Or had whatever extra code was needed for the microcode mods. > > Yes, or approached the hardware in a way that made the modifications > irrelevant. And how do you write software that will be able to communicate with hardware, irrelevent of what changes have been made to that hardware? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 20:50 +0200, Anthony Atkielski wrote: > Chris writes: > > > No - NOT the PC - the hardware that's in question. The Adaptec WITH the > > modified code. I'm willing to bet, it's not. > > Should I check for restrictions on chipset temperature, relative > humidity, and atmospheric pressure as well? Of course you should - if you are running it somewhat out off the ordinary, you should check that it will run with your peculiar setup. I think a bespoke hardware modification fits the bill perfectly for out of the ordinary, and so would require extra verification. I suppose if you where to run it at high temperatues, or a very humid environment, and the os throw up some errors, that would be the OS fault as well, since your hardware is above reproach? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues.Re: ssh password delay
> > No, I'll be told that as long as I'm dealing with children instead of > adults. this is around the fith time recently you have either insinuated or outright claimed that the participants of this mailing list are all immature children. And yet you return time and time again asking for help. What does this say about you? You have now also started taking your attitute into many other threads, making it very difficult to sift through the techunicaly relevent and helpful threads thanks to your inability to control your tantrums. You are spoiling this list for the people who would like to work together to solve their problems. Yes, you can be kill mailed, but that will not remove your replies. It looks like the only solution is to filter out any mail containing your name anywhere in the text (even this is not fool proof due to unquoted citations), and this will mean that many useful or genuine mails will be filtered also due to having your name in it. Yes everyone on this list are immature children, and yes no-one will listen to any objective critisism of their mightly religious icon FreeBSD. Any problem anyone gives is obviously the fault of other people because FreeBSD is perfect. Now that you have agreement, please be on your way to find the adult company you seek. Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anthony's drive issues
In an effort to try to stop this list from becoming Antony personal
anger outlet forum, I would like to put in my 2p worth.
Antony is displaying typical bully boy tactics - aggressively attacking
any response that does not coincide with what he want to hear while
throwing out and endless stream of pugnacious remarks ('immature
teenagers', 'secret tree house club' etc.). It seems either he has a
inability to communicate with any degree of sophistication, or he is
uninterested in the answer and is merely trolling.
Antony: Your annoyance seems to hinge on the fact that you have asked a
question, and not been told how exactly how to fix it to your liking.
When given possible solutions, you answer with sarcasm and rudeness,
rather than a polite 'thanks, I tried that, but it didn't help' etc.
I speak for myself, but I am sure there are a large amount of people of
a similar disposition on this list - I am on this list primarily to get
answers. If a question is asked which I think I can help with, I will
answer. If not, I will not say a word (I am sure no-one would like to
see 300+ 'I don't know' replies). I will answer becuase I have a natural
tendancy to try to help people. That tendacy disappears very fast when I
start to dislike someone, and making sharp rude and arogent replies is a
very quick way to be disliked.
You continuely compare the level of support of FreeBSD to Windows and
other corporate products. That is a void comparison. They support you
because that is what you paid for. No-one is paid to support you, and
while I am sure there are plenty of people who would like to push
FreeBSD into higher usage, I could not care less who else is using it
(again, I am sure I am not alone in this), and would rather see less
people with your attitude using it.
Stop running around yelling its not fair that people won't play by your
rules, and get over yourself. Take a breather, come back and show a bit
of respect to the people you are asking for help, or don't come back.
Regards,
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
