Any way to fix '/usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by ... not found'?

2010-08-12 Thread Dmitry Marakasov
] Is there a way to fix that, maybe some linker magic? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-hackers@freebsd.org mailing list http

Re: NFS write corruption on 8.0-RELEASE

2010-02-12 Thread Dmitry Marakasov
time with a message server is alive again). Also I've seen another strange thing - not only the mount dies but the network is flooded with NFS traffic. Last time I've seen it quite a while ago, so I don't remember the circumstances and direction of the traffic. -- Dmitry Marakasov . 55B5 0596

Re: NFS write corruption on 8.0-RELEASE

2010-02-12 Thread Dmitry Marakasov
corruption if they rely on locking. I know - I have no processes that use locks on that filesystems. Also there's only a single client. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru

Re: NFS write corruption on 8.0-RELEASE

2010-02-12 Thread Dmitry Marakasov
failed which leads to file corruption. Personally I definitely prefer the first. Yeah, but I have mostly desktop-(NAS w/torrents) setup so I prefer the second. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp

NFS write corruption on 8.0-RELEASE

2010-02-10 Thread Dmitry Marakasov
. Any ideas? PS. Diffs of corrupted blocks in a text format are here: http://people.freebsd.org/~amdmi3/diff.1.txt http://people.freebsd.org/~amdmi3/diff.2.txt http://people.freebsd.org/~amdmi3/diff.3.txt -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3

[patch] kernel iconv improvements

2009-04-27 Thread Dmitry Marakasov
-cp_from = cp; + for (; *cp; cp++) + *cp = toupper(*cp); } else csp-cp_from = iconv_unicode_string; csp-cp_data = data; --- iconv.c.patch ends here --- -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd

-pthread propagation

2009-04-01 Thread Dmitry Marakasov
in the above mentioned error case (cc'ing hackers@). So should -pthread be forced in ldflags 1) Only in ports that explicitely use threads 2) In all ports that link with -lthr implicitely, including through other ports? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd

Re: VirtualBox looks for FreeBSD developer

2008-10-10 Thread Dmitry Marakasov
://amdmi3.ru/files/virtualbox-port.tar.gz -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D [EMAIL PROTECTED] ..: jabber: [EMAIL PROTECTED]http://www.amdmi3.ru ___ freebsd-hackers@freebsd.org mailing list http

Re: Transferring ports

2008-03-13 Thread Dmitry Marakasov
* Ivan Voras ([EMAIL PROTECTED]) wrote: I have an idea and a request for people familiar with ports pkgdb infrastructure: a utility (preferably written in C, Python or as a shell script) that would transfer *installed* ports from one system tree to the other, including their dependencies. It

Re: absolute vs. relative offsets in disklabel

2006-08-06 Thread Dmitry Marakasov
* Dag-Erling Sm?rgrav ([EMAIL PROTECTED]) wrote: Recent `disklabel differences FreeBSD, DragonFly' thread gave me a thought - why do we have absolute offsets in disklabel? We don't, AFAIK. Since the transition to GEOM, the offsets are relative to the start of the containing provider. It has

Re: absolute vs. relative offsets in disklabel

2006-08-01 Thread Dmitry Marakasov
* Dan Nelson ([EMAIL PROTECTED]) wrote: Recent `disklabel differences FreeBSD, DragonFly' thread gave me a thought - why do we have absolute offsets in disklabel? AFAIK, on NetBSD and OpenBSD, label is not necessarily located `near' filesystems stored in it's partitions - and even

absolute vs. relative offsets in disklabel

2006-07-31 Thread Dmitry Marakasov
Hi! Recent `disklabel differences FreeBSD, DragonFly' thread gave me a thought - why do we have absolute offsets in disklabel? AFAIK, on NetBSD and OpenBSD, label is not necessarily located `near' filesystems stored in it's partitions - and even disklabel utility shows absolute offsets (with 'c'

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Dmitry Marakasov
* Matthew Dillon ([EMAIL PROTECTED]) wrote: Oh, very cute! A terrible hack if you ask me, but cute all the same! I don't consider it a hack. Pretty expected and consistent behaviour - any block device (be it a whole disk or just a partition) is scanned by geom for magic numbers, and if any

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Dmitry Marakasov
* David Gilbert ([EMAIL PROTECTED]) wrote: Dmitry About `lack' of partitions - don't forget that labels can be Dmitry nested. Just do `bsdlabel -w /dev/ad0s1e` - you'll get Dmitry /dev/ad0s1ea. Don't also forget that gpt(8) exists and seems to provide for large numbers of partitions. It

Re: disklabel differences FreeBSD, DragonFly

2006-07-29 Thread Dmitry Marakasov
* Matthew Dillon ([EMAIL PROTECTED]) wrote: felt that 8 partitions is restrictive. My main home server has 10 and the main DragonFly box has 11. There is another solution for FreeBSD folks, however. You *DO* have four slices to play with. You can put a disklabel with 8

Re: New Welcome message for FreeBSD

2006-07-28 Thread Dmitry Marakasov
* Giorgos Keramidas ([EMAIL PROTECTED]) wrote: New motd-welcome message for FreeBSD. http://www.cwt.uz/motd best regards I like it! Very good. I don't. It is pretty content free when compared with our current default motd. I agree, FreeBSD is serious OS, and it's not good idea to