Ubuntu Utah

, order viagra online, ultram er, depakote, about phentermine, cialis and zoloft delayed ejaculation alternatives,

here are the notes I took during the meeting. They are mostly what he wrote on the board so hopefully they will help with the video in understanding what he was discussing on the board.

Summary

1.Bios
a.Post
i. CPU
ii. RAM
iii.Output
iv. Input
v.Bootable Device
2.MBR
a.512 bytes total
i. first 446 is the IPL
ii.next 64 bytes
iii.2 byte closing
b.(hd0,1) is drive 1, partition 2
c.drive 6, part 2 is (hd5,1)
d.in the newest versions of Linux no more hd, all is sd devices
e.initrd.img is the initial ramdisk that is 7 x kernel size, and initrd.img includes most of the rudimentary drivers for items such as drives etc.
3.Kernel - kernel /boot/vmlinuz-2.6.22-14-generic
a.initrd initrd /boot/initrd.img-2.6.22-14
4.INIT
a.mount / as rw where it was ro previously
b.ps -ef | grep init ---- gives parent process as second line
c.pstree | less ----- shows process tree
d.init cannot be killed and is protected
i.on a debian box – execute rcS to start things
ii.runs K scripts then S scripts
iii.sysv-rc-conf --list ---> shows the runlevel for each
iv.sys-rc-conf –levels 345 bitlbee on
v.runlevel ----> show previous and current runlevels
vi.telinit # --- changes runlevel
vii.who -r ---> shows the runlevels and time entered
viii.S scripts are symbolic links to the init.d directory and the S and K sends either start or stop respectively
e.last thing it does is mounts the filesystem rw
f./etc/rc2.d/S99rc.local ---> file to put things starting up automatically, one of the final steps and can be customized to suit your needs
5.ttys
6.X11

Redhat/Fedora/Centos Runlevels

emergency
s, S, single
1 – single user mode
2 – multiuser mode without nfs
3 – multiuser mode with nfs
4 - N/A
5 – multiuser w/ GUI
6 – reboot
0 - HALT

Debian Based systems
emergency
s, S, single
1 – single user mode
2 – multiuser w/ GUI
3 – multiuser w/ GUI
4 – multiuser w/ GUI
5 – multiuser w/ GUI
6 – reboot
0 - HALT

booting with a single after the kernel line to boot to single mode to get root access boots to single mode command prompt as root

PROTECT GRUB

grub-md5 crypt
creates a password for the grub

then paste it into the first line of the grub
password –md5 @$##@$#$%#$%$#%#$%$#%$#

PROTECT BOOT OFF OF BOOTABLE MEDIA

PASSWORD PROTECT BIOS – and set no additional boot devices

PHYSICALLY PROTECT THE BOX

SYSTEM V inittab
can change default runlevel to 6 or 0 to hose the machine

Upstart is the alternate to SYSTEMV init

TO REMOUNT THE FILESYSTEM TO FIX IS
mount -o remount,rw /
to remount the filesystem to fix errors

the formatting here is messy, so if you want the open office version email me at bmac2@maildragon.com and ask and I can email you the original.

I always thought of the boot-up as a magic system that just got the machine up to speed and running. I was wrong, I didn't realize I had that much power over my system from the pressing of the power button, to the log in prompt. I've always seen it as a black box, Don't know how it really works, didn't care ow it worked as long as it works.

Now that I know, I going to have to look more into this. I'd rather not mess with it if it works. But if I have to its good to know.

All and all I'm glad this was my first meeting and the subject matter while a bit heavy for this Ubuntu/Linux newbie it gives me a good idea on whats going on and what to look into in the near future, maybe even to further secure my Box.

Since my rig is a home unit with little if any private info on it. No real need, I said so once before already today, "Better to have it and not need it then to need it and not have it..."

Thanks guys... Good lesson, Look forward to the next meeting...