Re: perl, rrdtool issue
Actually I did portupgrade -rf, and still have the issue with that bsdpan-RRDp-0.99.0. And because of that my munin isn't working, I'm getting email like: Can't locate Munin/Common/Defaults.pm in @INC (@INC contains: It seems that you need to reinstall Munin, not RRDtool. And from the error message, it still uses Perl 5.12 Olivier /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .) at /usr/local/lib/perl5/site_perl/5.12.4/Munin/Master/Update.pm line 14. On 2012 November 15 Thursday at 8:37 AM, Olivier Nicole wrote: Laszlo, Yesterday I issued the following command which I regretted: portupgrade -CPy, and this little tool installed perl 5.12 while perl 5.10 was already on the system. Since then everything is messed up. Now I deleted perl 5.10 and reinstalled perl 5.10 and everything which depends on it and still have the following error: What I usually do is upgrading every Perl packages after I upgraded Perl. Something like portupgrade -R perl should do. Or do it manually, one port at a time if you are afraid to break something else. For having done it recently, from perl to rrdtool it's less than 10 ports to get it back working. best regards, olivier # portversion -v [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 626 packages found (-1 +0) (...) done] Stale dependency: bsdpan-RRDp-0.99.0 -- perl-5.10.1_7 -- manually run 'pkgdb -F' to fix, or specify -O to force. I tried pkgdb -F but it can't fix, also tried to delete rrdtool and reinstall, but still the same issue. I'm running 8.3-RELEASE-p3. Do you have any idea how to solve this issue? Thx! Laszlo ___ 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 ___ 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: 'device' representation in the filesystem questions
On 11/14/12 23:38, Robert Bonomi wrote: it appears that FreeBSD, at least 8.0 and later: a) no longer uses 'raw' devices for anything b) no longer uses 'block' devices for anything c) randomly assigns device 'major' numbers d) doesn't use device 'minor' numbers for anything. e) as a result of c) and d), there is no way to establish 'device' physical characteristics from the 'node' information. Is there a wizzard who can confirm/deny? I'm not a wizard, I don't even count as a sorcerer's apprentice, but I can answer some of these. Firstly block devices were dropped when the unified VM cache came in as the semantics were incompatible. The Architecture Handbook has this rather terse entry about them: http://www.freebsd.org/doc/en/books/arch-handbook/driverbasics-block.html As for major device numbers, in the original days of Unix the device table was just that - an array in the kernel indexed by major device number to get the device operation switch. (Actually there were two tables, one for cdevs and one for bdevs, but the principle's the same.) Device nodes in the file system were simple special inodes containing a (major, minor) pair and created statically by mknod. However, as more devices with different drivers came along it made sense to switch to the current model in which devices are discovered dynamically, both at boot and as they're plugged in and out. and /dev is a magic file system maintained by the kernel and daemons. It's a long time since I was very familiar with kernel internals, but I presume internally devices are now pointers and the device numbering fields returned by stat are simply for backwards compatibility. As for the rest, you need someone more familiar with current kernel internals than I am - my main kernel hacking days ran from the Sixth Edition to BSD 4.2 and faded out as System V.4 came in. If no one turns up here, maybe try freebsd-hackers@ Or, if there's a better place to ask, can anyone point me there? There are significant performance and 'addressability' issues when doing i/o directly to 'fixed block' devices, especially 'write-once' media.` The classical 'block' device type was a reliable indicator of 'fixed block' behavior, how does one make that determination today? Is there any way to get 'classic' mag-tape behavior -- where, for example a read(2) returned the lesser of the bytes in the block, and positioned to the beginning of the next, regardless of whether the etire content of the current block had been read ?` I haven't seen a real mag tape drive in over a decade, so have no hope of commenting on that. ___ 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
Light word processor plus the occasional spreadsheet
Hello I mainly use LibreOffice and it works for me. My problem now is that the build time for LibreOffice on a little older hardware is very long. Is there an alternative to writer that does not take that long to build? If I can get an alternative to Calc also it's a plus but not a big problem. The main work I do will still be done on machines that can build LibreOffice. Now and then I need to open an attached file, maybe edit it and send it back. It's for that purpose I need the light version. Thanks /Leslie ___ 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: Light word processor plus the occasional spreadsheet
On Thu, 15 Nov 2012 10:06:56 +0100, Leslie Jensen wrote: Hello I mainly use LibreOffice and it works for me. My problem now is that the build time for LibreOffice on a little older hardware is very long. Why not use the binary install method (pkg_add -r)? The default options should work fine. Is there an alternative to writer that does not take that long to build? Yes, you can use abiword, part of the Gnome office suite, but it's a standalone word processor. If I can get an alternative to Calc also it's a plus but not a big problem. There is gnumeric for that task, the companion of abiword. :-) -- 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: Light word processor plus the occasional spreadsheet
Polytropon skrev 2012-11-15 10:12: On Thu, 15 Nov 2012 10:06:56 +0100, Leslie Jensen wrote: Hello I mainly use LibreOffice and it works for me. My problem now is that the build time for LibreOffice on a little older hardware is very long. Why not use the binary install method (pkg_add -r)? The default options should work fine. Maybe I'll try that. I never got into packages, I always ended up compiling dependencies anyway so I dropped it ;-) Thanks! Is there an alternative to writer that does not take that long to build? Yes, you can use abiword, part of the Gnome office suite, but it's a standalone word processor. If I can get an alternative to Calc also it's a plus but not a big problem. There is gnumeric for that task, the companion of abiword. :-) ___ 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: Mounting SD card.
I think that's pretty much standard behaviour. The solution appears to be to wake it up with the following incantation: dd if=/dev/null of=/dev/da0 count=0 That's what works here. See the thread starting with http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html true /dev/da0 is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. Could you also do a read such as dd if=/dev/da0 of=/dev/null bs=16k count=1 ? Tom ___ 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: Mounting SD card.
On Thursday 15 November 2012 02:06:02 Warren Block wrote: true /dev/da0 is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. Thanks Warren. I wasn't aware of that option, it's certainly much neater and less prone to typing errors. -- Mike Clarke ___ 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: Mounting SD card.
On Thu, 15 Nov 2012 09:43:42 +, Mike Clarke wrote: On Thursday 15 November 2012 02:06:02 Warren Block wrote: true /dev/da0 is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. Thanks Warren. I wasn't aware of that option, it's certainly much neater and less prone to typing errors. Is there a recommended way to automate the GEOM re-tasting so SD cards can be accessed without further interaction (by simply using the correct mount command)? -- 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: Advanced Format Drive ?
In message alpine.bsf.2.00.1211142231420.58...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Ronald F. Guilmette wrote: ... Given these facts, I am more than a little surpised to learn (or rather just to realize) that the good old traditional fdisk and bsdlabel tools do not have ways to explicitly specify minimum alignment _and_ that these tools are still being distributed with FreeBSD. There may be a way, I haven't bothered to look. As I said, gpart does everything fdisk and bsdlabel can do. Well, given that newfs has been ``fixed'' so that its defaults will Do The Right Thing with the latest generation of (4KB block) disks, I for one would like to register my vote for fdisk and bsdlabel to either (a) be likewise fixed so that they also will default to Doing The Right Thing (with the current generation of disks) or else (b) be removed from future releases, based on the fact that (apparently) they are now so old that nobody cares about them anymore and/or that their defaults, when (foolishly?) relied upon, are likely to produce Bad Performance, aka Bad Behavior. And also, please don't forget the other points I mentioned, i.e. that the man page for fdisk makes several references to alignment on ``cylinder'' and/or ``head'' boundaries. Are those things even relavant anymore? Have they been, anytime in the past 10+ years? (I am guessing that there may be other similarly antiquated references to boundaries that haven't been meaningful for a long long time also in the bdslabel man page, although I confess that didn't even look.) ___ 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: Advanced Format Drive ?
In message alpine.bsf.2.00.1211142250370.58...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Ronald F. Guilmette wrote: I'm looking at the examples section of the gpart(8) man page. May I assume that if I just want to merely ``try out'' GPT... you know... taking it out on the road for a first time test run... that I can just do the first five (5) commands listed under EXAMPLES and then that will be enough to go ahead and try installing FreeBSD into the created freebsd-ufs partition? Even assuming that the answer is yes, I have still more questions... Where are these magic numbers coming from?? I am specifically talking about the number 34 in the -b 34 option and also the number 162 in the -b 162 option. Tha man page just tosses those into the example command lines without saying a word about them. And you can probably guess what it is that is especially troubling to me about them... neither one of them is divisible by 8 (i.e. 4KB/512B). So would the examples in the current gpart(8) man page produce an Epic Fail when and if they were used with a modern Advanced Format drive? -b is the beginning block of a partition. 34 is a magic value, the size of a standard GPT partition table. It probably wouldn't have hurt anything to mention that in the gpart man page. And what about 162? Is that magic too? If so, how? I seriously do not know. A good overall reference on GPT is the Wikipedia page: http://en.wikipedia.org/wiki/GUID_Partition_Table Remember that the man page is a reference, not a tutorial. Actually, it is clearly both. We all know that man pages are primarily supposed to be (minimal?) reference documents, but you cannot claim with a straight face that any man page that contains an EXAMPLES section is not also serving as a rudimentary tutorial. Personally, I find the minimalist tutorials that are often found within EXAMPLES sections of man page quite helpful, gpart(8) included. But in this specific case the pulling of number, apparently out of thin air (at least from the point of view of the uninitiated) rather significantly degrades the educational value. I wanted more specific notes that followed best practices, and that was the source for this article: http://www.wonkity.com/~wblock/docs/html/disksetup.html It is very helpful (and very appreciated!) that you were kind enough to create that document, which is clearly more unambiguously a tutorial. But really, the gpart(8) man page got me about 97% of the way there, even without me having to consult external references. If it just had not been for those mystery numbers... In general, you create a partition scheme first. This can be MBR, GPT, or others. (But use GPT.) Yea. I got that part. Rather than combine the bootcode with the partition table, GPT just uses a small partition for it. Since the standard GPT allows for up to 128 partitions, there's no reason not to use them. Got it. Thanks. Next come other partitions for UFS or ZFS filesystems or swap. Right. That's it, really. The rest is details the man page can explain, like additional options for alignment. (The creation of the first UFS partition in the article does not use -a because older versions of gpart did unexpected things when -a and -b were combined. The alignment produced is correct.) Questions: In your tutorial document, you say: Create a boot partition to hold the loader, size of 512K. How big is that thing (gpart boot loader), actually? Half a megabyte seems rather a bit large-ish, certainly relative to ye olde MBR loader, which I gather was limited to... what? 32KB (minus a little for the partition table) ? Also, when creating the partition to hold the GPT boot loader, shouldn't that gpart add operation include a -b 4k option, you know, on a modern Advanced Format disk? If not, why not? You also go on to say: Create partition for /. It should start at the 1M boundary for proper sector alignment on 4K sector drives. Come again? Sorry, but you just lost me entirely. In order to get proper sector alignment on one of these newer Advanced Format (4k) drives, why on earth should it be necessary to begin a partition at some alignment which is greater than the obvious minimum, i.e. 4KB ? ___ 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
Shut-down when access to NFS share is gone
I managed to shut down a machine with an NFS share before the connected client was shut down. Now this client won't shut down. It stands at : All buffers synced. I suspect it's waiting for the NFS server in order to disconnect. Is there any time-out I must wait for? Will it help to bring the NFS server back up? Can I in anyway tell such a client to ignore such an error? Thanks /Leslie ___ 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: Advanced Format Drive ?
In messagealpine.bsf.2.00.1211142250370.58...@wonkity.com, In general, you create a partition scheme first. This can be MBR, GPT, or others. (But use GPT.) Unless you want to dual boot with WinXP in which case use MBR still? Chris ___ 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: Advanced Format Drive ?
On 11/15/12 12:41, Ronald F. Guilmette wrote: In message alpine.bsf.2.00.1211142250370.58...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Ronald F. Guilmette wrote: I'm looking at the examples section of the gpart(8) man page. May I assume that if I just want to merely ``try out'' GPT... you know... taking it out on the road for a first time test run... that I can just do the first five (5) commands listed under EXAMPLES and then that will be enough to go ahead and try installing FreeBSD into the created freebsd-ufs partition? Even assuming that the answer is yes, I have still more questions... Where are these magic numbers coming from?? I am specifically talking about the number 34 in the -b 34 option and also the number 162 in the -b 162 option. Tha man page just tosses those into the example command lines without saying a word about them. And you can probably guess what it is that is especially troubling to me about them... neither one of them is divisible by 8 (i.e. 4KB/512B). So would the examples in the current gpart(8) man page produce an Epic Fail when and if they were used with a modern Advanced Format drive? -b is the beginning block of a partition. 34 is a magic value, the size of a standard GPT partition table. It probably wouldn't have hurt anything to mention that in the gpart man page. And what about 162? Is that magic too? If so, how? I seriously do not know. The man example should be taken as a whole. You've got /sbin/gpart add -b 34 -s 128 -t freebsd-boot ad0 which gives you a 128 block partition starting at block 34, so the next free block is 162, and the next partition is explicitly started there in /sbin/gpart add -b 162 -s 1048576 -t freebsd-ufs ad0 No magic, just arithmetic. :-) ___ 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: high performance server design approach
On Tue, Nov 13, 2012 at 08:23:38AM -0200, Friedrich Locke wrote: 0) To have a single process accepting incoming connection on port 80 and send the new socket fd to one of the http server in a round-roubin manner, DJB's publicfile does something rather similar. http://cr.yp.to/publicfile.html You could spend all day wondering. But if you really want to know and not just argue, you should do as the author of that web server says: Profile. Don't speculate. It may just be that context switches are not the real bottleneck in your service. ___ 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: Shut-down when access to NFS share is gone
On Thu, Nov 15, 2012 at 7:37 AM, Leslie Jensen les...@eskk.nu wrote: I managed to shut down a machine with an NFS share before the connected client was shut down. Now this client won't shut down. It stands at : All buffers synced. I suspect it's waiting for the NFS server in order to disconnect. Is there any time-out I must wait for? Will it help to bring the NFS server back up? Can I in anyway tell such a client to ignore such an error? http://www.freebsd.org/cgi/man.cgi?query=mount_nfssektion=8 If the server becomes unresponsive while an NFS file system is mounted, any new or outstanding file operations on that file system will hang uninterruptibly until the server comes back. To modify this default be- haviour, see the *intr* and *soft* options. -- 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
Re: Shut-down when access to NFS share is gone
Thank you :-) I'll study it closer. /Leslie 2012-11-15 15:15, Adam Vande More skrev: On Thu, Nov 15, 2012 at 7:37 AM, Leslie Jensen les...@eskk.nu wrote: I managed to shut down a machine with an NFS share before the connected client was shut down. Now this client won't shut down. It stands at : All buffers synced. I suspect it's waiting for the NFS server in order to disconnect. Is there any time-out I must wait for? Will it help to bring the NFS server back up? Can I in anyway tell such a client to ignore such an error? http://www.freebsd.org/cgi/man.cgi?query=mount_nfssektion=8 If the server becomes unresponsive while an NFS file system is mounted, any new or outstanding file operations on that file system will hang uninterruptibly until the server comes back. To modify this default be- haviour, see the *intr* and *soft* options. ___ 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: Light word processor plus the occasional spreadsheet
On Thu, Nov 15, 2012 at 10:06:56AM +0100, Leslie Jensen wrote: Is there an alternative to writer that does not take that long to build? Maybe wordgrinder? http://wordgrinder.sourceforge.net/ Never tried it on FreeBSD (mostly because I refuse to install Lua) but it never takes long to build if it does work. :P ___ 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: Mounting SD card.
On Thu, 15 Nov 2012, Thomas Mueller wrote: I think that's pretty much standard behaviour. The solution appears to be to wake it up with the following incantation: dd if=/dev/null of=/dev/da0 count=0 That's what works here. See the thread starting with http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html true /dev/da0 is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. Could you also do a read such as dd if=/dev/da0 of=/dev/null bs=16k count=1 Unfortunately, no. Retastes are only done after a device has been opened for write. true(1) is nice for that because it never actually writes anything. This still feels awkward and dangerous to me, and I'd like to see an explicit gretaste command. ___ 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: Advanced Format Drive ?
On Thu, 15 Nov 2012, Chris Whitehouse wrote: In messagealpine.bsf.2.00.1211142250370.58...@wonkity.com, In general, you create a partition scheme first. This can be MBR, GPT, or others. (But use GPT.) Unless you want to dual boot with WinXP in which case use MBR still? Yes. The same for Vista or Windows 7, mostly. AFAIK, Windows 7 64-bit on a UEFI system is the only Windows that will boot from GPT. As I've said before, consider using VMs rather than dual booting. ___ 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
One disk shown as two in gsmartcontrol
I'm configuring smartd on a newly installed system, 9.1-RC3 The message below is in my /var/log/messages Nov 15 14:39:49 blj01 kernel: ada0: Maxtor 6B300S0 BANC1G10 ATA-7 SATA 1.x dev ice Nov 15 14:39:49 blj01 kernel: ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192 bytes) Nov 15 14:39:49 blj01 kernel: ada0: 286188MB (586114704 512 byte sectors: 16H 63 S/T 16383C) Nov 15 14:39:49 blj01 kernel: ada0: Previously was known as ad18 Using the GUI gsmartcontrol shows two disks but it's the same disk shown as ada0 and as ad18. I use the following string in /usr/local/etc/smartd.conf /dev/ada0 -a -o on -S on -s (S/../.././11|L/../../6/15) -m name@mail.server Is this normal behaviour? /Leslie ___ 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: Advanced Format Drive ?
On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: In your tutorial document, you say: Create a boot partition to hold the loader, size of 512K. How big is that thing (gpart boot loader), actually? Half a megabyte seems rather a bit large-ish, certainly relative to ye olde MBR loader, which I gather was limited to... what? 32KB (minus a little for the partition table) ? /boot/gptboot is 15K, /boot/gptzfsboot is 39K. A code limitation makes 512K the largest this partition can be made. So I make it that big so it won't have to be increased for bigger boot loaders later. And the space is not wasted because of the next partition... Also, when creating the partition to hold the GPT boot loader, shouldn't that gpart add operation include a -b 4k option, you know, on a modern Advanced Format disk? If not, why not? -a 4k, yes. It doesn't really matter. The loader is read only at boot, once, and it's tiny. So it doesn't really matter if it reads at 30M/second or 500M/second. But yes, for consistency, I'll modify that so the start of the freebsd-boot partition is at 40. You also go on to say: Create partition for /. It should start at the 1M boundary for proper sector alignment on 4K sector drives. Come again? Sorry, but you just lost me entirely. In order to get proper sector alignment on one of these newer Advanced Format (4k) drives, why on earth should it be necessary to begin a partition at some alignment which is greater than the obvious minimum, i.e. 4KB ? Starting the first filesystem partition at 1M is a semi-standard, used by various vendors including Microsoft. Besides being aligned to 4K, it's also aligned to bigger values that can be important for performance on devices like SSDs. And that explains the oversized boot partition. It's space that would be unused otherwise. ___ 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: Advanced Format Drive ?
On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: In message alpine.bsf.2.00.1211142231420.58...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Ronald F. Guilmette wrote: ... Given these facts, I am more than a little surpised to learn (or rather just to realize) that the good old traditional fdisk and bsdlabel tools do not have ways to explicitly specify minimum alignment _and_ that these tools are still being distributed with FreeBSD. There may be a way, I haven't bothered to look. As I said, gpart does everything fdisk and bsdlabel can do. Well, given that newfs has been ``fixed'' so that its defaults will Do The Right Thing with the latest generation of (4KB block) disks, I for one would like to register my vote for fdisk and bsdlabel to either (a) be likewise fixed so that they also will default to Doing The Right Thing (with the current generation of disks) or else (b) be removed from future releases, based on the fact that (apparently) they are now so old that nobody cares about them anymore and/or that their defaults, when (foolishly?) relied upon, are likely to produce Bad Performance, aka Bad Behavior. It's legacy code, and that's always a tough call: update and lose the legacy, or leave it alone and increasingly less useful. Since gpart is available, there's little pressure to change fdisk or bsdlabel. And also, please don't forget the other points I mentioned, i.e. that the man page for fdisk makes several references to alignment on ``cylinder'' and/or ``head'' boundaries. Are those things even relavant anymore? Have they been, anytime in the past 10+ years? (I am guessing that there may be other similarly antiquated references to boundaries that haven't been meaningful for a long long time also in the bdslabel man page, although I confess that didn't even look.) I'd say closer to 20 years. But again, it's that legacy thing. And with FreeBSD, the odds are pretty good that somebody is still running legacy hardware. ___ 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: Mounting SD card.
On Thu, 15 Nov 2012, Polytropon wrote: Is there a recommended way to automate the GEOM re-tasting so SD cards can be accessed without further interaction (by simply using the correct mount command)? Not AFAIK. Could depend on hardware also; some card readers might not need it. ___ 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: One disk shown as two in gsmartcontrol
On Thu, 15 Nov 2012, Leslie Jensen wrote: I'm configuring smartd on a newly installed system, 9.1-RC3 The message below is in my /var/log/messages Nov 15 14:39:49 blj01 kernel: ada0: Maxtor 6B300S0 BANC1G10 ATA-7 SATA 1.x dev ice Nov 15 14:39:49 blj01 kernel: ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192 bytes) Nov 15 14:39:49 blj01 kernel: ada0: 286188MB (586114704 512 byte sectors: 16H 63 S/T 16383C) Nov 15 14:39:49 blj01 kernel: ada0: Previously was known as ad18 Using the GUI gsmartcontrol shows two disks but it's the same disk shown as ada0 and as ad18. I use the following string in /usr/local/etc/smartd.conf /dev/ada0 -a -o on -S on -s (S/../.././11|L/../../6/15) -m name@mail.server Is this normal behaviour? Yes. It's a backwards-compatibility thing. ___ 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: 9.1 permissions in the / directory
On Wed, Nov 14, 2012 at 05:12:59PM -0500, Joseph Mays wrote: Have a recently set up 9.1 RC1 system. Someone (not me, just sayin') did a chmod 600 in the / directory. Needless to say this caused numerous problems. I tried to change them back as best I could by comparing them to an older directory, but some things are still not right. Trying to log in, via either console or ssh as anyone other than root. Ssh gets: %ssh mays@[redacted] Password: Last login: Wed Nov 14 15:50:37 2012 Could not chdir to home directory /home/mays: Permission denied /bin/tcsh: Permission denied Connection to [redacted] closed. % followed by a disconnect. Console complains about the /home/user directory not being there (though it is and the permissions look normal), says it's logging in with slash instead, then says /bin/tcsh: no such file or directory, though /bin/tcsh is there and permissions look fine. I'm attaching a screenshot of the message log that shows up on console logins. So, two questions. What is causing the problem, and does anyone have anything that shows what the normal / directory permissions for 9.1 RC1 should look like? First, login fails to read the user's home directory, because the permissions on either /usr or /home (depending on whether your /home is a directory, or a symlink to /usr/home) don't allow it to see any contained files or directories, even though, from what you say, all contained files and subdirectory permissions are correct. It then attempts to fall back to using / as an emergency home for this session, but then fails to find /bin/tcsh, because the permissions on /bin prevent it from seeing anything it contains. Second, you can restore most, if not all, of the correct permissions with the mtree tool. Log in as root, and then run this: # cd / # mtree -Uef /etc/mtree/BSD.root.dist The mtree specification file, /etc/mtree/BSD.root.dist, contains a list of the files and directories that are installed in a standard FreeBSD system, along with the correct ownership and permissions for those objects. The -U flag tells mtree to modify any objects that don't match the specification, and the -e flag tells it not to warn about files it finds on disk but not in the specification file. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpnuhNxAl49N.pgp Description: PGP signature
Re: Mounting SD card.
On Thu, Nov 15, 2012 at 3:06 AM, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Mike Clarke wrote: On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote: If I boot the system and plug the SD card in, the green led doesn't even switch on and there is only a /dev/da0 that I can not mount. If I boot the system with the card plugged in, the green led is on and there is a /dev/da0s1 device that I can't still mount because mount_msdosfs returns an Input/Output error after some time. I think that's pretty much standard behaviour. The solution appears to be to wake it up with the following incantation: dd if=/dev/null of=/dev/da0 count=0 That's what works here. See the thread starting with http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html true /dev/da0 That doesn't work for me, but the dd operation does. What can be the difference? is a little shorter and safer. The search keywords for this are GEOM retaste or retasting. ___ 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: Mounting SD card.
El día Thursday, November 15, 2012 a las 05:57:45PM +0100, Fernando Apesteguía escribió: On Thu, Nov 15, 2012 at 3:06 AM, Warren Block wbl...@wonkity.com wrote: On Wed, 14 Nov 2012, Mike Clarke wrote: On Wednesday 14 November 2012 19:43:30 Fernando Apesteguía wrote: If I boot the system and plug the SD card in, the green led doesn't even switch on and there is only a /dev/da0 that I can not mount. If I boot the system with the card plugged in, the green led is on and there is a /dev/da0s1 device that I can't still mount because mount_msdosfs returns an Input/Output error after some time. I think that's pretty much standard behaviour. The solution appears to be to wake it up with the following incantation: dd if=/dev/null of=/dev/da0 count=0 That's what works here. See the thread starting with http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/212109.html true /dev/da0 That doesn't work for me, but the dd operation does. What can be the difference? Both commands open the file /dev/da0 for: open(/dev/da0,O_WRONLY|O_CREAT|O_TRUNC,0666) = 3 without writing any myte to it; you can proof this with: # truss dd if=/dev/null of=/dev/da0 count=0 and # truss sh EOF true /dev/da0 EOF matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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
9.0 crash, ssd or filesystem problem?
Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 /usr got error 6 while accessing filesyustem cpuid=0 panic: softdep_deallocate_dependencies:unrecovered I/O error KBD: stack backtrace: #0 ... kbd_backtrace+0x5e #1 ... panic+0x187 #2 ... clear_remove+0 #3 ... brelse+0x60 (ada0:ahcich1:0:0:0): lost device #4 ... bufdone+0x68 #5 ... g_io_schedule_up+0xa6 #6 ... fork_exit+0x11f #7 ... fork_trampoline+0xe This happens consistently when doing portmaster www/firefox ... firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found The firefox build said it was going to build audio/alsa also, so to make things easier after rebooting I would do portmaster audio/alsa which would succeed, and then again try portmaster www/firefox which would always fail the same way. The interesting part about the above is that after the crash, the firefox build would say it needed to build audio/alsa again. I tried doing portmaster lang/perl5.12 to rebuild perl and get it placed somewhere different on the ssd, but I'm still getting a consistent crash after I get the firefox-16.0.2,1 depends on file: /usr/local/bin/perl5.12.4 - found line. I'm guessing it's crashing on something after the perl; how to find out what it is? Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Gary ___ 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: 9.0 crash, ssd or filesystem problem?
On Thu, Nov 15, 2012 at 1:18 PM, Gary Aitken free...@dreamchaser.orgwrote: Error 6 is ENXIO, device not configured; not sure exactly what that means. This machine has: 16G mem 0.5G swap 2G /tmp 4G /var Is any of that likely to be related to the problem? Given an addr in the failure error: g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 how does one relate that addr to the partitioning scheme? ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) Thanks for any insights, Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. -- 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
Re: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012 13:30:43 -0600 Adam Vande More amvandem...@gmail.com wrote: Sounds like you have bad hardware. Drive, cable, controller etc. Probably wouldn't hurt to do a fsck either. *After* identifying and fixing the hardware problem, otherwise you may make things worse. -- Steve O'Hara-Smith at...@sohara.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
ale0: could not disable Tx/Rx MAC(0x00000004)!
Hello, I got the following problem today: 66nneewwnnffss sseerrvveerr 119922..116688..00..225544:://hhoommee//mmaaggee:: nnoto t rreespsopnonddiinngg newnfs server 192.168.0.254:/home/mage: not responding ale0: could not disable Tx/Rx MAC(0x0004)! ale0: link state changed to DOWN ale0: could not disable Tx/Rx MAC(0x0004)! ale0: link state changed to UP in6_purgeaddr: err=65, destination address delete failed Nov 15 22:08:02 rivendell dhclient[1186]: short write: wanted 20 got 0 bytes Nov 15 22:08:02 rivendell dhclient[1186]: exiting. Only a hard reboot fixed the issue (the network was completely frozen) This is with: ale0@pci0:2:0:0:class=0x02 card=0x83041043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Atheros Communications' device = 'AR8121/AR8113/AR8114 Gigabit or Fast Ethernet' class = network subclass = ethernet on: FreeBSD rivendell 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0: Thu Nov 1 18:35:54 CET 2012 root@rivendell:/usr/obj/usr/src/sys/CUSTOM amd64 Any idea what could be the cause of this ? Thank you, Julien ___ 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: Advanced Format Drive ?
In message 50a4f2c8.5040...@qeng-ho.org, Arthur Chance free...@qeng-ho.org wrote: On 11/15/12 12:41, Ronald F. Guilmette wrote: -b is the beginning block of a partition. 34 is a magic value, the size of a standard GPT partition table. It probably wouldn't have hurt anything to mention that in the gpart man page. And what about 162? Is that magic too? If so, how? I seriously do not know. The man example should be taken as a whole. You've got /sbin/gpart add -b 34 -s 128 -t freebsd-boot ad0 which gives you a 128 block partition starting at block 34, so the next free block is 162, and the next partition is explicitly started there in /sbin/gpart add -b 162 -s 1048576 -t freebsd-ufs ad0 No magic, just arithmetic. :-) Ah! Silly me! Thank you. (I did miss that.) Regards, rfg ___ 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: Advanced Format Drive ?
In message alpine.bsf.2.00.1211150828040.62...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: In your tutorial document, you say: Create a boot partition to hold the loader, size of 512K. How big is that thing (gpart boot loader), actually? Half a megabyte seems rather a bit large-ish, certainly relative to ye olde MBR loader, which I gather was limited to... what? 32KB (minus a little for the partition table) ? /boot/gptboot is 15K, /boot/gptzfsboot is 39K. A code limitation makes 512K the largest this partition can be made. So I make it that big so it won't have to be increased for bigger boot loaders later. It wouldn't hurt to add the above info to your tutorial page. And the space is not wasted because of the next partition... Huh? Oh, oh, OK. I read down to the end of your message and now understand. You meant that the space is not wasted because you will subsequently arrange to have the next following partition begin at 1MB, yes? Also, when creating the partition to hold the GPT boot loader, shouldn't that gpart add operation include a -b 4k option, you know, on a modern Advanced Format disk? If not, why not? -a 4k, yes. Yea. Sorry. That's what I meant... -a 4k. It doesn't really matter. The loader is read only at boot, once, and it's tiny. So it doesn't really matter if it reads at 30M/second or 500M/second. OK. I understand. Thanks. (I did supect that this was the rationale.) But yes, for consistency, I'll modify that so the start of the freebsd-boot partition is at 40. It looks prettier that way. Besides which, you probably want to get your readers in the habit of doing things generally on 4KB boundaries, because (as I have just learned) they are probably going to need to start doing that before too long, even if they don't already need to just yet. You also go on to say: Create partition for /. It should start at the 1M boundary for proper sector alignment on 4K sector drives. Come again? Sorry, but you just lost me entirely. In order to get proper sector alignment on one of these newer Advanced Format (4k) drives, why on earth should it be necessary to begin a partition at some alignment which is greater than the obvious minimum, i.e. 4KB ? Starting the first filesystem partition at 1M is a semi-standard, used by various vendors including Microsoft. Yeabut why or how does Microsoft get involved at all with the position of my *FreeBSD* partition?!? If I began my FreeBSD partition at, say 768KB, would anything from Microsoft be even likely to even notice? Besides being aligned to 4K, it's also aligned to bigger values that can be important for performance on devices like SSDs. I see. That's also another useful tidbit of knowledge that you may also wish to impart to readers of your tutorial. I can only speak for myself, but I for one (perhaps because I have never owned an SSD myself) was totally unaware that those had any such additional alignment issues. And that explains the oversized boot partition. It's space that would be unused otherwise. Got it. Thanks. Regards, rfg P.S. I really do think that it is a serious omission that the gpart(8) man page doesn't really say anything regarding proper or desirable use of the add -a option. If it were up to me, I'd put in just a couple of short notes that would say at least something about 4K being Good and Desirable for modern drives, and 1M being Good and Desirable for SSDs. But maybe that kind of info does really belong in something more like an actual tutorial document... you know... something like, um, your's. ___ 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: Advanced Format Drive ? GPT ?
Warren Block wrote: On Wed, 14 Nov 2012, Ronald F. Guilmette wrote: I'm looking at the examples section of the gpart(8) man page. May I assume that if I just want to merely ``try out'' GPT... you know... taking it out on the road for a first time test run... that I can just do the first five (5) commands listed under EXAMPLES and then that will be enough to go ahead and try installing FreeBSD into the created freebsd-ufs partition? Even assuming that the answer is yes, I have still more questions... Where are these magic numbers coming from?? I am specifically talking about the number 34 in the -b 34 option and also the number 162 in the -b 162 option. Tha man page just tosses those into the example command lines without saying a word about them. And you can probably guess what it is that is especially troubling to me about them... neither one of them is divisible by 8 (i.e. 4KB/512B). So would the examples in the current gpart(8) man page produce an Epic Fail when and if they were used with a modern Advanced Format drive? -b is the beginning block of a partition. 34 is a magic value, the size of a standard GPT partition table. A good overall reference on GPT is the Wikipedia page: http://en.wikipedia.org/wiki/GUID_Partition_Table Remember that the man page is a reference, not a tutorial. I wanted more specific notes that followed best practices, and that was the source for this article: http://www.wonkity.com/~wblock/docs/html/disksetup.html In general, you create a partition scheme first. This can be MBR, GPT, or others. (But use GPT.) Rather than combine the bootcode with the partition table, GPT just uses a small partition for it. Since the standard GPT allows for up to 128 partitions, there's no reason not to use them. Next come other partitions for UFS or ZFS filesystems or swap. That's it, really. The rest is details the man page can explain, like additional options for alignment. (The creation of the first UFS partition in the article does not use -a because older versions of gpart did unexpected things when -a and -b were combined. The alignment produced is correct.) ___ 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 Aloha Warren, I looked over the GPT sample and have a question. In the fstab entries, something that uses msdosfs, (thumb drive maybe). Can you enter it directly in the fstab after the basic partitions and other /dev have been entered in the initial setup? Thanks. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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: Advanced Format Drive ?
In message alpine.bsf.2.00.1211150844350.62...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: Well, given that newfs has been ``fixed'' so that its defaults will Do The Right Thing with the latest generation of (4KB block) disks, I for one would like to register my vote for fdisk and bsdlabel to either (a) be likewise fixed so that they also will default to Doing The Right Thing (with the current generation of disks) or else (b) be removed from future releases, based on the fact that (apparently) they are now so old that nobody cares about them anymore and/or that their defaults, when (foolishly?) relied upon, are likely to produce Bad Performance, aka Bad Behavior. It's legacy code, and that's always a tough call: update and lose the legacy, or leave it alone and increasingly less useful. Since gpart is available, there's little pressure to change fdisk or bsdlabel. Well, I'll tell you seriously that I, for one, didn't get the memo as the saying goes. Honestly, this discussion is the first time that I personally ever heard that fdisk and/or bsdlabel were being relegated to the dustbin of history. (But then again, I don't get out much, or enough, it seems.) Maybe the man pages should contain notes/warnings saying explicitly This tool is now depreciated in favor of gpart. What do you think? Is that a suggestion worthy of a formal PR? And also, please don't forget the other points I mentioned, i.e. that the man page for fdisk makes several references to alignment on ``cylinder'' and/or ``head'' boundaries. Are those things even relavant anymore? Have they been, anytime in the past 10+ years? (I am guessing that there may be other similarly antiquated references to boundaries that haven't been meaningful for a long long time also in the bdslabel man page, although I confess that didn't even look.) I'd say closer to 20 years. Um yea. That's probably closer to the mark. Sigh. Time flies when you're having fun. (And they also like arrows, I'm told.) But again, it's that legacy thing. And with FreeBSD, the odds are pretty good that somebody is still running legacy hardware. Yea, you are undoubtedly right about that. I wonder... can FreeBSD still run on 386s? I can envision a humorous boot-time message that somebody may see someday... Sorry, FreeBSD cannot run on this hardware. Please invest in something that was actually manufactured this century (20xx). :-) ___ 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
WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
Hello, from a freshly installed FreeBSD 9.0-RELEASE I did a freebsd-update to bring it to the latest patch level. After: # freebsd-update fetch I got this message: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. What does this exactly mean? Is the whole 9.0 Series approaching EOL, or does this only apply to the initial 9.0-RELEASE _AND NOT_ to e.g. 9.0-RELEASE-p3 ? Where can I find more information on the planned lifecycles of the current and upcoming releases? Are there any? Thanks kind regards Matthias -- Matthias Petermann matth...@d2ux.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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
On Thu, Nov 15, 2012 at 1:57 PM, Matthias Petermann matth...@d2ux.net wrote: Where can I find more information on the planned lifecycles of the current and upcoming releases? Are there any? http://www.freebsd.org/security/ Scroll down about halfway. 9.0 is a regular release, EOL is January 31, 2013. Alternate releases are extended releases, so 9.1 will have a 2 year support span. - M ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
On Thu, Nov 15, 2012 at 3:57 PM, Matthias Petermann matth...@d2ux.netwrote: Hello, from a freshly installed FreeBSD 9.0-RELEASE I did a freebsd-update to bring it to the latest patch level. After: # freebsd-update fetch I got this message: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. What does this exactly mean? Means exactly what it says. 9.0 will soon be unsupported. Things like p1, p2 etc are patchsets to a release, they are not a release onto themselves. http://www.freebsd.org/security/#sup -- 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
Re: Advanced Format Drive ?
On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: In message alpine.bsf.2.00.1211150828040.62...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: In your tutorial document, you say: Create a boot partition to hold the loader, size of 512K. How big is that thing (gpart boot loader), actually? Half a megabyte seems rather a bit large-ish, certainly relative to ye olde MBR loader, which I gather was limited to... what? 32KB (minus a little for the partition table) ? /boot/gptboot is 15K, /boot/gptzfsboot is 39K. A code limitation makes 512K the largest this partition can be made. So I make it that big so it won't have to be increased for bigger boot loaders later. It wouldn't hurt to add the above info to your tutorial page. The problem with that sort of detail is that too much of it obscures the point, which in this case is just trying to show the right way to set up disks without overwhelming the reader. And the space is not wasted because of the next partition... Huh? Oh, oh, OK. I read down to the end of your message and now understand. You meant that the space is not wasted because you will subsequently arrange to have the next following partition begin at 1MB, yes? Yes. Besides which, you probably want to get your readers in the habit of doing things generally on 4KB boundaries, because (as I have just learned) they are probably going to need to start doing that before too long, even if they don't already need to just yet. It does do that, although it's not overt. Starting the first filesystem partition at 1M is a semi-standard, used by various vendors including Microsoft. Yeabut why or how does Microsoft get involved at all with the position of my *FreeBSD* partition?!? There are other vendors and some RAID systems that also use 1M as a starting point. Sticking to that de facto standard helps keep us as compatible as possible with other systems and partitioning software. The cost in space is tiny, and it's a lot easier to do when setting up the disk than after the filesystems are populated. If I began my FreeBSD partition at, say 768KB, would anything from Microsoft be even likely to even notice? I can't say I've tested it. I see this as low-cost insurance. For less than 1M of space, try to be as compatible with other systems and software that exists. Besides being aligned to 4K, it's also aligned to bigger values that can be important for performance on devices like SSDs. I see. That's also another useful tidbit of knowledge that you may also wish to impart to readers of your tutorial. I can only speak for myself, but I for one (perhaps because I have never owned an SSD myself) was totally unaware that those had any such additional alignment issues. Again, I'm trying to avoid too much of that type of detail in that particular article. I've considered writing a separate SSD article, but have not done it yet. P.S. I really do think that it is a serious omission that the gpart(8) man page doesn't really say anything regarding proper or desirable use of the add -a option. If it were up to me, I'd put in just a couple of short notes that would say at least something about 4K being Good and Desirable for modern drives, and 1M being Good and Desirable for SSDs. But maybe that kind of info does really belong in something more like an actual tutorial document... you know... something like, um, your's. I can see it both ways. A short mention of those values in that section of gpart(8) would be helpful. The 1M value is controversial to some people. Of course, some people think that calling bare bsdlabel disks dangerously dedicated or using an MBR is controversial. ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
Hi, On Thu, 15 Nov 2012 14:35:52 -0800 Michael Sierchio ku...@tenebras.com wrote: http://www.freebsd.org/security/ Scroll down about halfway. 9.0 is a regular release, EOL is January 31, 2013. Alternate releases are extended releases, so 9.1 will have a 2 year support span. Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Kind regards, Matthias -- Matthias Petermann matth...@d2ux.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: Advanced Format Drive ?
In message alpine.bsf.2.00.1211151456450.66...@wonkity.com, Warren Block wbl...@wonkity.com wrote: It wouldn't hurt to add the above info to your tutorial page. The problem with that sort of detail is that too much of it obscures the point, which in this case is just trying to show the right way to set up disks without overwhelming the reader. personal opinion Some things are inherently overwhelming, and there is no use to try to hide the fact. It just makes matters worse. /personal opinion P.S. I really do think that it is a serious omission that the gpart(8) man page doesn't really say anything regarding proper or desirable use of the add -a option. If it were up to me, I'd put in just a couple of short notes that would say at least something about 4K being Good and Desirable for modern drives, and 1M being Good and Desirable for SSDs. But maybe that kind of info does really belong in something more like an actual tutorial document... you know... something like, um, your's. I can see it both ways. A short mention of those values in that section of gpart(8) would be helpful. The 1M value is controversial to some people. Yeabut for some people, even evolution is controversial. Of course, some people think that calling bare bsdlabel disks dangerously dedicated or using an MBR is controversial. Actually, you can count me among the folks who think that the adjective dangerously may be stretching it a bit, in this context. ___ 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: 9.0 crash, ssd or filesystem problem?
On Thu, 15 Nov 2012, Gary Aitken wrote: Trying to rebuild ports, I'm consistently getting the following: ahcich1 Timeout on slot 13 port 0 ^ slot varies g_vfs_done() ada0p6 [WRITE(offset=38838571008 length=4096)]error=6 That seems familiar, maybe others have reported it. Is this a motherboard controller, or add-in? After a backup, I'd make sure the motherboard and controller BIOS are up to date. And also the SSD firmware. ~$ gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 41943040 2 freebsd-ufs (20G) / 419432021048576 3 freebsd-swap (512M)swap 429917788388608 4 freebsd-ufs (4.0G) /var 513803864194304 5 freebsd-ufs (2.0G) /tmp 55574690 192216088 6 freebsd-ufs (91G) /usr 2477907782278869- free - (1.1G) It would not cause this problem, but those partitions are not aligned. That would only affect speed, not reliability. ___ 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: Advanced Format Drive ?
Warren, In the EXAMPLES section of the gpart(8) man page, they do this: /sbin/gpart bootcode -b /boot/pmbr ad0 In your document however, you first create an explicit (special) partition named gpboot and then you do this instead: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 Who is right in this case? I did the former, and did not get any error. The gpart(8) man page says: ... First, a protective MBR is embedded into the first disk sector from the /boot/pmbr image... however it appears to me that the steps in your tutorial are effectively installing a copy of the /boot/pmbr file into block #40 of the disk. Yes? But isn't a copy of /boot/pmbr really supposed to end up in the first 512 bytes of the disk, i.e. block #0 ? ___ 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: Advanced Format Drive ? GPT ?
On Thu, 15 Nov 2012, Al Plant wrote: I looked over the GPT sample and have a question. In the fstab entries, something that uses msdosfs, (thumb drive maybe). Can you enter it directly in the fstab after the basic partitions and other /dev have been entered in the initial setup? Short answer: yes, but... Longer answer: most flash drives have an MBR partition setup with one partition filling the whole device. Since it's not GPT, it won't/can't have GPT labels on the partitions. But the GEOM system will create a label for the MSDOS filesystem if it has been given a volume name. That label will appear in /dev/msdosfs/ and can be used in an /etc/fstab entry. ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
On 15 November 2012, at 14:46, Matthias Petermann wrote: Hi, On Thu, 15 Nov 2012 14:35:52 -0800 Michael Sierchio ku...@tenebras.com wrote: http://www.freebsd.org/security/ Scroll down about halfway. 9.0 is a regular release, EOL is January 31, 2013. Alternate releases are extended releases, so 9.1 will have a 2 year support span. Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Yes. I have done that from 9.0 to 9.1-RC1 and later RC2. It takes longer than you would like, but works just fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Texlive
15.11.2012, 23:45, Belgacem Jellali belgacem.jell...@gmail.com: Salut J'aime beaucoup FreeBSD, mais je ne peux pas l'utiliser au quotidien car j'ai besoin de TexLive2012 et les ports FreeBSD ne le fournissent pas. Y-a-t'il un moyen pour installer TexLive2012? si oui, je ne supprimerai jamais FreeBSD pour installer une Linyx. Merci Not 100% sure, google translation was good, but I guess you're looking for http://code.google.com/p/freebsd-texlive/ -- Aldis Berjoza FreeBSD addict ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
On Thu, 15 Nov 2012 23:46:53 +0100 Matthias Petermann matth...@d2ux.net wrote: Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Yes, it is. Andreas -- GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 ___ 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: Advanced Format Drive ?
(This stuff would probably be a lot less confiusing if I actually knew what I was doing, but...) OK, Warren, I've just done the following steps. The first two I drew from the manpage examples, and then followed those up with two commands from your tutorial. /sbin/gpart create -s GPT ada0# manpage example is wrong, ad0 - ada0 /sbin/gpart bootcode -b /boot/mbr ad0 # manpage wrong again, pmbr - mbr gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ada0 gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 That last one, done at the suggestion of your tutorial page, has me completely perplexed, because of what is said, very explicitly, in the gpart(8) manpage: bootcode Embed bootstrap code into the partitioning scheme's metadata on the geom (using -b bootcode) or write bootstrap code into a partition (using -p partcode and -i index). Please note the use of the word or. The man page is telling me to _either_ use the -p option _or else_ use the -p and -i options together. But you are telling me to use all three in one go! Forgive me, but I'm confused. (As you can tell by now, I am often easily confused. Sorry.) ___ 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
eGalax USB touch panel on ExoPC Slate vs. FreeBSD and X11
Okay. I have my doubts that anyone will be able to answer this question but I'm going to try anyway. I have an ExoPC Slate tablet with FreeBSD 9.0 freshly installed on it, and it has the following touch screen device: ugen0.2: eGalax Inc. at usbus0 ums0: eGalax Inc. USB TouchController, class 0/0, rev 1.10/10.06, addr 2 on usbus0 tablet# usbconfig -u 0 -a 2 dump_device_desc ugen0.2: USB TouchController eGalax Inc. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0eef idProduct = 0x72a1 bcdDevice = 0x1006 iManufacturer = 0x0001 eGalax Inc. iProduct = 0x0002 USB TouchController iSerialNumber = 0x no string bNumConfigurations = 0x0001 I put the complete dmesg.boot from FreeBSD 9.0 on the tablet at: http://people.freebsd.org/~wpaul/exopc/dmesg.boot This device is detected by the ums(4) driver as a USB mouse. However, it doesn't quite work right as the ums(4) driver doesn't support multitouch gestures. It senses taps on the screen as button presses, but the cursor doesn't move. My question is: Can someone please tell me how to get this device to work with Xorg in FreeBSD (in this case, FreeBSD 9.0)? Here are some things I'd prefer you didn't tell me: - Try the uep(4) driver! Yes, I know about the uep(4) driver. It's for a different class of device. It doesn't support this one. - Try this patch! I'm hoping for an officially supported solution rather than an experimental patch. I mean, it's not that I don't appreciate someone's hard work and all, but these things have been around for a while now; you'd think support for it would already be integrated. And besides, it works with Linux. (You don't know how long I've been wanting to say that.) - Go to this web page! This _might_ be an acceptable answer _IF_ the said page contains specific instructions which are known to work. I already searched through many web pages before I came here. - Hey Bill, why don't you just write your own driver? Because I don't write FreeBSD drivers anymore, and I certainly don't write USB HID drivers, and because fuck you, that's why. (Note: I said that last part with a smile on my face, just in case it wasn't clear. Sometimes people have a hard time grasping my particular brand of humor.) This particular touch screen is basically a USB HID class device. I suspect there's some kind of gimmick you can do with libusb to get it to work with the X server, but I've already spent some time on various experimenmts and come up empty. As I said, I'm hoping there's official support for this kind of device, and I just need to know the right magic incantation to turn it on. Any help would be appreciated. -Bill -- = -Bill Paul(510) 749-2329 | Member of Technical Staff, wp...@windriver.com | Master of Unix-Fu - Wind River Systems = I put a dollar in a change machine. Nothing changed. - George Carlin = ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
Andreas == Andreas Rudisch cyb.@gmx.net writes: Andreas On Thu, 15 Nov 2012 23:46:53 +0100 Andreas Matthias Petermann matth...@d2ux.net wrote: Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Andreas Yes, it is. Can I go from 8.3 directly to 9.1, or should I stop over at 9.0 first? -- 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: Advanced Format Drive ?
NEVERMIND! It took me awhile, but I think I've finally got the hang of this gpart/GPT stuff... well... mostly anyway (but see below). I understand now that /boot/mbr is a regular sort of MBR, with regular sort of MBR bootstrap code, whereas /boot/pbmr is the ``protected'' MBR record that says, in effect I am not a normal MBR. I am special and I'm here to tell you that this drive actually uses the GPT scheme. I've also figured out that despite the gpart(8) man page's unfortunate use of the word or, it is evidently the case that when doing gpart bootcode ... it is perfectly OK to use all three of the -b, -p, and -i options together, and that doing so has (I think) the equivalent effect to invoking gpart bootcode ... once with only the -b option and then once again with only the -p and -i options together. I think that I have only two final questions: 1) I can't remember now if the ``guided'' partitioning approach that is offered to folks who are installing FreeBSD 9.x itself offers a GPT option or not. Does it? (If not, and if MBR is really now considered antiquated, then I would think that the install process really should offer a GPT option, if it isn't doing so already.) 2) Not knowing any better, on this fresh install that I'm doing now (of 9.1-RC3) when it got down to the point where it asked me how I wanted to partition, I selected the exit to shell option. Once I got a shell prompt, I proceeded to do bascially everything that's suggested in the The New Standard Method section of Warren's nice tutorial. My assumption was that I could do this, get all of my shiny new GPT partitions just the way I wanted them, and just simply exit the shell... an action which, I had hoped, would return me to the install process at a point where I would then be asked to assign mount points to each of my newly created GPT partitions, and then, hopefully, the rest of the install process would proceed in an entirely customary way. Sadly, this did not happen. After exiting from the shell, the install process _did_ resume, however the first thing it did was to check the integrity of the distributions (kernel+base) that I had selected earlier, and once it was satisfied that they were OK, it immediately started to try to extract everything from those two distribution files. It is easy to undeerstand why this last step failed virtually immediately with the error message: Error while extracting base.txz: Can't set user=0/group=0 for .Can't update time for . Obviously (and quite reasonably) the install process did not have any clear idea of where exactly it was supposed to be extracting the files to, because I had not even assigned mount points for any of my brand new GPT partitions yet. So, um, I'm wondering... Is this a bug, or a feature of the current FreeBSD install process? Should I be filing a PR on this? -=-=-=-=-=-=-=-=-=-=-=-=- A footnote: Since my first try at installing using a GPT partitioning scheme crashed and burned (as described above), I naturally hit the reset button on the machine in question and just started over from the beginning of the whole install process, hoping that I would (this time) be able to make use of the various GPT partitions that I had already set up. (See above.) After the obligatory preliminary questions, I finally I came to the place in the process where it wanted to know if I wanted to do guided, manual, or shell partitioning. At this point, I figured that it made little difference which one I choose (because I'd already created the partitions, and even newfs'd them all) and now I only needed to assign mount points. So I selected the easy choice... guided... and immediately I got an error message that said there is not enough free space on the drive to install FreeBSD. (Gr!) Oh well! Along with that error message, I was given an option to open the partition editor, so I took that option and then just assigned proper mount points to all of the partitions that I'd already created, and then, finally, I clicked on Finish. From there, everything went fine and I successfully installed a minimal 9.1-RC3 system, and then successfully booted it. But then I started to wonder if maybe Warren had left out the instructions for performing this final critical step (assigning mount points) in his tutorial, so I went back and looked at it to see if he had mentioned it, and I see that it doesn't say a word about mount points. Warren? Was this a deliberate or inadvertant ommission? Is the subject of mount points outside of the scope of what you had been intending to cover in your tutorial? And how exactly do mount points get associated with partitions (in particular GPT partitions) anyway? Are these just another partition attribute? The gpart(8) man page is also utterly silent on the subject of mount points, even though they are quite obviously a rather critical component of what it takes to make a partition useful on/to FreeBSD. P.S. Assigning
Re: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
On 15 November 2012, at 17:04, Randal L. Schwartz wrote: Andreas == Andreas Rudisch cyb.@gmx.net writes: Andreas On Thu, 15 Nov 2012 23:46:53 +0100 Andreas Matthias Petermann matth...@d2ux.net wrote: Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Andreas Yes, it is. Can I go from 8.3 directly to 9.1, or should I stop over at 9.0 first? For me that was not possible. My disks were partitioned and labeled when FreeBSD 4.7 was new. The size of the root partition was now too small for 9.0. I had to do a complete install and reformat of the drives to get to 9.0. My root partition was a bit small for 7.x as I had to delete the symbol files to make it fit. ___ 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
How close is 9.1 to release?
Have begun getting warnings from freebsd-update that 9.0 is close to its EOL, but the successor release (9.1) is not even out yet... which means that there's no way to gauge its stability or quality by watching for reported problems. How's 9.1-RELEASE coming? Any showstoppers? --Brett Glass ___ 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: Mounting SD card.
On 16/11/2012 02:25, Warren Block wrote:
On Thu, 15 Nov 2012, Polytropon wrote:
Is there a recommended way to automate the GEOM re-tasting so
SD cards can be accessed without further interaction (by simply
using the correct mount command)?
Not AFAIK. Could depend on hardware also; some card readers might not
need it.
I haven't tried this ---
Given that the reader is a usb device could it be added to the devd setup?
Something like -
attach 200 {
device-name da[0-9]+;
match vendor 0x058f;
match product 0x6362;
action /usr/bin/true /dev/${device-name};
};
Saved to /usr/local/etc/devd/SD.conf
vendor and product are from my internal reader that I never use as I
never did get it to mount a card - I have an external reader that works
fine. There should be a more generic way to recognise card readers.
___
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: Advanced Format Drive ?
On Thu, 15 Nov 2012, Ronald F. Guilmette wrote: I think that I have only two final questions: 1) I can't remember now if the ``guided'' partitioning approach that is offered to folks who are installing FreeBSD 9.x itself offers a GPT option or not. Does it? (If not, and if MBR is really now considered antiquated, then I would think that the install process really should offer a GPT option, if it isn't doing so already.) GPT is the default for bsdinstall. 2) Not knowing any better, on this fresh install that I'm doing now (of 9.1-RC3) when it got down to the point where it asked me how I wanted to partition, I selected the exit to shell option. Once I got a shell prompt, I proceeded to do bascially everything that's suggested in the The New Standard Method section of Warren's nice tutorial. My assumption was that I could do this, get all of my shiny new GPT partitions just the way I wanted them, and just simply exit the shell... an action which, I had hoped, would return me to the install process at a point where I would then be asked to assign mount points to each of my newly created GPT partitions, and then, hopefully, the rest of the install process would proceed in an entirely customary way. It would, but you have to mount the new filesystems in a certain spot. bsdinstall shows a prompt about that. And how exactly do mount points get associated with partitions (in particular GPT partitions) anyway? Are these just another partition attribute? The gpart(8) man page is also utterly silent on the subject of mount points, even though they are quite obviously a rather critical component of what it takes to make a partition useful on/to FreeBSD. GPT partitions appear in /dev as the drive name followed by p and the partition number, similar to the old slice/partition notation. So instead of /dev/ada0s1a, it will typically be /dev/ada0p2. These are entered in /etc/fstab as normal. My guide uses GPT labels, which are superior in many ways to fixed device names, but also not really covered by that article. P.S. Assigning mount points appears to be one thing that the new swiss- army-knife of gpart _cannot_ do. Given that, I have to ask... What if any command line tool is available to associate partitions with mount points? /etc/fstab, same as normal. ___ 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: Mounting SD card.
On Fri, 16 Nov 2012 13:25:28 +1030, Shane Ambler wrote:
On 16/11/2012 02:25, Warren Block wrote:
On Thu, 15 Nov 2012, Polytropon wrote:
Is there a recommended way to automate the GEOM re-tasting so
SD cards can be accessed without further interaction (by simply
using the correct mount command)?
Not AFAIK. Could depend on hardware also; some card readers might not
need it.
I haven't tried this ---
Given that the reader is a usb device could it be added to the devd setup?
Something like -
attach 200 {
device-name da[0-9]+;
match vendor 0x058f;
match product 0x6362;
action /usr/bin/true /dev/${device-name};
};
Saved to /usr/local/etc/devd/SD.conf
vendor and product are from my internal reader that I never use as I
never did get it to mount a card - I have an external reader that works
fine. There should be a more generic way to recognise card readers.
Interesting approach, but I can already predict where it would
fail at least for my setup: I have an internal card reader for
SD, CF and other kinds of media, connected per internal USB to
the main board. The device files representing the slots are
present since system startup: da0, da1, da2. They do not change
when a card is inserted. In fact, the OS does not notice if a
card is inserted (or even removed). Using the true /dev/da0
approach causes the card to be recognized, as some of the cards
can have a /dev/da0s1 primary DOS partition which has to be
mounted (instead of blindly trying /dev/da0).
However, this approach might work with external 35 in 1 card
readers connected to external USB _with_ the card being present
when attached to the system.
Sadly, the handling of that specific kind of removable media is
still sub-optimum, nearly near-pessimum, si se oblivisci quae
vellet. :-)
--
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: Texlive
On Thu, Nov 15, 2012 at 10:44:54PM +0100, Belgacem Jellali wrote: Salut J'aime beaucoup FreeBSD, mais je ne peux pas l'utiliser au quotidien car j'ai besoin de TexLive2012 et les ports FreeBSD ne le fournissent pas. Y-a-t'il un moyen pour installer TexLive2012? si oui, je ne supprimerai jamais FreeBSD pour installer une Linyx. Vous pouvez bien installer TeXLive en aller à http://www.tug.org/texlive/acquire-netinstall.html et download install-tl-unx.tar.gz Si vous faites cs que c'est dit là et changez votres $PATH - voilà - TeXLive marche. N'installez pas le port /usr/ports/print/teTeX-texmf en même temps. Sabine -- Nicht das Schicksal zu aendern, sondern sich ihm zu unterwerfen, macht den Heroismus des autoritaeren Charakters aus. (E. Fromm) ___ 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: WARNING: FreeBSD 9.0-RELEASE is approaching its End-of-Life date.
Hi Andreas, do I understand it right - the default behaviour of freebsd-update will be to update a 9.0 system to 9.1 when it becomes available? So this is a rolling procedure? I ask this because I could not find a parameter etc. in the man page which may influent this, e.g. to limit updates to stay in a main release (9.0, 9.0-p1, 9.0-p., 9.0-p12) but don't upgrade to 9.1. Kind regards, Matthias Am Freitag, 16. November 2012 00:25 CET, Andreas Rudisch cyb.@gmx.net schrieb: On Thu, 15 Nov 2012 23:46:53 +0100 Matthias Petermann wrote: Thanks for the clearification. One technical thing: is it possible, to upgrade from FreeBSD 9.0 to 9.1 with the freebsd-update utility? Yes, it is. ___ 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
