Re: static linked files in /usr/bin
On Mon, Jun 12, 2000 at 12:42:42PM +0400, Juriy Goloveshkin wrote: > but /usr/bin and /usr/lib usualy live at the same filesystem and if > /usr/lib may be broken, what we may say about /usr/bin? Statically linked binaries in /usr/bin/ will still be usable. You didn't think about what I said. Tar *is* a recovery tool. I've killed libc.so.* and ld-elf.os before suffiently bad that I was quite glad tar was statically linked. > maybe RELEASE-bin* must be splited? say... configs,binaries and developer > stuff(includes,gcc stuff, lib*.a, developer's manpages) Diffs? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: static linked files in /usr/bin
On Sun, 11 Jun 2000, David O'Brien wrote: > On Sun, Jun 11, 2000 at 09:00:34PM +0400, Juriy Goloveshkin wrote: > > Why a lot of files in /usr/bin(sbin) are static linked? > > for example, tar: static - 272832 bytes(83416 dynamic) > > IMO tar should live in /bin as it is used to restore a system from tape. > I don't know why ``dump'' is in /usr/sbin -- only restore should be > there. > > /usr/bin/tar is statically linked so it isn't depended on /usr/lib/ which > may be terribly broken (and thus why you are doing a restore). but /usr/bin and /usr/lib usualy live at the same filesystem and if /usr/lib may be broken, what we may say about /usr/bin? I think utilities in /usr/... must be dynamicaly linked. btw, I compared the size of bin-tarballs in 2.8 and current distributions. I downloaded 2.8 by modem without spending SO many time... current minimal installation require to download 30-35Mb! maybe RELEASE-bin* must be splited? say... configs,binaries and developer stuff(includes,gcc stuff, lib*.a, developer's manpages) Bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: static linked files in /usr/bin
On Sun, Jun 11, 2000 at 09:00:34PM +0400, Juriy Goloveshkin wrote: > Why a lot of files in /usr/bin(sbin) are static linked? > for example, tar: static - 272832 bytes(83416 dynamic) IMO tar should live in /bin as it is used to restore a system from tape. I don't know why ``dump'' is in /usr/sbin -- only restore should be there. /usr/bin/tar is statically linked so it isn't depended on /usr/lib/ which may be terribly broken (and thus why you are doing a restore). > is it magic of /usr/src/gnu folder? Has nothing to do with it. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
static linked files in /usr/bin
Hi all! Why a lot of files in /usr/bin(sbin) are static linked? for example, tar: static - 272832 bytes(83416 dynamic) is it magic of /usr/src/gnu folder? Bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
