My Sunday (or the Chronicles of a Linux Install)

My morning

My morning

The box onto which Linux is to be installed

The box onto which Linux is to be installed

dustpuppy's internals

dustpuppy's internals

Shared console

Shared console

The new IBM Model M keyboard

The new IBM Model M keyboard

Linux installs are fun

Linux installs are fun

First cup of coffee

First cup of coffee

Second cup of coffee

Second cup of coffee

Lunch

Lunch

After six hours of work, CentOS 5.5 is finally copying files

After six hours of work, CentOS 5.5 is finally copying files

About these ads
  1. #1 by Andrew D. on February 6, 2011 - 11:19 PM

    What was unique about this installation that it took 6 hours to get CentOS installed? I don’t remember my former server taking that long.

    • #2 by Joshua on February 7, 2011 - 5:46 AM

      I needed to duplicate a filesystem layout on different hardware. Well, I had LVM on top of RAID-5 and now I needed to do straight RAID-5 so I needed to make partitions for mdraid, meaning I had to do the division (by 3). Then I had to build the metadevices with the correct paritions for each filesystem.

      I also have only a single working DVD burner and a single working DVD reader :-(

      So yeah, it was mostly just minor crap holding me up all morning. That and I had to copy the entire filesystem off to external disk and then copy parts of it back after the system was installed.

    • #3 by Joshua on February 7, 2011 - 7:10 AM

      And it took more like 12 hours, actually. Most of that was spent waiting for dump/restore and looking for working CD/DVD drives. The actual install (including laying out 16 filesystems and doing the RAID-5 partition size calculations and metadevice composition commands by hand) took about 2 hours. A 3TB array takes just a bit of time to resync afterwards also, during which time I didn’t want to bug the machine – a reboot in the middle of a software RAID-5 rebuild could doom the entire array.

      • #4 by Joshua on February 7, 2011 - 7:12 AM

        And you try dumping 1T of an ext3fs filesystem off to USB 1.1 disk. It’s not quick. :P

    • #5 by Joshua on February 7, 2011 - 7:15 AM

      Thanks for phrasing that that way, BTW. You could’ve easily just said “WTF? Are you stupid? How did it take you 6 hours?” But you immediately went for the classier “What was unique about this setup?” :-)

      But a big part of it was lack of planning on my part. I forgot that (a) the BIOS in that box is too old to boot from USB drive and (b) I had only one working DVD-ROM drive that that was in my mom’s box. (The working DVD burner is in my Alienware and I’m not touching that box. I paid $2600 for it and I aim to keep it working perfectly for a very long time – that means minimizing stress on connectors and minimizing the risk of bumping components and such.)

      • #6 by Andrew D. on February 7, 2011 - 2:13 PM

        Had this been some random person on the internet, I might have said that, but I know you well enough to know that if something computer-related takes you a while, it’s very likely a complex issue. :D

        USB 1.1 ports make me a sad panda. We have a few on our old public/shared computers at work and it’s not fun to copy things on or off of there.

        • #7 by Joshua on February 7, 2011 - 2:19 PM

          It doesn’t help that this is the oldest box I own or that the CPU is purposely underclocked for stability because it’s not the most reliable thing ever.

  2. #8 by Joshua on February 7, 2011 - 8:04 AM

    I’m decaffeinating somewhat today after yesterday’s 6 cups of coffee + about 64oz of cola. I’m still a bit twitchy as it is. I only had one cup of coffee today so look for me to be pretty out of it by this afternoon/ :-)

    • #9 by Chadwick on February 7, 2011 - 12:40 PM

      Well clearly you just need a line of coke to smooth out the edges and get you through the day, yes?

      • #10 by Joshua on February 7, 2011 - 12:44 PM

        Heh. I’m good with decaffeinating. The headaches only happen if I go a few days without caffeine. Otherwise it’s just lethargy and lack of focus as I detoxify.

  3. #11 by Kevin Z. on February 8, 2011 - 3:39 PM

    How many hertz is DustPuppy’s CPU clocked at?

    • #12 by Joshua on February 8, 2011 - 4:03 PM

      1600 – supposed to be 1666. It’s an AthlonXP 2000+ but it shows up as a 1900+ because of underclocking:

      # cat /proc/cpuinfo
      processor       : 0
      vendor_id       : AuthenticAMD
      cpu family      : 6
      model           : 8
      model name      : AMD Athlon(tm) XP 1900+
      stepping        : 1
      cpu MHz         : 1597.667
      cache size      : 256 KB
      fdiv_bug        : no
      hlt_bug         : no
      f00f_bug        : no
      coma_bug        : no
      fpu             : yes
      fpu_exception   : yes
      cpuid level     : 1
      wp              : yes
      flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up nonstop_tsc ts
      bogomips        : 3195.33
      
  4. #13 by Joshua on February 8, 2011 - 5:58 PM

    What I’ve been doing since then: Getting stuff moved back onto dustpuppy. Today: dovecot IMAP server and GNU mailman list manager. Here’s my current local SELinux policy:

    
    module local 1.0;
    
    require {
            type spamc_t;
            type semanage_t;
            type spamd_t;
            type fs_t;
            type sendmail_t;
            type file_t;
            type procmail_t;
            type var_log_t;
            type dovecot_t;
            type updpwd_t;
            class fifo_file write;
            class file { rename read lock create ioctl write getattr link unlink append };
            class dir { search write getattr remove_name add_name };
            class filesystem getattr;
    }
    
    #============= dovecot_t ==============
    allow dovecot_t file_t:dir { write remove_name search add_name };
    allow dovecot_t file_t:file { rename write getattr read lock create unlink };
    
    #============= procmail_t ==============
    allow procmail_t file_t:dir { write remove_name search getattr add_name };
    allow procmail_t file_t:file { read lock create write getattr link unlink append };
    allow procmail_t var_log_t:file append;
    
    #============= semanage_t ==============
    allow semanage_t file_t:dir getattr;
    allow semanage_t fs_t:filesystem getattr;
    
    #============= spamc_t ==============
    allow spamc_t sendmail_t:fifo_file write;
    allow spamc_t var_log_t:file append;
    
    #============= spamd_t ==============
    allow spamd_t file_t:dir { write search getattr add_name };
    allow spamd_t file_t:file { read getattr ioctl };
    
    #============= updpwd_t ==============
    allow updpwd_t fs_t:filesystem getattr;
    
    

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 48 other followers

%d bloggers like this: