Dear All ,
I have installed FreeBSD 7.2 amd64 RC1 from DVD .iso to test its
installation issues .
It detected hardware correctly and installed without any problems , but
during installation of the packages the following errors
occurred :
Add of package ...name of package... aborted , error code 1 :
apache-1.3.41
links-0.98,1
apache+mod_ssl-1.3.41+2.8.31
ghostscript7-nox11-7.07_20
emacs-22.3
Number of failed packages is significantly less than failed packages of
Release 7.1 amd64 installation .
Due to failed package installation , at the end Gnome in 7.1 Release and
Stable was unusable , at least because
terminal was not available in Gnome menus with nearly empty menus .
Other points may be the following :
(1) During user definition password confirmation is not asked but in root
password definition it is asked .
For the user , the same password entry box may be re-used for
password confirmation without changing
screen design because entered password is not plainly visible and
during password confirmation it is not necessary
to keep it there , and it does not require much work to include it .
( During installation of 7.1 , I carefully first recorded password on
paper , entered it , later it did not worked . )
(2) CD/DVD drive is NOT released when the message ... ( be sure to remove
any floppies/CDs/DVDs from the drives ) .
(3) When shutdown is selected from Gnome menu either by the first user or
the root , within displayed dialog box
there is no a Shutdown item .
It is necessary for the root open a terminal console , and enter
shutdown -p now command .
PC definition : Intel DG965WH main board with 2 GB memory , PS/2 mouse and
keyboard .
Installation Options : Starting FreeBSD menu : Default
Standard installation
Fresh install ( SATA II Disk cleared
before start of installation and all of the disk allocated )
Standard boot
Disk layout : Default
All distributions selected
All of the ports categories
containing all of the packages selected with the following categories
excluded
: accessibility ( entries selected on dependency )
chinese , ipv6 , japanese ,
korean , palm .
IPv6 : No
DHCP : Yes , Ethernet to ADSL router :
Yes , worked .
Gateway : No
iNetd and Network services : No
SSH login : No
FTP : No
NFS Server : No
NFS Client : No
Console Settings : No
Time zone setting : Yes
Mouse : Tested , Worked
Packages : Selected , Installed
User : Defined
Thank you very much
Mehmet Erol Sanliturk
On Sat, 2009-04-18 at 19:04 -0400, Mehmet Erol Sanliturk wrote: Thanks for the testing and feedback.> I have installed FreeBSD 7.2 amd64 RC1 from DVD .iso to test its > installation issues . > > It detected hardware correctly and installed without any problems , but > during installation of the packages the following errors > occurred : > > Add of package ...name of package... aborted , error code 1 : > > apache-1.3.41 > links-0.98,1 > apache+mod_ssl-1.3.41+2.8.31 > ghostscript7-nox11-7.07_20 > emacs-22.3 > > Number of failed packages is significantly less than failed packages of > Release 7.1 amd64 installation . > Due to failed package installation , at the end Gnome in 7.1 Release and > Stable was unusable , at least because > terminal was not available in Gnome menus with nearly empty menus .To be honest it never occured to me that someone would attempt to install all of the packages (or at least as many as you indicated in your summary that you did). The package failures you mention were almost certainly caused by conflicts (e.g. apache-1.3.41 and apache +mod_ssl-1.3.41+2.8.31 failing because apache-2.2.11_4 got installed first). When deciding what packages to include on the media as of late I haven't been taking the issue of possible conflicts into mind. Like I said I'm afraid it just never occured to me someone would just select "virtually all of them" as you did. I'll take this into consideration moving forward but just so you know it likely won't be addressed as part of 7.2-REL. It's likely you would need to be at least a little more selective in what packages you install if you want to avoid these sorts of package install failures caused by conflicts.> Other points may be the following : > > (1) During user definition password confirmation is not asked but in root > password definition it is asked . > For the user , the same password entry box may be re-used for > password confirmation without changing > screen design because entered password is not plainly visible and > during password confirmation it is not necessary > to keep it there , and it does not require much work to include it . > > ( During installation of 7.1 , I carefully first recorded password on > paper , entered it , later it did not worked . ) > > (2) CD/DVD drive is NOT released when the message ... ( be sure to remove > any floppies/CDs/DVDs from the drives ) .Those are both fixed in head (what will become 8.0). I chose to not MFC those changes because they rearrange questions which might throw off people who are used to the older behavior, it's best to phase in that sort of thing as part of a new branch.> (3) When shutdown is selected from Gnome menu either by the first user or > the root , within displayed dialog box > there is no a Shutdown item . > It is necessary for the root open a terminal console , and enter > shutdown -p now command .That one is a question for the Gnome folks but I *think* that's the intended behavior unless you configure the machine to launch the graphical interface as part of booting up. :-) -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090418/2ca0ed32/attachment.pgp
On Sat, 18 Apr 2009 19:04:26 -0400 Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> wrote:> (3) When shutdown is selected from Gnome menu either by the first > user or the root , within displayed dialog box > there is no a Shutdown item . > It is necessary for the root open a terminal console , and enter > shutdown -p now command .Have you installed sudo? I think those options (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is available. -- Bruce Cran
Bruce Cran wrote:> On Sat, 18 Apr 2009 19:04:26 -0400 > Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> wrote: > > > >> (3) When shutdown is selected from Gnome menu either by the first >> user or the root , within displayed dialog box >> there is no a Shutdown item . >> It is necessary for the root open a terminal console , and enter >> shutdown -p now command . >> > > Have you installed sudo? I think those options > (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is > available. > >Fact is you will get these options either if you have sudo and your user account is authorized to shutdown / reboot (this is the fallback method though) or if PolicyKit is configured (see /usr/local/etc/PolicyKit/PolicyKit.conf) to allow shutdown/reboot. Entries will look similar to these: <match action="org.freedesktop.hal.power-management.shutdown"> <match user="yourusername"> <return result="yes"/> </match> </match> <match action="org.freedesktop.hal.power-management.reboot"> <match user="yourusername"> <return result="yes"/> </match> </match> Have a look at http://www.freebsd.org/gnome/docs/halfaq.html for more HAL fun ;)
On Sat, Apr 18, 2009 at 8:09 PM, Bruce Cran <bruce@cran.org.uk> wrote:> On Sat, 18 Apr 2009 19:04:26 -0400 > Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> wrote: > > > > (3) When shutdown is selected from Gnome menu either by the first > > user or the root , within displayed dialog box > > there is no a Shutdown item . > > It is necessary for the root open a terminal console , and enter > > shutdown -p now command . > > Have you installed sudo? I think those options > (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is > available. > > -- > Bruce CranIt is very likely , because I had selected all of the packages . I do not know why HAL uses sudo for such a result . Actually I am using FreeBSD 7.1 i386 Stable again all of the packages installed but Gnome shut down menu is NOT affected by selection of sudo . Now I have checked my 7.1 i386 . sudo is installed and Gnome shutdown menu for the user ( not root ) included into operator group for USB mounts shows the menu item shudtdown . This means that there is a difference between i386 and amd64 shutdown rules in Gnome menus . Thank you very much Mehmet Erol Sanliturk
On Sat, Apr 18, 2009 at 8:20 PM, Manolis Kiagias <sonic2000gr@gmail.com>wrote:> Bruce Cran wrote: > > On Sat, 18 Apr 2009 19:04:26 -0400 > > Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> wrote: > > > > > > > >> (3) When shutdown is selected from Gnome menu either by the first > >> user or the root , within displayed dialog box > >> there is no a Shutdown item . > >> It is necessary for the root open a terminal console , and enter > >> shutdown -p now command . > >> > > > > Have you installed sudo? I think those options > > (suspend/shutdown/hibernate) only get displayed if HAL sees sudo is > > available. > > > > > Fact is you will get these options either if you have sudo and your user > account is authorized to shutdown / reboot (this is the fallback method > though) or if PolicyKit is configured (see > /usr/local/etc/PolicyKit/PolicyKit.conf) to allow shutdown/reboot. > > Entries will look similar to these: > > <match action="org.freedesktop.hal.power-management.shutdown"> > <match user="yourusername"> > <return result="yes"/> > </match> > </match> > <match action="org.freedesktop.hal.power-management.reboot"> > <match user="yourusername"> > <return result="yes"/> > </match> > </match> > > Have a look at http://www.freebsd.org/gnome/docs/halfaq.html for more > HAL fun ;) >Nearly all of my expressed ideas about FreeBSD is not about my own requirements but especially newly beginning users . This point is utmost importance for me because my profession was the teaching of programming languages to the students in the University by starting from Introduction to computing . In those days computers were not available as they are today . I know how difficult is to make a start to learning to use a computing systems with respect to observations of the students . Then I want to emphasize the points that will be difficult for the new users to overcome at the beginning . If we do not reduce usage difficulty level of FreeBSD as much as possible it will prevent adoption of FreeBSD so much . Why FreeBSD so important for me is not a good question because FreeBSD is an excellent operating system with an immensely invested efforts by its very valuable developers and I think it is second to none . For my own difficulties : I wish - the Handbook includes more examples . - the man pages includes more examples for typical situations . In that respect my idea is that freebsd-questions and other lists contain excellent cases and solutions to them . In those days there is a concept of data mining . Actually these lists are containing very good sample cases and their solutions . By traversing the questions and problems and answers to them may be utilized to enhance the man pages and the handbook . This requires extensive knowledge about the Handbook and man pages which I do not have yet . Knowledgeable FreeBSD developers may contribute to this process . It is known that ideas expressed in mailing lists may be utilized for this process and my opinion is that no one will object to utilization of his/her ideas in such a utilization . Thank you very much . Mehmet Erol Sanliturk.