Tuesday, July 28, 2015
virtual machine prototype
To start I use VBoxManage startvm vmnamehere
I have the base os installed
installed ssh server
now working on authentication...
looking at aptitude log to find packages...
ldap-auth-client
ldap-auth-config
auth-client-config
libnss-ldap
libpam-ldap
nscd
[INSTALL, DEPENDENCIES] libgssrpc4:amd64
[INSTALL, DEPENDENCIES] libkadm5clnt-mit9:amd64
[INSTALL, DEPENDENCIES] libkadm5srv-mit9:amd64
[INSTALL, DEPENDENCIES] libkdb5-7:amd64
[INSTALL] krb5-config:amd64
[INSTALL] krb5-user:amd64
[INSTALL, DEPENDENCIES] libxcrypt1:amd64
[INSTALL] libpam-krb5:amd64
[INSTALL] libpam-unix2:amd64
skipping the install config, I am going to copy the config files that are working
ldap.conf
krb5.conf
nsswitch.conf
stopped/started nscd and the authentication piece looks ok
now test a few more things, and then the prototype should be ok
need to set up fstab...
I think I'm mostly done. Time to start working on www
shutting down the prototype
cloning
changing the ip address to 44 for now
changing the mac address
migrating
Moving to command line mode
http://community.linuxmint.com/tutorial/view/460
Installing apache2
now mediawiki
.. for some reason it wants a running postgresql
.. now to find the config stuff
virtual machines
I'm going to try using virtual machines for most of the boxes, so I'm setting a prototype first.
TODO:
request bios passwords
set intel vt for direct io on
enable remote wake up
1. Set the network device to bridged so I can statically assign ip
2. Upgrade packages
2a. I'm not confident the upgrade was fully effective, so I'm going to start over on the virtual image
3. Setting up the authentication via libpam/libnss
Setting up the file server
This will be a physical only machine
Need to migrate a disk over for additional space
Will set up another machine is capable as taking over, in the mean time though it will run a virtual machine(s) to support other things.
1. updating
2. changing to text boot
3. adding ssh
4. adding btrfs
5. changing /home to btrfs
update:
The file server is setup and operational
TODO:
request bios passwords
set intel vt for direct io on
enable remote wake up
1. Set the network device to bridged so I can statically assign ip
2. Upgrade packages
2a. I'm not confident the upgrade was fully effective, so I'm going to start over on the virtual image
3. Setting up the authentication via libpam/libnss
Setting up the file server
This will be a physical only machine
Need to migrate a disk over for additional space
Will set up another machine is capable as taking over, in the mean time though it will run a virtual machine(s) to support other things.
1. updating
2. changing to text boot
3. adding ssh
4. adding btrfs
5. changing /home to btrfs
update:
The file server is setup and operational
Thursday, June 04, 2015
opensuse 13.2 / sssd
I've tried before, with some trouble getting the authentication to work correctly. Trying again.
Installing a fresh copy of 13.2 on a project room machine
Install complete, going into yast to configure network and set up nfs mounting, need to work on wireless connectivity also
setting up the wireless password, it is stored in /etc/sysconfig/network/ifcfg-w.... whatever the device is
wireless working, networking ok,
nfs up, had to delete the usr/local btrfs subvolume... perhaps reconsider mounting /usr/local...
now kerberos
trying yast under user authentication, it seems to be at least installing the right packages for me
yuck..., sssd is not something that is working for me, and there is no clear path to fix it... (I had started this a few days ago, but had left it as a draft...)
mint / nscd
So, I've been trying mint and so far not too bad. The gui is a bit different and my ubuntu/debian is rusty, but it is coming back.
One headache I had forgotten about is nscd, it caches data, so when you make changes to the authentication system it helpfully returns the old data. blah. I spent a couple hours re-learning that lesson. On the bright side, it looks like mint will work out.
This page was useful
http://www.openldap.org/lists/openldap-technical/201403/msg00107.html
Monday, March 02, 2015
hard drives
In Ausable 309 on Friday we swapped drives between 157 and 158 to verify that the one in 158 was bad. It was. Strangely enough, when trying to boot 158 later, it gave an out of memory error in grub. I installed another copy of the OS, and grub was then happy.
In Ausable 113, this morning 104 was showing hard drive problems. I fsck'ed it, and it boots now, but it probably needs to be reimaged.
Subscribe to:
Posts (Atom)