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.
Pages: [1]
1
Installation and Upgrades / Re: Q: SAMBA Roaming Profile and how to change fileshare folder location & names
« on: February 01, 2008, 09:53:10 pm »
I second the elimination of the underscore. I, too, have modified my smb.conf.mas file and eliminated the underscore.
But I suspect that the underscore's there to eliminate any potential for sharename conflicts.
For instance, someone unknowingly creates a group named ebox-internal-backups the share will be _ebox-internal-backups and will not conflict with the predefined share of the same name.
But I suspect that the underscore's there to eliminate any potential for sharename conflicts.
For instance, someone unknowingly creates a group named ebox-internal-backups the share will be _ebox-internal-backups and will not conflict with the predefined share of the same name.
2
Installation and Upgrades / Re: System Updates vs. System Components
« on: February 01, 2008, 09:47:19 pm »
What's the relationship between Ebox Components and System Updates? Are they the same thing? What are their dependencies on each other?
Documentation (below) doesn't seem to make this very clear... I see that System updates are the Debian packages installed on the ebox box. But aren't the ebox components also based on the debian ebox packages?
6.2. eBox components
At Software → eBox components you can install, upgrade or remove different existing eBox packages. Some packages won't be uninstalled, so these are needed for eBox correct working.
6.3. System updates
You can manage the software at the system where eBox is installed with the same ease as components management.
Documentation (below) doesn't seem to make this very clear... I see that System updates are the Debian packages installed on the ebox box. But aren't the ebox components also based on the debian ebox packages?
6.2. eBox components
At Software → eBox components you can install, upgrade or remove different existing eBox packages. Some packages won't be uninstalled, so these are needed for eBox correct working.
6.3. System updates
You can manage the software at the system where eBox is installed with the same ease as components management.
3
Installation and Upgrades / System Updates vs. System Components
« on: January 30, 2008, 10:33:21 pm »
I have a 0.9.99 version that I'd like to upgrade to 0.11.99 with minimal problems.
What do I need to do in order to upgrade?
System Updates or System Components? Both?
Recommended Order? What could get broken if I do both?
I've also made some manual changes to some conf.mas files as well and want to make sure I retain those, too. Is there signifcant changes in the squid.conf.mas, dansguardian.conf.mas and smb.conf.mas files between these versions that I won't be able to just use the ones I have from 0.9.99?
Below is what I'm getting listed in System Updates and System Components
System Updates:
OpenVPN server 0.9.99 0.11.99
Certificate Authority Manager for eBox 0.9.99 0.11.99
SOAP server to communicate with eBox control center none 0.11.99
eBox control center to control several eBoxes at the same time none 0.11
Network configuration 0.9.99 0.11.99
DHCP server 0.9.99 0.11.99
Mail filter module 0.9.99 0.11.99
Instant messaging (Jabber) 0.9.99 0.11.99
Web Server none 0.11.99
Base framework 0.9.99 0.11.99
Mail server 0.9.99 0.11.99
eBox DNS server 0.9.99 0.11.99
Traffic shaper for eBox 0.9.99 0.11.99
NTP server 0.9.99 0.11.99
Software management 0.9.99 0.11.99
User and Group management 0.9.99 0.11.99
File sharing 0.9.99 0.11.99
Object management 0.9.99 0.11.99
Proxy cache and content filter 0.9.99 0.11.99
Printer sharing 0.9.99 0.11.99
Services management none 0.11.99
Firewall 0.9.99 0.11.99
System components:
bind9 Internet Domain Name Server
libisccc0 Command Channel Library used by BIND
bind9-host Version of 'host' bundled with BIND 9.X
apache-common support files for all Apache webservers
clamav antivirus scanner for Unix
dnsutils Clients provided with BIND
esofttool ebox software tool
clamav-freshclam downloads clamav virus databases from the Internet
libdns16 DNS Shared Library used by BIND
apache-perl versatile, high-performance HTTP server with Perl support
clamav-base base package for clamav, an anti-virus utility for Unix
libebox eBox common library for server and client
libisccfg0 Config File Handling Library used by BIND
clamav-daemon antivirus scanner daemon
runit a UNIX init scheme with service supervision
liblwres1 Lightweight Resolver Library used by BIND
libapache-mod-perl integration of perl with the Apache web server
libisc7 ISC Shared Library used by BIND
What do I need to do in order to upgrade?
System Updates or System Components? Both?
Recommended Order? What could get broken if I do both?
I've also made some manual changes to some conf.mas files as well and want to make sure I retain those, too. Is there signifcant changes in the squid.conf.mas, dansguardian.conf.mas and smb.conf.mas files between these versions that I won't be able to just use the ones I have from 0.9.99?
Below is what I'm getting listed in System Updates and System Components
System Updates:
OpenVPN server 0.9.99 0.11.99
Certificate Authority Manager for eBox 0.9.99 0.11.99
SOAP server to communicate with eBox control center none 0.11.99
eBox control center to control several eBoxes at the same time none 0.11
Network configuration 0.9.99 0.11.99
DHCP server 0.9.99 0.11.99
Mail filter module 0.9.99 0.11.99
Instant messaging (Jabber) 0.9.99 0.11.99
Web Server none 0.11.99
Base framework 0.9.99 0.11.99
Mail server 0.9.99 0.11.99
eBox DNS server 0.9.99 0.11.99
Traffic shaper for eBox 0.9.99 0.11.99
NTP server 0.9.99 0.11.99
Software management 0.9.99 0.11.99
User and Group management 0.9.99 0.11.99
File sharing 0.9.99 0.11.99
Object management 0.9.99 0.11.99
Proxy cache and content filter 0.9.99 0.11.99
Printer sharing 0.9.99 0.11.99
Services management none 0.11.99
Firewall 0.9.99 0.11.99
System components:
bind9 Internet Domain Name Server
libisccc0 Command Channel Library used by BIND
bind9-host Version of 'host' bundled with BIND 9.X
apache-common support files for all Apache webservers
clamav antivirus scanner for Unix
dnsutils Clients provided with BIND
esofttool ebox software tool
clamav-freshclam downloads clamav virus databases from the Internet
libdns16 DNS Shared Library used by BIND
apache-perl versatile, high-performance HTTP server with Perl support
clamav-base base package for clamav, an anti-virus utility for Unix
libebox eBox common library for server and client
libisccfg0 Config File Handling Library used by BIND
clamav-daemon antivirus scanner daemon
runit a UNIX init scheme with service supervision
liblwres1 Lightweight Resolver Library used by BIND
libapache-mod-perl integration of perl with the Apache web server
libisc7 ISC Shared Library used by BIND
Pages: [1]