[SOLVED] Validating F 17-64 live desktop.iso

[jeb3121]

Hi All,

I'm running F 16-64 live desktop on a dual-core AMD 7550 with 4G RAM and a separate 300G drive for linux.

My rationale for running the live version is that I'd rather install apps when I want them. My use is a pretty basic emigration from XP and I'm still not very far up the learning curve.

I validated F 16 in windows but decided to do F 17 in linux

The example in 3.4.*Validating in Linux is:
$ cd Downloads
$ sha256sum Fedora-17-i386-DVD.iso

I assume my 2nd line will be:
sha256sum Fedora-17-x86_64-Live-Desktop.iso
which has the complete name of the downloaded file.

However I searched Add/Remove Software for sha256sum and drew a blank. Nor could I find anything in Admin Tools that seemed to be what I need.

I probably just need a name for the hash program. Or a command line to d/l it

I assume it'll be useable for future upgrades as well.

Another question is about the example is that it doesn't require the root user(symbol #); why is that?

jeb

[smr54]

If you mean from a Fedora install, the way to find out what package provides a command is

yum provides */commandname

So, in this case

yum provides */sha256sum

We find that it's actually in the coreutils package.

coreutils-8.15-6.fc17.x86_64 : A set of basic GNU tools commonly used in shell
: scripts
Repo : fedora
Matched from:
Filename : /usr/bin/sha256sum

[DBelton]

Also, this link tells you just about everything you need to know

https://fedoraproject.org/en/verify

[jeb3121]

Originally Posted by smr54

If you mean from a Fedora install, the way to find out what package provides a command is

yum provides */commandname

So, in this case

yum provides */sha256sum

We find that it's actually in the coreutils package.

coreutils-8.15-6.fc17.x86_64 : A set of basic GNU tools commonly used in shell
: scripts
Repo : fedora
Matched from:
Filename : /usr/bin/sha256sum

Thank you. I ran:
sha256sum Fedora-17-x86_64-Live-Desktop.iso

then matched the hash at https://fedoraproject.org/en/verify

Now to burn the CD

Thanks again to you and DBelton for your help

Next problem:
I'd like to know which items are in the coreutils. Since yum seems to be dl/install would: yum coreutils-8.15-6.fc17.x86_64 put it where I can access it?

If not where can I find a list of coreutils contents?

jeb

[DBelton]

Here is the page for coreutils. you can probably find most of your answers there.

http://www.gnu.org/software/coreutils/

To install coreutils:

yum install coreutils

[jeb3121]

Quote: Here is the page for coreutils. you can probably find most of your answers there.

http://www.gnu.org/software/coreutils/

To install coreutils:

yum install coreutils
end Quote

Hi,

I yummed coreutils but I don't know where it went. I don't find it in Downloads and even when I use root I still can't find usr or bin.

The install seems to be for F 16 from what I see in the terminal which is reasonable since that's the current version.

What I'd like is someplace where I could find something like:
coreutils
sha256sum determine hash for specified software

jeb

[smr54]

rpm -ql coreutils|grep bin

will show you what commands are in it.

The q is for query, l is for list (a lower case L, not the numeral one). Running it as I show above, with the pipe key | and then grep bin will show what is in /usr/bin or /usr/sbin. (Otherwise, you get a complete list of everything it installs such as whatever files it might put in /etc, /lib, /usr/share/man, and so on.)

[jeb3121]

Originally Posted by smr54

rpm -ql coreutils|grep bin

will show you what commands are in it.

The q is for query, l is for list (a lower case L, not the numeral one). Running it as I show above, with the pipe key | and then grep bin will show what is in /usr/bin or /usr/sbin. (Otherwise, you get a complete list of everything it installs such as whatever files it might put in /etc, /lib, /usr/share/man, and so on.)

Thanks again. Combined with the titles in the coreutils directory, I should be able to sort it out.

jeb

[smr54]

If you want to mark any thread that you've started as solved, you can click the thread tools link at the top--that should give you the option to mark it solve.d