Re: Keeping /etc/localtime up-to-date
Matthias Andree wrote: > > If they're in the same physical FS there's no need for a symlink. > > You might as well use a hardlink. > > And then discuss how all the time zone configuration tools deal > with /etc/localtime - truncate/overwrite, direct overwrite ... In that case neither a symlink nor a hardlink is safe, regardless of whether /etc and /usr/share/timezone are in the same FS. Either truncate/overwrite or direct overwrite will trash the target of a symlink just as they would the file identified by a hardlink. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
on 29/03/2011 23:29 Baptiste Daroussin said the following: > ok let's try to say it simpler :) the main goal is to keep it simple > for now, simple and rock solid, so that we can replace pkg_install and > do some cleanup in the ports tree, add the "must have" features while > doing that. And only when we will be ready for that and that portmgr > have decided that it is mature enough to replace pkg_install, only > after that we will start improving with new features and new changes. > > I thinks changing the package name scheme is not a "must have" > feature, it for sure is and intresting feature, but what about pushing > to after the first stable release? managing architecture as we plan to > do it is enough imho. Oh, yes, I realize all this and totally agree with it. Given how huge and how visible our ports and packages systems are, it's better to be slow and cautious. All the ideas that I suggested were more for the "next step" than for now. Thank you for the work! -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [ECFT] pkgng 0.1-alpha1: a replacement for pkg_install
2011/3/31 Andriy Gapon : > on 29/03/2011 23:29 Baptiste Daroussin said the following: >> ok let's try to say it simpler :) the main goal is to keep it simple >> for now, simple and rock solid, so that we can replace pkg_install and >> do some cleanup in the ports tree, add the "must have" features while >> doing that. And only when we will be ready for that and that portmgr >> have decided that it is mature enough to replace pkg_install, only >> after that we will start improving with new features and new changes. >> >> I thinks changing the package name scheme is not a "must have" >> feature, it for sure is and intresting feature, but what about pushing >> to after the first stable release? managing architecture as we plan to >> do it is enough imho. > > Oh, yes, I realize all this and totally agree with it. > Given how huge and how visible our ports and packages systems are, it's > better to > be slow and cautious. > All the ideas that I suggested were more for the "next step" than for now. > And noted in my personnal TODO list :) > Thank you for the work! > -- > Andriy Gapon > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
mountd stuck in ZFS code. (fwd)
re-posting here to see if I'm more successful: --- Begin Message --- I have been running the experimental nfs/mount for some time now, and it mostly works, except with this particular case, where the mountd just gets stuck: mountd 11762 [dp->dp_config_rwlock] 8.93r 0.00u 0.00s 0% 1320k and stops respondig. I can't reproduce it at will, but it happens quiet often. The host in question is an nfs/zfs server, runing 8-stable and zfs ZFS pool version 15 ZFS filesystem version 4 cheers, danny ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" --- End Message --- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Switching to [KMGTPE]i prefixes?
On Fri, Mar 25, 2011 at 10:13:04AM +, Alexander Best wrote: > On Fri Mar 25 11, Bruce Cran wrote: > > On Fri, 25 Mar 2011 00:21:15 + > > Alexander Best wrote: > > > > > i hacked up humanized_number(3) a bit in order to produce the > > > following df(1) output: > > > [...] > > > 4.2Gi 4.2Gi 0B 100% 0 0 100% /media/dvd > > > > I don't know if it's correct, but Snow Leopard uses "Bi" for bytes. > > hmmm...i'm wondering why they do that. there's no reason for that, because > 1 bytes is 8 bit no matter if you use a power of one or a power of ten. > Given the output above it would only be safe to assume that you are refering to a BLOCKSIZE=K when denoting size as "Gi". It would be more proper if this was to denote the size as "GiB" so the end result can be determined whether or not it is really "Gib". "[X]i" in it self does not signify the size of the data by which the result was calculated but only that the result has been calculated by 1024^N and seems to have been a mislead representation by other OS's. So whether were using BLOCKSIZE of "b B K M G T P..." can we adjust this so it displays the increment correctly please ? http://en.wikipedia.org/wiki/Byte http://en.wikipedia.org/wiki/Megabyte http://en.wikipedia.org/wiki/Gigabyte [...] http://en.wikipedia.org/wiki/Template:Quantities_of_bits http://en.wikipedia.org/wiki/Orders_of_magnitude_%28data%29 -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN pgpTCRbGNbhb2.pgp Description: PGP signature
issue with devstat_buildmatch(3) and certain strings
hi there, devstat_buildmatch(3) crashes with certain strings. you can test this by doing one of: iostat -t "," iostat -t ",," iostat -t "da," iostat -t ",da," iostat -t ",da" iostat -t "da,scsi," iostat -t ",da,scsi" iostat -t "da,,scsi" i've tried, but wasn't able to fix this properly. cheers. alex -- a13x ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
