Results 21 to 25 of 25
I was a System 38 operator and we got a new toy - a Vax. It was an Unix based machine which none of us really new anything about. In ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-03-2013 #21
At the time and for a long time afterwards I wondered why it would allow such a thing to happen but these days I get it. I actually understand and approve of the philosophy which Doug Gwyn expresses beautifully.Originally Posted by Doug Gwyn"I used to be with it, then they changed what it was.
Now what was it isn't it, and what is it is weird and scary to me.
It'll happen to you too."
The Fifth Continent
- 08-04-2013 #22
- Join Date
- May 2013
When you delete the spell checker, you expect to delete only the spell checker (as you have installed it), rather than deleting all the Office Packages + Nautilus + the whole graphical desktop + half of the OS
yum history info <the selected number>
yum history undo <the correct number>
- 08-04-2013 #23
RE: If you have not removed essential system files
... and disabled essential system services, upon which the system becomes damaged beyond recovery.
This is the point. Which are these essential system packages and system services, the deletion of which or disabling respectively will bring the system to a state of beyond recorvery. How can an observer distinguish between system and non-system packages.
RE: the deletion of gcc
gcc is not critically fatal to the system. It is fatal to the package installer (to compile from source), but one can restore the system on the grounds of rpm packages, for example.
- 08-04-2013 #24
- Join Date
- May 2013
How can an observer distinguish between system and non-system packages.
As you mention, gcc is not a critical program for the system to run, unlike glibc discussed above. If you try and create your own bootdisks, that is, CDs that will boot a linux system, you will find that such systems don't actually need very much to boot and run. When I was creating these disks all I needed was a kernel and a root filesystem that had a version of glibc installed in a linux filesystem which included the directories /etc /bin /dev /lib /proc and /tmp I think. You just need a few tools to manipulate files for which a progam called busybox was good (it's a single program that has lots of dressed down versions of cp, rm, mount etc) and a bootloader like syslinux. There's a bootdisk HOWTO if you want to get into it. My point, I suppose is that it was by experience that I learnt what is essential to a linux system, which is possibly not the answer to your question that an inexperienced user might want to hear.
- 08-04-2013 #25
RE: ... in the context of the original problem
The idea was for the OS to have somewhere expert knowledge about the minimum set of services, for example, for it to operate properly.
Some list: rsyslog, messagebus ... udev-post
and in the very moment in which the user tries to disable udev-post for example, a message to be issued:
***** Fatal Settings Error ***** Disabling this service will leave the kernel without devices upon boot & the OS will be damaged? Do you know how to run udev from the grub?