I could never understand how any user - be it experienced or not - could cope with "Windows Explorer". Once you've seen this tool (package) TotalCommander, you'll never want to return again. But you may have to, on the next machine.:)
Still waiting for a Linux version.;-)
(Like I never got the notion about what is good about "Internet Explorer", except that "it's just there" [duh!], and that it's allegedly most standard conform - or used to be.)
Yup, "killnetscape" is frequently called.;-). It sorta depends a little bit on your flavor of "pidof", or whether you've got a PID-file, but it's nice for cleaning the lock file and the ~/core dump, while you're at it.
> I have make for my own use a netscape > rpm with the same spec as redhat Precisely, should be no problem if you get the src.rpm, replace the tar.gz in/usr/src/redhat/SOURCES, hack at the spec file (usually, you'll only have to push the version number up).
> i would like to know if i should use > linux-2.0glibc version as with 4.61 I believe so, in RedHat Rawhide (pre-6.1), the Netscape RPMs require compat-glibc/libs, which is the 2.0 series of glibc. Check the RPM changelog entry of Fri Aug 20 1999 on rpmfind.net! But this is valid for 4.61, perhaps 4.7 is built against a newer glibc - aaah dream on.;-)
I actually run 4.61 without compat-glibc but rather with the standard glibc-2.1 (as delivered with RedHat 6.0), and I suppose all my crashes (locks) aren't glibc issues - but who knows.
Are you sure? In the "Select OS" selection box, it first lists "Win*", then comes a line saying "PLATFORMS BELOW AVAILABLE IN 5.0 ONLY". Thanks, I've got that version.
Actually, a Solaris alpha/beta version is mentioned in the README packaged with G2 for Linux, but nowhere to be found.
> And an alpha Alpha version would be nice, too, but I don't see that happening anytime soon...
Well, if you look at the rpm, it's built by RedHat (not only for RedHat), so I guess they might be pushing for an Alpha and a SPARC build as well, as soon as they get them running.
Get hold of the pgcc-1.1.3 source rpm ( pgcc-1.1.3-3mdk.src.rpm) from Mandrake, if you plan to use pgcc anyway:-). It provides (apart from pgcc, of course) a libstdc++ package, which includes libstc++-2.8.0 and 2.9.0 (and various others) for compatibility to older packages. Built it yesterday, works fine. (Hey, now there's a use for rpm -bb --short-circuit... Building pgcc takes 3 hours on my machine, and I had the change to spec file tons'o'times.:-( )
After having Slack'ed for quite a while, I found it's almost as easy to build your own packages under RedHat, using "RPM -b?". The document "Maximum RPM" is quite some help, but it's easier looking at other people's spec files.
I've installed pgcc-1.1.1 to replace gcc/egcs (RedHat-5.2), using the RPMs linked to from the PGCC website and compiled my kernel with -mpentium -DCPU=i586 or the likes.
Since then, config.guess of each and every source package using configure bails out. "Can't determine host type" or the likes.
I've been adding "--host=`uname -m`-`uname -s | tr [A-Z] [a-Z]`" to my *.spec files, but that's stupid. Any suggestions?
Oh yeah, and doesn't it make sense that if one writes an x86 emulator, that it should be able to run on computers other than an x86? (sorry if that sounded hostile...)
Absolutely. I need an x86 emulator running on Sparc/SunOS, in order to run those darned DOS programs;-) which just are better. Linux on an emulator is a bit slow, admittedly. Yet.
We (my company, my development department) can even top that: OC-192/STM-64 over WDM, which will be 16x (or 32x) 10GBit/s on one fiber. You don't want it at home, your HD'd be full in the wink of an eye.
We (my company, my development department) can even top that: OC-192/STM-64 over (PDF), which will be 16x (or 32x) 10GBit/s on one fiber. You don't want it at home, your HD'd be full in the wink of an eye.
Well, think on... Now you know what those little stickers "Designed for Microsoft Windows 9x" are meant for! Stick'em on your garbage can, toilet seat, hand gun,...
I need my company's proxies to support gopher. It's the only way to do semi-telnet out to the internet (things like `finger' -> `telnet host 79' -> `gopher://host:79/0user', but more complex as well, such as "VRFY"/"EXPN" on port 25). Keep it, it's nice and simple.:-)
Slashdot Mirror
You've gotta agree on this 100%.
:)
;-)
I could never understand how any user - be it experienced or not - could cope with "Windows Explorer". Once you've seen this tool (package) TotalCommander, you'll never want to return again. But you may have to, on the next machine.
Still waiting for a Linux version.
(Like I never got the notion about what is good about "Internet Explorer", except that "it's just there" [duh!], and that it's allegedly most standard conform - or used to be.)
gibson
(Source is available.)
I could actually make a nice junkbuster feature request list. ;-)
Otherwise, aye to all the suggestions. I miss those features mentioned at the top of the thread each and every day!
> rpm with the same spec as redhat
Precisely, should be no problem if you get the src.rpm, replace the tar.gz in
> i would like to know if i should use ;-)
> linux-2.0glibc version as with 4.61
I believe so, in RedHat Rawhide (pre-6.1), the Netscape RPMs require compat-glibc/libs, which is the 2.0 series of glibc. Check the RPM changelog entry of Fri Aug 20 1999 on rpmfind.net! But this is valid for 4.61, perhaps 4.7 is built against a newer glibc - aaah dream on.
I actually run 4.61 without compat-glibc but rather with the standard glibc-2.1 (as delivered with RedHat 6.0), and I suppose all my crashes (locks) aren't glibc issues - but who knows.
Personally, I believe it'll be M$ Jolly-ett, though.
P.S.: I know, I know, better use IDs than filenames.
--
f y cn rd ths y mst hv bn sng nx
Actually, a Solaris alpha/beta version is mentioned in the README packaged with G2 for Linux, but nowhere to be found.
Okay, smarty pants, where?
Well, if you look at the rpm, it's built by RedHat (not only for RedHat), so I guess they might be pushing for an Alpha and a SPARC build as well, as soon as they get them running.
Get hold of the pgcc-1.1.3 source rpm ( pgcc-1.1 .3-3mdk.src.rpm) from Mandrake, if you plan to use pgcc anyway :-). It provides (apart from pgcc, of course) a libstdc++ package, which includes libstc++-2.8.0 and 2.9.0 (and various others) for compatibility to older packages. Built it yesterday, works fine. (Hey, now there's a use for rpm -bb --short-circuit... Building pgcc takes 3 hours on my machine, and I had the change to spec file tons'o'times. :-( )
Thanks, AC, that helps. You saved my day. :-) So time to send a bug report to the pgcc folks?
After having Slack'ed for quite a while, I found it's almost as easy to build your own packages under RedHat, using "RPM -b?". The document "Maximum RPM" is quite some help, but it's easier looking at other people's spec files.
Since then, config.guess of each and every source package using configure bails out. "Can't determine host type" or the likes.
I've been adding "--host=`uname -m`-`uname -s | tr [A-Z] [a-Z]`" to my *.spec files, but that's stupid. Any suggestions?
Absolutely. I need an x86 emulator running on Sparc/SunOS, in order to run those darned DOS programs ;-) which just are better. Linux on an emulator is a bit slow, admittedly. Yet.
Glad you pointed it out. :-)
1) It's OC-48, pay attention. OC-3c = 155Mbit. OC-12 = 648Mbit. OC-48 - 2.4Gbit. OC-96 - 10Gbit.
Actually, OC-192 is 10Gbit/s.
We (my company, my development department) can even top that: OC-192/STM-64 over WDM, which will be 16x (or 32x) 10GBit/s on one fiber. You don't want it at home, your HD'd be full in the wink of an eye.
Glad you pointed it out.
1) It's OC-48, pay attention. OC-3c = 155Mbit. OC-12 = 648Mbit. OC-48 - 2.4Gbit. OC-96 - 10Gbit.
Actually, OC-192 is 10Gbit/s.
We (my company, my development department) can even top that: OC-192/STM-64 over (PDF), which will be 16x (or 32x) 10GBit/s on one fiber. You don't want it at home, your HD'd be full in the wink of an eye.
Well, think on... Now you know what those little stickers "Designed for Microsoft Windows 9x" are meant for! Stick'em on your garbage can, toilet seat, hand gun, ...
I need my company's proxies to support gopher. It's the only way to do semi-telnet out to the internet (things like `finger' -> `telnet host 79' -> `gopher://host:79/0user', but more complex as well, such as "VRFY"/"EXPN" on port 25). Keep it, it's nice and simple. :-)