Questions about Jail
Hi I think Jail on FreeBSD 8.2 can generate 2 jailed machine using the same version of FreeBSD, for example, on a 8.2 AMD64 Jailer, I can create 2 or more FreeBSD 8.2 amd64 Jailed machine. My question is: can I install other version of FreeBSD on the Jailed environment? If yes, which steps shall I do? Still using make world or other easier way? thanks James Y Chen IT Engineering Juniper Networks ___ 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: Questions about Jail
2012-04-03 08:20, James Y Chen skrev: Hi Hello My question is: can I install other version of FreeBSD on the Jailed environment? Since all jails use the same kernel I think you can not do that. There has been a lot of changes between versions of freebsd. ___ 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: Questions about Jail
James Y Chen wrote: Hi I think Jail on FreeBSD 8.2 can generate 2 jailed machine using the same version of FreeBSD, for example, on a 8.2 AMD64 Jailer, I can create 2 or more FreeBSD 8.2 amd64 Jailed machine. My question is: can I install other version of FreeBSD on the Jailed environment? If yes, which steps shall I do? Still using make world or other easier way? In many respects a Jail is more like a super-duper chroot, as opposed to other virtualization technologies such as VMWare, Xen, or KVM hypervisor(s). The closest parallel is probably Solaris Containers, if you are familiar with Solaris. There will only be one running kernel at the heart of a jail based machine. So the bottom line short answer to your question is basically no. Possibly you may wish to read this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-intro.html -Mike ___ 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: Vodafone/Huawei K3770 with usb_modeswitch
Dnia wtorek, 3 kwietnia 2012 12:12:56 Ahmed Ossama pisze: # dmesg | tail umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0 cd0: Vodafone CD ROM (Huawei) 2.31 Removable CD-ROM SCSI-2 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present try loading u3g module first. If that doesn't work then simple ejecting the cdrom should help: cdcontrol -f /dev/cd0 eject For long term solution there should be a patch for the u3g module. Please look in u3g.c file for similar solutions, there should be a few of them. I found out that under linux the usbserial module is unloaded then loaded using: # modprobe usbserial vendor=0x12d1 product=0x14c9 But I don't know how to do that under FreeBSD. I have no clue what to do, and any help is very much appreciated. --- Best Regards, Ahmed Ossama -- Pozdrawiam, Maciej Milewski ___ 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: booting a CD-ROM
gs_stol...@juno.com wrote: I have an old FreeBSD system that I haven't used for a long time and I have forgotten the passwords. This machine has FreeBSD-4.3 and FreeBSD-4.7 on it, and also MS' Windows98 . I tried getting onto that system by booting with a CD-ROM which started going and gave me the following messages: boot from ATAPI CD-ROM CD Loader 1.2 Building the boot loader arguments Relocating the loader and the BTX The system then did not output for a liitle over 5 minutes and then typed: Starting the and after this I waited for over 5 minutes but the system did not type anything else. Then I tried booting that CD-ROM on another system where it booted successfully and the program on it ( FreesBIE version 2) ran and I could communicate with it. I suspect a problem with the boot loader on the first system. Where can I get a new boot loader for that system?Since I want to get a modern FreeBSD (version 9.1 or higher), I expect that will include a new multi-system loader on it that I can use on the old system if I can load just that. How can I load just the boot loader? Also, what is the structure of the password files (is this on the web with a per system-version note so if it has been changed over time, I can find those I need) on those systems, and how can I find and clear out the password for root so I can get in and set its password and then the other passwords? Thanks in advance for your help. You did not specify which/what version of FreeBSD CD-ROM you were attempting this with. IIRC way back then bootable CDs used a floppy-emulation mechanism. If the hardware and its' BIOS is that old a modern day boot CD won't work as it is not emulating a floppy disk any longer. Your best bet would be to locate a FreeBSD version 4.7 disk and try that. A long time ago there used to be included 2 floppy images that could be written out to floppy disks, thus creating bootable floppies. In lieu of not being able to boot from CD-ROM if there is a 1.44MB floppy drive in the box you may be able to boot off the floppies. I'm a little rusty with dim memories, but essentially you want to boot into single user mode. I think it used to be you'd break into the loader by hitting the space bar during the the little twirlie period when a '/' is spinning in the upper left corner of your screen. You would need some basic familiarity with vi such as how to do a basic edit and then save the file. Essentially what vipw does is open the password file using vi as the editor. You could then null out the root password by replacing the crypto string in the second field with a * character. When you save the file using vi commands and exit you will see a message about the password database being updated. This is actually a FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT-PW Note the instructions for mounting / read-write, and the mount -a. The vipw lives in /usr/sbin, so /usr needs to be mounted in order to use it. -Mike ___ 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: Printer recommendation please
Jerry je...@seibercom.net wrote: Obviously you are not aware of the latest trend towards the movement to standardize PDF as the standard print format. I would recommend you start by reading the documentation located at: http://www.linuxfoundation.org/collaborate/workgroups/openprinting and continue on from there. That page seems to be concerned with using PDF, rather than PS, as a common intermediate print language in CUPS. I see nothing there relevant to sending PDF directly to a printer. While there might be some rational for your security concerns on a business network in regards to wireless networks, they are not really relevant on a home networks. The simple ease of use that a wireless network gives a user on a home network far outweigh any pseudo claims of espionage. Following that line of reasoning to its logical conclusion would lead one to believe that home networks have no need of any malware protection, e.g. anti-virus. Any ISP which has had to deal with incidents precipitated by customers' infected machines -- including but likely not limited to DDoS and spambots -- would likely disagree. Furthermore, there are means of encrypting print data ... Utterly irrelevant to the topic under discussion, which is the additional malware exposure that a PDF-accepting printer has relative to a printer that accepts only PCL and/or PS. I maintain that an attacker can more easily trick a less-than- paranoid user into sending a malware print file to a PDF-accepting printer than to a non-PDF-accepting printer, simply because PDF is such a commonly used distribution format. If someone prints a malware PDF file that they have downloaded, and the process of printing it does not require that it be transformed in any way (such as conversion to PS) before being sent to the printer, their only protection from disaster is whatever validation may be built into the printer itself. (Keep in mind that what started the malware discussion was Poly's link to a report stating that some printers do not sufficiently validate an update firmware job.) Granted the identical exposure exists for a PS printer if the downloaded malware file is identified as a PS file, however the risk is much less in practice because distribution of PS files is sufficiently uncommon that most unsophisticated users would have no idea what to do with one if they were to come across it. By the way, since you seem so concerned over your printers security, I assume that you all ready have it at least password protected. No need. I have no wireless at all -- everything is hardwired -- and I trust my firewall. There's no way for anyone to either sniff or inject anything from outside (i.e. without physical access to the network on the secure side of the firewall). ___ 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: Printer recommendation please
On 04/04/12 04:22, per...@pluto.rain.com wrote: Jerryje...@seibercom.net wrote: By the way, since you seem so concerned over your printers security, I assume that you all ready have it at least password protected. No need. I have no wireless at all -- everything is hardwired -- and I trust my firewall. There's no way for anyone to either sniff or inject anything from outside (i.e. without physical access to the network on the secure side of the firewall). And of course you can't login to firewall from the internet, and therefore no CE devices exposed. This then allows you to concentrate on what happens inside your network, without worrying about outside forces getting in without your knowledge. ___ 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: Printer recommendation please
On Tue, 03 Apr 2012 11:22:24 -0700 per...@pluto.rain.com articulated: Jerry je...@seibercom.net wrote: Obviously you are not aware of the latest trend towards the movement to standardize PDF as the standard print format. I would recommend you start by reading the documentation located at: http://www.linuxfoundation.org/collaborate/workgroups/openprinting and continue on from there. That page seems to be concerned with using PDF, rather than PS, as a common intermediate print language in CUPS. I see nothing there relevant to sending PDF directly to a printer. PDF is slowly, but surely, becoming the default printing format on several operating systems. A relatively quick check will reveal that more and more manufacturers are now starting to natively support this print format. While there might be some rational for your security concerns on a business network in regards to wireless networks, they are not really relevant on a home networks. The simple ease of use that a wireless network gives a user on a home network far outweigh any pseudo claims of espionage. Following that line of reasoning to its logical conclusion would lead one to believe that home networks have no need of any malware protection, e.g. anti-virus. Any ISP which has had to deal with incidents precipitated by customers' infected machines -- including but likely not limited to DDoS and spambots -- would likely disagree. Your line of reasoning has somehow gotten totally sidetracked. At no point did I state that NO security measures were ever need. Obviously, everyone needs to establish a certain security baseline for his/her system. Whether or not that system is wireless or hard wired makes absolutely no difference. In fact, I might make a case that it is easier to navigate a hard wired system as opposed to a wireless one since most hard wired systems do not require passwords or certificates to access various components of said system. You stated further on that you have no password or certificate protection on your system. One grenade and you all die. Furthermore, there are means of encrypting print data ... Utterly irrelevant to the topic under discussion, which is the additional malware exposure that a PDF-accepting printer has relative to a printer that accepts only PCL and/or PS. FROM YOUR ORIGINAL POST: All the more reason to avoid wireless. (I had been thinking more along the lines of someone intercepting sensitive print files, e.g. tax returns, as they were being sent to the printer.) I again restate my original statement that there exists means of encrypting data sent to a printer. Whether or not you choose to employ them is your business. Requiring security certificates to access the printer offers even greater protection. I maintain that an attacker can more easily trick a less-than- paranoid user into sending a malware print file to a PDF-accepting printer than to a non-PDF-accepting printer, simply because PDF is such a commonly used distribution format. If someone prints a malware PDF file that they have downloaded, and the process of printing it does not require that it be transformed in any way (such as conversion to PS) before being sent to the printer, their only protection from disaster is whatever validation may be built into the printer itself. (Keep in mind that what started the malware discussion was Poly's link to a report stating that some printers do not sufficiently validate an update firmware job.) And some do. It is a constantly moving target. You make a better mouse trap, they make a better mouse. It is the degree of paranoia that you are willing to live with. If the user spends his/her time visiting porno sites, then they can reasonably expect to be infected with a malignant file. It is virtually impossible to protect someone from their own bad habits. Please, don't waste your time with the, I caught it from a toilet seat explanation. While you could get infected spending a day in the Smithsonian Institution, your odds greatly increase if you spend it in a whore house. Granted the identical exposure exists for a PS printer if the downloaded malware file is identified as a PS file, however the risk is much less in practice because distribution of PS files is sufficiently uncommon that most unsophisticated users would have no idea what to do with one if they were to come across it. By your own words, the problem exists. The question here is the degree of exposure. By the way, since you seem so concerned over your printers security, I assume that you all ready have it at least password protected. No need. I have no wireless at all -- everything is hardwired -- and I trust my firewall. There's no way for anyone to either sniff or inject anything from outside (i.e. without physical access to the network on the secure side of the firewall). Don't worry Captain Smith, this ship can't sink. On a serous note, I have spent the last
Re: modem
On Tue, 3 Apr 2012 09:39:38 +0700, Erich Dollansky wrote: Hi, On Tuesday 03 April 2012 06:49:55 tim smith wrote: My us robotics serial modem worked without issue on previous freebsd versions. With 9, user ppp term, I get /dev/cuau0/ device failed to open Suggestions? what does ls /dev say? Is the modem at least seen by FreeBSD? Erm... seen by FreeBSD? I have never noticed something like that. The OS sees the _serial port_ devices and assigns a device in /dev, but the modem itself does not cause any further action. I've been using an Elsa Microlink serial modem in the past. By the time the serial subsystem in FreeBSD changed, I didn't use it anymore, but I assume /dev/cuau0, /dev/cuau0.init and /dev/cuau0.lock should be present when the serial port is configured correctly. See man 4 sio for details. A ppp session protocol would also be interesting for diagnosis purposes. -- 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: Printer recommendation please
On Tue, 3 Apr 2012 08:40:05 -0400, Jerry wrote: On a serous note, I have spent the last 12 hours, more or less, checking with my friends and business associates. Not a single one has ever had or knows of a single incident of anyone actually ever being infected or having suffered any negative reaction to having printed a PDF file. Most, but not all of these friends / associates are Microsoft users; however, that should not invalidate the statistics. That might be a problem: Malicious acts take place in the background. The time where a virus would pop a funny message on the screen are long over. In Windows land, there are limited resources for means of diagnostics and troubleshooting. Many people believe (and please take that word seriously) that they have no virus, and if you bring a laptop with a traffic scanner (e. g. Wireshark, ex Ethereal), you can see scary things happen on their network. In worst case, the police rushes in, takes all the PCs, and the sloppy explaination they give is: We're investigating a case of copyright infringement, we suspect your PCs being an active sharepoint of copyrighted material. While Windows and its programs presents lots of bells whistles to the user, there's no real chance to find out what's _really_ happening behind that curtain. There are _tons_ of programs out there that can be considered snake oil in regards of security. Windows users know 'em, many of them use 'em. I can imagine if PDF printers spread more and more, they become more interesting to attackers, and malware like Professional Printer Anti-Malware Check XXL Super High Security Programs will spread, waiting for the poor-minded victims to run them, and BANG! printer pwn'd. This is the _first_ step into turning a corporate network into a botnet. If the attacker is able to hide inside a printer, it's much easier for him to do sniper attacks with precision as he is in control of a full-featured networking devices that nobody recognizes... or verifies. Running virus scans, malware scans and so on on Windows PCs has become standard by the majority of its users. Printers are not concerned here, and maybe there are no proper tools available to do the pending tests. Applying that consideration to PDF files, virus scanners would have to check them before they are sent to the printer. In fact, the FOSS society claims MS is more vulnerable to infections/hijacking then they are. This is due to its usage share. I believe if Linux (for example) would run on 90% of home PCs, attackers would concentrate their activities on that platform. Given the statement that the platform is more secure in a technical way (by design and implementation), attackers would potentially try to access the weakest part: the user. This kind of attack is different from those that work in a technical way (e. g. overwriting a printer's firmware silently and secretly), because it does not depend on technical vulnerabilities in the first place. FOSS or not, people have to understand that security is not a static thing, it's a process that involves _them_ to act. A Linux server with telnet enabled and empty root password is as dangerous as a Windows PC in a corporate network. Now there's something interesting hidden: Let's say a malicious file is sent to the printer to compromise it. It's send from a Linux workstation. Will Linux (to keep this example) have to contain a kind of PDF virus scanner by default? Take into mind what I said about behind the curtain. When a printer is compromised, and it acts maliciously within a Linux environment that is poorly secured, I agree with your statement that using a FOSS system does not imply security per se. The original PDF code was written years ago. Since about 2006 hackers have started finding vulnerabilities in it. That's a well-known fact in IT security. As I said, it's up to the manufacturers to properly deal with the security issues as good as possible. If they _can_ remove certain attack vectors for example by ignoring specific sections of PDF data, it would be a benefit for security without actually reducing functionality. It starts beginning complicated if there is a feature that is needed which can be used _against_ the system. Maybe data validation can help here... There was one that attacked scanned documents in MS Office. That problems was fixed over two years ago. Virtually all PDF attacks now target Web Browsers. A case can be made that viewing PDF files in a Web Browser is far more likely to infect a machine than printing such document ever could. Yes, that approach is welcome to attackers as it allows them to take over a full-featured Windows PC within seconds - the user just has to visit a certain web page. By auto-open magic of certain MUAs it's even easier to accomplish. Attacking a printer, however, is much more silent. Why? Because nobody CARES. Printers are not in the scope of security. Does anyone imagine to run a virus check on a printer? Does the
Re: Printer recommendation please
On Tue, 03 Apr 2012 11:22:24 -0700, per...@pluto.rain.com wrote: Jerry je...@seibercom.net wrote: Obviously you are not aware of the latest trend towards the movement to standardize PDF as the standard print format. I would recommend you start by reading the documentation located at: http://www.linuxfoundation.org/collaborate/workgroups/openprinting and continue on from there. That page seems to be concerned with using PDF, rather than PS, as a common intermediate print language in CUPS. I see nothing there relevant to sending PDF directly to a printer. See this page: http://www.linuxfoundation.org/collaborate/workgroups/openprinting/pdfasstandardprintjobformat It discusses (quite short, I admit) programs outputting PDF instead of PS when generating printing data. Handing that data over to the printer does not involve any conversion or intermediate formats anymore. The functionality of CUPS would then be reduced to what the system's default printer spooler does (and did since the 1970's): Read data from a program and send it to the printer. Only the format of data has changed: pure text, text with control characters, PS, PCL, PDF. It starts at the application front. While there might be some rational for your security concerns on a business network in regards to wireless networks, they are not really relevant on a home networks. The simple ease of use that a wireless network gives a user on a home network far outweigh any pseudo claims of espionage. Following that line of reasoning to its logical conclusion would lead one to believe that home networks have no need of any malware protection, e.g. anti-virus. Any ISP which has had to deal with incidents precipitated by customers' infected machines -- including but likely not limited to DDoS and spambots -- would likely disagree. Home networks and carelessly treated corporate networks make the majority of what causes trouble on the Internet. Don't notice == doesn't exist. :-) I maintain that an attacker can more easily trick a less-than- paranoid user into sending a malware print file to a PDF-accepting printer than to a non-PDF-accepting printer, simply because PDF is such a commonly used distribution format. In regards of the web being a main source of attacks, few lines of Javascript would allow to automatically access the printer and send it some PDF data, drive-by attacks made simple. If someone prints a malware PDF file that they have downloaded, and the process of printing it does not require that it be transformed in any way (such as conversion to PS) before being sent to the printer, their only protection from disaster is whatever validation may be built into the printer itself. (Keep in mind that what started the malware discussion was Poly's link to a report stating that some printers do not sufficiently validate an update firmware job.) That's why I _hope_ printer manufacturers will take care about that topic. As far as it's _possible_ to validate PDF data that _might_ be a threat, it should be done, and in worst case, malicious portions of the data should be ignored. Granted the identical exposure exists for a PS printer if the downloaded malware file is identified as a PS file, however the risk is much less in practice because distribution of PS files is sufficiently uncommon that most unsophisticated users would have no idea what to do with one if they were to come across it. Furthermore, PS files would - on most cases - undergo another conversion, for example to PCL. A PS interpreter would have to be exploited to carry malicious code from PS to PCL (if the PCL language allows the same kind of hostile manipulation as the PS language would). In this case, FOSS is a good shield. Code that gets many reviews by the _public_ is less prone to contain backdoors (phrase incorrectly used) that would allow such mis-interpretation. -- 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: Printer recommendation please
On 04/03/12 23:30, Polytropon wrote: On Tue, 3 Apr 2012 08:40:05 -0400, Jerry wrote: On a serous note, I have spent the last 12 hours, more or less, checking with my friends and business associates. Not a single one has ever had or knows of a single incident of anyone actually ever being infected or having suffered any negative reaction to having printed a PDF file. Most, but not all of these friends / associates are Microsoft users; however, that should not invalidate the statistics. That might be a problem: Malicious acts take place in the background. The time where a virus would pop a funny message on the screen are long over. In Windows land, there are limited resources for means of diagnostics and troubleshooting. Many people believe (and please take that word seriously) that they have no virus, and if you bring a laptop with a traffic scanner (e. g. Wireshark, ex Ethereal), you can see scary things happen on their network. In worst case, the police rushes in, takes all the PCs, and the sloppy explaination they give is: We're investigating a case of copyright infringement, we suspect your PCs being an active sharepoint of copyrighted material. While Windows and its programs presents lots of bells whistles to the user, there's no real chance to find out what's _really_ happening behind that curtain. There are _tons_ of programs out there that can be considered snake oil in regards of security. Windows users know 'em, many of them use 'em. I can imagine if PDF printers spread more and more, they become more interesting to attackers, and malware like Professional Printer Anti-Malware Check XXL Super High Security Programs will spread, waiting for the poor-minded victims to run them, and BANG! printer pwn'd. This is the _first_ step into turning a corporate network into a botnet. If the attacker is able to hide inside a printer, it's much easier for him to do sniper attacks with precision as he is in control of a full-featured networking devices that nobody recognizes... or verifies. Running virus scans, malware scans and so on on Windows PCs has become standard by the majority of its users. Printers are not concerned here, and maybe there are no proper tools available to do the pending tests. No. A traffic sniffer would be required to intercept traffic and discover any abnormalities. Most sysadmins wouldn't pay much attention, but you can bet it _will_ require a printer technician with training on the model to fix it- firmware usually requires either passworded telnet access or similar, possibly in conjunction with service software only available to the dealer- and may provide yet a whole new market for office machine service. I'd say sysadmins would expect the manufacturer to actually handle this issue. Applying that consideration to PDF files, virus scanners would have to check them before they are sent to the printer. In fact, the FOSS society claims MS is more vulnerable to infections/hijacking then they are. This is due to its usage share. I believe if Linux (for example) would run on 90% of home PCs, attackers would concentrate their activities on that platform. Given the statement that the platform is more secure in a technical way (by design and implementation), attackers would potentially try to access the weakest part: the user. This kind of attack is different from those that work in a technical way (e. g. overwriting a printer's firmware silently and secretly), because it does not depend on technical vulnerabilities in the first place. FOSS or not, people have to understand that security is not a static thing, it's a process that involves _them_ to act. A Linux server with telnet enabled and empty root password is as dangerous as a Windows PC in a corporate network. Now there's something interesting hidden: Let's say a malicious file is sent to the printer to compromise it. It's send from a Linux workstation. Will Linux (to keep this example) have to contain a kind of PDF virus scanner by default? Take into mind what I said about behind the curtain. When a printer is compromised, and it acts maliciously within a Linux environment that is poorly secured, I agree with your statement that using a FOSS system does not imply security per se. Having found a poorly 'written' pdf, I believe a simple pdf2pdf (using gs with similar commands as pdf2ps) will be sufficient to 'clean' the pdf file- or render it harmless. But essentially running through the cups filters (speaking of the general user) will do this I think- easily verified. Incidentally the pdf was written using MS Office, which offers yet another can o' worms. The original PDF code was written years ago. Since about 2006 hackers have started finding vulnerabilities in it. That's a well-known fact in IT security. As I said, it's up to the manufacturers to properly deal with the security issues as good as possible. If they _can_ remove certain attack vectors for example by ignoring specific sections of PDF
Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
Guys, The crash on my machine with debugging has evaded me for a few days. I'm still looking for further suggestions of things I should grab from the DDB when it happens again. Thanks for the help everyone! ___ 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
Looking for commercial Antivir / Antispam for latest freebsd
Hi all, I am writing this email for asking if someone can suggest a good commercial product for antivir/antispam that supports the latest FreeBSD release (8.x and 9.x) . Actually we are using BitDefender but it refuses to install in newer release due some compatibility problem with compatx ports. I have tried to check on the net but the search engines give me back only outdated results, products not compatible anymore or linux only based. Some focus points: - It must work on FreeBSD 8.x or newer (better if amd64 too). - It should work as milter interface in sendmail base system. - It should have (but it is not mandatory) a web interface where the admin / users check the results of the activity or the service status. Thanks very much for your tips / inputs / suggestions :-) P.s. I am happily using clamav too and it works great, but my company need also a commercial solution. Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://utenti.gufi.org/~gmarco/ ___ 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: Questions about Jail
James Y Chen wrote: Hi I think Jail on FreeBSD 8.2 can generate 2 jailed machine using the same version of FreeBSD, for example, on a 8.2 AMD64 Jailer, I can create 2 or more FreeBSD 8.2 amd64 Jailed machine. My question is: can I install other version of FreeBSD on the Jailed environment? If yes, which steps shall I do? Still using make world or other easier way? thanks James Y Chen IT Engineering Juniper Networks In most cases your jail environment will function ok as long as its the same base release level. Example, host=8.0 jail1=8.1 and jail2=8.2 But host=8.2 and jail1=9.0 will have unknown reliability. Technically there is no checks stopping someone from doing this and from the outside all will look correct, but it will fail and you may lose both the host and jail. There is a system utility called qjail that simplifies jail building. http://qjail.sourceforge.net/ Its in the ports system. ___ 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: current pids per tty
On 3 April 2012 04:19, takCoder tak.offic...@gmail.com wrote: Hi Everyone, i'm trying to find out a way to list *all* the pids of which running in the background of or as the parent *of the current tty* device my shell file is running on.. is there a quick way to find it out as for commands like tty (for current tty) or whoami (for current user) or i should just grep and sed the output of commands like w or ...? as you may know, W(1)'s output just shows the number of pts devices in its tty column.. so it won't be that easy to grep them all(i'm somehow new in shell scripting as well).. and i need the detailed info about related processes; like FROM or WHAT outputs of w command.. (BTW, i'm trying to write a reporting per-tty shell script for my FreeBSD system..) it would be very kind of you giving me any tips or tricks on this. tcsh sh both have a builtin called jobs (there is an executable named /usr/bin/jobs, but . . . well run cat /usr/bin/jobs see for yourself). I dunno if that encompasses everything you want to do. -- -- ___ 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
make buildkernel - error: 'IOSIZE_MAX' undeclared
Hi, Today I tried to build a new system/kernel for one of my boxes running FreeBSD9. make buildworld went ok, however during make buildkernel I got this: -- Cut here -- /usr/src/sys/kern/subr_uio.c: In function 'uiomove_faultflag': /usr/src/sys/kern/subr_uio.c:194: error: 'TDP_RESETSPUR' undeclared (first use in this function) /usr/src/sys/kern/subr_uio.c:194: error: (Each undeclared identifier is reported only once /usr/src/sys/kern/subr_uio.c:194: error: for each function it appears in.) /usr/src/sys/kern/subr_uio.c: In function 'uiomove_frombuf': /usr/src/sys/kern/subr_uio.c:259: error: 'IOSIZE_MAX' undeclared (first use in this function) /usr/src/sys/kern/subr_uio.c: In function 'copyinuio': /usr/src/sys/kern/subr_uio.c:486: error: 'IOSIZE_MAX' undeclared (first use in this function) *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Cut here -- Has anybody seen this? Better yet - any known cure against this problem? Please note that I've cvsup-ed the sources right before building the system/kernel, so they should be up to date. I also tried re-cvsuping several times, but the error stays. Thanks much in advance for your help, -ewald ___ 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
IPv6 default-route - gone
Hi, After installing a new machine under FreeBSD9 I discovered that the IPv6-configuration I had in place with FreeBSD8 does no longer work. Here's what I've got in /etc/rc.conf: ipv6_enable=YES ipv6_ifconfig_em0=2001:76c:2218:2009::11/64 ipv6_defaultrouter=2001:76c:2218:2009::1 The interface address correctly shows up under ifconfig however the default route doesn't seem to be installed, so I'm basically cut off the Internet in terms of IPv6. Please note that the above config has worked unser FreeBSD8 - in fact I've got a couple of boxes under FreeBSD8 with this exact same config. Has the IPv6-related config changed from FBSD 8 - FBSD 9? Thanks much in advance for any help, -ewald ___ 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: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
On 4/2/2012 3:59 PM, Joe Greco wrote: On 4/2/2012 11:43 AM, Joe Greco wrote: As a user, you can't win. If you don't report a problem, you get criticized. If you report a problem but can't figure out how to reproduce it, you get criticized. If you can reproduce it but you don't submit a workaround, you get criticized. If you submit a workaround but you don't submit a patch, you get criticized. If you submit a patch but it's not in the preferred format, you get criticized. I'm still not sure what you're taking as criticism. Nothing I've said was intended that way, nor should it be read that way. If you feel that you've been criticized by others in the manner you describe, you should probably take it up with them on an individual basis. It certainly seemed to me that As much as I'm sensitive to your production requirements, realistically it's not likely that you'll get a helpful result without testing a newer version. 8.2 came out over a year ago, many many things have changed since then. was an unwarranted criticism for reasons that I've already explained. Everything in that paragraph is a fact. If you feel criticized when people state facts, I'm not sure how much I can help you. Please note, I didn't say, You're an idiot for running old stuff. I even explicitly stated that I understood *why* the OP is running an old version. Nevertheless, the facts are what they are. The only way we can deal rationally with the world is to acknowledge reality and deal with it. Wishing it were otherwise isn't really useful. :) Or perhaps this: And since you can't reliably reproduce the problem, how do you expect us to? I understand that these sorts of bugs are difficult/annoying, etc. Been there, done that. Which would appear to be suggesting that either (or possibly both): 1) The reporter has a duty to be able to reliably reproduce the problem prior to reporting, and/or 2) That there was some unreasonable expectation on the reporter's part that you were expected to reproduce it. Quite the contrary, I was responding to your implication that there is some other answer that we should be able to give the OP, other than Try a newer version. Various people have chimed in on the thread, all have offered suggestions, none of which (AFAICS) have helped. I continue to maintain that the best course of action for the OP would be to try the latest 8-stable. And BTW, there are (at least) 2 reasons for that. First, the bug may actually be fixed. But second, we're in the middle of a release cycle for 8.3 right now. If the bug persists in the latest code it will be easier to get the right eyes onto the problem. That benefits both the OP and the community at large. Doug ___ 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
phpmyadmin port files errors
Just downloaded phpmyadmin for 9.0 system. The port files seem to be named wrong. Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v make install command issues error message Don't know how to make install. I see on the web ports system that this port was just updated 5 days ago. Looks like a error was made. These files should not have the ,v suffix. Removing the ,v file name suffix and issuing make install generated a bunch of other error messages. Dead in the water until this gets fixed. If this is indeed an error with the port then I will submit a bug report. ___ 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: phpmyadmin port files errors
On Tue, Apr 03, 2012 at 03:14:39PM -0400, Fbsd8 thus spake: Just downloaded phpmyadmin for 9.0 system. The port files seem to be named wrong. Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v make install command issues error message Don't know how to make install. I see on the web ports system that this port was just updated 5 days ago. Looks like a error was made. These files should not have the ,v suffix. Removing the ,v file name suffix and issuing make install generated a bunch of other error messages. Dead in the water until this gets fixed. If this is indeed an error with the port then I will submit a bug report. This looks incorrect. I just brought down a fresh copy of this port, and don't see files named this way. How are you getting the port, and how are you installing it? These files look like they are directly out of CVS. -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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: IPv6 default-route - gone
On 03/04/2012 18:40, Ewald Jenisch wrote: Hi, After installing a new machine under FreeBSD9 I discovered that the IPv6-configuration I had in place with FreeBSD8 does no longer work. Here's what I've got in /etc/rc.conf: ipv6_enable=YES ipv6_ifconfig_em0=2001:76c:2218:2009::11/64 ipv6_defaultrouter=2001:76c:2218:2009::1 The interface address correctly shows up under ifconfig however the default route doesn't seem to be installed, so I'm basically cut off the Internet in terms of IPv6. Please note that the above config has worked unser FreeBSD8 - in fact I've got a couple of boxes under FreeBSD8 with this exact same config. Has the IPv6-related config changed from FBSD 8 - FBSD 9? Thanks much in advance for any help, -ewald Hi, Yeah it's changed in 9. Here's what I have, for autoconfig use with a tunnel: ipv6_network_interfaces=re0 ifconfig_re0_ipv6=inet6 accept_rtadv ip6addrctl_policy=ipv6_prefer ...and it works For static I'd have: #ipv6_network_interfaces=re0 #ifconfig_re0_ipv6=my_end_of_tunnel_ipv6_ip prefixlen 64 #ipv6_defaultrouter=their_end_of_tunnel_ipv6_ip #ip6addrctl_policy=ipv6_prefer but I've not tried it static yet. -- freebsd at growveg dot 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
Re: modem
On Mon, Apr 02, 2012 at 04:49:55PM -0700, tim smith wrote: My us robotics serial modem worked without issue on previous freebsd versions. With 9, user ppp term, I get /dev/cuau0/ device failed to open * If you have built a custom kernel, check that the kernel config includes the uart device, or that it is loaded as a module. * Does the failure to open list an error number (see 'man errno')? if so, please post it here. * If the error is EPERM or EACCES, check that the ppp process has read/write access to the device. * If there is anything related to the error in your ppp logfile, please post it as well. Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp70LhQUQgvh.pgp Description: PGP signature
Re: current pids per tty
On Tue, Apr 3, 2012 at 12:33 PM, ill...@gmail.com ill...@gmail.com wrote:
On 3 April 2012 04:19, takCoder tak.offic...@gmail.com wrote:
Hi Everyone,
i'm trying to find out a way to list *all* the pids of which running in
the
background of or as the parent *of the current tty* device my shell file
is
running on.. is there a quick way to find it out as for commands like tty
(for current tty) or whoami (for current user) or i should just grep and
sed the output of commands like w or ...?
as you may know, W(1)'s output just shows the number of pts devices in
its
tty column.. so it won't be that easy to grep them all(i'm somehow new in
shell scripting as well).. and i need the detailed info about related
processes; like FROM or WHAT outputs of w command.. (BTW, i'm trying to
write a reporting per-tty shell script for my FreeBSD system..)
it would be very kind of you giving me any tips or tricks on this.
tcsh sh both have a builtin called jobs (there is an executable
named /usr/bin/jobs, but . . . well run cat /usr/bin/jobs see for
yourself). I dunno if that encompasses everything you want to do.
Across all TTYs, something like this would probably work:
sudo fstat | awk '$5 ~ /^\/dev/ $8 ~ /tty/ { printf %s %s %s\n, $1,
$8, $3; }' | sort -k1,2
from there, if you think you need to trace the process trees down, you can
use this list of pids and ps to do the rest ...
hopefully that helps
--
--
___
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
--
regards,
matt
___
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: current pids per tty
On Tue, 3 Apr 2012 16:47:57 -0400, Matthew Story wrote:
Across all TTYs, something like this would probably work:
sudo fstat | awk '$5 ~ /^\/dev/ $8 ~ /tty/ { printf %s %s %s\n, $1,
$8, $3; }' | sort -k1,2
from there, if you think you need to trace the process trees down, you can
use this list of pids and ps to do the rest ...
Or use pstree from ports.
--
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
Cattle Copper Boluses from Santa Cruz Animal Health
Are you having trouble viewing this e-mail? [1]Click here to view it from our website. To ensure that you continue receiving emails from us, please add [2]santacruzbiotechnol...@scbt.com to your e-mail address book. [3][USEMAP:20120402_cattle_email1.jpg] Copyright © 2012 Santa Cruz Biotechnology, Inc. Santa Cruz Biotechnology, Inc. and the Santa Cruz Biotechnology, Inc. logo are registered trademarks of Santa Cruz Biotechnology, Inc. All content contained in this website is property of Santa Cruz Biotechnology, Inc. and may be used only with the expressed written permission of Santa Cruz Biotechnology, Inc. All rights reserved. Santa Cruz Biotechnology, Inc. is located at 2145 Delaware Avenue, Santa Cruz, CA 95060 USA Email: [4]webmas...@scbt.com If you desire to not receive our e-mail bulletins at freebsd-questions@freebsd.org, simply [5]unsubscribe or forward this email message to webmas...@scbt.com. Santa Cruz Biotechnology, Inc. References 1. http://www.scbt.com/emails/redirect.php?lang=enpromo=cattle_20120402url=ah_cattle.html 2. mailto:santacruzbiotechnol...@scbt.com 3. LYNXIMGMAP:file://localhost/tmp/tmpYF9Gig.html#cow 4. mailto:webmas...@scbt.com 5. http://www.scbt.com/email_bulletin.php?eid=freebsd-questions@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: using clang (was: Re: ps, clang and make variables)
On Sun, 1 Apr 2012 17:57:31 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Sun, 1 Apr 2012, Conrad J. Sabatier wrote: On Sun, 1 Apr 2012 14:11:29 -0500 Conrad J. Sabatier conr...@cox.net wrote: On Sun, 1 Apr 2012 12:29:45 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: Have you tried clang with ccache? Any tricks? No, I haven't tried that. Actually, I don't believe I've ever even tried using ccache at all (at least, not that I can recall). :-) You've piqued my curiosity here. :-) I'm doing a buildworld at the moment using ccache with clang. So far, all is well, no problems. Didn't do anything special to get started, just ccache make -DNO_CLEAN -j8 buildworld (I have all that clang-enabling stuff already in /etc/make.conf). I know this first run won't really show me much, other than that it *will* compile OK. Subsequent runs should be interesting, though. :-) A few tests earlier today showed that with everything in cache, it took about 1.5 to 2 times as long to build with clang versus gcc 4.2.1. It was faster with a full cache than without, of course: clang took 38 minutes with nothing in cache, about 12 minutes with everything cached, and gcc buildworlds have been as fast as six minutes. A gcc all-cached test I just tried was 7:47. For some reason, buildworlds on this Core I5 are much faster when running powerd -a hadp than without. And somewhat variable. Well, unfortunately, I'm unable to do a successful buildworld at the moment, with or without ccache, so the results are still up in the air on that. :-) Will keep trying, though. I *hate* when this happens! :-) -- Conrad J. Sabatier conr...@cox.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
Re: phpmyadmin port files errors
On Tue, 03 Apr 2012 15:14:39 -0400 Fbsd8 fb...@a1poweruser.com wrote: Just downloaded phpmyadmin for 9.0 system. The port files seem to be named wrong. Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v make install command issues error message Don't know how to make install. I see on the web ports system that this port was just updated 5 days ago. Looks like a error was made. These files should not have the ,v suffix. Removing the ,v file name suffix and issuing make install generated a bunch of other error messages. Dead in the water until this gets fixed. If this is indeed an error with the port then I will submit a bug report. That looks like the version control colloquially files (RCS, CVS, etc..). -- Michael Hughes Log Home living is the best mich...@thehugheslogcabin.net signature.asc Description: PGP signature
compiling glib20 failed
hi gurus: i got problem with compiling glib20: === glib-2.28.8_4 depends on file: /usr/local/bin/perl5.10.1 - found /libexec/ld-elf.so.1: /usr/local/lib/liblzma.so.5: version XZ_5.0 required by /usr/bin/xz not defined === Missing license file for LGPL20 in /usr/ports/devel/glib20/work/glib-2.28.8/COPYING *** Error code 1 Stop in /usr/ports/devel/glib20. *** Error code 1 basically i was trying to install tshark on freebsd 8.1 but it told me i need to upgrade glib but i got into this mess. thanks ___ 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: compiling glib20 failed
Hi, when did you update your ports tree? It works here on 8.3 with a ports tree from last week. Erich On Wednesday 04 April 2012 10:02:51 gahn wrote: hi gurus: i got problem with compiling glib20: === glib-2.28.8_4 depends on file: /usr/local/bin/perl5.10.1 - found /libexec/ld-elf.so.1: /usr/local/lib/liblzma.so.5: version XZ_5.0 required by /usr/bin/xz not defined === Missing license file for LGPL20 in /usr/ports/devel/glib20/work/glib-2.28.8/COPYING *** Error code 1 Stop in /usr/ports/devel/glib20. *** Error code 1 basically i was trying to install tshark on freebsd 8.1 but it told me i need to upgrade glib but i got into this mess. thanks ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-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
Fwd: microSD ext3 file system
Hello, I have some trouble with a microSD card (or with the controler) in my Linux based cellphone (Openmoko Freerunner). One of the hints I got is to check the microSD card with a Linux tool badblocks(8) http://linux.die.net/man/8/badblocks As I do not have Linux boxes at home, I looked into our ports with no luck for badblocks... Is there some equivalent in FreeBSD which I could use to check /dev/da0 (as this the microSD is presented in my laptop) for bad 'sectors'? FWIW, I've found as well this very interesting article: https://lwn.net/Articles/428584/ which says for example: «... In contrast, the more common SD cards and USB flash drives are very sensitive to specific access patterns and can show very high latencies for writes unless they are used with the preformatted FAT32 file layout. As an example, a desktop machine using a 16 GB, 25 MB/s CompactFlash card to hold an ext3 root filesystem ended up freezing the user interface for minutes during phases of intensive block I/O, despite having gigabytes of free RAM available. Similar problems often happen on small embedded and mobile machines that rely on SD cards for their file systems. ...» Thanks matthias - Forwarded message from Matthias Apitz g...@unixarea.de - Date: Mon, 2 Apr 2012 19:52:40 +0200 From: Matthias Apitz g...@unixarea.de To: commun...@lists.openmoko.org Subject: microSD ext3 file system Hello, After some hours of testing I'm now totally lost with creating an ext3 file system on a (new) 4GB micro SD card. Using my FR (running SHR) I created one new partition on the SD with fdisk(1) and it looks like this: root@om-gta02 ~ # fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 3953 MB, 3953131520 bytes 4 heads, 16 sectors/track, 120640 cylinders Units = cylinders of 64 * 512 = 32768 bytes Sector size (logical/physical): 512 bytes / 512 bytes Disk identifier: 0x0aecb0ac Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 120640 3860472 83 Linux Then I created the ext3 file system on it with: root@om-gta02 ~ # mkfs.ext3 /dev/mmcblk0p1 mke2fs 1.41.9 (22-Aug-2009) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 241440 inodes, 965118 blocks 48255 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=989855744 30 block groups 32768 blocks per group, 32768 fragments per group 8048 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 32 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. now mounting against the /etc/fstab line failes: root@om-gta02 ~ # mount /media/card mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mounting with -t ext3 works and after this as well mounting with the normal line in fstab(5) works too: root@om-gta02 ~ # mount -t ext3 /dev/mmcblk0p1 /media/card root@om-gta02 ~ # umount /media/card root@om-gta02 ~ # mount /media/card root@om-gta02 ~ # and it is really mounted: root@om-gta02 ~ # mount ... /dev/mmcblk0p1 on /media/card type ext3 (rw,errors=continue,data=ordered) now I create a dir and copy over some files from the host connected via USB: root@om-gta02 ~ # mkdir /media/card/dic host: $ scp -rp stardict-duden-2.4.2 root@miko:/media/card/dic duden.ifo 100% 155 0.2KB/s 00:00 duden.idx 100% 2360KB 786.7KB/s 00:03 duden.dict.dz 100% 6719KB 559.9KB/s 00:12 scp: /media/card/dic/stardict-duden-2.4.2/duden.dict.dz: Read-only file system scp: /media/card/dic/stardict-duden-2.4.2/duden.idx.oft: Read-only file system scp: /media/card/dic/stardict-duden-2.4.2/duden(2).idx.oft: Read-only file system the SCP fails and magically now the SD in the FR is mounted read-only: root@om-gta02 ~ # mount ... /dev/mmcblk0p1 on /media/card type ext3 (ro,errors=continue,data=ordered) What is wrong or what do I wrong with this SD card? Thanks matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ Openmoko community mailing list commun...@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community - End forwarded message - -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11 |
Re: microSD ext3 file system
On Wed, Apr 4, 2012 at 12:25 AM, Matthias Apitz g...@unixarea.de wrote: I have some trouble with a microSD card (or with the controler) in my Linux based cellphone (Openmoko Freerunner). One of the hints I got is to check the microSD card with a Linux tool badblocks(8) http://linux.die.net/man/8/badblocks Not exactly what you are asking for but something like this: recoverdisk /dev/da0 /dev/da0 -- Adam Vande More ___ 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
