Re: Plan for F22 KDE updates after F23 release?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Am 04.10.2015 um 06:18 schrieb Eric Griffith:
On Oct 3, 2015 18:35, "Reindl Harald" <h.reindl@xxxxxxxxxxxxx
 > that only works for users just browsing the web, reading some emails
and using a random instant messenger - not if you *really* use your computer

Off the high horse. You're not elite or special just because you
customize things.

i am just tired of the "in case of troubles just install from scratch"-attitude as the holy grail to solve problems when it's coming from users with 5-minutes setups where i live-CD with a external USB disk as storage would be enough for most cases

 > for me it takes 3-4 days to get configurations and customizations
back to a fresh install, besides i am responsible for around 35 Fedora
installs which would mean 105 days of work - that would be finally a
half release cycle

I can't image how many changes you make to a default install to require
3-4 days o.O

well, than you can't imagine complex network / testserver / development setups with a cloned and mirrored setup on two locations of people doing 5 fulltime jobs...........
___________________________

Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/md1       ext4   29G  7.0G   22G  25% /
/dev/md0       ext4  485M   55M  426M  12% /boot
/dev/md2       ext4  3.6T  1.9T  1.7T  53% /tmp

/dev/md0:
        Version : 1.0
  Creation Time : Wed Jun  8 13:10:48 2011
     Raid Level : raid1
     Array Size : 511988 (500.07 MiB 524.28 MB)
  Used Dev Size : 511988 (500.07 MiB 524.28 MB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Sun Oct  4 01:31:03 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

Name : localhost.localdomain:0 (local to host localhost.localdomain)
           UUID : 1d691642:baed26df:1d197496:4fb00ff8
         Events : 922

    Number   Major   Minor   RaidDevice State
       0       8       49        0      active sync   /dev/sdd1
       5       8       33        1      active sync   /dev/sdc1
       4       8        1        2      active sync   /dev/sda1
       6       8       17        3      active sync   /dev/sdb1
---------------------------------------------------------------------------------
/dev/md1:
        Version : 1.1
  Creation Time : Wed Jun  8 13:10:52 2011
     Raid Level : raid10
     Array Size : 30716928 (29.29 GiB 31.45 GB)
  Used Dev Size : 15358464 (14.65 GiB 15.73 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sun Oct  4 10:51:20 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : near=2
     Chunk Size : 512K

Name : localhost.localdomain:1 (local to host localhost.localdomain)
           UUID : b7475879:c95d9a47:c5043c02:0c5ae720
         Events : 20084

    Number   Major   Minor   RaidDevice State
       0       8       50        0      active sync set-A   /dev/sdd2
       5       8       34        1      active sync set-B   /dev/sdc2
       4       8        2        2      active sync set-A   /dev/sda2
       6       8       18        3      active sync set-B   /dev/sdb2
---------------------------------------------------------------------------------
/dev/md2:
        Version : 1.1
  Creation Time : Wed Jun  8 13:10:56 2011
     Raid Level : raid10
     Array Size : 3875222528 (3695.70 GiB 3968.23 GB)
  Used Dev Size : 1937611264 (1847.85 GiB 1984.11 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sun Oct  4 04:00:51 2015
          State : active
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : near=2
     Chunk Size : 512K

Name : localhost.localdomain:2 (local to host localhost.localdomain)
           UUID : ea253255:cb915401:f32794ad:ce0fe396
         Events : 1297383

    Number   Major   Minor   RaidDevice State
       0       8       51        0      active sync set-A   /dev/sdd3
       5       8       35        1      active sync set-B   /dev/sdc3
       4       8        3        2      active sync set-A   /dev/sda3
       6       8       19        3      active sync set-B   /dev/sdb3
---------------------------------------------------------------------------------
Personalities : [raid10] [raid1]
md2 : active raid10 sdb3[6] sda3[4] sdd3[0] sdc3[5]
      3875222528 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
      bitmap: 4/29 pages [16KB], 65536KB chunk

md1 : active raid10 sdb2[6] sda2[4] sdd2[0] sdc2[5]
      30716928 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md0 : active raid1 sdb1[6] sda1[4] sdd1[0] sdc1[5]
      511988 blocks super 1.0 [4/4] [UUUU]

unused devices: <none>
---------------------------------------------------------------------------------
___________________________

/usr/bin/netstat -u -t -l | wc -l
388
___________________________

/usr/sbin/iptables --list --numeric --verbose | wc -l
1500
___________________________

br-guest: flags=67<UP,BROADCAST,RUNNING> mtu 1500
inet 192.168.10.1 netmask 255.255.255.0 broadcast 192.168.10.255
ether 28:10:7b:ca:be:52 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-lan: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST> mtu 1500
inet 192.168.2.2 netmask 255.255.255.0 broadcast 192.168.2.255
ether 28:10:7b:ca:be:51 txqueuelen 0 (Ethernet)
RX packets 98246 bytes 38137395 (36.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 88602 bytes 95382215 (90.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

br-wan: flags=67<UP,BROADCAST,RUNNING> mtu 1500
inet *** netmask 255.255.255.0 broadcast 255.255.255.255
ether 00:50:8d:b5:cc:de txqueuelen 0 (Ethernet)
RX packets 30942340 bytes 16917315819 (15.7 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9653778 bytes 5392391601 (5.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lan-guest: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ac:16:2d:a1:74:ec txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7980000-f79fffff

lan-phone: flags=67<UP,BROADCAST,RUNNING> mtu 1500
ether ac:16:2d:a1:74:ef txqueuelen 1000 (Ethernet)
RX packets 30263 bytes 4638478 (4.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18584 bytes 5417664 (5.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7800000-f787ffff

lan-spare: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ac:16:2d:a1:74:ed txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7900000-f797ffff

lan-tv: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ac:16:2d:a1:74:ee txqueuelen 1000 (Ethernet)
RX packets 1615 bytes 318635 (311.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6266 bytes 1047090 (1022.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7880000-f78fffff

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 0 (Lokale Schleife)
RX packets 1849151 bytes 488603436 (465.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1849151 bytes 488603436 (465.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmnet1: flags=67<UP,BROADCAST,RUNNING> mtu 1500
ether 00:50:56:c0:00:01 txqueuelen 1000 (Ethernet)
RX packets 122387 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 16067305 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.196.2 netmask 255.255.255.0 broadcast 192.168.196.255
ether 00:50:56:c0:00:08 txqueuelen 1000 (Ethernet)
RX packets 4177935 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8242146 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vpn-client: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1472
inet **** netmask 255.255.255.0 broadcast 10.0.0.255
ether ca:4e:dd:1e:0c:b3 txqueuelen 100 (Ethernet)
RX packets 11596618 bytes 11890829528 (11.0 GiB)
RX errors 0 dropped 71133 overruns 0 frame 0
TX packets 7260877 bytes 537925416 (513.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vpn-server: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 192.168.11.1 netmask 255.255.255.255 destination 192.168.11.2
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wan: flags=67<UP,BROADCAST,RUNNING> mtu 1500
ether 24:be:05:1a:c0:27 txqueuelen 100 (Ethernet)
RX packets 31334579 bytes 17691695681 (16.4 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11496591 bytes 5562580615 (5.1 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7c00000-f7c20000

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 28:10:7b:ca:be:51 txqueuelen 50 (Ethernet)
RX packets 66356 bytes 34555486 (32.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 100630 bytes 94422191 (90.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan1: flags=67<UP,BROADCAST,RUNNING> mtu 1500
ether 28:10:7b:ca:be:52 txqueuelen 50 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


And if you're really maintaining 30+ computers then why aren't you using
kickstart files and centralized configuration management? That right
there would cut down most of the downtime, if it would ever be needed.

because that computers need to be online 365/24 and host services?

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org

[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux