Re: Licenses for 10.2?

David Bolt wrote:
Those can be faulty burned or can otherwise be useless.

That's where disc verification comes in. K3b will verify the burnt image
matches the original ISO image. Not sure about other GUI writers,
although growisofs doesn't. That's still easily remedied by asking
md5sum to produce a checksum for both the burnt image and the ISO. If
they don't match, burn a new copy and recheck.

I can perfectly make a useless and unbootable ISO that verifies
perfectly, just using makeSUSEdvd and a verified CD 1. Just buy the
boxed set and distribute the xml file over email and let people put that
on a floppy.

That way people do not have to burn anything. Have no need of anything
installed on the achine and so on.

That depends on how the installationis done. Leave it passwordless and
right after the first boot, have it download the real passwd file.

By adding a script to do it to /etc/rc.d/boot.local? That might work.
Add in a few checks to make sure the passwd and shadow files had really
been fetched and then delete itself if the have, or force a reboot if
they haven't.

No, by adding it to 'first boot'. After installation, you have a
'firstboot' option in YaST setup that completes the installation. What
you can do is remove the login and password stuff. Add the download of
the file right after the recognition of the Network card.

I am unsure how dangerous it would be to put the file on the CD and
just replace the rpm containing /etc/passwd

1) Buy a boxed set for each branch

They can't because the license forbids it. Each branch has to purchase a
copy.

Please re-read. I said to buy a boxed set FOR EACH BRANCH. That means
that each branch has to purchase a copy.

2) Download it

Same as 1.

No. Each branch can download their own openSUSE. With FTP, with
Bittorrent, with whatever.

Depends on the number of branches. A small number, and located close
together, is probably not too bad a method. Lots of branches, or where
they're large distances apart, may cause some problems.

Unless the branches have an IT person available who would need to do the
installation anyway. Bring them all together for a week for inhouse
training (You will need that) and include 1 afternoon installing
machines.

It would also depend on what timeframe you are talking about. It would
be best to have two systems running next to each other for a period of
time and do the transfer one by one.

Probably the easiest of the lot. Specify a minimal install specification
and leave the implementation to the local IT department. Yes it means
you don't end up with identical systems but, as long as they meet the
minimum specs, does it really matter?

Once the systems have been installed, you can take over and force them
to become identical. YaST, Network Services, Remote administration.
Or just do it over ssh.
#!/bin/bash
for MACHINE in `machine_list`
do
ssh -i ~/.ssh/ssh-key root@machine somescript_there
done

The first somescript_there would be a e.g.
wget -O /root/sbin/first_script ftp://example.com/first_script
That can contain all other scripts you might need (and remove itself)
Once you have that running, you will have an easy way of mainting as
much machines as you bandwith can handle.

That if all machines are directly accesible. If not, then you will need
to have at least one server that does the same in chain to all others.

It will take some scripting, but after a while updating one or 1.000
machines is the same.

Obviously you will need to think seriously about chown and chmod. As
almost everything can be done remotely, you can centralize much of your
IT. That leaves the need for clear structure and instruction to those

Also calculate in the fact that some IT personell will find it degrading
to not do those things anymore and the best will leave.

In a smaller company with say two-three branches I would say that this
should be an at least 6 months project. And that is after all lights are
green. Testing, looking what each department wants, needs and gets.
re-testing, small launch for a specific targeted and measurable group.
Get feedback, improve. Then do the smalles branch. Wait a months and if
they are still alive, do the next one.
Do the largest branch last.

Take a holiday for a month and leave you phone at home. When you come
back either everybody will kill you or, well, they will kill you anyway,
because nobody likes change.

houghi
--
At the source of every error which is blamed on the computer you will
find at least two human errors, including the error of blaming it on
the computer.
.

Relevant Pages

  • Re: Licenses for 10.2?
    ... That's where disc verification comes in. ... md5sum to produce a checksum for both the burnt image and the ISO. ... 'firstboot' option in YaST setup that completes the installation. ...
    (alt.os.linux.suse)
  • Re: Re:how to make an iso file with all the update , or integrate the into
    ... but there seems that nobody is adding the new updates to a new iso ... What you linked to was the download for Windows Xp Service Pack 3 ... It dod not include *all* the updates, ... your Windows Installation media. ...
    (microsoft.public.windowsupdate)
  • Re: Linux clients in network - experiences?
    ... as you're bound to buy more machines, deal with hardware failures, etc. ... can deal with installation, tough you may want to hack it so that most ... you'll need a secure channel to the install server (we use a dedicated ssh ... the Packages.gz lists that apt-get uses on "normal" ...
    (Debian-User)
  • Re: Software Update - Distribution Status; How is this reported back to SMS?
    ... For all new machines that are added to the network, ... office2003 sp2 pre-installed with SP2 before the advanced client is ... installed via Client Push Installation. ... The compliance reports indicate ...
    (microsoft.public.sms.admin)
  • Re: Problems with Email, cusmapi
    ... VFP ships with MAPI controls, ... Does MAPI get installed during the automatic installation of Outlook? ... line of code fails on the machine where the program fails and ... WOULD fail on those machines as well. ...
    (microsoft.public.fox.helpwanted)