for the impatient: Linux LibreOffice works on FreeBSD
Hi, since there has been various issues building LibreOffice from ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs fine for me. I downloaded Linux' x86 tar package, did tar xf to get RPMs and finally: for i in *rpm; do rpm2cpio $i | cpio -ivd; done That created opt/libreoffice3.5. You can move where you like and start it using libreoffice3.5/program/soffice. (I'm tracking 9-STABLE with Linux compatibility enabled it this matters.) May this help someone lazy or impatient like me... Oli ___ 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
Help solving the sysadm's nightmare
Hi: I have inherited a problem that is no cause for envy, the previous administrators had no idea what they were doing, so problems with a permission denied would be solved by chown -R 777 /whatever! Needless to say, it's a mess, and ofcourse everything is critical there is no room for interruption of service. Now, I have no idea which processes actually require access to those files, what privileges these processes run with and which files are actually executable or just plain files. What I know is that lots of files are on samba shares and lots of files are used by uniface9 application, but I don't know much about uniface or if this is actually executed on the client or on the server. At this moment my project is to migrate servers with these permissions to new servers, but those who prepared the OS have maintained the permissions from the older version because it's easier than actually investigating or understanding what's going on and find a solution. *sigh* So, how can I - determine if files are actually unix executables or just plain files (or windows executables)? - determine which users actually need read or write access to these files? the second is what I think is the most difficult, I need some lsof daemon to log access... Thanks for any suggestions. Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ 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: Help solving the sysadm's nightmare
On 19/07/2012 07:55, Erik Nørgaard wrote: So, how can I - determine if files are actually unix executables or just plain files (or windows executables)? file(1) should help. - determine which users actually need read or write access to these files? This is in most cases entirely a local policy matter. As in: you write up a proposal for how access control policy should be implemented and get it signed off by your managers before applying it. You'll need to present things with rational justifications: something along the lines of: Only the web-dev team and root (sys-admins) need write access to the doc-root www-data pseudo user (the UID apache runs as) needs read access to doc-root the second is what I think is the most difficult, I need some lsof daemon to log access... If you enable system accounting, I believe the detailed logs should show you all of the fileio broken down by user. Note that on a busy server, system accounting can generate a *large* amount of data, and it is likely to affect performance, so use with care. See lastcomm(1), sa(8), accton(8), acct(5) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Help solving the sysadm's nightmare
administrators had no idea what they were doing, so problems with a permission denied would be solved by chown -R 777 /whatever! Needless to say, great. rm -rf /whatever would be even better! it's a mess, and ofcourse everything is critical there is no room for interruption of service. Now, I have no idea which processes actually require access to those files, what privileges these processes run with and which files are actually executable or just plain files. i can only help you with base system and ports permissions, and /var and /etc just look how it should be What I know is that lots of files are on samba shares and lots of files are used by uniface9 application, but I don't know much about uniface or if this is actually executed on the client or on the server. look at samba config to check as what user directories are accessed. set it as such user and chmod 700 is enough. At this moment my project is to migrate servers with these permissions to new servers, but those who prepared the OS have maintained the permissions from the older version because it's easier than actually investigating or understanding what's going on and find a solution. *sigh* So, how can I - determine if files are actually unix executables or just plain files (or windows executables)? man file - determine which users actually need read or write access to these files? depends on software lsof will not help 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: fsck on FAT32 filesystem?
developed countries. Not really sure what you wanted to imply, as SMB looks like americanism to me. as well as SOHO. As not the first time, some people here when lacking arguments say i work for larger company. We have more servers in one place. Esp. second is nopt something to be proud about. more and more such people, and complete newbies or IT specialists dominate this forum. sad. ___ 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: fsck on FAT32 filesystem?
1) There's a _reason_ the gov't requires hard drives with anthing higher than 'somewhat' classified data on them to be =physically= destroyed before leving the secure area. no. for modern hard drives it was already proved that dd if=/dev/zero of=/dev/disk bs=1m is enough to make data unreadable. for very old drives it may not ___ 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: fsck on FAT32 filesystem?
entitled to have opinions, *BUT* the Gospel According to Wojciech is -not- 'the answer' for everybody, in every situation. *IF* you ever learn that, Seems like you have 45 years of experience in words. nothing more. Aggression is normal today from such people, that have good position in some companies and fear anyone could read any other than established opinions. That's all. Still I already see FreeBSD future is to get fd up completely, as such people tend to dominate such a forum. The question is how long. ___ 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
Huawei E173 modem doesn't work on FreeBSD 9
Hi Folks, I'm failed to access E173 modem on FreeBSD 9.0 using serial port. Yes, I got information from the web that this device is not supported yet by the default driver, and the u3g driver need to be updated. ( http://freebsd.1045724.n5.nabble.com/usb-159919-Patch-for-HUAWEI-E173-u3g-umodem-td4716191.html). I already follow all the instruction but unfortunately still failed. Till now i'm stuck with this device. I turn to Ubuntu server, the modem works well there. Bellow is output of usbconfig: # usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen4.1: EHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.2: HUAWEI Mobile HUAWEI at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: USB Keykoard USB at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON # usbconfig -d 4.2 dump_device_desc ugen4.2: HUAWEI Mobile HUAWEI at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1c05 bcdDevice = 0x0102 iManufacturer = 0x0002 HUAWEI iProduct = 0x0001 HUAWEI Mobile iSerialNumber = 0x no string bNumConfigurations = 0x0001 Do you have any suggestions guys? 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: Twitter.com is loading slowly after updating to Firefox 13.0.1
18.07.2012 4:01, Wojciech Puchar пишет: and the other running 9.0-STABLE. After updating Firefox from 12.0 to 13.0.1, whenever I access twitter.com, I can log in but after that a message appears saying that Twitter.com is loading slowly, and the site is practically unusable - clicking on any of the links has no effect. i don't think it is freebsd related question. anyway - use firefox 10.0.0.5-esr from ports. +1 ___ 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: How to donate code
Le Wed, 18 Jul 2012 12:53:00 +0300, Виталий Туровец core...@corebug.net a écrit : Hello, The general advice is mail the patch to -hackers for review. If you don't get a reply or if people like it, submit a PR so it doesn't get lost. Be aware that the latency for some patches could be longer than you expect. :( I already realize that :( The secret is to not expect anything :) FWIW unified diff format patches are much preferred. (diff -u) Okay, i'll rewrite this code under -current OS build and mail the unified diff patch to -hackers list. I remember vaguely a thread on hacker@ about ifconfig and netmask, you may want to check it : http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2011-04/msg00078.html (IPV4 non-CIDR netmasks are valid). ___ 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: How to donate code
2012/7/19 Patrick Lamaiziere patf...@davenulle.org: Le Wed, 18 Jul 2012 12:53:00 +0300, Виталий Туровец core...@corebug.net a écrit : Hello, The general advice is mail the patch to -hackers for review. If you don't get a reply or if people like it, submit a PR so it doesn't get lost. Be aware that the latency for some patches could be longer than you expect. :( I already realize that :( The secret is to not expect anything :) FWIW unified diff format patches are much preferred. (diff -u) Okay, i'll rewrite this code under -current OS build and mail the unified diff patch to -hackers list. I remember vaguely a thread on hacker@ about ifconfig and netmask, you may want to check it : http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2011-04/msg00078.html (IPV4 non-CIDR netmasks are valid). The thread you mentioned was about dotted decimal notation and i'm trying to add !CIDR! notation e.g. 1.1.1.1/32 :) -- ~~~ WBR, Vitaliy Turovets Systems Administrator Corebug.Net +38(093)265-70-55 VITU-RIPE X-NCC-RegID: ua.tv ___ 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: fsck on FAT32 filesystem?
Jerry jerry at seibercom.net writes: ... I couldn't have said it better myself. Wojciech lives in his own little world, which is fine as long as he doesn't try to visit mine. He sounds like he works at a small Polish SMB, more commonly referred to as a SOHO in more developed countries. I have just blocked him so I don't have to read his TROLLish bullshit. Hi Jerry, while I respect your personal decision to /dev/null Wojciech, it seems to me that you are firing with a big gun and actually hurting yourself. If you join a public list you must be prepared to hear opinions that are different from yours, controversial, fill it in. These opinions, valid or not, give you an understanding of what is going on in the field of interest. Otherwise, you may run the danger of building a wall around yourself. While it is not a case here, I have seen few people on other lists to do the same just because they were not able to comprehend a topic discussed, and in frustration they killfiled the person involved. Similarly, all cry babies who for the same reasons want to ban/moderate out/ whatever people from a list irritate me as well. There is an old saying that 'you should not enter the kitchen if you can not stand the heat. So, if you can not change it, relax and enjoy it :-) jb ___ 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: fsck on FAT32 filesystem?
Otherwise, you may run the danger of building a wall around yourself. everyone should judge by his/her own brain which opinions are right. Actually in every moment i try to encourage EVERYONE to turn on his/her brain that we all have but rarely use. To be ever able to use ones brain properly all widely known truth, standard practices etc.. should be forgotten at least for a moment. Mantras are always against clear thinking and understanding. The most important repeated mantra i am righting is that FreeBSD (or any Free unix) should be easier to newbies. This already killed linux long time ago, NetBSD too, and going to kill FreeBSD. Most of newbies are not the ones that are likely to learn anything. They want click-click interface to install and run something so they can add FreeBSD knowledge to their CV. They can do ONLY harm to FreeBSD. Some get hired and results in problems described in thread Help solving the sysadm's nightmare for the man hired after them.. While it is not a case here, I have seen few people on other lists to do the same just because they were not able to comprehend a topic discussed, and in frustration they killfiled the person involved. it's still nothing wrong to add a rule to redirect someones (mine) mail to /dev/null, but the way they do this: - showing whole world they do this - showing whole world their .procmailrc (so happy they finally learnt procmail?) - performing personal attacks every time they disagree. Doesn't look like serious people's behavior. ___ 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: fsck on FAT32 filesystem?
On Thu, 19 Jul 2012 10:15:17 +0200 (CEST) Wojciech Puchar articulated: 1) There's a _reason_ the gov't requires hard drives with anthing higher than 'somewhat' classified data on them to be =physically= destroyed before leving the secure area. no. for modern hard drives it was already proved that dd if=/dev/zero of=/dev/disk bs=1m is enough to make data unreadable. for very old drives it may not Would you be so kind as to point out the proof of that statement? Please provide an address or location where the documentation supporting that statement can be found. By the way, NOT READABLE is not equal to UNRECOVERABLE. -- Carmel ✌ carmel...@hotmail.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: fsck on FAT32 filesystem?
for very old drives it may not Would you be so kind as to point out the proof of that statement? sorry but i didn't save that article on hard drive. So no proof if you don't believe me i've actually read it. The main point is that you have - track - intra-track gap - finite precision of writing head positioning. When you write on track second time, head isn't positioned exactly as before so very thin stripe of previous recording remain. With sophisticated enough tools you may recover it, requiring like 10 times smaller head than normal. With modern drives size of magnetic domains are larger than this imperfection. If drive record properly this stripes of leftover recording are just too small to be stable. Even if it would, no hardware exist to do this, except maybe scanning electron microscope which would take years to scan whole surface of disk IMHO. Not sure if it can see surface magnetization as i don't precisely know how such microscope works. But i know it needs some time to scan even tiny thing. Please provide an address or location where the documentation supporting that statement can be found. By the way, NOT READABLE is not equal to UNRECOVERABLE. yes i know the difference. Finally i am not sure if bulk erases can actually erase drives, for sure they can destroy disk electronics so disk appears cleared. The field needed to clear modern magnetic media are just enormous. They are enormous under normal operation of disk, but power is small as track width is defined in nanometers. If it would be my data to be erased i would just do dd if=/dev/zero of=disk bs=.. or if really paranoid then after this dd if=/dev/urandom of=disk bs=.. or if very paranoid then will just put that drives into fireplace, which would heat them over curie point which would definitely demagnetize whole media. more sure than bulk eraser, and definitely secure, for free. ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs fine for me. I downloaded Linux' x86 tar package, did tar xf to get RPMs and finally: for i in *rpm; do rpm2cpio $i | cpio -ivd; done That created opt/libreoffice3.5. You can move where you like and start it using libreoffice3.5/program/soffice. (I'm tracking 9-STABLE with Linux compatibility enabled it this matters.) May this help someone lazy or impatient like me... what's wrong in /usr/ports/editors/openoffice-3 ? ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
On Thu, Jul 19, 2012 at 7:11 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs [...] May this help someone lazy or impatient like me... what's wrong in /usr/ports/editors/openoffice-3 Oracle ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
On Thu, Jul 19, 2012 at 2:41 AM, Vaclav Kadlcik kro...@gmail.com wrote: Hi, since there has been various issues building LibreOffice from ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs fine for me. I downloaded Linux' x86 tar package, did tar xf to get RPMs and finally: for i in *rpm; do rpm2cpio $i | cpio -ivd; done That created opt/libreoffice3.5. You can move where you like and start it using libreoffice3.5/program/soffice. (I'm tracking 9-STABLE with Linux compatibility enabled it this matters.) May this help someone lazy or impatient like me... Oli Thanks for sharing this! OO should have been replaced by LO a long time ago on 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: fsck on FAT32 filesystem?
This topic went totally off, but anyway there are interesting bits, do you say that e.g. Gutmann method is totally unneeded? -- View this message in context: http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728126.html Sent from the freebsd-questions mailing list archive at Nabble.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: fsck on FAT32 filesystem?
On Thu, 19 Jul 2012 12:49:50 +0200 (CEST) Wojciech Puchar articulated: Otherwise, you may run the danger of building a wall around yourself. everyone should judge by his/her own brain which opinions are right. Actually in every moment i try to encourage EVERYONE to turn on his/her brain that we all have but rarely use. To be ever able to use ones brain properly all widely known truth, standard practices etc.. should be forgotten at least for a moment. Citation needed examples please. Mantras are always against clear thinking and understanding. I don't think you understand the meaning of the word mantras. The most important repeated mantra i am righting is that FreeBSD (or any Free unix) should be easier to newbies. Citation needed. This already killed linux long time ago, NetBSD too, and going to kill FreeBSD. Really, I must have missed the funeral. Most of newbies are not the ones that are likely to learn anything. They want click-click interface to install and run something so they can add FreeBSD knowledge to their CV. That statement goes beyond stupid. At some point, everyone is a newbie. If your statement is to be taken at face value, then the majority of new users would, according to you, never bother to learn anything. You might want to try and back that up with some verifiable facts. Furthermore, in regards to your click-click interface statement, the Ubuntu operating system is gaining traction everyday. Everyone is not locked into the c.1990's. They can do ONLY harm to FreeBSD. Citation needed. Some get hired and results in problems described in thread Help solving the sysadm's nightmare for the man hired after them.. While it is not a case here, I have seen few people on other lists to do the same just because they were not able to comprehend a topic discussed, and in frustration they killfiled the person involved. I have witnessed your posts on Dovecot being ridiculed as nothing more than TROLLing. it's still nothing wrong to add a rule to redirect someones (mine) mail to /dev/null, but the way they do this: - showing whole world they do this - showing whole world their .procmailrc (so happy they finally learnt procmail?) - performing personal attacks every time they disagree. procmail -- really? While everyone is free to use what ever solution they find advantageous, I would certainly not recommend procmail. Procmail is widely used on Unix-based systems and stable, but no longer maintained. Many users have switched to maildrop. Personally, I prefer sieve with Dovecot. Just a personal preference and yet far more robust. Doesn't look like serious people's behavior. Your actions mimic that of a TROLL. You make blanket statements sans any verifiable proof or documentation; i.e. dd being the ultimate disk recovery utility or its ability to absolutely, positively erase any HD without any possibility of it being recovered. I can understand why informed users might block you. I think I will be following their lead. It seems that you have managed to annoy, infuriate and offend users on at least two lists, this one and Dovecot, and I am sure several others as well. At least you have a perfect batting average. -- Carmel ✌ carmel...@hotmail.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
for the impatient: Linux LibreOffice works on FreeBSD
Vaclav Kadlcik writes: since there has been various issues building LibreOffice from ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs fine for me. Excellent work. Two questions: 1) Is there a port? 2) Have you considered submitting one? :-) Robert Huff ___ 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
Job Targeting
How it works? We have a team of resourcers. You post your contract job. Our in house resourcers find matching candidates on our 600,000 strong contractor database for your live role. We send your live job to the top 100-200 matching candidates. You receive only the highest quality applications. We are so confident in this new product that we are offering a 1st month money back guarantee. Call 0203 535 7930 or click here to arrange a free no obligation demonstration http://emarketing.emailjunkies.co.uk/private/jcO4/mVI/cW7G7t6/unsubscribe/16656593 ___ 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: fsck on FAT32 filesystem?
Am 19.07.2012, 13:27 Uhr, schrieb Jakub Lach jakub_l...@mailplus.pl: This topic went totally off, but anyway there are interesting bits, do you say that e.g. Gutmann method is totally unneeded? You may be interested in the epilogue to Gutmann's paper: http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html#Epilogue Quote: For any modern PRML/EPRML drive, a few passes of random scrubbing is the best you can do. As the paper says, A good scrubbing with random data will do about as well as can be expected. This was true in 1996, and is still true now. Nice picture: http://en.wikipedia.org/wiki/File:MFM_AFM_JANUSZ_REBIS_INFOCENTRE_PL_HDD_MAGNETIC_MEMORY_EVOLUTION.png -- View this message in context: http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728126.html Sent from the freebsd-questions mailing list archive at Nabble.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 ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
what's wrong in /usr/ports/editors/openoffice-3 Oracle oracle donated everything to apache foundation. ___ 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: fsck on FAT32 filesystem?
can add FreeBSD knowledge to their CV. That statement goes beyond stupid. At some point, everyone is a You proved well enough about what stupid means. esp your mail carmel...@hotmail.com that's truly a mail address that System Admin should be proud of ;) At least you don't worry about backups. Hotmail (or gmail or else) do archive everything you ever sent or received so you don't fear data loss. ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
On Thu, Jul 19, 2012 at 8:02 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: what's wrong in /usr/ports/editors/openoffice-3 Oracle oracle donated everything to apache foundation. Yes, but not before creating a big mess, stagnating development and forcing the core team out of Oracle to create LO and I guess [pure speculation] that in the end it backfired and Larry (aka we'll simply take it) was left with no resources to maintain it and had no choice but to let it go, maybe in an attempt to save face, who knows. ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
On 07/19/12 09:41, Vaclav Kadlcik wrote: Hi, since there has been various issues building LibreOffice from ports lately and not everyone can or wants follow all the patches flying around, I'd like to share that the Linux binary build runs fine for me. I downloaded Linux' x86 tar package, did tar xf to get RPMs and finally: for i in *rpm; do rpm2cpio $i | cpio -ivd; done That created opt/libreoffice3.5. You can move where you like and start it using libreoffice3.5/program/soffice. (I'm tracking 9-STABLE with Linux compatibility enabled it this matters.) May this help someone lazy or impatient like me... Oli ___ 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 libreoffice-3.5.5 Just upgraded libreoffice to version 3.5.5 using ports. Didn't have any trouble installing is, nor upgrading it. :; uname -a FreeBSD box2 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 01:47:53 UTC 2012 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 :; pkg_info -x libreoffice Information for libreoffice-3.5.5 What sort of errors did you encounter while building the package using the ports? ___ 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: fsck on FAT32 filesystem?
Wojciech Puchar wojtek at wojtek.tensor.gdynia.pl writes: ... This should clear up some confusion. Will it ? Disk Wiping One Pass Is Enough http://www.anti-forensics.com/disk-wiping-one-pass-is-enough ... --- http://www.anti-forensics.com/disk-wiping-one-pass-is-enough-part-2-this-time-wi th-screenshots ... What about magnetic force microscopy? ... Sans Computer Forensics on Magnetic Force Microscopy ... Secure Deletion of Data from Magnetic and Solid-State Memory by Peter Gutmann (35 pass wipe originated from Mr. Gutmann) ... --- ... So why are there so many recommendations for multiple passes during disk wiping? ... Another method I use quite a bit is to just hook a drive up to a Linux system or pop a bootable Live CD in the machine and boot into a Linux environment to use the DD command. It can be as simple as this: dd if=/dev/zero of=/dev/[DISK HERE] Enjoy it ! jb ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
Alexander Kapshuk writes: Just upgraded libreoffice to version 3.5.5 using ports. Didn't have any trouble installing is, nor upgrading it. deletia What sort of errors did you encounter while building the package using the ports? Check the last few weeks of office@ and ports@; there are multiple people (including me) reporting problems, especially with 9.recent and -Current. Robert Huff ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
On 07/19/12 15:46, Robert Huff wrote: Check the last few weeks of office@ and ports@; there are multiple people (including me) reporting problems, especially with 9.recent and -Current. Robert Huff Could be because I'm running the RELEASE version then. ___ 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: fsck on FAT32 filesystem?
Follow up is even more interesting than epilogue, especially: Another problem with the article is the fact that a magnetic force microscope, which is a scanning probe microscope, is nothing like an electron microscope, and yet the article repeatedly refers to using an electron microscope to try and recover data (the same mistake has also been pointed out by others). So saying the chances of recovery of any amount of data from a drive using an electron microscope are negligible is quite true, in the same way that saying the chances of recovery of any amount of data from a drive using an optical microscope are negligible is true And DiskStroyer kit made me chuckle. If I comprehend it correctly, that doesn't make Gutmann method obsolete in principle, it only means that those passes were tailored at (various) old technology, and on modern drives could be bit overkill and just as good as random scrubs. That's still makes a robust procedure, even If overkill and dated (which isn't exactly bad thing). Thanks for replies. -- View this message in context: http://freebsd.1045724.n5.nabble.com/fsck-on-FAT32-filesystem-tp5727015p5728161.html Sent from the freebsd-questions mailing list archive at Nabble.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: fsck on FAT32 filesystem?
On 19/07/2012 09:15, Wojciech Puchar wrote: no. for modern hard drives it was already proved that dd if=/dev/zero of=/dev/disk bs=1m is enough to make data unreadable. for very old drives it may not How about data stored in remapped sectors, or any flash cache? The Secure Erase command (https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase) may clear all that data too, but without any guarantees it's better to destroy the disk than risk leaving classified data on it. -- Bruce Cran ___ 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: fsck on FAT32 filesystem?
On Thu, 19 Jul 2012, Carmel wrote: On Thu, 19 Jul 2012 10:15:17 +0200 (CEST) Wojciech Puchar articulated: 1) There's a _reason_ the gov't requires hard drives with anthing higher than 'somewhat' classified data on them to be =physically= destroyed before leving the secure area. no. for modern hard drives it was already proved that dd if=/dev/zero of=/dev/disk bs=1m is enough to make data unreadable. for very old drives it may not Would you be so kind as to point out the proof of that statement? Please provide an address or location where the documentation supporting that statement can be found. By the way, NOT READABLE is not equal to UNRECOVERABLE. I hesitate to intervene in this dispute, but my posting Can intelligence agencies recover overwritten data? at http://www.nber.org/sys-admin/overwritten-data-gutmann.html will iluminate this discussion. dan feenberg -- Carmel ? carmel...@hotmail.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 ___ 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: fsck on FAT32 filesystem?
How about data stored in remapped sectors, or any flash cache? how about being able to restore random 0.1% of former user data. Not really useful. Flash cache is quite recent idea, nobody serious would like to scrap such a drive instead of reuse. ___ 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: Help solving the sysadm's nightmare
On Thu, 19 Jul 2012 08:55:29 +0200, Erik Nørgaard wrote: Now, I have no idea which processes actually require access to those files, what privileges these processes run with and which files are actually executable or just plain files. For differentiating files' nature, use file file(s) to identify if it's an executable, a script (which _may_ or _may not_ need +x attributes), or just some random text or binary file. Regarding access to files: You could first determine which programs are installed on that server and create a testing bed for them, e. g. using jails on a separate system. Then you can use tools like lsof to see what files are accessed, and in which matter (read, read/write). At this occassion, you can also examine what files have been installed to the system by this program's installer process, and what attributes they do _properly_ have. You can find information about _what_ is installed _where_ and _how_ in the package lists of each port. You can use them to compare currently installed stuff with how it should be. Regarding the OS, there's another helpful mechanism to investigate: Check out the files /etc/mtree which can be used to automatically compare the definitions with their current (probably malformed) real counterparts. Also see man mtree for details. At this moment my project is to migrate servers with these permissions to new servers, but those who prepared the OS have maintained the permissions from the older version because it's easier than actually investigating or understanding what's going on and find a solution. *sigh* I think the most safe method would be if you install a new server from scratch, install the PROGRAMS as needed, and then first copy the DATA with _default_ permissions and check if everything works. If you see that the new system works properly, you can easily switch over from the old system. If you have successfully done it, take the box to the admin who was responsible for it and drop it onto his head, so he can recover from professionality. :-) So, how can I - determine if files are actually unix executables or just plain files (or windows executables)? As I said, file, mtree, pkg-plist. - determine which users actually need read or write access to these files? Talk to the users (or better to their superiors, or anyone who is partially able to talk about what they're doing). User access should be separated and kept inside /home. There are very few cases where this method is not sufficient. Maybe you can find such a case and prepare a _proper_ solution to deal with it. If it's about what _programs_ need to access, check their documentation and configuration files. the second is what I think is the most difficult, I need some lsof daemon to log access... I think it's quite hard to determine requirements in vivo. The more restricted your testing bed is, the more precise are your findings and therefor your answers. Have as few variables as possible. On a server actually running, using a malformed configuration and many altered settings (where you can't even properly tell _what_ has been altered!), testing will be quite hard. -- 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: fsck on FAT32 filesystem?
agencies recover overwritten data? at http://www.nber.org/sys-admin/overwritten-data-gutmann.html at first - it should be asked can agencies recover your data without being overwritten first. just use geli(8) then second problem is even less problem. Finally use geli (or similar method) ALWAYS, no matter if you have highly important data, naked girls photos or just games. Just to say NO to any government agencies that terrorize you using your own money. At least in Poland you are not required by law to provide any passwords. Encryption is legal. At second - the basic claim that overwriting 1 with 1 differs from overwriting 0 with 1 at magnetization level is quite a proof of lack of understanding physics. Hint: magnetic hysteresis. What hard drive manufacturers want is to use magnetic material with largest hysteresis so difference between one and zero is highest. Can all paranoid here finally put their hard drives to fire so they will heat over curie point, and then - end that offtopic? ___ 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: fsck on FAT32 filesystem?
On Thu, 19 Jul 2012 16:26:57 +0200 (CEST), Wojciech Puchar wrote: agencies recover overwritten data? at http://www.nber.org/sys-admin/overwritten-data-gutmann.html at first - it should be asked can agencies recover your data without being overwritten first. Sure, because it's stored on Facebook in the Cloud. :-) Finally use geli (or similar method) ALWAYS, no matter if you have highly important data, naked girls photos or just games. Just to say NO to any government agencies that terrorize you using your own money. At least in Poland you are not required by law to provide any passwords. Encryption is legal. That depends on local legislation. As you said, it's legal in Poland, but it's not in the UK anymore, if I understood it correctly. Related article, I thought I'd share it with the list: http://falkvinge.net/2012/07/12/in-the-uk-you-will-go-to-jail-not-just-for-encryption-but-for-astronomical-noise-too/ It also contains a link to the actual law. Can all paranoid here finally put their hard drives to fire so they will heat over curie point, and then - end that offtopic? Why pollute the environment with fire? What's wrong with a good old-fashioned hammer session, executed on the disk platters? :-) -- 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
lpd+samba question
is there any simple way to get data about workstation that prints using lpd from samba? what i need is to get IP/name of workstation that queued a print job to lpd subsystem through samba. or is the only way to change everything to print to lpd directly using lpd protocol? quite a bit of work but possible. I want to do accounting, not just how many pages are printed on each printer (done), but WHO printed it. No problem for local user, but not with samba. ___ 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
zfs tuning on ia64
Most of http://wiki.freebsd.org/ZFSTuningGuide is for i386 and amd64. I'm using zfs on ia64 r238540. Not sure how much of the advice given apply in my case. I have: # grep ZFS /var/run/dmesg.boot ZFS filesystem version: 5 ZFS storage pool version: features support (5000) # zpool upgrade -v |tail 23 Slim ZIL 24 System attributes 25 Improved scrub stats 26 Improved snapshot deletion performance 27 Improved snapshot creation performance 28 Multiple vdev replacements For more information on a particular version, including supported releases, see the ZFS Administration Guide. # zpool list NAME SIZE ALLOC FREECAP DEDUP HEALTH ALTROOT tank 33.8G 148K 33.7G 0% 1.00x ONLINE - # zpool status pool: tank state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 errors: No known data errors # # dmesg|grep memory real memory = 6442450944 (6144 MB) avail memory = 6279823360 (5988 MB) # sysctl -a |grep vm.kmem vm.kmem_map_free: 1551581184 vm.kmem_map_size: 26427392 vm.kmem_size_scale: 4 vm.kmem_size_max: 0 vm.kmem_size_min: 0 vm.kmem_size: 1578090496 # Do the vm.kmem tunables look reasonable? Thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
Alejandro == Alejandro Imass a...@p2ee.org writes: Alejandro Yes, but not before creating a big mess, stagnating Alejandro development and forcing the core team out of Oracle to create Alejandro LO and I guess [pure speculation] that in the end it Alejandro backfired and Larry (aka we'll simply take it) was left Alejandro with no resources to maintain it and had no choice but to let Alejandro it go, maybe in an attempt to save face, who knows. Repeat story with Hudson (Jenkins) and MySQL (MariaDB) and OpenSolaris (Illumos). The only good thing they seem *not* to have screwed with is VirtualBox. Maybe they haven't discovered they own it yet. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
What sort of errors did you encounter while building the package using the ports? The first problem is that it now demands clang-devel, which conflicts with chromium which still wants regular clang. Any idea how likely it is that chromium will build if I tell it to use clang-devel? R's, John ___ 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: for the impatient: Linux LibreOffice works on FreeBSD
The only good thing they seem *not* to have screwed with is VirtualBox. not really. The backend part of virtualbox is great. The frontend with is UUIDS for everything, XML and other trash is plain terrible. But still - nothing better exist for the need now. ___ 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: lpd+samba question
I didn't try by myself, but what about something like print command = /usr/bin/lpr -P%p -J%J -U%I -r %f in smb.conf? I'm sorry to say that you additionally probably have to change /usr/src/usr.sbin/lpr/common_source/ctlinfo.c near line 87 to #define OTHER_USERID_CHARS -_. /* special chars valid in a userid */ and to recompile lpd: cd /usr/src/usr.sbin/lpr make clean make install At less I've to do so to make the dot . a valid character within a user name. Hope this helps and best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de On Thu, 19 Jul 2012, Wojciech Puchar wrote: is there any simple way to get data about workstation that prints using lpd from samba? what i need is to get IP/name of workstation that queued a print job to lpd subsystem through samba. or is the only way to change everything to print to lpd directly using lpd protocol? quite a bit of work but possible. I want to do accounting, not just how many pages are printed on each printer (done), but WHO printed it. No problem for local user, but not with samba. ___ 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: lpd+samba question
I didn't try by myself, but what about something like print command = /usr/bin/lpr -P%p -J%J -U%I -r %f in smb.conf? I'm sorry to say that you additionally probably have to change /usr/src/usr.sbin/lpr/common_source/ctlinfo.c near line 87 to #define OTHER_USERID_CHARS -_. /* special chars valid in a userid */ and to recompile lpd: cd /usr/src/usr.sbin/lpr make clean make install This is exactly what i asked for. Thank you very much for help. ___ 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
