Why Linux executable googleearth can't find proper libstdc++.so.6 ?
I installed port google-earth. When I run 'googleearth' I get such messages: ./googleearth-bin: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./libgoogleearth_lib.so) ./googleearth-bin: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./libbase.so) Thinking that it picks up FreeBSD libs instead of Linux ones I added LD_LIBRARY_PATH=/compat/linux/usr/lib, and I got the similar messages again: ./googleearth-bin: /compat/linux/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./libgoogleearth_lib.so) ./googleearth-bin: /compat/linux/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./libbase.so) Why I get these messages about GLIBCXX_3.4.9? Is it a bug in port? Or in package? Or in system? /etc/make.conf has the line, if that matters: OVERRIDE_LINUX_BASE_PORT=fc6 Yuri ___ 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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 22:54, nealhogan@ wrote: It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. I speak english, french, italian, some spanish and german as well as latvian... but I would never attempt to translate into any language other than English... and then not without the help of the original language's originator. ;-) since I'm in the mood PJ, you certainly sound like a scholar . . . you speak many languages and have a strict translation policy, yet (given those two points) it doesn't follow you have any idea how to use any of those languages. You prefer drama and at some point we're going to realize that there is no wolf? KISS! (google for translation). Dear Neal, Stop being a pathetic reply artist. Hit [Delete] next time or learn how to lead-in your replies so everyone knows who your replying to. He actually has a real point its just not caught with all the unneeded attention your bring to hist statement about language. Little over dramatic and pathetic give it up its email PS: echo \ '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc Your best friend. -- ;; dataix.net!jhell 2048R/89D8547E 2009-09-30 ;; BSD since FreeBSD 4.2Linux since Slackware 2.1 ;; 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E ___ 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
pf, ssh related question
Hello,
I have the following annoying thing: all the time I runpfctl -F all -f
/etc/pf.conf I got disconnected from my remote machine.
Do you have any idea how can I avoid this?
Here is my pf.conf
#MACROS
ext_if=rl0
int_if=rl1
good_ip={192.168.1.0/24}
icmp_types=echoreq
set skip on lo
scrub in
block in
pass out keep state
antispoof quick for { lo $int_if }
#incoming ssh
pass in log quick on $int_if inet proto tcp from $good_ip to ($int_if) port 22
flags S/SA keep state
#incoming http
pass in log quick on $int_if inet proto tcp from $good_ip to ($int_if) port 80
flags S/SA keep state
pass in inet proto icmp all icmp-type $icmp_types keep state
___
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: pf, ssh related question
On 17 okt 2009, at 11:53, Dánielisz László laszlo_daniel...@yahoo.com wrote: Hello, I have the following annoying thing: all the time I runpfctl -F all - f /etc/pf.conf I got disconnected from my remote machine. Do you have any idea how can I avoid this? You cannot avoid when you flush all your current states. Peter -- http://www.boosten.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: Best procedure for full backup of live system
Nerius Landys wrote: dd if=/dev/ad4 of=MBR_backup bs=512 count=1 to back up the MBR, so I can recontruct the boot program and partition table. But they don't mention that in the Handbook. While that will back up the Master Boot Record, it's not sufficient for the general case of MS-DOS style partitions. It will only include the primary and extended partitions. The logical partitions, which exist inside an extended partition, are a linked list whose elements are distributed across your disk somewhere. If you have any extended partitions, you need to back them up too. They aren't part of the 512-byte MBR so just using dd to grab the first 512 bytes won't do. The Linux sfdisk program can create a machine readible text file that includes any logical partitions. Does FreeBSD also have sfdisk? Perhaps it's in ports. I don't have my FreeBSD box handy right now so I can't just look. ... and as has been pointed out, you'll also want your BSD disklabel which is a whole different beast. Mike -- Michael David Crawford m...@prgmr.com prgmr.com - We Don't Assume You Are Stupid. Xen-Powered Virtual Private Servers: http://prgmr.com/xen ___ 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: small question about tape-based dumps
Am Freitag, den 16.10.2009, 20:43 -0600 schrieb Tim Judd: Replies inline On 10/16/09, Jerry McAllister jerr...@msu.edu wrote: --8 snip, snap... --8 Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. --8 snip, snap... --8 That means, that after ervery dump, the tape drive is automatically writing an EOF. It is not necessary to write with mt -f /dev/nsa0 weof the EOF again. Thanks for any input! --TJ With regards Stevan Tiefert ___ 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: pf, ssh related question
2009/10/17 Dánielisz László laszlo_daniel...@yahoo.com: Hello, I have the following annoying thing: all the time I runpfctl -F all -f /etc/pf.conf I got disconnected from my remote machine. Do you have any idea how can I avoid this? If you are just trying to reload the changes made to pf.conf, use /etc/rc.d/pf reload. That flushes everything except for the state table, leaving your connections intact. Another method is to set flags any for each rule, which should allow connections to recover after the states are flushed, but this would be a bad idea security-wise. - Max ___ 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: pf, ssh related question
Theoretically if you sent a syn packet from the same source port at
tne same time as you reloaded the rules you coyld get around it.
However the practicalities of this make it not worth the hassle,
especially if you dont control the firewall yiur traversing through
the client end. Best to live with it
On 10/17/09, Dánielisz László laszlo_daniel...@yahoo.com wrote:
Hello,
I have the following annoying thing: all the time I runpfctl -F all -f
/etc/pf.conf I got disconnected from my remote machine.
Do you have any idea how can I avoid this?
Here is my pf.conf
#MACROS
ext_if=rl0
int_if=rl1
good_ip={192.168.1.0/24}
icmp_types=echoreq
set skip on lo
scrub in
block in
pass out keep state
antispoof quick for { lo $int_if }
#incoming ssh
pass in log quick on $int_if inet proto tcp from $good_ip to ($int_if) port
22 flags S/SA keep state
#incoming http
pass in log quick on $int_if inet proto tcp from $good_ip to ($int_if) port
80 flags S/SA keep state
pass in inet proto icmp all icmp-type $icmp_types keep state
___
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
--
Sent from my mobile device
___
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: I hate to bitch but bitch I must
On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done Dunno, maybe it's because E is my SL, but I fail to see the problem here. The meaning is clearly (SECTION BUGS, ffs) The friggin program should have a feature it's currently lacking. That's not to say I haven't had my share of gripes with man pages, it's just that if you ignore the man page structure and associated meaning, you're in for trouble. Just like with any message. -- roman ___ 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: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
Why I get these messages about GLIBCXX_3.4.9? Is it a bug in port? Or in package? Or in system? /etc/make.conf has the line, if that matters: OVERRIDE_LINUX_BASE_PORT=fc6 Yes, it does matter. This is a binary port, and the party that built the binaries (Google) compiled them against a fairly recent libstdc++. You are trying to link these binaries with an older version of libstdc++ in Fedora Core 6 which doesn't include the newer symbols, and getting a symbol-version error. Fedora Core 6 was released in October 2006 and reached it's end-of-life in Dec. 2007. Use a newer Linux base port, preferably the newest that will work on your platform and with your software. If you've an older version of FreeBSD that doesn't support the newer Linux base ports, then you'll have to upgrade, or do some really nasty hacking. This question is more appropriate in the freebsd-ports or freebsd-emulation mailing lists. b. ___ 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: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
b. f. wrote: Why I get these messages about GLIBCXX_3.4.9? Is it a bug in port? Or in package? Or in system? /etc/make.conf has the line, if that matters: OVERRIDE_LINUX_BASE_PORT=fc6 Yes, it does matter. This is a binary port, and the party that built the binaries (Google) compiled them against a fairly recent libstdc++. You are trying to link these binaries with an older version of libstdc++ in Fedora Core 6 which doesn't include the newer symbols, and getting a symbol-version error. Fedora Core 6 was released in October 2006 and reached it's end-of-life in Dec. 2007. Use a newer Linux base port, preferably the newest that will work on your platform and with your software. If you've an older version of FreeBSD that doesn't support the newer Linux base ports, then you'll have to upgrade, or do some really nasty hacking. This question is more appropriate in the freebsd-ports or freebsd-emulation mailing lists. b. Record 20080318 in /usr/ports/UPDATING says that in order for skype to work OVERRIDE_LINUX_BASE_PORT=fc6 should be set. I did that in order to make skype work. I believe latest versions of skype don't work work FreeBSD because FreeBSD only uses OSS audio and newer skypes are non-OSS. So now if I remove that line from /etc/make.conf skype is likely to break and google-earth to be fixed. How can I have both working? Looks like for some unknown reason linux has incompatible files libstdc++.so.6 in different versions instead of bumping number in name. Is it possible to have several linux bases under different install bases? Yuri ___ 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: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
On 10/17/09, Yuri y...@rawbw.com wrote: b. f. wrote: Record 20080318 in /usr/ports/UPDATING says that in order for skype to work OVERRIDE_LINUX_BASE_PORT=fc6 should be set. I did that in order to make skype work. I believe latest versions of skype don't work work FreeBSD because FreeBSD only uses OSS audio and newer skypes are non-OSS. So now if I remove that line from /etc/make.conf skype is likely to break and google-earth to be fixed. That entry also says that Fedora 8 can be used, which was the latest Linux base port at the time the entry was made, and the skype port Makefile says Fedora Core 6 __or later__ can be used. So presumably later Linux base ports will also work: try the most recent Linux base emulation port that is available for your platform. Looks like for some unknown reason linux has incompatible files libstdc++.so.6 in different versions instead of bumping number in name. The library's interface (API/ABI) hasn't changed, so the major version number should remain the same. With the use of symbol versions, new symbols, or different library symbols with the same interface can be added, with the appropriate version number information, so that binaries compiled against different versions of the symbols can all be used with the library. So there is backwards-compatibility with earlier versions of the library, but binaries that have been linked with newer symbol versions during compilation will not link at run-time against older versions of the library that don't have the new versions of the symbols. See: http://people.redhat.com/drepper/symbol-versioning http://people.freebsd.org/~deischen/symver/freebsd_versioning.txt Is it possible to have several linux bases under different install bases? Yes, if you patch the run-time linker as PC-BSD does, or if you use different environment variables or libmap.conf(5) to ensure the right libraries are loaded when using different binaries. But this can get messy -- try to use a new Linux base port for all of your ports first. b. ___ 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: GEOM label clarification
in message 20091017005844.77c28cc1.free...@edvax.de, wrote Polytropon thusly... On Sat, 17 Oct 2009 00:43:37 +0300, Manolis Kiagias son...@otenet.gr wrote: Is this your normal '/' filesystem, and is it mounted? If it is reboot your system and select 'single user mode' from the loader.menu Then use glabel in the single user mode prompt. This will not work if you just 'shutdown now', you have to reboot into single user mode. Isn't it sufficient to unmount any partitions and keep / in -o ro mode, and then perform the glabel command, which is obviously best done in single user mode? # shutdown now # umount /home /usr /var /tmp # mount -r / # glabel label rootfs /dev/ad0s1a That did not work for the 3-4 times I had tried on 6.[2-4]-STABLE. Booting regulary in single user mode (choice 4 or 5) also did not allow glabel'ing (for root). - parv -- ___ 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
Data Redundancy RAID 0+1 Vs 1+0 FREEBSD 7.4 STABLE
Hi folks, I'm thinking to build a Raid on my system and I'm getting documented abut 0+1 and 1+0 RAID systems. As far as I can see the best option is a 1+0 is the best option as if one of the from mirrors fails, the RAID still be redundant and in the case of a 0+1 RAID, If one of them fails, the RAID will be down until u replace the HD in question... So my question is, if I am right above, what are de benefits of mounting a RAID 0+1 ?? Cheers! -- () ASCII Ribbon Campaign | Against HTML e-mail /\ www.asciiribbon.org | Against proprietary extensions ___ 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: Data Redundancy RAID 0+1 Vs 1+0 FREEBSD 7.4 STABLE
Jeronimo Calvo wrote: Hi folks, I'm thinking to build a Raid on my system and I'm getting documented abut 0+1 and 1+0 RAID systems. As far as I can see the best option is a 1+0 is the best option as if one of the from mirrors fails, the RAID still be redundant and in the case of a 0+1 RAID, If one of them fails, the RAID will be down until u replace the HD in question... So my question is, if I am right above, what are de benefits of mounting a RAID 0+1 ?? For workloads that involve streaming large volumes of sequential data RAID 0+1 can perform very well. However, for the typical sort of workloads seen on a general purpose workstation, it offers no advantages over RAID10, and for the sort of workload you get with RDBMSes -- lots of randomly scattered small IOs -- RAID10 does the business. Given the poor resilience characteristics of RAID 0+1 the sequential data streaming workload would be better handled by RAID5(0) or RAID6(0) plus a good hardware RAID controller with plenty of battery backed cache RAM. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: I hate to bitch but bitch I must
Polytropon wrote: On Fri, 16 Oct 2009 21:29:04 -0400, PJ af.gour...@videotron.ca wrote: It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. As English is not my native language, I *now* understand the meaning of it should; in this case, it seems to mean something like basically, it is supposed to, but in this case, it does not, regarding the desired action. To be as precise as possible, it means normally it should work so go ahead; then the question is - what do you mean by normally. In our case above, the instructions were to do the operation with the disk not in use and the os in SUM. That's very clear. Now, I f they wanted to point out a bug, the bug means that there is an anomaly under certain circumstances - and in this case there really is no bug as it is very clear as to how the instructions should be used. If they consider the operation under a live files system a bug, then they should just make a warning and say something along the lines of do not use on live system as that may destroy data or something to that effect. I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. It's still possible that non-native speakers misunderstand. Of course... but what you need is cooperation between the two - and both should have some understanding of the particular area of expertise they are dealing with. Just a note: I find it strange that nobody looked into the problem of the confusion... I thought I had pointed out where the co;nfusion arises... and no one seems to have either understood the inconsistencies or bothere to read the explanation... oh well... let's keep on blundering away... ;-) ___ 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: I hate to bitch but bitch I must
Mark wrote: -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of PJ Sent: zaterdag 17 oktober 2009 3:50 To: Steve Bertrand Cc: Polytropon; freebsd-questions@freebsd.org Subject: Re: I hate to bitch but bitch I must but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed The meaning of 'should' is not nearly as narrow as you suggest. Often it also denotes reservation (as in the above example). To illustrate once more: Can I run dump on an active file system? It *should* run on an active file system, provided (enumerations of conditions which would need to be met; like preferably no disk-activity when making the backup). (Meaning: it can be done, but it's ill-advised, really.) And clearly it does not mean should be executed, done, carried out, performed. Another one: Will he run for President? Well, he should be able to get enough votes. (Meaning: if everything goes as planned, he might succeed, but it's by no means guaranteed he'll actually get enough votes). So, given the right intonation and context, This utility should work on active file systems. can certainly be understood to mean one could technically do so, but that it's not recommended. - Mark ___ 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 I think you're trying to take the meaning of should a little too far... to keep it simple, and without trying to intellectualize it, it simply means (and this can change within certain contexts) normally, it should work (in our context, here) but there is no implication of any warnings or dangers ... the normally is implied, the rest you can do with it as you wish, obviously at your rist... but even then the interpretation goes too far. As I suggested to Polytropon, in this particular case the instructions for the implementation of the procedure are very clear: use on an inactive system or SUM... so where's the bug... to suggest that it should work on an active system is confusing - if the author thought it important that it wouldl not work on an active system, perhaps he should have merely said do not use on an active system... that would be consistent and very clear. ;-) ___ 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: I hate to bitch but bitch I must
Warren Block wrote: On Fri, 16 Oct 2009, Bob Hall wrote: On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: BUGS This utility should work on active file systems. I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. I understand it, but see ambiguity in the word should. Easy enough to rewrite: BUGS This utility does not work on active file systems. Now here's my challenge to PJ: use send-pr(1) or the web PR interface at http://www.freebsd.org/send-pr.html to submit this as a doc bug report. That's how FreeBSD gets better, and how you help the next person in the same situation. -Warren Block * Rapid City, South Dakota USA As I mentioned earlier, I do not understand what the author really intended, so I am out of place making any judgments. All I was saying is that my understanding of all the instructions I found was and still is confused... as I mentioned, changing this is between the author and whoever translated, if that is the case. For me, I would still like to hear from somone who could clear up the confusion... read my explanation of what I found in themanuals and you will perhaps understand what is confusing (tunefs and glabel appear to be stumbling over each other and criss-crossing instructions. From the way things are written, it would appear that one must do tunefs before doing glabel and that they are interdependent. But tunefs says to do tunefs /home /disk-slice yet glabel is dealing with partitions... what does /home supposed to be a specific directory or a partition and how does it relate to the disk? And then, how does it relate to glabel? Manolis seems to have cleared things slightly on how to use glabel, but strangely it did not work for me. I am about to try again and will sen the fstab and ls disk prinouts as soon as I have another little problem sorted out... shortly or tomorrow. 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
Re: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
b. f. wrote: That entry also says that Fedora 8 can be used, which was the latest Linux base port at the time the entry was made, and the skype port Makefile says Fedora Core 6 __or later__ can be used. So presumably later Linux base ports will also work: try the most recent Linux base emulation port that is available for your platform. With those lines in /etc/make.conf: OVERRIDE_LINUX_BASE_PORT=f10 OVERRIDE_LINUX_NONBASE_PORTS=f10 everything works. But with f8 there were still problems. How would people know that they should set f10? Ideally this should be done my portupgrade. Or, at the very least, there should be a corresponding record in /usr/pots/UPGRADING. Record 20090831 mentions f10 in connection with some other port, but not as a general recommendation. Yuri ___ 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
Why scim menu in skype missing languages?
I upgraded to OVERRIDE_LINUX_BASE_PORT=f10 (from f6) in /etc/make.conf. And now scim menu from linux skype doesn't allow to choose any languages but English. How to fix? Yuri ___ 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: I hate to bitch but bitch I must
Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 df: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad12s1a 2026030 319112 154483617%/ devfs1 10 100%/dev /dev/ad12s1h 50777034 4 46714868 0%/backups /dev/ad12s1g 50777034 6276538 4043833413%/home /dev/ad12s1d 4058062 36 3733382 0%/tmp /dev/ad12s1f 50777034 5729324 4098554812%/usr /dev/ad12s1e 2026030 176070 1687878 9%/var linprocfs4 40 100%/usr/compat/linux/proc # ls /dev/ad* crw-r- 1 root operator0, 97 Oct 17 16:36 /dev/ad0 crw-r- 1 root operator0, 103 Oct 17 16:36 /dev/ad0s1 crw-r- 1 root operator0, 101 Oct 17 16:36 /dev/ad10 crw-r- 1 root operator0, 106 Oct 17 16:36 /dev/ad10s1 crw-r- 1 root operator0, 121 Oct 17 16:36 /dev/ad10s1a crw-r- 1 root operator0, 122 Oct 17 16:36 /dev/ad10s1b crw-r- 1 root operator0, 123 Oct 17 16:36 /dev/ad10s1c crw-r- 1 root operator0, 124 Oct 17 16:36 /dev/ad10s1d crw-r- 1 root operator0, 125 Oct 17 16:36 /dev/ad10s1e crw-r- 1 root operator0, 126 Oct 17 16:36 /dev/ad10s1f crw-r- 1 root operator0, 127 Oct 17 16:36 /dev/ad10s1g crw-r- 1 root operator0, 102 Oct 17 16:36 /dev/ad12 crw-r- 1 root operator0, 107 Oct 17 16:36 /dev/ad12s1 crw-r- 1 root operator0, 128 Oct 17 16:36 /dev/ad12s1a crw-r- 1 root operator0, 129 Oct 17 16:36 /dev/ad12s1b crw-r- 1 root operator0, 130 Oct 17 16:36 /dev/ad12s1c crw-r- 1 root operator0, 131 Oct 17 16:36 /dev/ad12s1d crw-r- 1 root operator0, 132 Oct 17 16:36 /dev/ad12s1e crw-r- 1 root operator0, 133 Oct 17 16:36 /dev/ad12s1f crw-r- 1 root operator0, 134 Oct 17 16:36 /dev/ad12s1g crw-r- 1 root operator0, 135 Oct 17 16:36 /dev/ad12s1h crw-r- 1 root operator0, 99 Oct 17 16:36 /dev/ad4 crw-r- 1 root operator0, 104 Oct 17 16:36 /dev/ad4s1 crw-r- 1 root operator0, 108 Oct 17 16:36 /dev/ad4s1a crw-r- 1 root operator0, 109 Oct 17 16:36 /dev/ad4s1b crw-r- 1 root operator0, 110 Oct 17 16:36 /dev/ad4s1c crw-r- 1 root operator0, 111 Oct 17 16:36 /dev/ad4s1d crw-r- 1 root operator0, 112 Oct 17 16:36 /dev/ad4s1e crw-r- 1 root operator0, 113 Oct 17 16:36 /dev/ad4s1f crw-r- 1 root operator0, 114 Oct 17 16:36 /dev/ad4s1g crw-r- 1 root operator0, 100 Oct 17 16:36 /dev/ad6 crw-r- 1 root operator0, 105 Oct 17 16:36 /dev/ad6s1 crw-r- 1 root operator0, 115 Oct 17 16:36 /dev/ad6s1a crw-r- 1 root operator0, 116 Oct 17 16:36 /dev/ad6s1b crw-r- 1 root operator0, 117 Oct 17 16:36 /dev/ad6s1c crw-r- 1 root operator0, 118 Oct 17 16:36 /dev/ad6s1d crw-r- 1 root operator0, 119 Oct 17 16:36 /dev/ad6s1e crw-r- 1 root operator0, 120 Oct 17 16:36 /dev/ad6s1f Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and ad6 is messed up FBSD I'm cheking setting up with clone of ad12 (dump/restore) Now I will try the glabel again... # shutdown now # glabel label rootfs /dev/ad12s1a glabel: Can't store metadata on /dev/ad0s1a manual: it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. It is also assumed that the
Re: I hate to bitch but bitch I must
Steve Bertrand wrote: PJ wrote: Steve Bertrand wrote: PJ wrote: Polytropon wrote: On Fri, 16 Oct 2009 17:54:23 -0400, PJ af.gour...@videotron.ca wrote: but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? It should. This means: Don't try that. :-) My printer isn't printing! But it should. No, it is not printing! Yes, but it should. :-) Aha! Gotcha! Whoever wrote that has made an unintentionnal booboo. It is a subtle difference and is indicative that whoever wrote it is not a native english user... the meaning is clearly should be executed, done, carried out, performed - should work means it can be carried out - I think the author meant to say should not be done If you feel that you've found a 'bug' within the manual/documentation of a piece of software or function, I highly recommend that you pass it by other users/developers ( as you've kind-of done here ), and then contact the person who is normally listed in the AUTHOR section of the man page after you get a consensus on whether the manual, the code or you have the bug :) If you believe the problem is an engish-linguistic one (and the man page is written in english), let the author know this. Provide the correct verbiage, and an explanation of what your words mean compared to theirs (remember, english may not be their first language). Also, take a look at RFC 2119 for the keyword 'SHOULD' and 'SHOULD NOT'. RFC 2119 is highly regarded as the authority for many keywords, and a quick reference of it may help when trying to explain to an author where you feel their documentation is incorrect (or lacking). What in the world is RFC 2119? (that's a rhetorical question) I prefer to stick to orinary dictionaries, like Oxford, Collins, Webster... then again, my college university studies were in English lit... but I'm afraid I have have neglected that and have been somewhat dragged down to the level of the plebes in the hope they may catch some of my meanings... :-D Cheers, Steve It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. I understand that I'm confused :) I am afraid that with all the globalization people still do not understand that translations should be left to experts... an by that I mean the final version should always, and I mean always, be by a native speaking person. That's an unfair thing to say. Are you saying that if someone with a French native tongue wrote software that would benefit everyone, and they wrote the manual in English to reach a broader audience, that the manual shouldn't be released unless proof-read and re-written by an English native? YES! There are plenty of people who would be happy to help the guy get the translation right... would you want someone to get a hold of a weapon and then misuse it because the instructions are in sanskrit? Vous faire ce travail, mon ami? Je n'aime pas d'accord avec votre utilisation du mot doit. You are definitely not a frog... ;-) ...the manual is available. I didn't mean to dis-respect you, I just meant that if one 'could' help, then the developer is the one to hit up. I speak english, french, italian, some spanish and german as well as latvian... but I would never attempt to translate into any language other than English... and then not without the help of the original language's originator. ;-) Nice... How 'bout Dutch ;) You will understand then: Ne dis pas que la documentation ne peuvent etre ecrites par un auteur si leur lange nest pas une espece indigen. Duh... that's not Dutch... Nice try... your Frenchreminds me of my German... great pronunciation, but the grammar is horrible ;-) Too many years ago I knew it well. Steve ___ 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: I hate to bitch but bitch I must
Bob Hall wrote: On Sat, Oct 17, 2009 at 02:34:40AM +, Mark wrote: Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Actually, what's happening here is dropping part of a sentence. It's common in English to shorten Yea, it should work, but it doesn't. Absolutely not! There is nothing to suggest either statement above. If one says it should work, it can mean (of course, it changes within different contexts) that all is ok and normal conditions (whatever they may be) will allow things to function correctly. There is certainly no implication about confidence... where do you get that? It can mean ver confident just as well. And dropping a sentence is a very presumptuous assumption. but is doesn't is a specific condition... and there can me innumerable conditions. If you look at the immediate context of what we are dealing with here, the author has clearly stated use in SUM and that implies an unmounted system. If he considers using it on an active system as a bug, then he should be clear about it and say do not use on an active system. to Yea, it should work. In order to catch the meaning, you have to be aware of context. Contrary to the OP's claim, this shows a pretty good grasp of English idiom. It's definitely not evidence that the man author is not a native speaker of English. On the other hand, it can be clarified so that the meaning is clear even without context. If the OP really believes that the present wording is a problem, other people have made suggestions on what to do about it. In the end, it's up to the author to clarify... I don't understand what he's trying to do as on my stem his instructions/example just do not work anyway. :-( ___ 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: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
On 10/17/09, Yuri y...@rawbw.com wrote:
b. f. wrote:
That entry also says that Fedora 8 can be used, which was the latest
Linux base port at the time the entry was made, and the skype port
Makefile says Fedora Core 6 __or later__ can be used. So presumably
later Linux base ports will also work: try the most recent Linux base
emulation port that is available for your platform.
With those lines in /etc/make.conf:
OVERRIDE_LINUX_BASE_PORT=f10
OVERRIDE_LINUX_NONBASE_PORTS=f10
everything works. But with f8 there were still problems.
Yes, I only said that Fedora 8 probably worked for Skype, not that it
had the necessary symbols for the new google-earth. :)
How would people know that they should set f10?
The port maintainer for google-earth should put the necessary
statements into the Makefile for that port in order to ensure that a
sufficiently new Linux base port is used. Email him and suggest that
he do so. If he doesn't respond, file a PR.
Ideally this should be done my portupgrade.
Well, not by portupgrade itself, but by the ports infrastructure, so
other ports management tools work as well.
Or, at the very least, there should be a corresponding record in
/usr/pots/UPGRADING.
Record 20090831 mentions f10 in connection with some other port, but not
as a general recommendation.
If you look at /usr/ports/Mk/bsd.port.mk, you will see that Fedora 10
is now the default emulation port on new releases of FreeBSD (I don't
know why it isn't on earlier versions: you can ask bsam@ why he chose
800076 as the cutoff, and not some other value. There may have been
some feature missing from earlier versions of FreeBSD that was
necessary to make emulation work well with the newer Linux software.):
# Allow the user to specify another linux_base version.
. if defined(OVERRIDE_LINUX_BASE_PORT)
. if ${USE_LINUX:L} == yes
USE_LINUX= ${OVERRIDE_LINUX_BASE_PORT}
. endif
. endif
# NOTE: when you update the default linux_base version (case yes),
# don't forget to update the Handbook!
. if exists(${PORTSDIR}/emulators/linux_base-${USE_LINUX})
LINUX_BASE_PORT=
${LINUXBASE}/bin/sh:${PORTSDIR}/emulators/linux_base-${USE_LINUX}
. else
. if ${USE_LINUX:L} == yes
. if ${OSVERSION} 800076
LINUX_BASE_PORT=
${LINUXBASE}/etc/fedora-release:${PORTSDIR}/emulators/linux_base-fc4
. else
LINUX_BASE_PORT=
${LINUXBASE}/etc/fedora-release:${PORTSDIR}/emulators/linux_base-f10
. endif
. else
IGNORE= cannot be built: there is no
emulators/linux_base-${USE_LINUX}, perhaps wrong use of USE_LINUX or
OVERRIDE_LINUX_BASE_PORT
. endif
. endif
So most people will automatically avoid this problem on FreeBSD 8.x,
and port maintainers should place additional safeguards in their port
Makefiles to ensure that users on earlier supported versions of
FreeBSD know what Linux base ports are acceptable.
In general, when you read entries in /usr/ports/UPDATING, especially
older entries, you should consider if anything has changed since those
entries were made that may affect the advice they offer, because
committers don't always revise older entries, and they may become
stale.
b.
___
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: I hate to bitch but bitch I must
On Sat, Oct 17, 2009 at 05:36:43PM -0400, PJ wrote: Bob Hall wrote: On Sat, Oct 17, 2009 at 02:34:40AM +, Mark wrote: Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Actually, what's happening here is dropping part of a sentence. It's common in English to shorten Yea, it should work, but it doesn't. Absolutely not! There is nothing to suggest either statement above. If one says it should work, it can mean (of course, it changes within different contexts) that all is ok and normal conditions (whatever they may be) will allow things to function correctly. There is certainly no implication about confidence... where do you get that? From common English usage. ___ 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: I hate to bitch but bitch I must
michael wrote: PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 ok, in short since i didn't see anyone answer this directly, your question of tunefs vs glabel: tunefs is for UFS: it labels a UFS filesystem, no matter the device, ie: ad or da. tunefs is part of the filesystem utilities for UFS. good example, can't tunefs -L SWAP /dev/ad0s1b if it is a swap. you can glabel it. glabel is for labeling a device itself. you can glabel an ntfs filesystem or ext2, whatever. Thanks for that, Michael. But can you explain what this means? It just is not clear for me. # tu;nefs -L home /dev/da3 This puts a label on that disk? So now it can be referred to as home? da3 = home ? I'll try to delve into the man glabel further... but things still look murky. ___ 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: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 16:28:18 -0400, PJ af.gour...@videotron.ca wrote: From the way things are written, it would appear that one must do tunefs before doing glabel and that they are interdependent. As it has been mentioned ealier and as far as I understood: tunefs -L is for UFS file systems only, while glabel label is for any media. But tunefs says to do tunefs /home /disk-slice yet glabel is dealing with partitions... No. Slices aren't involved here. Only partitions can hold file systems, and that is what labelling is about. what does /home supposed to be a specific directory or a partition and how does it relate to the disk? First ofg all, /home is just an arbitrary mount point; in fact, it is just a directory. The /etc/fstab file is the means that connects this directory to a device (in this case, a disk partition holding a file system). For example, if you # fsck /home and /home is mounted from /dev/ad0s1g, then the device ad0s1g will be checked. You CAN ONLY check devices. When you now remove the entry for /home from /etc/fstab, the command # fsck /home will fail. Still, you can check this partition, but you need to know its exact name, which would make # fsck /dev/ad0s1g the correct command. And then, how does it relate to glabel? The glabel can be used on any media, such as FreeBSD's UFS partitions. Those labels can take the place of the device in the /etc/fstab file, but so can UFSIDs as well as tunefs -L labels (for UFS file systems only). Manolis seems to have cleared things slightly on how to use glabel, but strangely it did not work for me. I am about to try again and will sen the fstab and ls disk prinouts as soon as I have another little problem sorted out... shortly or tomorrow. Sorry. Would be interesting. -- 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: I hate to bitch but bitch I must
PJ wrote: michael wrote: PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 ok, in short since i didn't see anyone answer this directly, your question of tunefs vs glabel: tunefs is for UFS: it labels a UFS filesystem, no matter the device, ie: ad or da. tunefs is part of the filesystem utilities for UFS. good example, can't tunefs -L SWAP /dev/ad0s1b if it is a swap. you can glabel it. glabel is for labeling a device itself. you can glabel an ntfs filesystem or ext2, whatever. Thanks for that, Michael. But can you explain what this means? It just is not clear for me. # tu;nefs -L home /dev/da3 This puts a label on that disk? So now it can be referred to as home? da3 = home ? yes. this makes a ufs label which you can access via /dev/ufs for example (my home system) jh...@ostracod (23:08:34 ~) 0 $ ls /dev/ufs SCRATCH SSDROOT SSDUSR SSDVAR jh...@ostracod (23:08:39 ~) 0 $ mount /dev/ufs/SSDROOT on / (ufs, local, noatime) devfs on /dev (devfs, local, multilabel) /dev/ufs/SSDUSR on /usr (ufs, local, noatime, soft-updates) /dev/ufs/SSDVAR on /var (ufs, local, noatime, soft-updates) /dev/ufs/SCRATCH on /scratch (ufs, local, noatime, gjournal) tmpfs on /tmp (tmpfs, local) devfs on /var/named/dev (devfs, local, multilabel) jh...@ostracod (23:08:41 ~) 0 $ cat /etc/fstab /dev/ufs/SSDROOT/ ufs rw,noatime 1 1 /dev/ufs/SSDUSR /usrufs rw,noatime 2 2 /dev/ufs/SSDVAR /varufs rw,noatime 2 2 /dev/label/SWAP noneswapsw 0 0 /dev/ufs/SCRATCH/scratchufs rw,noatime 2 2 tmpfs /tmptmpfs rw 0 0 note there I have also used glabel on the swap (command used was glabel label /dev/ad10p1) One thing to note with label, if you mount/use the device by is raw node, the label disapears. ie: [r...@ostracod ~]# swapoff -a swapoff: removing
Re: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 17:10:42 -0400, PJ af.gour...@videotron.ca wrote: Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 Let me clean it up to the basics: /dev/ad12s1a / ufs rw 1 1 - rootfs /dev/ad12s1b none swap sw 0 0 /dev/ad12s1d /tmp ufs rw 2 2 - tmpfs /dev/ad12s1e /var ufs rw 2 2 - varfs /dev/ad12s1f /usr ufs rw 2 2 - usrfs /dev/ad12s1g /home ufs rw 2 2 - homefs /dev/ad12s1h /backups ufs rw 2 2 - backupfs Alphabetical order is so much nicer to the eyes. :-) The names after - show arbitrary labels to be given to the partitions; in fact, you're free to name them Bob, Timmy or something else fitting your individual naming scheme. It should be recognizable, so forget about my silly suggestions. :-) Now I will try the glabel again... # shutdown now # glabel label rootfs /dev/ad12s1a glabel: Can't store metadata on /dev/ad0s1a As it has been suggested, try this in SUM which you enter from system startup, not by partial shutdown. According to this command, you forgot to unmount disks anyway. manual: it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. It is also assumed that the standard FreeBSD partition scheme is used, with /, /var, /usr and /tmp file systems, as well as a swap partition. Now, does that mean that glabel does not work if there are several disks on the system... it certainly does not say so nor does it adv ertise that this would not work if there are several ATA disks present.. I simply cannot imagine this, because you give the device name as a parametron to the glabel program. Maybe it's just mentioned because in most settings, ad0 is the boot disk, and FreeBSD is installed on this disk. The manuals cannot take things like massive multibooting into mind. Where would this end?! :-) Previously I had also tried a reboot press 4 with exactly the same results Really? Now THAT'S strange... So, what am I doing wrong... or where is the system screwed up... from my point of view, everything seems to work ok including Firefox, flashplugin, Openoffice, gimp, netbeans, etc. etc. etc. even conky... :-) When you've entered SUM by running boot -s at the loader prompt - I'm not familiar with the number thingy boot menu - you could try first running fsck -f on the partition in question, just to be sure everything is okay, and then run the glabel command. For this time, don't try to begin with the root file system; try /tmp, it's uncritical, and it's different from / which is mounted (hopefully ro), so all the requirements from the manual should be met. Perhaps this is just a frustrating mental exercise as the system works without glabeling partitions... it just would save some work if it could be implemented... then, if I were to look at it as a businessman... why am I wasting so much time, energy and mental suffering when just changing a few files will do the same thing and take less effort... oh! what price intellectual curiosity. ;-) Priceless. :-) -- 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: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 17:55:20 -0400, PJ af.gour...@videotron.ca wrote: But can you explain what this means? It just is not clear for me. # tu;nefs -L home /dev/da3 This puts a label on that disk? So now it can be referred to as home? da3 = home ? Yes, exactly that's the purpose. In such a setting, da3 would refer to a SCSI disk, and home is the label. It can - CAN! - be mounted on the /home directory. # mount /dev/label/home /home But of course, any other mountpoint is fine as well. The setting in /etc/fstab will do the correct thing - if setup correctly. :-) -- 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: small question about tape-based dumps
On Fri, 16 Oct 2009 17:37:32 -0400, Jerry McAllister jerr...@msu.edu said: J You can easily put more than one dump on a tape if there is room enough J for them. I actually rewind and skip between each dump of multiples J made to the same tape. I also use the no-rewind device for the tape. Whenever possible, I set aside a 4-8 Gb partition for a staging area. This has helped me avoid several nasty tape problems: a. Dump to a file on the staging area, compressing it if possible. b. Get an MD5/SHA1/whatever signature for the dump. c. Write it to tape. When all the dumps are finished, rewind the tape. Read each tape file, get the signature, and compare it to what you got before; this way, you know your backup is good. Tapes stretch and wrinkle, tape heads get out of alignment, tapes can bleed over time, etc. There are few things worse than trying to restore someone's file and finding out you have a screwed backup. Another advantage of a staging area is better tape use; if you're copying a single file to tape (most of which is still in cache from the signature check), the tape drive won't spend as much time polishing the heads waiting for something to write. -- Karl Vogel I don't speak for the USAF or my company The RAID was dirty *and* degraded (insert your mom joke here). --Mike Markley on Slashdot discussing Linux drives ___ 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: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 23:17:29 +0100, Vincent Hoffman vi...@unsane.co.uk wrote: yes. this makes a ufs label which you can access via /dev/ufs for example (my home system) jh...@ostracod (23:08:34 ~) 0 $ ls /dev/ufs SCRATCH SSDROOT SSDUSR SSDVAR [...] /dev/ufs/SCRATCH on /scratch (ufs, local, noatime, gjournal) ^^^ Wow! Last time I saw this was on EAW's WEGA (a UNIX System III compatible UNIX developed in the GDR for the P8000 workstation). There even was /etc/mount and /etc/fsck. :-) /dev/ufs/SSDVAR /varufs rw,noatime 2 2 /dev/label/SWAP noneswapsw 0 0 These two lines illustrate the different use of the results of glabel label for generic labels and tunefs -L for UFS labels very well. note there I have also used glabel on the swap (command used was glabel label /dev/ad10p1) A really honest question: What does the p in ad10p1 indicate? I always thought swap partitions are something like ad10b (an own partition right after the root partition a). One thing to note with label, if you mount/use the device by is raw node, the label disapears. [...] This used to confuse me greatly :) Why make a label available for something to mount that is already mounted and cannot be accessed through this label while being mounted? :-) The kernel messages show such messages about removing labels as soon as devices are mounted in the traditional way. -- 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: Why Linux executable googleearth can't find proper libstdc++.so.6 ?
b. f. wrote: If you look at /usr/ports/Mk/bsd.port.mk, you will see that Fedora 10 is now the default emulation port on new releases of FreeBSD (I don't know why it isn't on earlier versions: you can ask bsam@ why he chose 800076 as the cutoff, and not some other value. There may have been some feature missing from earlier versions of FreeBSD that was necessary to make emulation work well with the newer Linux software.): Now I remember: some time back (when f8 as default) skype had problem displaying UTF8 symbols and working with scim (scim doesn't display any non-English languages in skype). That's why I set fc6 as default for me, with which skype worked. With f10 the latter problem with skype still exists. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: phpMyAdmin install stopped in dependency 'libXau-1.0.4'
2009/10/16 Matthew Seaman m.sea...@infracaninophile.co.uk: Kikachi Kozumi wrote: Hi, I tried installing phpMyAdmin in an ezjail created jail already installed with apache22, mysql and php5 running FreeBSD 7.1-RELEASE i386 with no X11 (headless). The port install failed when dependency 'libXau-1.0.4' configure couldn't find gnome-config: ... checking for XAU... gnome-config: not found configure: error: Package requirements (xproto) were not met. ... I'm not sure if this issue is specific to my system or is it a ports issue but I found that libXau-1.0.4 was in the ports tree since January 2009 so it's less likely to be an issue with the port itself. Right now I'm not sure if the required gnome-config is lost from my system or was never there in the 1st place. What can I do to continue with phpMyAdmin installation? I'm also curious why the phpMyAdmin port requires libX11 libraries to build while the phpMyAdmin website states that php, mysql and apache are the requirements for running phpMyAdmin? [snip] Try placing WITHOUT_X11=yes into /etc/make.conf so it will build without the X related nonsense. -Mike Thank you. I added WITHOUT_X11=yes to /etc/make.conf and that did the trick. phpMyAdmin only depends on X through one of the optional extensions: php5-gd. If you disable the GD and PDF options in the configuration dialogue you'll not need to install any X related dependencies. Or you can rebuild graphics/gd using 'WITHOUT_X11=yes' if you want to be able to generate PDF of database schemas etc through phpMyAdmin. Hmmm... as far as I can tell, gnome-config is not a run-time dependency of phpMyAdmin even when compiled with all options enabled and with X11 support in the gd libraries. Either gnome-config is a build dependency from somewhere way down the dependency tree (ie. only needed to build something, not needed to run it) or you've got a misplaced 'USE_GNOME' somewhere. In general, USE_FOO is for port maintainers only and shouldn't appear in /etc/make.conf or any other Makefile that gets generally included everywhere. Use WITH/WITHOUT_FOO in /etc/make.conf to indicate global preferences. (Gentoo we ain't) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW I've used WITHOUT_X11=yes in /etc/make.conf and gotten phpMyAdmin installed. Thank for the advice regarding GD and PDF options. I'll keep them in mind. Won't be the last I'll see of phpMyAdmin. The port install failed when 'Configuring for libXau-1.0.4' - prerequisite of libX11 - couldn't find gnome-config. I just had this jail freshly configured less than a week ago as a BAMP server. I'm sure I haven't place USE_GNOME anywhere in the jail. The following is my pkg_info output, phpMyAdmin was the last thing I installed. # pkg_info apache-2.2.13 Version 2.2.x of Apache web server with prefork MPM. autoconf-2.62 Automatically configure source code on many Un*x platforms autoconf-wrapper-20071109 Wrapper script for GNU autoconf expat-2.0.1 XML 1.0 parser written in C freetype2-2.3.9_1 A free and portable TrueType font rendering engine gettext-0.17_1 GNU gettext package gmake-3.81_3GNU version of 'make' utility help2man-1.36.4_3 Automatically generating simple manual pages from program o jpeg-7 IJG's jpeg compression utilities libcheck-0.9.6 A unit test framework for C libgcrypt-1.4.4 General purpose crypto library based on code used in GnuPG libgpg-error-1.7Common error values for all GnuPG components libiconv-1.13.1 A character set conversion library libltdl-2.2.6a_1System independent dlopen wrapper libmcrypt-2.5.8 Multi-cipher cryptographic library (used in PHP) libpthread-stubs-0.1 This library provides weak aliases for pthread functions libtool-2.2.6a_1Generic shared library support script libxml2-2.7.6 XML parser library for GNOME libxslt-1.1.26 The XSLT C library for GNOME m4-1.4.13,1 GNU m4 mysql-client-5.4.2 Multithreaded SQL database (client) mysql-server-5.4.2 Multithreaded SQL database (server) p5-Authen-PAM-0.16_1 A Perl interface to the PAM library p5-DBI-1.60.9 The perl5 Database Interface. Required for DBD::* modules p5-Data-ShowTable-3.3 Perl5 module to pretty-print arrays of data p5-Mysql-modules-1.2219 Perl5 modules for accessing MySQL databases p5-Net-SSLeay-1.35_2 Perl5 interface to SSL p5-Storable-2.21Persistency for perl data structures p5-gettext-1.05_2 Message handling functions pcre-7.9Perl Compatible Regular Expressions library pdflib-7.0.4A C library for dynamically generating PDF pecl-pdflib-2.1.6_1 A PECL extension to create PDF on the fly perl-5.8.9_3Practical Extraction and Report Language
Re: I hate to bitch but bitch I must
Polytropon wrote: On Sat, 17 Oct 2009 23:17:29 +0100, Vincent Hoffman vi...@unsane.co.uk wrote: yes. this makes a ufs label which you can access via /dev/ufs for example (my home system) jh...@ostracod (23:08:34 ~) 0 $ ls /dev/ufs SCRATCH SSDROOT SSDUSR SSDVAR [...] /dev/ufs/SCRATCH on /scratch (ufs, local, noatime, gjournal) ^^^ Wow! Last time I saw this was on EAW's WEGA (a UNIX System III compatible UNIX developed in the GDR for the P8000 workstation). There even was /etc/mount and /etc/fsck. :-) Heh nothing so arcane here, I just use it as a scratch (disposable content) disk. /dev/ufs/SSDVAR /varufs rw,noatime 2 2 /dev/label/SWAP noneswapsw 0 0 These two lines illustrate the different use of the results of glabel label for generic labels and tunefs -L for UFS labels very well. note there I have also used glabel on the swap (command used was glabel label /dev/ad10p1) A really honest question: What does the p in ad10p1 indicate? I always thought swap partitions are something like ad10b (an own partition right after the root partition a). I partitioned my disk as GPT using gpart. no real reason, just because i could ;) this give partitions (p) instead of slices (s) (I think, not certain thats what the p and s stand for but it makes sense) I could also have used the gpt labels instead of generic glabel labels. [r...@ostracod /scratch]# dd if=/dev/zero of=dsk bs=1m count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 0.055245 secs (189804954 bytes/sec) [r...@ostracod /scratch]# mdconfig -a -t vnode -f dsk -u 10 [r...@ostracod /scratch]# gpart add -l MDDISK -t freebsd-ufs md10 md10p1 added [r...@ostracod /scratch]# ls /dev/gpt/ MDDISK One thing to note with label, if you mount/use the device by is raw node, the label disapears. [...] This used to confuse me greatly :) Why make a label available for something to mount that is already mounted and cannot be accessed through this label while being mounted? :-) The kernel messages show such messages about removing labels as soon as devices are mounted in the traditional way. Indeed, that makes sense. Vince ___ 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: I hate to bitch but bitch I must
2009/10/17 PJ af.gour...@videotron.ca Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 df: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad12s1a 2026030 319112 154483617%/ devfs1 10 100%/dev /dev/ad12s1h 50777034 4 46714868 0%/backups /dev/ad12s1g 50777034 6276538 4043833413%/home /dev/ad12s1d 4058062 36 3733382 0%/tmp /dev/ad12s1f 50777034 5729324 4098554812%/usr /dev/ad12s1e 2026030 176070 1687878 9%/var linprocfs4 40 100%/usr/compat/linux/proc # ls /dev/ad* crw-r- 1 root operator0, 97 Oct 17 16:36 /dev/ad0 crw-r- 1 root operator0, 103 Oct 17 16:36 /dev/ad0s1 crw-r- 1 root operator0, 101 Oct 17 16:36 /dev/ad10 crw-r- 1 root operator0, 106 Oct 17 16:36 /dev/ad10s1 crw-r- 1 root operator0, 121 Oct 17 16:36 /dev/ad10s1a crw-r- 1 root operator0, 122 Oct 17 16:36 /dev/ad10s1b crw-r- 1 root operator0, 123 Oct 17 16:36 /dev/ad10s1c crw-r- 1 root operator0, 124 Oct 17 16:36 /dev/ad10s1d crw-r- 1 root operator0, 125 Oct 17 16:36 /dev/ad10s1e crw-r- 1 root operator0, 126 Oct 17 16:36 /dev/ad10s1f crw-r- 1 root operator0, 127 Oct 17 16:36 /dev/ad10s1g crw-r- 1 root operator0, 102 Oct 17 16:36 /dev/ad12 crw-r- 1 root operator0, 107 Oct 17 16:36 /dev/ad12s1 crw-r- 1 root operator0, 128 Oct 17 16:36 /dev/ad12s1a crw-r- 1 root operator0, 129 Oct 17 16:36 /dev/ad12s1b crw-r- 1 root operator0, 130 Oct 17 16:36 /dev/ad12s1c crw-r- 1 root operator0, 131 Oct 17 16:36 /dev/ad12s1d crw-r- 1 root operator0, 132 Oct 17 16:36 /dev/ad12s1e crw-r- 1 root operator0, 133 Oct 17 16:36 /dev/ad12s1f crw-r- 1 root operator0, 134 Oct 17 16:36 /dev/ad12s1g crw-r- 1 root operator0, 135 Oct 17 16:36 /dev/ad12s1h crw-r- 1 root operator0, 99 Oct 17 16:36 /dev/ad4 crw-r- 1 root operator0, 104 Oct 17 16:36 /dev/ad4s1 crw-r- 1 root operator0, 108 Oct 17 16:36 /dev/ad4s1a crw-r- 1 root operator0, 109 Oct 17 16:36 /dev/ad4s1b crw-r- 1 root operator0, 110 Oct 17 16:36 /dev/ad4s1c crw-r- 1 root operator0, 111 Oct 17 16:36 /dev/ad4s1d crw-r- 1 root operator0, 112 Oct 17 16:36 /dev/ad4s1e crw-r- 1 root operator0, 113 Oct 17 16:36 /dev/ad4s1f crw-r- 1 root operator0, 114 Oct 17 16:36 /dev/ad4s1g crw-r- 1 root operator0, 100 Oct 17 16:36 /dev/ad6 crw-r- 1 root operator0, 105 Oct 17 16:36 /dev/ad6s1 crw-r- 1 root operator0, 115 Oct 17 16:36 /dev/ad6s1a crw-r- 1 root operator0, 116 Oct 17 16:36 /dev/ad6s1b crw-r- 1 root operator0, 117 Oct 17 16:36 /dev/ad6s1c crw-r- 1 root operator0, 118 Oct 17 16:36 /dev/ad6s1d crw-r- 1 root operator0, 119 Oct 17 16:36 /dev/ad6s1e crw-r- 1 root operator0, 120 Oct 17 16:36 /dev/ad6s1f Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and ad6 is messed up FBSD I'm cheking setting up with clone of ad12 (dump/restore) Now I will try the glabel again... # shutdown now # glabel label rootfs /dev/ad12s1a glabel: Can't store metadata on /dev/ad0s1a manual: it is
Re: I hate to bitch but bitch I must
On Sat, 17 Oct 2009, PJ wrote: Warren Block wrote: On Fri, 16 Oct 2009, Bob Hall wrote: On Fri, Oct 16, 2009 at 07:27:42PM -0400, PJ wrote: BUGS This utility should work on active file systems. I'm a native English speaker, and the manual makes perfect sense to me. It's very clear to me that since the statement is in the BUGS section, it means that the utility should, but doesn't. Since it follows a statement that the utility doesn't, the meaning is unambiguous. I understand it, but see ambiguity in the word should. Easy enough to rewrite: BUGS This utility does not work on active file systems. Now here's my challenge to PJ: use send-pr(1) or the web PR interface at http://www.freebsd.org/send-pr.html to submit this as a doc bug report. That's how FreeBSD gets better, and how you help the next person in the same situation. As I mentioned earlier, I do not understand what the author really intended, so I am out of place making any judgments. If that long thread didn't convince you, certainly nothing I can add will do it. PR 139705 submitted. -Warren Block * Rapid City, South Dakota USA ___ 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: I hate to bitch but bitch I must
2009/10/17 PJ af.gour...@videotron.ca michael wrote: PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE . what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 ok, in short since i didn't see anyone answer this directly, your question of tunefs vs glabel: tunefs is for UFS: it labels a UFS filesystem, no matter the device, ie: ad or da. tunefs is part of the filesystem utilities for UFS. good example, can't tunefs -L SWAP /dev/ad0s1b if it is a swap. you can glabel it. glabel is for labeling a device itself. you can glabel an ntfs filesystem or ext2, whatever. Thanks for that, Michael. But can you explain what this means? It just is not clear for me. # tu;nefs -L home /dev/da3 This puts a label on that disk? So now it can be referred to as home? da3 = home ? I'll try to delve into the man glabel further... but things still look murky. ___ 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 he has a raw file system on that device, ie dangerously dedicated, no partitions etc ___ 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: I hate to bitch but bitch I must
PJ wrote: Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 df: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad12s1a 2026030 319112 154483617%/ devfs1 10 100%/dev /dev/ad12s1h 50777034 4 46714868 0%/backups /dev/ad12s1g 50777034 6276538 4043833413%/home /dev/ad12s1d 4058062 36 3733382 0%/tmp /dev/ad12s1f 50777034 5729324 4098554812%/usr /dev/ad12s1e 2026030 176070 1687878 9%/var linprocfs4 40 100%/usr/compat/linux/proc # ls /dev/ad* crw-r- 1 root operator0, 97 Oct 17 16:36 /dev/ad0 crw-r- 1 root operator0, 103 Oct 17 16:36 /dev/ad0s1 crw-r- 1 root operator0, 101 Oct 17 16:36 /dev/ad10 crw-r- 1 root operator0, 106 Oct 17 16:36 /dev/ad10s1 crw-r- 1 root operator0, 121 Oct 17 16:36 /dev/ad10s1a crw-r- 1 root operator0, 122 Oct 17 16:36 /dev/ad10s1b crw-r- 1 root operator0, 123 Oct 17 16:36 /dev/ad10s1c crw-r- 1 root operator0, 124 Oct 17 16:36 /dev/ad10s1d crw-r- 1 root operator0, 125 Oct 17 16:36 /dev/ad10s1e crw-r- 1 root operator0, 126 Oct 17 16:36 /dev/ad10s1f crw-r- 1 root operator0, 127 Oct 17 16:36 /dev/ad10s1g crw-r- 1 root operator0, 102 Oct 17 16:36 /dev/ad12 crw-r- 1 root operator0, 107 Oct 17 16:36 /dev/ad12s1 crw-r- 1 root operator0, 128 Oct 17 16:36 /dev/ad12s1a crw-r- 1 root operator0, 129 Oct 17 16:36 /dev/ad12s1b crw-r- 1 root operator0, 130 Oct 17 16:36 /dev/ad12s1c crw-r- 1 root operator0, 131 Oct 17 16:36 /dev/ad12s1d crw-r- 1 root operator0, 132 Oct 17 16:36 /dev/ad12s1e crw-r- 1 root operator0, 133 Oct 17 16:36 /dev/ad12s1f crw-r- 1 root operator0, 134 Oct 17 16:36 /dev/ad12s1g crw-r- 1 root operator0, 135 Oct 17 16:36 /dev/ad12s1h crw-r- 1 root operator0, 99 Oct 17 16:36 /dev/ad4 crw-r- 1 root operator0, 104 Oct 17 16:36 /dev/ad4s1 crw-r- 1 root operator0, 108 Oct 17 16:36 /dev/ad4s1a crw-r- 1 root operator0, 109 Oct 17 16:36 /dev/ad4s1b crw-r- 1 root operator0, 110 Oct 17 16:36 /dev/ad4s1c crw-r- 1 root operator0, 111 Oct 17 16:36 /dev/ad4s1d crw-r- 1 root operator0, 112 Oct 17 16:36 /dev/ad4s1e crw-r- 1 root operator0, 113 Oct 17 16:36 /dev/ad4s1f crw-r- 1 root operator0, 114 Oct 17 16:36 /dev/ad4s1g crw-r- 1 root operator0, 100 Oct 17 16:36 /dev/ad6 crw-r- 1 root operator0, 105 Oct 17 16:36 /dev/ad6s1 crw-r- 1 root operator0, 115 Oct 17 16:36 /dev/ad6s1a crw-r- 1 root operator0, 116 Oct 17 16:36 /dev/ad6s1b crw-r- 1 root operator0, 117 Oct 17 16:36 /dev/ad6s1c crw-r- 1 root operator0, 118 Oct 17 16:36 /dev/ad6s1d crw-r- 1 root operator0, 119 Oct 17 16:36 /dev/ad6s1e crw-r- 1 root operator0, 120 Oct 17 16:36 /dev/ad6s1f Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and ad6 is messed up FBSD I'm cheking setting up with clone of ad12 (dump/restore) Now I will try the glabel again... # shutdown now # glabel label rootfs /dev/ad12s1a glabel: Can't store metadata on /dev/ad0s1a shutdown now will get you
Re: I hate to bitch but bitch I must
2009/10/17 Manolis Kiagias son...@otenet.gr PJ wrote: Manolis Kiagias wrote: PJ wrote: Manolis, my state of mind is quite clear... and I'm coping with everything quite allright... I'm not about to get mad at anyone or anything... but tell me, honestly, when you see the stuff I have described above? Woldn't that confuse anyone in their right mind? I am sorry, but there is something here, either some mistake on your part or some other weird problem on your system I can not think of. I don't seem to remember glabel ever failing to store metadata, unless 1) The device is non-existing 2) The device is mounted. As a matter of fact, I did the glabel stuff on a machine a few hours ago. This was already fully installed, I rebooted single user and was done in less than 2 minutes. And yes, if you get a metadata error, it means nothing was done so you are *not* to go and change fstab! Could you please send us /etc/fstab and the results of ls /dev/ad* Here are the outputs: fstab: # DeviceMountpointFStypeOptionsDumpPass# /dev/ad12s1bnoneswapsw00 /dev/ad12s1a/ufsrw11 /dev/ad12s1h/backupsufsrw22 /dev/ad12s1g/homeufsrw22 /dev/ad12s1d/tmpufsrw22 /dev/ad12s1f/usrufsrw22 /dev/ad12s1e/varufsrw22 /dev/acd0/cdromcd9660ro,noauto00 linproc /usr/compat/linux/proc linprocfs rw 0 0 df: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad12s1a 2026030 319112 154483617%/ devfs1 10 100%/dev /dev/ad12s1h 50777034 4 46714868 0%/backups /dev/ad12s1g 50777034 6276538 4043833413%/home /dev/ad12s1d 4058062 36 3733382 0%/tmp /dev/ad12s1f 50777034 5729324 4098554812%/usr /dev/ad12s1e 2026030 176070 1687878 9%/var linprocfs4 40 100%/usr/compat/linux/proc # ls /dev/ad* crw-r- 1 root operator0, 97 Oct 17 16:36 /dev/ad0 crw-r- 1 root operator0, 103 Oct 17 16:36 /dev/ad0s1 crw-r- 1 root operator0, 101 Oct 17 16:36 /dev/ad10 crw-r- 1 root operator0, 106 Oct 17 16:36 /dev/ad10s1 crw-r- 1 root operator0, 121 Oct 17 16:36 /dev/ad10s1a crw-r- 1 root operator0, 122 Oct 17 16:36 /dev/ad10s1b crw-r- 1 root operator0, 123 Oct 17 16:36 /dev/ad10s1c crw-r- 1 root operator0, 124 Oct 17 16:36 /dev/ad10s1d crw-r- 1 root operator0, 125 Oct 17 16:36 /dev/ad10s1e crw-r- 1 root operator0, 126 Oct 17 16:36 /dev/ad10s1f crw-r- 1 root operator0, 127 Oct 17 16:36 /dev/ad10s1g crw-r- 1 root operator0, 102 Oct 17 16:36 /dev/ad12 crw-r- 1 root operator0, 107 Oct 17 16:36 /dev/ad12s1 crw-r- 1 root operator0, 128 Oct 17 16:36 /dev/ad12s1a crw-r- 1 root operator0, 129 Oct 17 16:36 /dev/ad12s1b crw-r- 1 root operator0, 130 Oct 17 16:36 /dev/ad12s1c crw-r- 1 root operator0, 131 Oct 17 16:36 /dev/ad12s1d crw-r- 1 root operator0, 132 Oct 17 16:36 /dev/ad12s1e crw-r- 1 root operator0, 133 Oct 17 16:36 /dev/ad12s1f crw-r- 1 root operator0, 134 Oct 17 16:36 /dev/ad12s1g crw-r- 1 root operator0, 135 Oct 17 16:36 /dev/ad12s1h crw-r- 1 root operator0, 99 Oct 17 16:36 /dev/ad4 crw-r- 1 root operator0, 104 Oct 17 16:36 /dev/ad4s1 crw-r- 1 root operator0, 108 Oct 17 16:36 /dev/ad4s1a crw-r- 1 root operator0, 109 Oct 17 16:36 /dev/ad4s1b crw-r- 1 root operator0, 110 Oct 17 16:36 /dev/ad4s1c crw-r- 1 root operator0, 111 Oct 17 16:36 /dev/ad4s1d crw-r- 1 root operator0, 112 Oct 17 16:36 /dev/ad4s1e crw-r- 1 root operator0, 113 Oct 17 16:36 /dev/ad4s1f crw-r- 1 root operator0, 114 Oct 17 16:36 /dev/ad4s1g crw-r- 1 root operator0, 100 Oct 17 16:36 /dev/ad6 crw-r- 1 root operator0, 105 Oct 17 16:36 /dev/ad6s1 crw-r- 1 root operator0, 115 Oct 17 16:36 /dev/ad6s1a crw-r- 1 root operator0, 116 Oct 17 16:36 /dev/ad6s1b crw-r- 1 root operator0, 117 Oct 17 16:36 /dev/ad6s1c crw-r- 1 root operator0, 118 Oct 17 16:36 /dev/ad6s1d crw-r- 1 root operator0, 119 Oct 17 16:36 /dev/ad6s1e crw-r- 1 root operator0, 120 Oct 17 16:36 /dev/ad6s1f Sorry, but I don't see what this is going to tell you... ad0 is XP; ad10 is minimal FreeBSD 7.2; ad12 is 7.2 on 500gb; ad4 is 7.2 on 80gb; and ad6 is messed up FBSD I'm cheking setting up with clone of ad12 (dump/restore) Now I will try the glabel again... # shutdown now
Re: I hate to bitch but bitch I must
PJ wrote: michael wrote: PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. Seriously, now to the manual: To create a permanent label for a UFS2 file system without destroying any data, issue the following command: # tunefs -L /home/ /dev/da3 Oh? home is what? What does this have to do with the partitions? Here's from man glabel(8): EXAMPLES The following example shows how to set up a label for disk ``da2'', cre- ate a file system on it, and mount it: glabel label -v usr /dev/da2 newfs /dev/label/usr mount /dev/label/usr /usr [...] umount /usr glabel stop usr glabel unload The next example shows how to set up a label for a UFS file system: tunefs -L data /dev/da4s1a mount /dev/ufs/data /mnt/data Am I to understand that glabel is only for a new system? What's with the newfs... I'm trying to set labels on an system that is already set up. And, the glabel examle above is not for UFS file systems? Oh, that's for tunefs? So why are we even dealing with this glabel? from manual: # tunefs -L /home/ //dev/da3/ A label should now exist in /dev/ufs which may be added to /etc/fstab: /dev/ufs/home /home ufs rw 2 2 Why? Is this necessary? and somewhere I saw tunefs -L volume /dev/da0s1a or something like that. Does that mean that each partition should be tunefsd? Maybe the guys who programmed this stuff understand; I sure don't. I just want to be able to set the labels according to what they say can be done... so shy not have a clear and concise explanation? Do people who write this stuff ever read it? Tell me that its clear and simple and to the point... so far, I have been running back and forth between half a dozen web pages trying to understand what is going on... and doing things through a dense fog does not produce creative results! ___ 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 ok, in short since i didn't see anyone answer this directly, your question of tunefs vs glabel: tunefs is for UFS: it labels a UFS filesystem, no matter the device, ie: ad or da. tunefs is part of the filesystem utilities for UFS. good example, can't tunefs -L SWAP /dev/ad0s1b if it is a swap. you can glabel it. glabel is for labeling a device itself. you can glabel an ntfs filesystem or ext2, whatever. Thanks for that, Michael. But can you explain what this means? It just is not clear for me. # tu;nefs -L home /dev/da3 This puts a label on that disk? So now it can be referred to as home? da3 = home ? I'll try to delve into the man glabel further... but things still look murky. tunefs -L HOME /dev/da3 will put the label /dev/ufs/HOME pointing to /dev/da3 . da3=home. exactly correct. the main idea behind that is that you can move the device around, etc. since fstab is looking in /dev/ufs/NAMES_OF_DISKS/PARTITIONS instead of /dev/da[0-9] type setup. you can move it to any controller and still boot(if you have the driver for the controller). the glabel command can label ANY disk/slice/partition. its great when you get away form the old mbr setup and switch to gpt. gpt lets you have an arbitrary number of partitions. and when you think about it, names are so much better than numbers anyway, its why we use DNS on networks. imagine having to remember every ip you have to use. peace ___ 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: I hate to bitch but bitch I must
PJ wrote: manual: it is assumed that a single ATA disk is used, which is currently recognized by the system as ad0. It is also assumed that the standard FreeBSD partition scheme is used, with /, /var, /usr and /tmp file systems, as well as a swap partition. Now, does that mean that glabel does not work if there are several disks on the system... it certainly does not say so nor does it adv ertise that this would not work if there are several ATA disks present.. Previously I had also tried a reboot press 4 with exactly the same results It does say Example on top. And then again: For this *example* it is assumed that a single ATA disk is used,... It doesn't say what will not work with it. It simply assumes some defaults to give a reasonable example. Now, don't tell me this is ambiguous too... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 23:47:56 +0100, krad kra...@googlemail.com wrote: he has a raw file system on that device, ie dangerously dedicated, no partitions etc That's the standard mode for data disks that are not intended to be booted from. It's usable for USB sticks as well. There's no need for a slice. The comment no partitions is partially incorrect, because there is kind of a partition on the device. Note that this partition spans the whole device, which is indicated by the letter c. In this case, /dev/da0 is /dev/da0c. I think it was in FreeBSD 5 when the c for the whole disk / partition has been removed (well, it's still there, it's the reason that you usually can't create da0s1a, da0s1b AND da0s1c, because da0s1c is da0s1), from the disk devices as well as from the acd devices (acd0c is acd0 today). At least, it's correct to say that there's one file system on the disk. Tools like fdisk and bsdlabel haven't been involved in creating it, just # newfs /dev/da0 was the tool of choice. I'd like to add that I've used this method on PDs (phase change discs) as well; they were introduced as da0 to the device directory. No need for slices because the whole disc should be used as one volume. A final note: You can, however, create multiple partitions on a device with no underlying slice, such as da0a, da0b, da0d, da0e etc. And FreeBSD can boot from it without problems. It's always the MICROS~1 stuff that has problems with it. :-) -- 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: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 16:07:25 -0400, PJ af.gour...@videotron.ca wrote: Just a note: I find it strange that nobody looked into the problem of the confusion... I thought I had pointed out where the co;nfusion arises... and no one seems to have either understood the inconsistencies or bothere to read the explanation... oh well... let's keep on blundering away... ;-) I haven't been watching this thread closely, but I vaguely recall your confusion was caused by a manpage. If you can point me at the manpage text and tell me what seemed confusing or, at least, not clear enough, we can always try to fix the manpage. BTW, if you happen to find more manpage text that needs clarification, it's always a good idea to post your comments to the freebsd-doc list. This way someone from the Documentation Team may see them and do something about the confusing manpage text. pgpJFy8JKIEja.pgp Description: PGP signature
Re: I hate to bitch but bitch I must
On Sat, 17 Oct 2009 23:50:51 +0100, krad kra...@googlemail.com wrote: easiest way is to boot in on a live cd/usb label it all up with tunefs and edit the fstabs then reboot off disks Yes, that's the most comfortable way. FreeBSD's live disc should be completely fine. There's no problem with should work on / even if / is mounted ro. :-) -- 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: I hate to bitch but bitch I must
Manolis Kiagias wrote: PJ wrote: Now, does that mean that glabel does not work if there are several disks on the system... it certainly does not say so nor does it adv ertise that this would not work if there are several ATA disks present.. Previously I had also tried a reboot press 4 with exactly the same results Aha, as I said above then. If you've done this and you are still getting the can't store metadata message, I am really out of ideas. Just a WAG, but sysctl kern.geom.debugflags=16 possibly? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: I hate to bitch but bitch I must
Polytropon wrote: note there I have also used glabel on the swap (command used was glabel label /dev/ad10p1) A really honest question: What does the p in ad10p1 indicate? I always thought swap partitions are something like ad10b (an own partition right after the root partition a). ad10s1b is a traditional bsdlabel(8) generated partition. (ie. it's partition b on slice 1 of disk ad10) ad10p1 indicates use of gpt(8) partitioning. (ie. partition 1 on disk ad10) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: I hate to bitch but bitch I must
On Fri, Oct 16, 2009 at 05:54:23PM -0400, PJ wrote: Why is it that the manual pages, as thorough as they may be, are very, very confusing. Perhaps I am being too wary, but I find that too many instructions/examples are stumbling blocks to appreciation of the whole system: for instance, let's look at the instructions for changing disk labels with glabel or is it tunefs ? man glabel(8): for UFS the file system label is set with tunefs(8) http://www.freebsd.org/cgi/man.cgi?query=tunefssektion=8apropos=0manpath=FreeBSD+7.2-RELEASE. what happened to glabel? man tunefs(8) The *tunefs* utility cannot be run on an active file system. To change an active file system, it must be downgraded to read-only or unmounted. So, you have to run tunefs from an active file system to modify another disk? No, it clearly says tunefs CANNOT be run on an active filesystem. Then it says, in order to change an active file system you have to first make it a NOT active filesystem - eg make it read-only or just unmount it. but from man tunefs: BUGS This utility should work on active file systems. What in hades does this mean--just above it says cannot be run on active file systems. ??? That means it is a BUG that it won't work on an active files system - eg that someone should fix this defficiency and make it so it will work on an active filesystem. The man writer thinks it 'should' be able to work that way. jerry To change the root file system, the system must be rebooted after the file system is tuned. You can tune a file system, but you cannot tune a fish. How cute... And fish eat bugs. ___ 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: I hate to bitch but bitch I must
Matthew Seaman wrote: Manolis Kiagias wrote: PJ wrote: Now, does that mean that glabel does not work if there are several disks on the system... it certainly does not say so nor does it adv ertise that this would not work if there are several ATA disks present.. Previously I had also tried a reboot press 4 with exactly the same results Aha, as I said above then. If you've done this and you are still getting the can't store metadata message, I am really out of ideas. Just a WAG, but sysctl kern.geom.debugflags=16 possibly? Cheers, Matthew Ha, yes, the shoot in the foot sysctl :) Shouldn't be needed though - I was labelling a boot disk about half an hour ago and nothing else than pure 'glabel label' was required. There must be something else that stops it. Maybe running glabel with -v will help the OP (hopefully with a more detailed error message) ___ 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: small question about tape-based dumps
On Fri, Oct 16, 2009 at 08:43:26PM -0600, Tim Judd wrote: Replies inline On 10/16/09, Jerry McAllister jerr...@msu.edu wrote: On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / I understand that this creates a dumpfile on nsa0, and as I understand tapes (which may be wrong, which I ask for clarification here).. To mark a end-of-file to be able to fast-forward/rewind, why can't you use: mt -f /dev/nsa0 weof It's description in mt(1) says it writes the end-of-file mark at current position You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr So if we use weof, would the 2nd dump then be: dump 0af /dev/nsa0 /usr mt -f /dev/nsa0 weof thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var And 3rd: dump 0af /dev/nsa0 /var mt -f /dev/nsa0 weof etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline And I've never used offline, guess I'll start now. I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry With regards Stevan Tiefert Thanks for any input! --TJ ___ 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: small question about tape-based dumps
On 10/17/09, Jerry McAllister jerr...@msu.edu wrote: snip You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry snip If dump is the tool for tapes, and tar is named after tape archives... Do both of these utilities write the *proper* EOF to whatever medium it's writing to? I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. Please 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
Re: small question about tape-based dumps
Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: On 10/17/09, Jerry McAllister jerr...@msu.edu wrote: snip You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry snip If dump is the tool for tapes, and tar is named after tape archives... Please, no flamewar!!! Do both of these utilities write the *proper* EOF to whatever medium it's writing to? They both write EOF. I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? There is only one EOF: The EOF. Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. weof is not useless. There are some file operations without writing an EOF, like streams or something like that, but tar and dump are writing with an EOF at the end of files :-) ___ 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: small question about tape-based dumps
On 10/17/09, Stevan Tiefert stevan-tief...@kabelmail.de wrote: Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: On 10/17/09, Jerry McAllister jerr...@msu.edu wrote: snip You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry snip If dump is the tool for tapes, and tar is named after tape archives... Please, no flamewar!!! Wasn't planning on starting one. Sorry if it came across that way. Do both of these utilities write the *proper* EOF to whatever medium it's writing to? They both write EOF. I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? There is only one EOF: The EOF. Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. weof is not useless. There are some file operations without writing an EOF, like streams or something like that, but tar and dump are writing with an EOF at the end of files :-) So it's a item for good measure rather than an item as necessity in creating backups. Thanks for all the info. I'm happy knowing more. --Tim ___ 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: I hate to bitch but bitch I must
PJ wrote: [snip] I think you're trying to take the meaning of should a little too far... to keep it simple, and without trying to intellectualize it, it simply means (and this can change within certain contexts) normally, it should work (in our context, here) but there is no implication of any warnings or dangers ... the normally is implied, the rest you can do with it as you wish, obviously at your rist... but even then the interpretation goes too far. As I suggested to Polytropon, in this particular case the instructions for the implementation of the procedure are very clear: use on an inactive system or SUM... so where's the bug... to suggest that it should work on an active system is confusing - if the author thought it important that it wouldl not work on an active system, perhaps he should have merely said do not use on an active system... that would be consistent and very clear. ;-) Sorry, I'm not totally clear on everything either, but it is clearly contained within a section called 'BUGS'. This should set the context and will affect how the comment should be construed. If it were located anywhere else in the man page the context would be different, this altering the intended meaning or purpose. Content within any 'BUGS' section should not be considered for normal usage of a command, unless it is something you think you can/should try and it is warning you not to do so. It is more of a disclosure of 'gotcha' potential, aka 'here be dragons' or other potential method by which an admin may shoot him/herself in the foot. Just my meager $.02, fwiw -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I hate to bitch but bitch I must
Message: 9 Date: Sat, 17 Oct 2009 16:07:25 -0400 From: PJ af.gour...@videotron.ca Subject: Re: I hate to bitch but bitch I must To: Polytropon free...@edvax.de Cc: Steve Bertrand st...@ibctech.ca, freebsd-questions@freebsd.org freebsd-questions@freebsd.org Message-ID: 4ada23fd.8020...@videotron.ca Content-Type: text/plain; charset=UTF-8 Polytropon wrote: On Fri, 16 Oct 2009 21:29:04 -0400, PJ af.gour...@videotron.ca wrote: It is simple to understand Emglish but not so simple what was meant by whoever wrote it...I cannot correct something that I do not uderstand... come on, man, that should be easy to understand. As English is not my native language, I *now* understand the meaning of it should; in this case, it seems to mean something like basically, it is supposed to, but in this case, it does not, regarding the desired action. To be as precise as possible, it means normally it should work so go ahead; then the question is - what do you mean by normally. You made the blunder of using the word should in your definition of should :) In our case above, the instructions were to do the operation with the disk not in use and the os in SUM. That's very clear. Now, I f they wanted to point out a bug, the bug means that there is an anomaly under certain circumstances - and in this case there really is no bug as it is very clear as to how the instructions should be used. If they consider the operation under a live files system a bug, then they should just make a warning and say something along the lines of do not use on live system as that may destroy data or something to that effect. As others have mentioned, context is important. Somebody even suggested a re-wording dropping the word should. If there was a risk of data-loss, (somebody noted the program refuses to touch a live filesystem,) the bugs section would have read something more like: (Program) SHOULD NOT try writing to a live file-system. That is to say, the word should in a Bugs section implies a wish-list item. Meaning: it is technically possible, but the maintainers have not done the necessary (possibly tedious) work yet. Regards, James Phillips __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.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: I hate to bitch but bitch I must
On Fri, 16 Oct 2009 23:49:52 -0400 Bob Hall rjh...@gmail.com wrote: On Sat, Oct 17, 2009 at 02:34:40AM +, Mark wrote: Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Actually, what's happening here is dropping part of a sentence. It's common in English to shorten Yea, it should work, but it doesn't. Not really, but the only sensible meaning is that it should, in an ideal world, work. It seems that people are grasping for ambiguity here. If a phrase has one sensible meaning and other absurd meanings then there really is no ambiguity all unless one is trying to be deliberately obtuse. ___ 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: I hate to bitch but bitch I must
RW wrote: On Fri, 16 Oct 2009 23:49:52 -0400 Bob Hall rjh...@gmail.com wrote: On Sat, Oct 17, 2009 at 02:34:40AM +, Mark wrote: Actually, this has got very little to do with being a native English speaker or not. It's ere a matter of intonation (which, in writing, can only be conveyed to a certain degree, of course). 'Should' can certainly mean Don't try that. As in: Will the ice hold me? Well, technically it should. (Meaning: it probably will, but I'm not overly confident.) Actually, what's happening here is dropping part of a sentence. It's common in English to shorten Yea, it should work, but it doesn't. Not really, but the only sensible meaning is that it should, in an ideal world, work. It seems that people are grasping for ambiguity here. If a phrase has one sensible meaning and other absurd meanings then there really is no ambiguity all unless one is trying to be deliberately obtuse. i could have sworn this thread was about glabel and tunefs, whats with the grammar and linguistics? *note* not directed at RW ___ 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
