Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Saturn2888

Pages: 1 2 [3] 4 5 ... 36
I remember now, I had to move the files for scriptaculous into some eBox folder. I can't find where that is though.

Zentyal 2.0.1 upgraded from eBox 1.4.9

When I check the Users and Groups box in Modules, it freezes Zentyal. I had this problem before in the betas and someone said some kinda scriptuous or scriptus thing needed to be installed.

News and Announcements / Re: Zentyal 2.0-rc2 released!
« on: August 29, 2010, 02:36:05 pm »
Is there an address to the repo or just change 1.5 to 2.0 as usual?

News and Announcements / Re: Zentyal 2.0 release party!
« on: August 29, 2010, 02:32:24 pm »
I'm up for pictures of the event.

Installation and Upgrades / Re: Getting eBox to work on ARM
« on: August 09, 2010, 02:01:29 am »
Those aren't ARM though. These should be topics for another thread.

Installation and Upgrades / Re: Getting eBox to work on ARM
« on: August 08, 2010, 03:36:13 am »
I don't know what the verdict is. That's what I'm looking at myself actually; the Plus edition.

Ok thanks.

1.4.9. I went to an older snapshot, found the /etc/samba folder and restored it, restarted Samba, it's working; but eBox Samba is still stopped. It stopped working a few days ago but no one noticed because it was the weekend. That explains why I was having trouble w/ it over VPN.

Windows 7 for all clients. One of them it was on Vista and was newly upgraded to 7 so I had to run that reg fix, but it just had a ton of trouble. Actually restarting the eBox service messed it up more so I don't know what to do in that case. It was definitely working in 1.4.8, but when I upgraded my LDAP server to 1.5.8, I had to redo LDAP and re-setup this slave machine with LDAP so I don't know if that screwed it up or not. eBox Samba wasn't running after that on 1.4.8, but people were still able to connect.

Error (login): The trust relationship between this workstation and the primary domain failed.  (1789)
All of my clients are getting this error trying to login to the domain now. I don't know what to do. I tried setting up another machine as the PDC while this service isn't working, but that's not fixing anything. I don't know why it's not starting the service on the slave.

It's apparently already installed and upgraded which is strange. I'm glad there's a manual solution though.

Installation and Upgrades / Re: eBox package dependency list
« on: July 28, 2010, 04:58:31 pm »
eBox on ARM is going to be my next challenge. I'm gonna somehow get a hold of Ubuntu Lucid for ARM and run it in Qemu to see what happens. If anyone know where I can get these materials, I'll go ahead and try it.

The whole OpenWrt thing is sadly not going to pan out. I like eBox and am familiar with it. In comparison, OpenWrt uses up at most, 13MB of space to emulate most all of eBox's current functionality. It boots into memory so it would work great off a cheapo 64MB USB drive you have laying around, and will kinda sorta do exactly what you want. Might I mention it's an extremely fast interface that just loads everything instantly.

The problem is, it's not all interconnected, not everything is as easy to use as eBox, and who knows what features it's lacking. It's much easier to maintain and manage though because all you have to do is modify config files if you can't work with the interface instead of having no way of really backing up your eBox configuration in any portable manner. opkg isn't nearly as good or vibrant as aptitute, the repos are lacking some of my favorite CLI programs, and both cpan and cpanplus are heavily broken if I wanted to run perl scripts. That also rules out trying to fudge eBox on OpenWrt instead of Ubuntu, haha.

Personally, I prefer web interfaces that directly work with and manage config files because all of the functionality you could do without the interface you could do with it. There are always some limitations, but I think BackupPC is by far the best at giving you a fully-featured WUI which is basically just the config file in a nice wrapper. If eBox included a SysAdmin interface like that, I think I'd be overjoyed.

I like to play around w/ operating systems as if they were toys. Since OpenWrt doesn't work for me, eBox on ARM might. I'll constantly be looking for ways to lower my power usage whether that means going Atom or going ARM. ARM is going to be more restrictive and harder to configure, but it's surely going to be a lot more fun in the long run and something to brag about. The only way I can think Atom would come in handy is if all my servers became Atom servers (hopefully processors with VT), and I figure out a way to cluster them together, run them in an OS-level VM, and be happy everything is super portable. I mean, eBox in a VM means, if it goes down, just start up another one from an earlier snapshot. Lots of things to try, but OpenWrt is definitely out of the picture now.

Yeah, I like that. I think that's the future of eBox since it's starting to rely more heavily on LDAP. Now, how is PAM different than NSS? Or is PAM the Password Manager for NSS?

I have had this issue for quote some time and haven't thought much about it, but today it finally became an annoyance when trying to SSH.

:: BUG ::
The DNS server, when in dynamic mode, does not resolve itself. I cannot type in ebox.local instead of and have it resolve yet it resolves everything else.

It's straight-forward to put LDAP in Apache2 so BackupPC uses it but I've yet to actually accomplish that. I'm still working on getting HTTPS working too. This is just stuff I have completely no experience with and think if eBox is trying to unify all of these modules, that might be a next step since I'm not stupid, but I sure haven't figured it out either.

What's NSS anyway and how does it relate to what we've been talking about?

Pages: 1 2 [3] 4 5 ... 36