pkg_delete removes package and all files, which has been listed in pkg_plist file (%files section in RPM spec). From what I've understood, this means all files except configuration files, because they are not listed in pkg_plist (at least thats what porters handbook used to recommend). So in Debian terminology, you can remove, but you can't purge package.
pkg_info has option (-g), which will show files, which checksum doesn't match with recorded checksum.
What comes to dependencies, there are more than one kind of dependencies. There are dependencies that are required for building the package, there are dependencies that are required to run the programs that package provides, etc.. All dependencies are described by telling required file and port, which has that file, i.e. you could list/usr/local/bin/mutt as required file and mail/mutt as port, which has to be installed, if/usr/local/bin/mutt doesn't exist. When you are building port with make install, make file will automatically install all ports, which your port requires.
I hate to disappoint you, but if you do upgrade by source (install sources, build world and kernel, install them and mergemaster afterwards), you can do it without going to single-user mode or at least I've done it from 4.1->4.1.1 and then 4.1.1->4.2 and I am planning to do it with 4.2->4.3 as well. Each time, when I've done it, I've stopped all unnecessary processes before I've done the make installworld, but thats all..
When 5.0 comes out, things might get interesting,
but we'll see how things go when that happens.
At least for me, two main issues are ability to upgrade remotely and having large collection of reasonably uptodate packages.
In Linux front, RedHat fails on remote upgrade requirement. While Debian can cover upgrade pretty nicely, their package collection is smaller (at least on the application that I've needed) than FreeBSD ports and unless you want to be running unstable, your applications might be pretty old (its relative term, but...). As an example, there was quite long delay before Debian's testing upgraded their GNOME packages from 1.0.55 to newer.
PalmOS 4.0 claims that it would have "enchanced security - Put an automatic lock on your handheld..". Have they finally done something to PalmOS so that you get some REAL protection to the information in Palm or is this just "improved" version from the old password system. If so, it would be nice to have that single feature as security upgrade to PalmOS 3.3 and PalmOS 3.5 Palms, since complete PalmOS upgrade seems to be history.
Then again, if Palm doesn't consider it to be worthwhile to create security upgrade for old PalmOS versions, we can always use our money for one of those Linux or *BSD based PDAs, when its time to buy new PDA. With those, you have little bit more options regarding updates and such...
P.S. Yes, I am aware of GNU Keyring for PalmOS project, but it won't protect calendar and todo entries that I have in standard PalmOS applications.
I would assume that its the typical laptop story, where they will put "Designed for Microsoft Windows 9x" sticker on it. I guess the main question is that, are they going to create Linux drivers for all devices in the box (i.e. modem and camera) and are those drivers going to be OpenSource so that I can freely upgrade my kernel, if I want or upgrade as long as you please, but if our binary drivers don't work with your new kernel, your on your own.
If they would be willing to do the drivers for
Linux (binary or OpenSource...), another issue is that can I have preloaded with Linux and get discount, since I don't need Microsoft OEM software in machine.
Only problem in this solution is that at least PGP 6.5.1 for Windows, mutt and probably some other tools as well are nowdays supporting PGP/GPG passphrase caching.
Even though there is timeout in those passphrase caching systems, its not impossible to think that some virus in future would be smart enough to do PGP signing, when it comes across with machine, which has PGP installed and passphrase currently in cached.
Its kind of scary to think, how many people would open virus attachment without second thought since it has PGP signature to validate that it really came from sender and everyone has been saying that PGP makes e-mail safe.
If you buy standard Palm IIIx, it only has 4Mb memory in it. However it has expansion slot, which you can use for doubling the memory to 8Mb. Anyway original poster was correct in his statement that Palm IIIxe doubles the memory of earlier Palm IIIx.
Slashdot Mirror
pkg_info has option (-g), which will show files, which checksum doesn't match with recorded checksum.
What comes to dependencies, there are more than one kind of dependencies. There are dependencies that are required for building the package, there are dependencies that are required to run the programs that package provides, etc.. All dependencies are described by telling required file and port, which has that file, i.e. you could list /usr/local/bin/mutt as required file and mail/mutt as port, which has to be installed, if /usr/local/bin/mutt doesn't exist. When you are building port with make install, make file will automatically install all ports, which your port requires.
When 5.0 comes out, things might get interesting, but we'll see how things go when that happens.
With remote upgrades I mean upgrade from RH5.2 to
RH6.2 or RH6.2 to RH7.0 without any kind of physical access (i.e. console) to the machine.
In Linux front, RedHat fails on remote upgrade requirement. While Debian can cover upgrade pretty nicely, their package collection is smaller (at least on the application that I've needed) than FreeBSD ports and unless you want to be running unstable, your applications might be pretty old (its relative term, but ...). As an example, there was quite long delay before Debian's testing upgraded their GNOME packages from 1.0.55 to newer.
Then again, if Palm doesn't consider it to be worthwhile to create security upgrade for old PalmOS versions, we can always use our money for one of those Linux or *BSD based PDAs, when its time to buy new PDA. With those, you have little bit more options regarding updates and such...
P.S. Yes, I am aware of GNU Keyring for PalmOS project, but it won't protect calendar and todo entries that I have in standard PalmOS applications.
If they would be willing to do the drivers for Linux (binary or OpenSource...), another issue is that can I have preloaded with Linux and get discount, since I don't need Microsoft OEM software in machine.
-- .sig
No
Only problem in this solution is that at least PGP 6.5.1 for Windows, mutt and probably some other tools as well are nowdays supporting PGP/GPG passphrase caching.
Even though there is timeout in those passphrase caching systems, its not impossible to think that some virus in future would be smart enough to do PGP signing, when it comes across with machine, which has PGP installed and passphrase currently in cached.
Its kind of scary to think, how many people would open virus attachment without second thought since it has PGP signature to validate that it really came from sender and everyone has been saying that PGP makes e-mail safe.
If you buy standard Palm IIIx, it only has 4Mb
memory in it. However it has expansion slot, which
you can use for doubling the memory to 8Mb.
Anyway original poster was correct in his statement that Palm IIIxe doubles the memory of earlier Palm IIIx.