2,411
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 166:
Line 166: − + − + − + − + Line 183:
Line 183: − + − + − +
Commented out dead links (due to private setting of old SF bugtracker), reworked links to current bugtracker
*Why is there a delay after verifying administrator password?
*Why is there a delay after verifying administrator password?
On "slow" system, there is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions.
On "slow" system, there is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions.
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1264659&group_id=96750]]
<!--[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1264659&group_id=96750]]-->
*Use /server-manager, not /e-smith-manager
*Use /server-manager, not /e-smith-manager
In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager.
In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager.
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1275334&group_id=96750]]
<!--[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1275334&group_id=96750]]-->
*Why can the system not be named 'mail', 'ftp' or 'www'?
*Why can the system not be named 'mail', 'ftp' or 'www'?
If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. See these bug listings for details:
If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. <!--See these bug listings for details:
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1223012&group_id=96750]] [[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1264588&group_id=96750
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1223012&group_id=96750]] [[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1264588&group_id=96750 -->
This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method.
This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method.
Additionally, the kernel has grown too large for a floppy plus initrd. Even Redhat installs no longer offer to create a boot floppy at install time.
Additionally, the kernel has grown too large for a floppy plus initrd. Even Redhat installs no longer offer to create a boot floppy at install time.
More details can be found in [[Bugzilla:792]].
More details can be found in [[bugzilla:792]].
*4 disk install - md1 is raid1 and md2 is raid5
*4 disk install - md1 is raid1 and md2 is raid5
Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected.
Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected.
More information can be found in [[Bugzilla:759]].
More information can be found in [[bugzilla:759]].
*Anaconda crash from rescue mode when starting network interfaces
*Anaconda crash from rescue mode when starting network interfaces
There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon. Note however that this is no longer an issue with version 7.2. [[Bugzilla:712]]
There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon. Note however that this is no longer an issue with version 7.2. [[bugzilla:712]]
