Re: pf not seeing inbound packets on netgraph interface
Thinking -pf@ or -net@ would be a better place to discuss this, more chances of getting an answer. Out of curiosity why not use a gif interface ? I had that working just fine with racoon and was able to actually firewall traffic on it with PF, iirc.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Overwrite uncorrectable error LBA?
Smartctl is reporting an uncorrectable error for one of my disks: === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K2000 Device Model: Hitachi HDS722020ALA330 Serial Number:JK1130YAHXN28T LU WWN Device Id: 5 000cca 221db1d3f Firmware Version: JKAOA28A User Capacity:2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is:Tue Jan 3 09:38:46 2012 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled ... 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 1 ... Error 25 occurred at disk power-on lifetime: 7362 hours (306 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 68 d0 cd d0 00 Error: UNC at LBA = 0x00d0cdd0 = 13684176 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- 60 ab 60 90 d3 d0 40 00 33d+04:43:22.635 READ FPDMA QUEUED 60 ab 58 e5 d2 d0 40 00 33d+04:43:22.634 READ FPDMA QUEUED 60 ab 50 3a d2 d0 40 00 33d+04:43:22.634 READ FPDMA QUEUED 60 ab 48 8f d1 d0 40 00 33d+04:43:22.634 READ FPDMA QUEUED 60 ab 40 e4 d0 d0 40 00 33d+04:43:22.634 READ FPDMA QUEUED I'm reading this as LBA 13684176 being the one uncorrectable error. Since this disk is part of a ZRAID1 pool, I'd just overwrite that LBA to have the disk remap it, but I'm not sure how to address it properly: dd seemingly reads that LBA without problems? # dd if=/dev/ada0 iseek=13684176 count=1 of=/dev/null 1+0 records in 1+0 records out 512 bytes transferred in 0.025676 secs (19941 bytes/sec) I would have expected the disk to either take a long time or respond with an I/O error outright. Am I looking at the right LBA? I currently have a zpool scrub running, and I will start a long test after that just to make sure there's no further problems hiding. Any other suggestions? Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: nss_ldap and the linuxulator
Hi, if you look at the message of the linux base port, you will see that this part is discussed there. FreeBSD does not come with ldap by default, so does the linux base port. So far nobody complained loudly about the lack of a nss ldap port for the linuxulator, and nobody felt the pressure to create such a port and talk about it on the emulation list. Anyone who uses ldap in the linuxulator is free to create a corresponding port, quesions in case of problems creating such a port can be asked on the emulation mailinglist. Bye, Alexander. -- Send via an Android device, please forgive brevity and typographic and spelling errors. per...@pluto.rain.com hat geschrieben:Forwarding to emulation@, which is where the linuxulator gurus hang out (AFAIK). Please keep Da Rock in the Cc: Date: Mon, 02 Jan 2012 21:59:57 +1000 From: Da Rock freebsd-questi...@herveybayaustralia.com.au To: freebsd-questions@freebsd.org Subject: nss_ldap and the linuxulator I've just run into this snag again which I've resolved back in 7.x/8.1: the linuxulator cannot handle nss lookups from ldap. I ran a search for nss_ldap fedora 10 and simply extracted from the rpm the libnss_ldap*.so* in the usr/lib into the corresponding directory under /compat/linux. One then only has to copy or setup the ldap.conf in /compat/linux/etc/ and change /compat/linux/etc/nsswitch.conf so the it will check files and ldap as in the base. It works a charm when you have issues like the missus with acroread and others not working inexplicably. Run acroread from the command line will give you the clue: getpwuid_r(): failed due to unknown user id. This solution does fix this categorically. I hope this helps others, but I do have one question: why isn't this included in the ports already? I still haven't yet figured out cups and printer selection yet, but I have made some progress... :) Cheers ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: I have a Toshiba Satellite U505-S2950 laptop with a Realtek RTL8191SEvB wireless card built in. FreeBSD doesn't recognize this card and can't use it, but Ubuntu does. Would it be possible to go glom a Linux driver off the web someplace and install it in my FreeBSD and get the wireless to work? I'm using a USB Belkin in it now, but that's an unhandy thing sticking out like it does. Unfortunately the API's are completely different. Adrian Chadd does a lot of work on Wifi in FreeBSD, but I'm not sure if its on the todo list or not. Try a search on google... This is what drives me to pull my hair out. I have stated several times that all the *nix/*BSD consortium needs to do to become truly competitive in the market is to devise a uniform API that works the same on FreeBSD as on Ubuntu and every other non-windows based system. The concept is so simple that it amazes me that it was not implemented eons ago. The problem is that the non-windows operating system authors all behave live little children. None of them can simply get along. The all have to insist that they have the best and everyone else is wrong. They swing between Narcissism and Paranoia on any given day. You would have an easier time getting a Jew and a Muslim to sit down at a table and enjoy a ham dinner than you have of getting the powers that be in the non-windows community to agree to anything, other than their hatred of Microsoft of course. I have spoken with representatives of companies, the last one being Brother International, who plain out stated that they only support Microsoft (naturally - they offer the easiest and best documented system for driver installation) and a vanilla Linux solution. They openly stated that there is no way that they would even attempt to write software for a market as fractured as the *nix/*BSD community and then be straddled with the problem of supporting such software. Hell, every time someone in the BSD community dotted an i in the kernel source code the poor driver authors would have to rewrite their device code. Certainly a task I would not want to be assigned. Ubuntu is years ahead of FreeBSD in creating a useful and fully functional desktop, I read where they were working on making it possible to use a driver disk intended for Microsoft's Windows OS usable in Ubuntu. They were working on a method of simply extracting the code needed directly from a CD and using it directly on Ubuntu. Now that is what I call true forward thinking. The authors of FreeBSD, and to a lesser extend Linux remind me of group of of passengers left floating in the ocean after their ship sank. The best case scenario at that point would be to be rescued by another passing ship. However, while waiting for that to occur it would seem logical to grab onto any object that floated by and thereby allow the stranded individual a better chance at survival. If these were Ubuntu survivors there would be no question as to what they would choose to do, as well as some of the more enlighten *nix users. However, the *BSD users, especially the FreeBSD ones would rather drown than accept a solution that was not counter to what everyone else was trying to accomplish. I have, mistakenly I admit, stated that there are no drivers for lots of devices currently available on the market, especially the higher end ones. That statement is essentially incorrect. There are drivers for these devices, and other OSs are taking advantage of them. FreeBSD, in its unending war against simplicity and continued insistence on reinventing the wheel, refuses to avail itself of them. You can lead a horse to water; however, you cannot stop it from running head long into the desert and dying of thirst. Stupidity IS its own punishment. It took the Catholic church until 1992 to admit that Galileo Galilei was correct and the earth does rotate around the sun. So there is hope. Perhaps someday FreeBSD will become enlightened also. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Realtek RTL8191SEvB Linux driver?
Ladies and gentleman, I will be unplugged from my email until the 17th of January. In the mean time here's a video of a bunny opening your mail http://www.youtube.com/watch?v=LMyaRmTwdKs Your mail will not be forwarded and I will contact you when I come back, alternatively you can contact one of the other administrators or email i...@astalavista.com Merry christmas and a happy new year! Best regards, Sykadul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 04:41:10PM +1000, Da Rock wrote: New users are nearly always dismayed at the apparent difficulty of things, and should be warned that they will need to do some work under the hood in order to get what they want. The honesty can start immediately, it doesn't necessarily have to be a goal. When people think in freedom, think in rights. And rights are something that some authority give or steal. Multinationals think in what is good to sell. People like comfort over all. The taste of people is fantastically represented in the Wall-E movie; to arise and walk is not considered a right. Futurist?, my father, thirty years ago, to go to the corner to buy cigarettes, took the car; today he has half body paralyzed by an hemiplegia, and perhaps one day to arise and walk will not be a right for him. Let's avoid talking about non trivial tasks like hacking a kernel; for example, to copy or move a file you are free to choose between drag and drop with your mouse in a graphical file manager and open a console and use the command line, even in MS Windows. My wife, in case Finder.app crash, she reboot the machine. She ignores if an usb memory is filled up with hidden files used by Mac OS X; she ignores that files copied from a fat file system have executable flag on so she could resend an infected jpeg in an email to a MS Windows user customer. Furthermore she is not a good example of the average final user, because the machine for her (she is a graphical designer) is a tool, not a toy. The question is which immoral entity is stealing her rights? In an emacs mailing list I told Stallman that to teach people to be free is a contradiction. He called me defeatist. Walter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd server limits question
Hi there Huhammet What are the contents of the following files on you're CentOS 6.x shards ? /etc/security/limits.confand /etc/security/limits.d/90-nproc.conf What version of MongoDB are you running, is it from packages (if so who's) or is it self compiled? Have you tried running the MongoDB shards on the most recent CentOS 5.x release? If so what differences do you note, if any? This could help diagnose the source of you're problems. Also what is the current stack size of you're MongoDB shards (set via the -s parameter) ? And lastly what is the system load like at the heaviest transaction points (vmstat and iostat can help you out there) ? If this is a branded name server set what is the exact model and hardware configuration? Are you running 32bit or 64bit instances of MongoDB on 32bit or 64bit CentOS 6.x ? Regards,... Ross Cameron eMail : ross.came...@unix.net Phone : +27 (0)79 491-9954 On Mon, Jan 2, 2012 at 9:12 PM, Muhammet S. AYDIN whalb...@gmail.comwrote: Hello everyone. My first post here and I'd like to thank everyone who's involved within the FreeBSD project. We are using FreeBSD on our web servers and we are very happy with it. We have an online messaging application that is using mongodb. Our members send messages to the voice show's (turkish version) contestants. Our two mongodb instances ended up in two centos6 servers. We have failed. So hard. There were announcements and calls made live on tv. We had +30K/sec visitors to the app. When I looked at the mongodb errors, I had thousands of these: http://pastie.org/private/nd681sndos0bednzjea0g. You may be wondering why I'm telling you about centos. Well, we are making the switch from centos to freebsd FreeBSD. I would like to know what are our limits? How we can set it up so our FreeBSD servers can handle min 20K connections (mongodb's connection limit)? Our two servers have 24 core CPUs and 32 GBs of RAM. We are also very open to suggestions. Please help me out here so we don't fail deadly, again. ps. this question was asked in the forums as well however as someone suggested in the forums, i am posting it here too. -- Muhammet S. AYDIN http://compector.com http://mengu.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On 01/03/12 22:12, Walter Alejandro Iglesias wrote: On Tue, Jan 03, 2012 at 04:41:10PM +1000, Da Rock wrote: New users are nearly always dismayed at the apparent difficulty of things, and should be warned that they will need to do some work under the hood in order to get what they want. The honesty can start immediately, it doesn't necessarily have to be a goal. When people think in freedom, think in rights. And rights are something that some authority give or steal. Multinationals think in what is good to sell. People like comfort over all. The taste of people is fantastically represented in the Wall-E movie; to arise and walk is not considered a right. Futurist?, my father, thirty years ago, to go to the corner to buy cigarettes, took the car; today he has half body paralyzed by an hemiplegia, and perhaps one day to arise and walk will not be a right for him. Let's avoid talking about non trivial tasks like hacking a kernel; for example, to copy or move a file you are free to choose between drag and drop with your mouse in a graphical file manager and open a console and use the command line, even in MS Windows. My wife, in case Finder.app crash, she reboot the machine. She ignores if an usb memory is filled up with hidden files used by Mac OS X; she ignores that files copied from a fat file system have executable flag on so she could resend an infected jpeg in an email to a MS Windows user customer. Furthermore she is not a good example of the average final user, because the machine for her (she is a graphical designer) is a tool, not a toy. The question is which immoral entity is stealing her rights? That is the point after all. Rights are in the eye of the beholder... I personally prefer the ability to accomplish what I want with a stable system. Others may not. To do either requires a relinquishment of some other rights, but I would like to see less rights having to be relinquished in order to achieve my own freedom, and I work towards that for myself and others. If less rights had to be relinquished, others may rally to this flag as well. In an emacs mailing list I told Stallman that to teach people to be free is a contradiction. He called me defeatist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: I have a Toshiba Satellite U505-S2950 laptop with a Realtek RTL8191SEvB wireless card built in. FreeBSD doesn't recognize this card and can't use it, but Ubuntu does. Would it be possible to go glom a Linux driver off the web someplace and install it in my FreeBSD and get the wireless to work? I'm using a USB Belkin in it now, but that's an unhandy thing sticking out like it does. Unfortunately the API's are completely different. Adrian Chadd does a lot of work on Wifi in FreeBSD, but I'm not sure if its on the todo list or not. Try a search on google... This is what drives me to pull my hair out. I have stated several times that all the *nix/*BSD consortium needs to do to become truly competitive in the market is to devise a uniform API that works the same on FreeBSD as on Ubuntu and every other non-windows based system. The concept is so simple that it amazes me that it was not implemented eons ago. The problem is that the non-windows operating system authors all behave live little children. None of them can simply get along. The all have to insist that they have the best and everyone else is wrong. They swing between Narcissism and Paranoia on any given day. You would have an easier time getting a Jew and a Muslim to sit down at a table and enjoy a ham dinner than you have of getting the powers that be in the non-windows community to agree to anything, other than their hatred of Microsoft of course. I have spoken with representatives of companies, the last one being Brother International, who plain out stated that they only support Microsoft (naturally - they offer the easiest and best documented system for driver installation) and a vanilla Linux solution. They openly stated that there is no way that they would even attempt to write software for a market as fractured as the *nix/*BSD community and then be straddled with the problem of supporting such software. Hell, every time someone in the BSD community dotted an i in the kernel source code the poor driver authors would have to rewrite their device code. Certainly a task I would not want to be assigned. Ubuntu is years ahead of FreeBSD in creating a useful and fully functional desktop, I read where they were working on making it possible to use a driver disk intended for Microsoft's Windows OS usable in Ubuntu. They were working on a method of simply extracting the code needed directly from a CD and using it directly on Ubuntu. Now that is what I call true forward thinking. The authors of FreeBSD, and to a lesser extend Linux remind me of group of of passengers left floating in the ocean after their ship sank. The best case scenario at that point would be to be rescued by another passing ship. However, while waiting for that to occur it would seem logical to grab onto any object that floated by and thereby allow the stranded individual a better chance at survival. If these were Ubuntu survivors there would be no question as to what they would choose to do, as well as some of the more enlighten *nix users. However, the *BSD users, especially the FreeBSD ones would rather drown than accept a solution that was not counter to what everyone else was trying to accomplish. I have, mistakenly I admit, stated that there are no drivers for lots of devices currently available on the market, especially the higher end ones. That statement is essentially incorrect. There are drivers for these devices, and other OSs are taking advantage of them. FreeBSD, in its unending war against simplicity and continued insistence on reinventing the wheel, refuses to avail itself of them. You can lead a horse to water; however, you cannot stop it from running head long into the desert and dying of thirst. Stupidity IS its own punishment. It took the Catholic church until 1992 to admit that Galileo Galilei was correct and the earth does rotate around the sun. So there is hope. Perhaps someday FreeBSD will become enlightened also. Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. And thats not even touching the licensing issues. Or the simple design policies (such as userspace or kernel modules) that differ from platform to platform. Some ray of hope allowed some linux drivers to reach the horizon, but so far only usb is remotely possible. Perhaps you might become enlightened enough to do the research (like I did) on the background and core details of what is involved before you start a rant such as this. This has been brought to your attention before, only recently in fact. Start
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 3, 2012 at 1:41 AM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 01/03/12 12:06, Walter Alejandro Iglesias wrote: On Mon, Jan 02, 2012 at 12:33:20PM -0700, Chad Perrin wrote: Ubuntu, actually, has thrown out the baby with the bathwater. In its zeal to make things just work in a particular manner, it seems I would just like to add that is FreeBSD was so crappy open sour software, why does it run half the Internet? http://freebsdfoundation.blogspot.com/2011/12/apache-software-foundation-testimonial.html -- Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, 03 Jan 2012 08:46:54 -0600, Alejandro Imass a...@p2ee.org wrote: I would just like to add that is FreeBSD was so crappy open sour software, why does it run half the Internet? This must be a mistake. I was just assured this weekend that FreeBSD is a niche OS. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 09:01:47AM -0600, Mark Felder wrote: On Tue, 03 Jan 2012 08:46:54 -0600, Alejandro Imass a...@p2ee.org wrote: I would just like to add that is FreeBSD was so crappy open sour software, why does it run half the Internet? This must be a mistake. I was just assured this weekend that FreeBSD is a niche OS. Yah, and hat is its niche. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Wed, 04 Jan 2012 00:17:36 +1000 Da Rock articulated: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: I have a Toshiba Satellite U505-S2950 laptop with a Realtek RTL8191SEvB wireless card built in. FreeBSD doesn't recognize this card and can't use it, but Ubuntu does. Would it be possible to go glom a Linux driver off the web someplace and install it in my FreeBSD and get the wireless to work? I'm using a USB Belkin in it now, but that's an unhandy thing sticking out like it does. Unfortunately the API's are completely different. Adrian Chadd does a lot of work on Wifi in FreeBSD, but I'm not sure if its on the todo list or not. Try a search on google... This is what drives me to pull my hair out. I have stated several times that all the *nix/*BSD consortium needs to do to become truly competitive in the market is to devise a uniform API that works the same on FreeBSD as on Ubuntu and every other non-windows based system. The concept is so simple that it amazes me that it was not implemented eons ago. The problem is that the non-windows operating system authors all behave live little children. None of them can simply get along. The all have to insist that they have the best and everyone else is wrong. They swing between Narcissism and Paranoia on any given day. You would have an easier time getting a Jew and a Muslim to sit down at a table and enjoy a ham dinner than you have of getting the powers that be in the non-windows community to agree to anything, other than their hatred of Microsoft of course. I have spoken with representatives of companies, the last one being Brother International, who plain out stated that they only support Microsoft (naturally - they offer the easiest and best documented system for driver installation) and a vanilla Linux solution. They openly stated that there is no way that they would even attempt to write software for a market as fractured as the *nix/*BSD community and then be straddled with the problem of supporting such software. Hell, every time someone in the BSD community dotted an i in the kernel source code the poor driver authors would have to rewrite their device code. Certainly a task I would not want to be assigned. Ubuntu is years ahead of FreeBSD in creating a useful and fully functional desktop, I read where they were working on making it possible to use a driver disk intended for Microsoft's Windows OS usable in Ubuntu. They were working on a method of simply extracting the code needed directly from a CD and using it directly on Ubuntu. Now that is what I call true forward thinking. The authors of FreeBSD, and to a lesser extend Linux remind me of group of of passengers left floating in the ocean after their ship sank. The best case scenario at that point would be to be rescued by another passing ship. However, while waiting for that to occur it would seem logical to grab onto any object that floated by and thereby allow the stranded individual a better chance at survival. If these were Ubuntu survivors there would be no question as to what they would choose to do, as well as some of the more enlighten *nix users. However, the *BSD users, especially the FreeBSD ones would rather drown than accept a solution that was not counter to what everyone else was trying to accomplish. I have, mistakenly I admit, stated that there are no drivers for lots of devices currently available on the market, especially the higher end ones. That statement is essentially incorrect. There are drivers for these devices, and other OSs are taking advantage of them. FreeBSD, in its unending war against simplicity and continued insistence on reinventing the wheel, refuses to avail itself of them. You can lead a horse to water; however, you cannot stop it from running head long into the desert and dying of thirst. Stupidity IS its own punishment. It took the Catholic church until 1992 to admit that Galileo Galilei was correct and the earth does rotate around the sun. So there is hope. Perhaps someday FreeBSD will become enlightened also. Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. FreePiss, etcetera and their API's are like cheese and chalk! How the hell did you come up with that analogy? Further, who the hell is MAC's relative? To move right along, if a driver all ready exists for a device why not take full advantage of it? Obviously, you failed to read my statement regarding a unified API. There
Re: FreeBSD Kernel Internals Documentation
On Tue, 3 Jan 2012 09:01:47 -0600, Mark Felder wrote: On Tue, 03 Jan 2012 08:46:54 -0600, Alejandro Imass a...@p2ee.org wrote: I would just like to add that is FreeBSD was so crappy open sour software, why does it run half the Internet? This must be a mistake. I was just assured this weekend that FreeBSD is a niche OS. Maybe consider the chance that a FreeBSD OS can be turned into closed source (which the license explicitely allows) and put into some embedded device, a router, a DSL modem, a managed switch... In parts like this, you won't recognize FreeBSD anymore. If you consider such devices niche devices, think again: You'll find them near any Internet-connected computer and among the bowels of the whole Internet. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 3, 2012 at 10:14 AM, Polytropon free...@edvax.de wrote: On Tue, 3 Jan 2012 09:01:47 -0600, Mark Felder wrote: On Tue, 03 Jan 2012 08:46:54 -0600, Alejandro Imass a...@p2ee.org wrote: I would just like to add that is FreeBSD was so crappy open sour software, why does it run half the Internet? This must be a mistake. I was just assured this weekend that FreeBSD is a niche OS. Maybe consider the chance that a FreeBSD OS can be turned into closed source (which the license explicitely allows) and put into some embedded device, a router, a DSL modem, a managed switch... In parts like this, you won't recognize FreeBSD anymore. If you consider such devices niche devices, think again: You'll find them near any Internet-connected computer and among the bowels of the whole Internet. :-) Apple's OS X and iOS for starters. It was heavily based on *BSD, including parts of FBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, 03 Jan 2012 09:14:52 -0600, Polytropon free...@edvax.de wrote: Maybe consider the chance that a FreeBSD OS can be turned into closed source (which the license explicitely allows) and put into some embedded device, a router, a DSL modem, a managed switch... In parts like this, you won't recognize FreeBSD anymore. If you consider such devices niche devices, think again: You'll find them near any Internet-connected computer and among the bowels of the whole Internet. Well we just picked up some Juniper MX80s here at work. That's right, they can route 80gbit/s and the OS that controls the hardware is basically FreeBSD at the core. (I understand the actual routing is fully done in hardware, but still -- I can get a familiar FreeBSD shell and do what I wish with these devices.) I think FreeBSD is doing *just* fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On 01/04/12 01:06, Jerry wrote: On Wed, 04 Jan 2012 00:17:36 +1000 Da Rock articulated: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: I have a Toshiba Satellite U505-S2950 laptop with a Realtek RTL8191SEvB wireless card built in. FreeBSD doesn't recognize this card and can't use it, but Ubuntu does. Would it be possible to go glom a Linux driver off the web someplace and install it in my FreeBSD and get the wireless to work? I'm using a USB Belkin in it now, but that's an unhandy thing sticking out like it does. Unfortunately the API's are completely different. Adrian Chadd does a lot of work on Wifi in FreeBSD, but I'm not sure if its on the todo list or not. Try a search on google... This is what drives me to pull my hair out. I have stated several times that all the *nix/*BSD consortium needs to do to become truly competitive in the market is to devise a uniform API that works the same on FreeBSD as on Ubuntu and every other non-windows based system. The concept is so simple that it amazes me that it was not implemented eons ago. The problem is that the non-windows operating system authors all behave live little children. None of them can simply get along. The all have to insist that they have the best and everyone else is wrong. They swing between Narcissism and Paranoia on any given day. You would have an easier time getting a Jew and a Muslim to sit down at a table and enjoy a ham dinner than you have of getting the powers that be in the non-windows community to agree to anything, other than their hatred of Microsoft of course. I have spoken with representatives of companies, the last one being Brother International, who plain out stated that they only support Microsoft (naturally - they offer the easiest and best documented system for driver installation) and a vanilla Linux solution. They openly stated that there is no way that they would even attempt to write software for a market as fractured as the *nix/*BSD community and then be straddled with the problem of supporting such software. Hell, every time someone in the BSD community dotted an i in the kernel source code the poor driver authors would have to rewrite their device code. Certainly a task I would not want to be assigned. Ubuntu is years ahead of FreeBSD in creating a useful and fully functional desktop, I read where they were working on making it possible to use a driver disk intended for Microsoft's Windows OS usable in Ubuntu. They were working on a method of simply extracting the code needed directly from a CD and using it directly on Ubuntu. Now that is what I call true forward thinking. The authors of FreeBSD, and to a lesser extend Linux remind me of group of of passengers left floating in the ocean after their ship sank. The best case scenario at that point would be to be rescued by another passing ship. However, while waiting for that to occur it would seem logical to grab onto any object that floated by and thereby allow the stranded individual a better chance at survival. If these were Ubuntu survivors there would be no question as to what they would choose to do, as well as some of the more enlighten *nix users. However, the *BSD users, especially the FreeBSD ones would rather drown than accept a solution that was not counter to what everyone else was trying to accomplish. I have, mistakenly I admit, stated that there are no drivers for lots of devices currently available on the market, especially the higher end ones. That statement is essentially incorrect. There are drivers for these devices, and other OSs are taking advantage of them. FreeBSD, in its unending war against simplicity and continued insistence on reinventing the wheel, refuses to avail itself of them. You can lead a horse to water; however, you cannot stop it from running head long into the desert and dying of thirst. Stupidity IS its own punishment. It took the Catholic church until 1992 to admit that Galileo Galilei was correct and the earth does rotate around the sun. So there is hope. Perhaps someday FreeBSD will become enlightened also. Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. FreePiss, etcetera and their API's are like cheese and chalk! How the hell did you come up with that analogy? Further, who the hell is MAC's relative? To move right along, if a driver all ready exists for a device why not take full advantage of it? Obviously, you failed to read my statement regarding a unified API. There has been a serious push I have observed on the Linux forums towards consolidation of resources which would lead to
Re: Realtek RTL8191SEvB Linux driver?
On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Daniel Feenberg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Wed, 04 Jan 2012 01:28:17 +1000 Da Rock articulated: And it appears to be so alien to you that M$ might possibly not allow a unified API between closed and open source in _your_ so called free society, or that what make other systems different _is_ the API, license, policies, etc. You cannot change a system so fundamentally without _breaking_ it- *any* system. Have you had any experience in any of the fields you even claim to be knowledgeable in? I know university lecturers who aren't so don't even try to hide behind letter suffixes. Obviously you are having a very difficult time expression yourself in English. I understand that. I can't talk Spanish worth a crap. In any case, attempting to decipher your writings is more time consuming than I plan to allocate myself at this time. In any, Microsoft would have no say in what common API was agreed upon by a coalition of *nix/*BSD developers. I am totally and completely lost at how you even came to that conclusion. While Microsoft does undoubtedly write some drivers, all the the hardware drivers for devices that I have used for probably 10 years that I can document are written by and owned by entities other that Microsoft. If Microsoft actually had control over said drivers as you seem to believe, the EU aka USSREU would have attempted to have Microsoft release driver specific information to everyone with their hand out. Even Opera couldn't get the EU to bite on that one. There is no legal problem here. The problem is that it is easier to bitch about something and blame others than to form a consensus and correct the problem. There are all ready people working on it. Somehow though, I get the real impression that if a unified API were to be developed that FreeBSD would be the only one not on-board. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
Jerry, Sorry for top posting. Take offense if you like. The o= nly thing I have to say after experiencing the last few days on-list is to = (gently) point out that not everyone's goal in life is to run a system like= Windows. If that was what I wanted I'd be running Windows. I find F= reeBSD more intuitive and easier to use. And I'm prepared to accept that I = have to be a bit picky about the hardware I buy. I consider it a price wort= h paying. Would I like better hardware support? Of course! But if th= e price of that is a fundamental change to the OS interface, then I think t= he price is too high. It strikes me that Ubuntu are running very fas= t to turn Linux into Windows. They'll have good device support and a strong= GUI layer. I'm sure that will fit a lot of users needs, but /not mine/. People who wa= nt that should use Ubuntu. Or Windows. People who like the freedom and con= figurability offered by FreeBSD should use FreeBSD and accept the payoff. = And we should all just rub along, happy in the knowledge that we have chose= n the system we want. -- Pe= ter Harrison _ On 3 Jan 201= 2 12:11, Jerry je...@seibercom.net wrote: On Tue, 03= Jan 2012 16:44:30 +1000 Da Rock articulated: On 01= /03/12 11:15, Jeffrey McFadden wrote: I have a Toshiba Sate= llite U505-S2950 laptop with a Realtek RTL8191SEvB wireless= card built in. FreeBSD doesn't recognize this card and ca= n't use it, but Ubuntu does. Would it be po= ssible to go glom a Linux driver off the web someplace and = install it in my FreeBSD and get the wireless to work? I'm= using a USB Belkin in it now, but that's an unhandy thing = sticking out like it does. Unfortunately the API= 's are completely different. Adrian Chadd does a lot of work on= Wifi in FreeBSD, but I'm not sure if its on the todo list or no= t. Try a search on google... This is what drives me to pull my= hair out. I have stated several times that all the *nix/*BSD consort= ium needs to do to become truly competitive in the market is to devis= e a uniform API that works the same on FreeBSD as on Ubuntu and every= other non-windows based system. The concept is so simple that it ama= zes me that it was not implemented eons ago. The problem= is that the non-windows operating system authors all behave live lit= tle children. None of them can simply get along. The all have to insi= st that they have the best and everyone else is wrong. They swing b= etween Narcissism and Paranoia on any given day. You would have an ea= sier time getting a Jew and a Muslim to sit down at a table and enjoy= a ham dinner than you have of getting the powers that be in the non-= windows community to agree to anything, other than their hatred of Mi= crosoft of course. I have spoken with representatives of compa= nies, the last one being Brother International, who plain out stated = that they only support Microsoft (naturally - they offer the easiest = and best documented system for driver installation) and a vanilla Lin= ux solution. They openly stated that there is no way that they would = even attempt to write software for a market as fractured as the *nix/= *BSD community and then be straddled with the problem of supporting s= uch software. Hell, every time someone in the BSD community dotted an= i in the kernel source code the poor driver authors would have to = rewrite their device code. Certainly a task I would not want to be as= signed. Ubuntu is years ahead of FreeBSD in creating a useful = and fully functional desktop, I read where they were working on makin= g it possible to use a driver disk intended for Microsoft's Windows O= S usable in Ubuntu. They were working on a method of simply extractin g the code needed directly from a CD and using it directly on Ubuntu. Now that is what I call true forward thinking. The au= thors of FreeBSD, and to a lesser extend Linux remind me of group of = of passengers left floating in the ocean after their ship sank. The b= est case scenario at that point would be to be rescued by another pas= sing ship. However, while waiting for that to occur it would seem log= ical to grab onto any object that floated by and thereby allow the st= randed individual a better chance at survival. If these were Ubuntu s= urvivors there would be no question as to what they would choose to d= o, as well as some of the more enlighten *nix users. However, the *B= SD users, especially the FreeBSD ones would rather drown than accept = a solution that was not counter to what everyone else was trying to a= ccomplish. I have,
Re: Realtek RTL8191SEvB Linux driver?
On Tue, 3 Jan 2012 11:10:39 -0500 (EST) Daniel Feenberg articulated: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? This is a start in the right direction, but by no means an end to it. While it does work for some devices, I have tried using it on several wireless N devices for example with total failure. It also doesn't work at all for printer/scanner/fax/etcetera drivers. A unified API would eliminate all of this bullshit and make the setting up of and the maintenance of a system imminently easier. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
Polytropon wrote: Maybe consider the chance that a FreeBSD OS can be turned into closed source (which the license explicitely allows) and put into some embedded device, a router, a DSL modem, a managed switch... In parts like this, you won't recognize FreeBSD anymore. If you consider such devices niche devices, think again: You'll find them near any Internet-connected computer and among the bowels of the whole Internet. :-) Yes, BSD gets embedded not recognised. Some business notebook users years back who thought they were just running security enhanced MS_Win on their notebooks would have not understood their notebooks actually booted FreeBSD first, for `security stuff', then ran MS on top. http://www.google.co.uk/search?hl=ensource=hpq=utimaco+safeguard+freebsdbtnG=Google+Searchgbv=1 Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 03:06:11AM +0100, Walter Alejandro Iglesias wrote: On Mon, Jan 02, 2012 at 12:33:20PM -0700, Chad Perrin wrote: Ubuntu, actually, has thrown out the baby with the bathwater. In its zeal to make things just work in a particular manner, it seems hell-bent on ignoring all but one way to do things, even as it tries to dominate its entire market niche to the extent that it eclipses and marginalizes alternatives. My two cents with other point of view: OSs need popularity; it encourages hardware manufacturers to write drivers and, even better, share the source. That makes the existence of Ubuntu necessary for linux and indirectly to freebsd. Popularity certainly provides resources, especially in a community driven development model. Abandoning good sense in pursuit of popularity is self-defeating, though; working to build popularity by drawing potential users away from other, more technically excellent alternatives, or working to spread the homogenous mediocrity of one approach to all the alternatives, in no way to provide benefits to those other alternatives like you describe. Apologies if that sounds overly harsh as a characterization of what the Ubuntu project is doing -- I just had trouble coming up with a friendlier way to explain the problem with blind pursuit of popularity in this context. If you can formulate a friendlier version of the same message, please pretend I said that instead. Negate or hide obvious FreeBSD (or Linux) limitations is the same error than making look Ubuntu easier than it really is or worse, make it look like something that it definitely is not. New users feel fooled or betrayed, that's why some of them reacts complaining. Anyway I don't feel confident enough to assure if this is a good or bad marketing strategy. I remember, in a very bad network curse I did some years ago, a young classmate that after seeing for the first time the KDE desktop disappointed exclaimed: But, It is like Windows! I seem to recall pointing out the very same fact -- that pretending flaws do not exist is not productive. Your tone here seems to be presented as though you dispute what I said, though, which seems odd. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 01:12:11PM +0100, Walter Alejandro Iglesias wrote: On Tue, Jan 03, 2012 at 04:41:10PM +1000, Da Rock wrote: New users are nearly always dismayed at the apparent difficulty of things, and should be warned that they will need to do some work under the hood in order to get what they want. The honesty can start immediately, it doesn't necessarily have to be a goal. When people think in freedom, think in rights. And rights are something that some authority give or steal. Multinationals think in what is good to sell. People like comfort over all. The taste of people is fantastically represented in the Wall-E movie; to arise and walk is not considered a right. Futurist?, my father, thirty years ago, to go to the corner to buy cigarettes, took the car; today he has half body paralyzed by an hemiplegia, and perhaps one day to arise and walk will not be a right for him. You're confusing capability with right. These words are not the same because their meanings are not the same. I have a right to speak my mind, but if cancer requires the removal of my jaw so that I can no longer speak, I no longer have the capability of speaking at all. These are different things; a capability can be taken away, but a right cannot. This is what is meant by rights in the context of ethics. The law has its own jargon with its own definitions. The way you use right here is very much nonstandard for any context of which I'm aware, which means that before you can have a meaningful discussion with someone that involves such use of the term right you need to get them to buy into your definition of their own free will and agreement. Otherwise, the discussion will be nothing but disagreement and/or misunderstanding. So . . . please start with the denotative meanings of words, consider your audience, and use words accordingly. If you wish to use a term differently than how it is understood, make sure you clarify that fact up front. If others refuse to go along with it, find a different term to use that can better convey the meaning you wish to convey. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Exact timestamp for sorting and renaming files according to creation order
For a sorting script, I'm currently searching for a method to get file creation date and time as exactly as possible. The best resolution I could get was seconds. In case more than one file is created within the same second, it doesn't work precisely enough. It should work from sh script. For the purpose of preparing the sort list (that will be sorted and then be used as a template for renaming the files with a prefix and a counter), I'm using the stat program which creates output like this: % stat -f %N %B -t %Y-%m-%d_%H:%M:%S 1.txt 1.txt 2012-01-03_12:12:12 It's also possible to use the Epoch time format, but it doesn't provide a solution better than seconds: % stat -f %N %B -t %s 1.txt 1.txt 1325589132 I've read the manuals for stat as well as for strftime (which is the facility stat's -t parameter addresses), but found nothing that is more precise than seconds. Does anyone have a suggestion how to precisely determine the order files have been created? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Engineering Question
Hi Webmaster, I am proud to finally share my education site called http://www.onlineengineeringdegree.org with you! Searching for a degree program in Engineering was a difficult process for me. I created http://www.onlineengineeringdegree.org to make sure others do not have the same experience! On my homepage is a list of Engineering degree programs broken down by campus as well as detailed information about the degree and possible career choices. Would you help me reach prospective students with this beneficial site by adding it to your resources of http://freebsd.cdpa.nsysu.edu.tw/ports/science.html? Please let me know if there is anything else you need from me in order to add my link. Thanks for taking a look! Regards, Samantha Rhodes___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Exact timestamp for sorting and renaming files according to creation order
In the last episode (Jan 03), Polytropon said: For a sorting script, I'm currently searching for a method to get file creation date and time as exactly as possible. The best resolution I could get was seconds. In case more than one file is created within the same second, it doesn't work precisely enough. It should work from sh script. For the purpose of preparing the sort list (that will be sorted and then be used as a template for renaming the files with a prefix and a counter), I'm using the stat program which creates output like this: % stat -f %N %B -t %Y-%m-%d_%H:%M:%S 1.txt 1.txt 2012-01-03_12:12:12 It's also possible to use the Epoch time format, but it doesn't provide a solution better than seconds: % stat -f %N %B -t %s 1.txt 1.txt 1325589132 If you ask for the date to be printed in float (F) format, it gives more precision. The default is unsigned int (U) format. % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1306190895.046721049 I've read the manuals for stat as well as for strftime (which is the facility stat's -t parameter addresses), but found nothing that is more precise than seconds. Does anyone have a suggestion how to precisely determine the order files have been created? -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re[2]: reduce partition size. HELP
Здравствуйте, Polytropon. Вы писали 31 декабря 2011 г., 18:15:38: P On Sat, 31 Dec 2011 08:45:32 -0700 (MST), Warren Block wrote: On Sat, 31 Dec 2011, ??? ??? wrote: , Robert. ?? ?? 31 ??? 2011 ?., 5:16:33: RH =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= writes: Is there any way to reduce partition size on live system? RH No. RH Basic steps: RH 0) go to single-user; unmount partition RH 1) backup affected partition; test backup RH 2) delete old partition RH 3) create new/smaller partition RH 4) restore from backup is there a way to goto singe-user through ssh? Single-user and unmounted partitions are desirable but not required. See dump(8) about the -L option. P Of course. And in addition, how about that? P NOT TESTED! READ *FULLY* BEFORE DOING ANYTHING! P For this example, /dev/ad0s1a is the / partition. P There are other partitions (such as /var or /home) P associated to other device files. Let's also P assume /dev/ad0s1e is the /var partition. P Onto the /var partition (or /home or any scratch P oartition), copy the content from / (primarily P because of /sbin, /bin and maybe /etc); maybe P use this approach: P # cd /var P # dump -0 -L -a -u -f - /dev/ad0s1a | restore -r -f - P Make sure /var does _not_ contain directory P names identical to those found on the / partition! P As I said, maybe use /scratch. :-) P (Oh, and you can of course shorten the dump P parameters to -0Lauf and restore's to -rf, P but I chose this representation for making P implicitely clear why to use _those_ options.) P Then umount / and mount /var (I'll keep this P for the example) as the new / (which now has P all the things / should have): P # umount /var P # umount -f / ; mount -t ufs /dev/ad0s1e / I have not tryed, but man says that 'root can not be unmounted'... (( -f The file system is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. The root file system cannot be forcibly unmounted. P Then the device associated to / should be free P to be unmounted - a step desirable, but it should P be no a big problem to operate on the device P files associated with a _mounted_ partition. P The more I think about it... /var is a really P bad choice. Use /scratch, or at least /home. P AGAIN: NOT TESTED! MAY BLOWENFUSEN CORKENPOPPEN! :-) It will be very nice to have legacy installed mfsbsd in some reserved space in swap (like for kenel dumps) http://www.freebsd.org/doc/en/articles/remote-install/preparation.html and having, except single user mode, another option in boot promt: mfsbsd mode. and 'nextboot --mfsbsd' to set remotely that boot option. also be very very nice to have behaviour which loads mfsbsd in case of unproper unmount. Now it is promt to enter #/bin/sh path. Having mfsbsd installed allow remotely complete/correct all failed operations that cause normal loading. also AUTO booting mfsbsd in all cases that crash current system: panic, deadlock os something else, will allow to analise many things remotely and save, in some cases, many many time =) -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Exact timestamp for sorting and renaming files according to creation order
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Dan Nelson Sent: Tuesday, January 03, 2012 12:49 PM To: Polytropon Cc: FreeBSD Questions Subject: Re: Exact timestamp for sorting and renaming files according to creation order In the last episode (Jan 03), Polytropon said: For a sorting script, I'm currently searching for a method to get file creation date and time as exactly as possible. The best resolution I could get was seconds. In case more than one file is created within the same second, it doesn't work precisely enough. It should work from sh script. For the purpose of preparing the sort list (that will be sorted and then be used as a template for renaming the files with a prefix and a counter), I'm using the stat program which creates output like this: % stat -f %N %B -t %Y-%m-%d_%H:%M:%S 1.txt 1.txt 2012-01-03_12:12:12 It's also possible to use the Epoch time format, but it doesn't provide a solution better than seconds: % stat -f %N %B -t %s 1.txt 1.txt 1325589132 If you ask for the date to be printed in float (F) format, it gives more precision. The default is unsigned int (U) format. % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1306190895.046721049 And you can specify float precision ... % stat -f %N %.2FB /COPYRIGHT Will return only 2 decimal places. -- Devin I've read the manuals for stat as well as for strftime (which is the facility stat's -t parameter addresses), but found nothing that is more precise than seconds. Does anyone have a suggestion how to precisely determine the order files have been created? -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.2 fails to boot after install on Sun
Hi, I have tried installing 8.2 Sparc on a Sun system multiple times, using different options, and each time I do, it takes me back to the initial options screen, where I have to exit the install, forcing it to halt. I am never prompted to install a boot manager or anything else. I always get through the install process, installing packages, adding users, network settings, etc. When I power cycle the machine and change the boot settings back to defaults, it fails to boot. Any ideas? Thanks in advance, Leonard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Exact timestamp for sorting and renaming files according to creation order
On Tue, 3 Jan 2012 14:49:02 -0600, Dan Nelson wrote: If you ask for the date to be printed in float (F) format, it gives more precision. The default is unsigned int (U) format. % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1306190895.046721049 Strangely, I only get a 0 suffix for any time stamp, no matter if I create the file or apply the command as shown above to an existing file: % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1313951230.0 Am I missing some file system feature? Otherwise, this _exactly_ looks like what I'm searching for. It doesn't need to be a human-readable date representation. by the way, I'm running FreeBSD 8.2-STABLE/x86 of late August 2011 here, file system used is UFS2. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Write caching FreeBSD 9
Hi! In FreeBSD 7,8 there was an option for mtp driver to enable write cache. Is there a new one for FreeBSD 9, hw.mpt.enable_sata_wc=1 is no longer there. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Exact timestamp for sorting and renaming files according to creation order
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Polytropon Sent: Tuesday, January 03, 2012 1:00 PM To: Dan Nelson Cc: FreeBSD Questions Subject: Re: Exact timestamp for sorting and renaming files according to creation order On Tue, 3 Jan 2012 14:49:02 -0600, Dan Nelson wrote: If you ask for the date to be printed in float (F) format, it gives more precision. The default is unsigned int (U) format. % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1306190895.046721049 Strangely, I only get a 0 suffix for any time stamp, no matter if I create the file or apply the command as shown above to an existing file: % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1313951230.0 Am I missing some file system feature? Otherwise, this _exactly_ looks like what I'm searching for. It doesn't need to be a human-readable date representation. by the way, I'm running FreeBSD 8.2-STABLE/x86 of late August 2011 here, file system used is UFS2. On ZFS, all is well... % df -hT /raid1/jails/package8-1/COPYRIGHT Filesystem TypeSizeUsed Avail Capacity Mounted on raid1/jails/package8-1 zfs 835G672M835G 0% /raid1/jails/package8-1 % stat -f %N %FB /raid1/jails/package8-1/COPYRIGHT /raid1/jails/package8-1/COPYRIGHT 1324356049.328275367 But alas, on UFS2: % df -hT /COPYRIGHT Filesystem TypeSizeUsed Avail Capacity Mounted on /dev/mfid0s1a ufs 989M 64M846M 7%/ % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1279505857.0 -- Devin -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 11:14:01AM -0700, Chad Perrin wrote: On Tue, Jan 03, 2012 at 01:12:11PM +0100, Walter Alejandro Iglesias wrote: On Tue, Jan 03, 2012 at 04:41:10PM +1000, Da Rock wrote: New users are nearly always dismayed at the apparent difficulty of things, and should be warned that they will need to do some work under the hood in order to get what they want. The honesty can start immediately, it doesn't necessarily have to be a goal. When people think in freedom, think in rights. And rights are something that some authority give or steal. Multinationals think in what is good to sell. People like comfort over all. The taste of people is fantastically represented in the Wall-E movie; to arise and walk is not considered a right. Futurist?, my father, thirty years ago, to go to the corner to buy cigarettes, took the car; today he has half body paralyzed by an hemiplegia, and perhaps one day to arise and walk will not be a right for him. You're confusing capability with right. These words are not the same because their meanings are not the same. I have a right to speak my mind, but if cancer requires the removal of my jaw so that I can no longer speak, I no longer have the capability of speaking at all. These are different things; a capability can be taken away, but a right cannot. Dear Chad, You took literally what I wrote distorting all its meaning. I don't know if you did it in purpose because you though that I quoted you to debate with you. Sorry if I made think you that. Anyway I have the feeling that you will do it again if I try to explain you with other words what I really meant, falling in an infinite loop. Surely other people understood what I meant (at least Da Rock did); with one person I consider myself lucky. Besides, you know, my Tarzan's english is not worthy of the occasion :-). My fault, from now I will restrict my posts here to technical issues. Thanks for your patience and sorry for the misunderstanding. Walter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
Quoth Jerry on Tuesday, 03 January 2012: Obviously you are having a very difficult time expression yourself in English. Sorry, this one made me spew my coffee. The rest of the post I didn't find nearly as entertaining. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpmb7sx4WfCe.pgp Description: PGP signature
Re: FreeBSD Kernel Internals Documentation
Quoth Chad Perrin on Tuesday, 03 January 2012: On Tue, Jan 03, 2012 at 01:12:11PM +0100, Walter Alejandro Iglesias wrote: On Tue, Jan 03, 2012 at 04:41:10PM +1000, Da Rock wrote: New users are nearly always dismayed at the apparent difficulty of things, and should be warned that they will need to do some work under the hood in order to get what they want. The honesty can start immediately, it doesn't necessarily have to be a goal. When people think in freedom, think in rights. And rights are something that some authority give or steal. Multinationals think in what is good to sell. People like comfort over all. The taste of people is fantastically represented in the Wall-E movie; to arise and walk is not considered a right. Futurist?, my father, thirty years ago, to go to the corner to buy cigarettes, took the car; today he has half body paralyzed by an hemiplegia, and perhaps one day to arise and walk will not be a right for him. You're confusing capability with right. These words are not the same because their meanings are not the same. I have a right to speak my mind, but if cancer requires the removal of my jaw so that I can no longer speak, I no longer have the capability of speaking at all. These are different things; a capability can be taken away, but a right cannot. This is what is meant by rights in the context of ethics. The law has its own jargon with its own definitions. The way you use right here is very much nonstandard for any context of which I'm aware, which means that before you can have a meaningful discussion with someone that involves such use of the term right you need to get them to buy into your definition of their own free will and agreement. Otherwise, the discussion will be nothing but disagreement and/or misunderstanding. So . . . please start with the denotative meanings of words, consider your audience, and use words accordingly. If you wish to use a term differently than how it is understood, make sure you clarify that fact up front. If others refuse to go along with it, find a different term to use that can better convey the meaning you wish to convey. If everyone followed your advice here, Chad, then 99% of the arguments on the Internet would evaporate. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpcGDtvtfWLt.pgp Description: PGP signature
Re: Exact timestamp for sorting and renaming files according to creation order
In the last episode (Jan 03), Polytropon said: On Tue, 3 Jan 2012 14:49:02 -0600, Dan Nelson wrote: If you ask for the date to be printed in float (F) format, it gives more precision. The default is unsigned int (U) format. % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1306190895.046721049 Strangely, I only get a 0 suffix for any time stamp, no matter if I create the file or apply the command as shown above to an existing file: % stat -f %N %FB /COPYRIGHT /COPYRIGHT 1313951230.0 Am I missing some file system feature? Otherwise, this _exactly_ looks like what I'm searching for. It doesn't need to be a human-readable date representation. by the way, I'm running FreeBSD 8.2-STABLE/x86 of late August 2011 here, file system used is UFS2. Try raising the vfs.timestamp_precision sysctl above zero. That gives me useful fractional values on ufs. % sysctl -d vfs.timestamp_precision vfs.timestamp_precision: File timestamp precision ( 0: seconds, 1: sec + ns accurate to 1/HZ, 2: sec + ns truncated to ms, 3+: sec + ns (max. precision)) -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Mon, 2 Jan 2012 12:33:20 -0700 Chad Perrin articulated: Now you have really peaked my interest. On any given day, on a Windows based forum, the terms: FreePiss, open-sore, Lsuck etcetera are freely thrown around. On Linux based forums, terms like: Winblows, Microsucks, etcetera are freely used. Would you please be so kind as to explain to me why it is morally correct to use one set of terms but not the other? It is either right or it is wrong. You cannot be slightly pregnant. I personally find such terms morally repugnant; however, since they are commonly used on this forum it appears that they are socially acceptable. Would you not concur or are you going to try and bullshit your way out of this one? 1. I didn't say it was morally correct to use one set of derogatory forms and morally incorrect to use the other. You are attributing arguments to me I never made. I just spent a half hour rereading every post on this thread to see if I had inadvertently stated that you had stated in any way that it was morally correct. Guess what, there aren't any such statements. Neither did I make a claim that you supported such actions. I never attributed any such remarks to you. I simple asked for you to explain why it would be morally correct to do so. Your reading comprehensive skills are seriously lacking. The fact that you would spend time to defend yourself against a non-existent claim totally amazes me. Seriously, have you ever been diagnosed with paranoia? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Jerry, there are so many things that are so wrong and so un-pc in this statement that it is more than ridiculous. But we will ignore the political/religious sentiments and try to stick to the technical. Winblows, Mac, Linux, BSD, others APIs are like cheese and chalk (although Mac is a closer relative than any other). By your logic we should be getting Winblows drivers to work on BSD. Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) I had considered that as an answer, but the device is wifi and the firmware makes it damn near impossible to use in this way. NDIS setup is less than user friendly at the best of times without the additional hoops for the firmware loading. I've tried it myself before. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 3, 2012 at 4:39 PM, Jerry je...@seibercom.net wrote: On Mon, 2 Jan 2012 12:33:20 -0700 Chad Perrin articulated: Now you have really peaked Piqued. Although it is misused here. Google it. my interest. On any given day, on a Windows based forum, the terms: FreePiss, open-sore, Lsuck etcetera are freely thrown around. On Linux based forums, terms like: Winblows, Microsucks, etcetera are freely used. Would you please be so kind as to explain to me why it is morally correct to use one set of terms but not the other? It is either right or it is wrong. You cannot be slightly pregnant. I personally find such terms morally repugnant; however, since they are commonly used on this forum it appears that they are socially acceptable. Would you not concur or are you going to try and bullshit your way out of this one? 1. I didn't say it was morally correct to use one set of derogatory forms and morally incorrect to use the other. You are attributing arguments to me I never made. I just spent a half hour rereading every post on this thread to see if I had inadvertently stated that you had stated in any way that it was morally correct. Guess what, there aren't any such statements. Neither did I make a claim that you supported such actions. I never attributed any such remarks to you. I simple asked for you to explain why it would be morally correct to do so. Your reading comprehensive skills are seriously lacking. The fact that you would spend time to defend yourself against a non-existent claim totally amazes me. Seriously, have you ever been diagnosed with paranoia? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
Jerry je...@seibercom.net wrote: Chad Perrin articulated: Now you have really peaked my interest. On any given day, on a Windows based forum, the terms: FreePiss, open-sore, Lsuck etcetera are freely thrown around. On Linux based forums, terms like: Winblows, Microsucks, etcetera are freely used. Would you please be so kind as to explain to me why it is morally correct to use one set of terms but not the other? It is either right or it is wrong. You cannot be slightly pregnant. I personally find such terms morally repugnant; however, since they are commonly used on this forum it appears that they are socially acceptable. Would you not concur or are you going to try and bullshit your way out of this one? 1. I didn't say it was morally correct to use one set of derogatory forms and morally incorrect to use the other. You are attributing arguments to me I never made. I just spent a half hour rereading every post on this thread to see if I had inadvertently stated that you had stated in any way that it was morally correct. Guess what, there aren't any such statements. Jerry demonstrates, yet again, his intellectual dishonesty, and blindness. Anyone who reads what Jerry actually wrote, _as_quoted_verbaitm_above_, an -- unlike former President Clinton, understands what is' means -- will have no trouble verifying that Jerry *did8, in fact, impute that viewpoint to Chad. Neither did I make a claim that you supported such actions. I never attributed any such remarks to you. I simple asked for you to explain why it would be morally correct to do so. Jerry lies. nothing unusual about that, though. Jerry's reading comprehension skills -- of his *own* writing _ ar seriously lacking. He can't even _honestly_, or _accurately_ report what he previously wrote. Even when he quotes it. He did *NOT* ask the prior poster to explain why it _would_be_ morally correct...HE demanded that they explain why it *IS* morally correct... Implicit in that choice of verb (is) is a presumption that the other person accepts/believes the 'truth' of the claim for which the explananation is demanded. Given his constant criticizm of other's writing and/or reading skills, Jerry cannot -- believably, that is -- claim that this was an inavertent/unintentional error in usage on his part. Your reading comprehensive skills are seriously lacking. The fact that you would spend time to defend yourself against a non-existent claim totally amazes me. The extent -- both in breadth, and depth -- of Jerry's delusions is not merely 'impressive; it is *truely* amazing. As is his constant projection of _his_ deficiencies on others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Wed, 4 Jan 2012, Da Rock wrote: On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) At http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Category:USB almost 800 compatible devices are listed. Not everything, but I have found that a willingness to spend a few dollars on a different card helps immensely in enjoying FreeBSD and Linux. For me at least it is easier to find a compatible card than to write a compatible driver. I would also observe that most people involved with computers, whether as users or developers, have little symphathy for people with different needs from the device. This is a great impediment to progress. It is a mistake to assume that because you don't need something, another person's desire for it is illegitimate. In this case, I fully agree that it is an injustice that hardware vendors do not supply FreeBSD drivers, but that does not mean that users requiring such drivers are immoral or of poor character, and therefore to be ignored or insulted. There is little that FreeBSD coders and users can do about that injustice directly, however it is within their power to mitigate it with the NDIS wrapper. If that wrapper allows another user to enter the FOSS world, that will (in the fullness of time) contribute to reforming the vendor. Daniel Feenberg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Tue, Jan 3, 2012 at 5:30 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 01/04/12 02:10, Daniel Feenberg wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** config-network-setup.htmlhttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/**man.cgi?section=8topic=**ndiscvthttp://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) I had considered that aan answer, but the device is wifi and the firmware Excuse my ignorance (again) but what does this mean? ...the Firmware... For now I have reverted this machine to Ubuntu; it's just a machine I set up for my wife to browse the net so she can keep her 30,000 pictures on a Windows box virus-free and it's too much hassle to have the belkin thingy sticking out the side trying to get knocked off. (Just as an aside I don't know why there seems to be so much resentment for Ubuntu here, it looks free and open to me, but what do I know?) Anyway, back to the point, I mostly started using PC-BSD because it's more secure than Windows, and because even at my age (retired) I can continue to learn something just for the fun of it, and because... well, it's difficult to express. I've messed with Linux on and off since Debian 1.2, then had to focus hard on Windows so I could get good enough at it to make a living as a Windows desktop tech in a nationwide health care company... now I find myself attracted to PC-BSD, which has the same stated intent, btw, as Ubuntu, to make a desktop that ordinary users (which just about defines me) can use. Excuse the blather. The point: Does anyone think it might be worth the effort to try to run ndisgen on the Windows drivers? makes it damn near impossible to use in this way. NDIS setup is less than user friendly at the best of times without the additional hoops for the firmware loading. I've tried it myself before. __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On Tue, Jan 3, 2012 at 6:38 PM, Daniel Feenberg feenb...@nber.org wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** config-network-setup.htmlhttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/**man.cgi?section=8topic=**ndiscvthttp://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) At http://sourceforge.net/apps/**mediawiki/ndiswrapper/index.** php?title=Category:USBhttp://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Category:USB almost 800 compatible devices are listed. Not everything, but I have found that a willingness to spend a few dollars on a different card helps immensely in enjoying FreeBSD and Linux. For me at least it is easier to find a compatible card than to write a compatible driver. um, well, yeah, but it's a laptop. :/ And I bought it before FreeBSD ever crossed my mind. sigh I would also observe that most people involved with computers, whether as users or developers, have little symphathy for people with different needs from the device. This is a great impediment to progress. It is a mistake to assume that because you don't need something, another person's desire for it is illegitimate. In this case, I fully agree that it is an injustice that hardware vendors do not supply FreeBSD drivers, but that does not mean that users requiring such drivers are immoral or of poor character, and therefore to be ignored or insulted. There is little that FreeBSD coders and users can do about that injustice directly, however it is within their power to mitigate it with the NDIS wrapper. If that wrapper allows another user to enter the FOSS world, that will (in the fullness of time) contribute to reforming the vendor. Daniel Feenberg __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On 01/04/12 10:38, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) At http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Category:USB almost 800 compatible devices are listed. Not everything, but I have found that a willingness to spend a few dollars on a different card helps immensely in enjoying FreeBSD and Linux. For me at least it is easier to find a compatible card than to write a compatible driver. Indeed :) I did notice that the card in question wasn't on that list. But my own experience with ndiswrapper and wifi cards were far less than satisfactory- the firmware always got in the road. But I may have just been too stupid at the time :) I would also observe that most people involved with computers, whether as users or developers, have little symphathy for people with different needs from the device. This is a great impediment to progress. It is a mistake to assume that because you don't need something, another person's desire for it is illegitimate. In this case, I fully agree that it is an injustice that hardware vendors do not supply FreeBSD drivers, but that does not mean that users requiring such drivers are immoral or of poor character, and therefore to be ignored or insulted. There is little that FreeBSD coders and users can do about that injustice directly, however it is within their power to mitigate it with the NDIS wrapper. If that wrapper allows another user to enter the FOSS world, that will (in the fullness of time) contribute to reforming the vendor. No they are absolutely not of poor character, I agree. Some messages can be misconstrued, though, in that the replies can be terse and more logical than sympathetic. Sometimes it is easier to replace with a different card than flog a dead horse, although a user may take offense for emotional or financial reasons more than logical. Mitigation is a difficult path as I have found personally, although NDIS helps immensely with wired nics (not so much of a problem these days), and I believe Luigi Rizzo's work with the linuxulator and drivers is to be applauded ten fold. It takes a great deal of time though- I put forward the idea when I was still a BSD pup not entirely realising the challenges :) Luigi (and his colleagues) has been working hard ever since to facilitate the more challenging aspects of multimedia drivers (whether or not that had to do with my comments or not, I don't know). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Realtek RTL8191SEvB Linux driver?
On 01/04/12 10:48, Jeffrey McFadden wrote: On Tue, Jan 3, 2012 at 5:30 PM, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 01/04/12 02:10, Daniel Feenberg wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** config-network-setup.htmlhttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/**man.cgi?section=8topic=**ndiscvthttp://www.gsp.com/cgi-bin/man.cgi?section=8topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) I had considered that aan answer, but the device is wifi and the firmware Excuse my ignorance (again) but what does this mean? ...the Firmware... For now I have reverted this machine to Ubuntu; it's just a machine I set up for my wife to browse the net so she can keep her 30,000 pictures on a Windows box virus-free and it's too much hassle to have the belkin thingy sticking out the side trying to get knocked off. (Just as an aside I don't know why there seems to be so much resentment for Ubuntu here, it looks free and open to me, but what do I know?) A lot of hardware runs its own software (called firmware) on it which these days is uploaded when the OS loads the driver. This way updates to the firmware are made easily because its on the disk and not embedded in the hardware (think BIOS updates). Ubuntus fine. Its a stepping stone to understand how *nix runs. The current change in policy direction can raise a few eyebrows here though, but no one holds a grudge against it here. You'll have to ignore Jerry's rants though and the ensuing dialogue- its just the fly in the ointment here. Anyway, back to the point, I mostly started using PC-BSD because it's more secure than Windows, and because even at my age (retired) I can continue to learn something just for the fun of it, and because... well, it's difficult to express. I've messed with Linux on and off since Debian 1.2, then had to focus hard on Windows so I could get good enough at it to make a living as a Windows desktop tech in a nationwide health care company... now I find myself attracted to PC-BSD, which has the same stated intent, btw, as Ubuntu, to make a desktop that ordinary users (which just about defines me) can use. Admirable, and you'll get a lot of support here- a lot have had the same experience and may be in the same boat. If you have the time and want to give back you'll learn a lot more as well. Excuse the blather. The point: Does anyone think it might be worth the effort to try to run ndisgen on the Windows drivers? By all means. Follow the instructions in the handbook and have a go, your experience may differ than my own. There are a factors against you, such as its not on that less than exhaustive list supplied (although mine was, and yet...), and the firmware loading. If you get stuck with it, then please ask for help and someone may have an answer. If nothing else you'll gain experience :) Laptops are almost never completely supported so don't stress, I've had my own issues over the years - they always seem to be one step behind. But that distance is shrinking rapidly: thanks guys! :) Part of the fun is trying to get it to work on yet a different model of laptop... But if it fails and you have to fall back to Ubuntu thats ok, you won't be ostracised; you may even be able to get some answers for your Ubuntu problems here (it can happen...). Just keep watching the list and you'll gain some more knowledge and experience, throw in a few well placed questions here and there helps too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
Jerry, FreeBSD Questions isn't the place to argue about how all OSes should use a universal API, and how Ubuntu is doing such a good job. In an ideal world, everyone would speak the same language, use the same currency, and have identical power outlets. Unfortunately, the last time I checked, we don't live in this world. Some people are trying to make that world possible, but until then, you'll have to face the fact that a universal API doesn't exist. APIs for a scripting or programming are nothing compared to what operating systems deal with. POSIX already does a good job of making sure that these systems (BSD, Solaris, Unix, Linux, etc) have a relatively similar API. The fact is that the kernel lives at such a low level that any change will have drastic consequences. Perhaps some people don't WANT a universal API to exist. If every driver on Windows worked equally well on FreeBSD, Microsoft may find itself out of profit. Equally, if FreeBSD ran the same applications on Microsoft, somebody would be slightly upset that they can't make a profit. On a more positive note, a universal API would help everyone. Since everyone here (including me) like it as it is, why don't you take initiative and put together something? Perhaps you should start out by creating another system specification that all of the existing operating systems could adapt. Write a kernel for it. Create your own operating system that can run everything. I'd use that system. Wireless cards work perfectly on my Toshiba laptop. In fact, the current one I use is a USB wireless adapter. The GENERIC kernel finds my cards perfectly. In addition, I like it when I get to control every single piece of software I put on my system. I switched FROM Linux because of this. If you don't like FreeBSD, you don't have to. If you want to improve it, please go ahead! Sincerely, Kevin Zheng ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.2 fails to boot after install on Sun
On Tue, January 3, 2012 15:33, Miller, Leonard wrote: Hi, I have tried installing 8.2 Sparc on a Sun system multiple times, using different options, and each time I do, it takes me back to the initial options screen, where I have to exit the install, forcing it to halt. I am never prompted to install a boot manager or anything else. I always get through the install process, installing packages, adding users, network settings, etc. Your install experience sounds normal and successful. When you are finished and exit the installer, it should take you to the openboot prompt. All you *should* need to do is type in 'boot', the system will reboot and boot to disk. You don't need to worry about a boot manager as multibooting isn't supported on this platform. When I power cycle the machine and change the boot settings back to defaults, it fails to boot. If it fails to boot, I'm assuming it is stopping at the OpenBoot prompt? Can you elaborate further? What happens when you type 'boot disk' at the openboot prompt? If it boots, auto-boot may not be set correctly, which can be rectified by 'setenv auto-boot? true' at the openboot prompt. If that does not work, what is the output of 'printenv' - specifically what is 'boot-device' set to? Also, some further reading on installing FreeBSD on sparc64: http://www.freebsdwiki.net/index.php/Sparc_-_Installing_FreeBSD -and for more detail- http://www.freebsdwiki.net/index.php/Installation_on_Ultra_5 Hope this helps, James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Kernel Internals Documentation
On Tue, Jan 03, 2012 at 02:07:36PM -0800, Chip Camden wrote: Quoth Chad Perrin on Tuesday, 03 January 2012: So . . . please start with the denotative meanings of words, consider your audience, and use words accordingly. If you wish to use a term differently than how it is understood, make sure you clarify that fact up front. If others refuse to go along with it, find a different term to use that can better convey the meaning you wish to convey. If everyone followed your advice here, Chad, then 99% of the arguments on the Internet would evaporate. Thanks for noticing! -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
