fsck gave up on me!

2007-11-03 Thread lawrence.petrykanyn


  Hi,
  I have been using FreeBSD 6.2 for a couple of months now with no major
  snags.  Until now.  I did a portupgrade this morning and afterwards,
  when I logged in as a user into Gnome, my desktop was missing most of
  the programs (Accessories, System Tools, etc.).
  I rebooted the machine and "that other" terminal screen came up
  (Single User?) and I was prompted to "run fsck manually" so I did so.
  Well, fsck gave up on me.  I have no idea what happened or why.  Can
  anyone help me understand what is going on with my machine and any
  possible actions I can take to resolve this?


  Script started on Fri Nov  2 17:13:22 2007
  You have mail.
  root# fscd[Kk
  ** /dev/ad1s1a (NO WRITE)
  ** Last Mounted on /
  ** Root file system
  ** Phase 1 - Check Blocks and Sizes
  CANNOT READ BLK: 524544
  CONTINUE? [yn] y
  THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
  ** Phase 2 - Check Pathnames
  ** Phase 3 - Check Connectivity
  ** Phase 4 - Check Reference Counts
  ** Phase 5 - Check Cyl groups
  CANNOT READ BLK: 524544
  CONTINUE? [yn] y
  THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
  CG 2: BAD MAGIC NUMBER
  FREE BLK COUNT(S) WRONG IN SUPERBLK
  SALVAGE? no
  SUMMARY INFORMATION BAD
  SALVAGE? no
  fsck: /dev/ad1s1a: Segmentation fault: 11
  kirkwood# exit
  exit
  Script done on Fri Nov  2 17:14:23 2007

  Thank you in advance,
  Larry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Unable to delete a package

2007-09-17 Thread lawrence.petrykanyn

Hi, Peter:


> ===>  Installing for libgda3-1.9.102_3
> ===>  libgda3-1.9.102_3 conflicts with installed package(s):
>  libgda2-1.2.4_1,1
>  They install files into the same place.
>  Please remove them first with pkg_delete(1).

As people have noted you can use -f to force deletion. The problem you
are experiencing would typically happen either because you are trying
to install some top-level packages that are truly in conflict, in the
sense that they depend on conflicting versions of libgda.

Alternatively, you have older versions of various packages installed
that depend on the older version of libgda3, and are now trying to
install the gnome stuff from a newer ports tree. In this case you may
want to perform a full upgrade (using
portupgrade/portmanagaer/portmaster/etc).


I'm using the command 'portsnap fetch update' each time before I do a 'make 
install clean' hoping that will cover me. I used portupgrade with 5.4 but 
switched to portsnap with 6.2 because I believed from the Handbook that it 
was a 'new and improved' way of maintaining my ports tree. Is this correct?  
Does portsnap do a better job than portupgrade or portsmanager?  Do they all 
do the same thing (...in real life as well as on paper...)?  Does portsnap 
automatically upgrade my programs or just the ports tree?  And if I am using 
portsnap, can I use portupgrade or portsmanager as well, or will they cause 
a conflict?




forcibly deleting the package will work, but the other packages
depending on them will very likely break.


I was concerned that something like that might happen but wasn't sure. 
Thanks!




> (As an aside, is it okay to run these installations from a terminal 
window

> from inside the Gnome GUI environment, or should I be outside of Gnome
> altogether when I do program installations/upgrades?)

It doesn't matter, except in so far as any actions would kill your
running terminal. I would suspect that the already running terminal
would survive (certainly this is the case with most), though I don't
know if the gnome terminal is doing stuff even after initial start-up
that might cause it to die.

(To be strict of course it's always safest to not run stuff you are
actively upgrading, while upgrading. In practice though it "tends to
work".)


I prefer to do upgrades and installations from outside the GUI.  But I've 
added 'gdm_enable=Yes' to my rc.conf file so that the graphical login screen 
appears for most daily use.  In order to get to the pre-GUI terminal as 
root, I have to log in as root into the GUI, comment out 'gdm_enable=Yes' in 
my rc.conf file, then reboot the machine so that I can run portsnap (or 
whatever) in the pre-GUI terminal.  Then after running portupgrade, I have 
to re-edit my rc.conf in order to re-enable gdm and reboot again.  Is there 
an easier way to get the pre-GUI terminal without having to reboot after 
commenting out 'gdm_enable=Yes' in my rc.conf file and then re-inserting it 
after I do an upgrade?  I've tried Alt-Ctl-Backspace, and that does kill 
Gnome, but then it just bounces me back into the graphical login screen.


Much appreciated,
Larry


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Unable to delete a package

2007-09-17 Thread lawrence.petrykanyn

Hi,

(I originally posted this on the freebsd-gnome mailing list and then 
realized that list was for people actively working on Gnome.  I don't know 
if my question is a Gnome-specific issue or if it is an issue that can arise 
when installing programs in general.)


I am currently using FreeBSD 6.2 RELEASE and I am trying to install 
gnome2-office via the ports collection.  After running 'portsnap fetch 
update' I 'make install clean' in the gnome2-office directory. It goes well 
until:


   *
   *
   *
gmake[2]: Entering directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102/doc/C'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102/doc/C'
gmake[2]: Entering directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102/doc'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102/doc'
gmake[1]: Leaving directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102/doc'
gmake[1]: Entering directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102'
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory
`/usr/ports/databases/libgda3/work/libgda-1.9.102'
===>  Installing for libgda3-1.9.102_3
===>  libgda3-1.9.102_3 conflicts with installed package(s):
 libgda2-1.2.4_1,1
 They install files into the same place.
 Please remove them first with pkg_delete(1).
*** Error code 1
Stop in /usr/ports/databases/libgda3.
*** Error code 1
Stop in /usr/ports/math/gnumeric.
*** Error code 1
Stop in /usr/ports/math/gnumeric.
*** Error code 1
Stop in /usr/ports/editors/gnome2-office.
***


  ...so I:


root# pkg_delete libgda2-1.2.4_1,1
pkg_delete: package 'libgda2-1.2.4_1,1' is required by these other packages
and may not be deinstalled:
py25-gnome-extras-2.14.3_3
straw-0.27
gnome2-fifth-toe-2.18.3
***


   ...so I then try to install the new libgda separately:

root# make install clean
===>  Installing for libgda3-1.9.102_3
===>  libgda3-1.9.102_3 conflicts with installed package(s):
 libgda2-1.2.4_1,1
 They install files into the same place.
 Please remove them first with pkg_delete(1).
*** Error code 1

I am new to the subtle inner workings of FreeBSD.  Could anyone please
advise, suggest, or comment on how I should proceed?  It seems that
I can't install the new libgda unless I delete the old one, but I am
prevented from deleting the old one because at least three other programs
are dependent upon it.

(As an aside, is it okay to run these installations from a terminal window
from inside the Gnome GUI environment, or should I be outside of Gnome
altogether when I do program installations/upgrades?)

Thanks,
Larry


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Problem with Gnome2 Installation

2007-08-29 Thread lawrence.petrykanyn


  Hi, Predrag!

  Thank you for responding to my question.  I installed 6.2 Release, but
  did a minimum installation so I did not install Xorg from the release
  (I think).  I then installed Xorg-7.2 from the ports collection.  I
  took your advice and used the "make BATCH=yes install clean" command
  the installation was successful.  Thanks again.  I now can't seem to
  get Gnome to run even though I followed the instructions in the
  handbook, but I'll post that question in the Gnome forum as you
  suggested.

  BTW - Do you use portupgrade, portmaster or portsnap?  Any comments on
  which to use?  Is it okay to use more than one or does that corrupt
  the integrity of the ports tree?

  Thanks again,

  Larry
  __

From:  Predrag Punosevac <[EMAIL PROTECTED]>
To:  <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject:  Re: Problem with Gnome2 Installation
Date:  Mon, 27 Aug 2007 23:43:42 -0700
>[EMAIL PROTECTED] wrote:
>>
>>   Hi,
>>
>>   I just installed FreeBSD6.2 onto my home computer.  I chose
the
>>   'minimum installation' option.  I then installed the ports
tree
>>by
>>   'portsnap fetch', followed by 'portsnap extract', and then
>>'portsnap
>>   fetch upgrade'.  Then I successfully installed Xorg via the
>>ports
>>   tree.  I then configured and tested X11.  So far, all went
very
>>well.
>>
>>   Next, I wanted to install the Gnome Desktop Environment, so
'cd
>>   /usr/ports/x11/gnome2' followed by 'make install clean'.  The
>>   installation went well for over two hours, and then it stopped
>>with
>>   the message that I have included from the script file below.
>>
>>   I have a few questions:
>>   1.  How can I continue, and complete, the installation of
Gnome?
>>   2.  What, besides general Googling and checking the FreeBSD
>>archives,
>>   can I do when the installation generates an error message like
>>the one
>>   below that is merely descriptive and not prescriptive?  (I'd
>>like to
>>   not have to come running to this forum every time an
>>installation
>>   doesn't succeed.  I realize that a learning curve is involved,
>>but I'm
>>   willing to do a bit of research if I can find the right
>>resources.  I
>>   did look at /usr/ports/UPDATING but didn't find anything that
>>looked
>>   relevant.)
>>   3.  In the past (5.4), I have used 'portupgrade' to maintain
my
>>ports
>>   tree.  I understand that 'portsnap' is a new utility that is
>>supposed
>>   to be easier to use and more reliable.  So does this mean that
I
>>can
>>   do all of my ports tree maintenance with 'portsnap' and never
>>use
>>   'portupgrade' again?
>>
>>   Any advice, suggestions, or comments would be appreciated!
>>
>>   Thank you,
>>   Larry
>>
>>   Error Message **
>>  (Excerpt)
>>   *
>>   *
>>   *
>>   ===>   gnome-control-center-2.18.1_1 depends on shared
library:
>>xml2.5
>>   - found
>>   ===>   gnome-control-center-2.18.1_1 depends on shared
library:
>>xslt.2
>>   - found
>>   ===>   gnome-control-center-2.18.1_1 depends on shared
library:
>>linc.1
>>   - found
>>   ===>   gnome-control-center-2.18.1_1 depends on shared
library:
>>   metacity-private.0 - not found
>>   ===>Verifying install for metacity-private.0 in
>>   /usr/ports/x11-wm/metacity
>>   ===>  Building for metacity-2.18.5
>>   gmake  all-recursive
>>   gmake[1]: Entering directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5'
>>   Making all in src
>>   gmake[2]: Entering directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
>>   gmake  all-recursive
>>   gmake[3]: Entering directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
>>   Making all in wm-tester
>>   gmake[4]: Entering directory
>>
`/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
>>   gmake[4]: Nothing to be done for `all'.
>>   gmake[4]: Leaving directory
>>
`/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
>>   Making all in tools
>>   gmake[4]: Entering directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
>>   gmake[4]: Nothing to be done for `all'.
>>   gmake[4]: Leaving directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
>>   Making all in themes
>>   gmake[4]: Entering directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
>>   gmake[4]: Nothing to be done for `all'.
>>   gmake[4]: Leaving directory
>>   `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
>>   gmake[4]: Ente

Problem with Gnome2 Installation

2007-08-27 Thread lawrence.petrykanyn


  Hi,

  I just installed FreeBSD6.2 onto my home computer.  I chose the
  'minimum installation' option.  I then installed the ports tree by
  'portsnap fetch', followed by 'portsnap extract', and then 'portsnap
  fetch upgrade'.  Then I successfully installed Xorg via the ports
  tree.  I then configured and tested X11.  So far, all went very well.

  Next, I wanted to install the Gnome Desktop Environment, so 'cd
  /usr/ports/x11/gnome2' followed by 'make install clean'.  The
  installation went well for over two hours, and then it stopped with
  the message that I have included from the script file below.

  I have a few questions:
  1.  How can I continue, and complete, the installation of Gnome?
  2.  What, besides general Googling and checking the FreeBSD archives,
  can I do when the installation generates an error message like the one
  below that is merely descriptive and not prescriptive?  (I'd like to
  not have to come running to this forum every time an installation
  doesn't succeed.  I realize that a learning curve is involved, but I'm
  willing to do a bit of research if I can find the right resources.  I
  did look at /usr/ports/UPDATING but didn't find anything that looked
  relevant.)
  3.  In the past (5.4), I have used 'portupgrade' to maintain my ports
  tree.  I understand that 'portsnap' is a new utility that is supposed
  to be easier to use and more reliable.  So does this mean that I can
  do all of my ports tree maintenance with 'portsnap' and never use
  'portupgrade' again?

  Any advice, suggestions, or comments would be appreciated!

  Thank you,
  Larry

  Error Message **
 (Excerpt)
  *
  *
  *
  ===>   gnome-control-center-2.18.1_1 depends on shared library: xml2.5
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library: xslt.2
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library: linc.1
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library:
  metacity-private.0 - not found
  ===>Verifying install for metacity-private.0 in
  /usr/ports/x11-wm/metacity
  ===>  Building for metacity-2.18.5
  gmake  all-recursive
  gmake[1]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5'
  Making all in src
  gmake[2]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake  all-recursive
  gmake[3]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  Making all in wm-tester
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
  Making all in tools
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
  Making all in themes
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[4]: Nothing to be done for `all-am'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[3]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[2]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  Making all in po
  gmake[2]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/po'
  file=`echo cs | sed 's,.*/,,'`.gmo \
 && rm -f $file && /usr/local/bin/msgfmt -o $file cs.po
  cs.po:1160:72: invalid multibyte sequence
  cs.po:1160: keyword "a" unknown
  cs.po:1160:76: parse error
  cs.po:1161: end-of-line within string
  /usr/local/bin/msgfmt: found 4 fatal errors
  gmake[2]: *** [cs.gmo] Error 1
  gmake[2]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/po'
  gmake[1]: *** [all-recursive] Error 1
  gmake[1]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5'
  gmake: *** [all] Error 2
  *** Error code 2
  Stop in /usr/ports/x11-wm/metacity.
  *** Error code 1
  Stop in /usr/ports/sysutils/gnome-control-center.
  *** Error code 1
  Stop in /usr/ports/x11/gnome-applets.
  *** Error code 1
  Stop in /usr/ports/x11/gnome2.
  *** Error code 1
  Stop in /usr/ports/x11/gnome2.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Installation Disc Won't Boot

2007-08-25 Thread lawrence.petrykanyn

Hi, Manoliis:

I took your advice.  I copied the burned iso file into a FreeBSD directory 
and ran md5 and the check digits did not match.  I then copied my downloaded 
iso image from Win98 into FreeBSD and ran md5 and the digits did match.  So 
there was nothing wrong with the iso of disc1 that I downloaded from the web 
site into Win98.  It must have been the burning of the file in Win98 with 
Nero Express that was the problem.


So I burned another copy of the iso in FreeBSd with burncd using:
  burncd -f /dev/acd1 6.2-RELEASE-i386.iso fixate
and it booted just fine.

Thanks for all of your suggestions and advice.  Now I will be spending the 
better part of the weekend doing the installation of 6.2.  Wish me luck.


Have a great day,
Larry




From: Manolis Kiagias <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
CC: freebsd-questions@freebsd.org
Subject: Re: Installation Disc Won't Boot
Date: Fri, 24 Aug 2007 21:34:12 +0300

[EMAIL PROTECTED] wrote:
>
>   Hi,
>
>   I am unable to boot from 6.2-RELEASE i386-disc1.iso.  I have
>   downloaded it and burned it three times without success.
>
>   I am currently running Win98SE and FreeBSD 5.4 on a dual boot.  I had
>   decided to reformat my hard drives so I reinstalled Win98SE and would
>   like to install FreeBSD 6.2.  I downloaded the disc 1 iso image and
>   burned it to a disc in Win98.  I had to boot from my CDrom to
>   reinstall Win98 so I know that my boot priority is correct and that my
>   CDrom is working properly.  I looked at the burned cd with the
>   6.2-RELEASE i386-disc1.iso file on it in FreeBSD 5.4 and everything
>   appears to be there, including a folder called 'boot'.  But I just
>   can't seem to boot from it.
>
>   1.  Is there something simple I'm missing?

Could be that you are burning the file as a real file on a disk instead
of burning it as an image?
You need to select the option from your program that is similar to
"create cd from iso image"

>   2.  Should I just try downloading (it takes four hours) and burning
>   more copies again?  (I've already done it three times...)

No. Instead you should check the file you already downloaded

>   3.  Is the fact that I'm burning it in Win98 a problem?

Not really, no

>   4.  Is there anything I can do in FreeBSD 5.4 to see if the file is
>   corrupted?
>
Yes. From the site you downloaded the iso files, download the CHECKSUM
files as well.
There are two of them, CHEKSUM.md5 and CHECKSUM.SHA256
One would be enough to validate your download. For example look at the
CHECKSUM.md5 file:
For disk1, the checksum is:

MD5 (6.2-RELEASE-i386-disc1.iso) = 3d27214700687c0b5390e8b6dd3706e3

you can validate this with the md5 command from FreeBSD, or if you don't
wish to reboot from win98, here is and md5 command for windows:

http://www.fourmilab.ch/md5/md5.zip

use something like:

md5 6.2-RELEASE-i386-disc1.iso

and compare the output to the one on the file.
>   BTW - I installed FreeBSD 5.4 from discs that I purchased through
>   FreeBSD Mall.  I thought I would do it from the 6.2-RELEASE
>   i386-disc1.iso file on FreeBSD's web site this time.
>

I've bought stuff from them: copies of the handbook, tshirts, sticker,
beastie dolls :)
Good service.

>   Any suggestions, advice, or comments would be greatly appreciated.
>
>   Thanks,
>   Larry
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>
Best of luck,

Manolis



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Installation Disc Won't Boot

2007-08-24 Thread lawrence.petrykanyn


  Hi,

  I am unable to boot from 6.2-RELEASE i386-disc1.iso.  I have
  downloaded it and burned it three times without success.

  I am currently running Win98SE and FreeBSD 5.4 on a dual boot.  I had
  decided to reformat my hard drives so I reinstalled Win98SE and would
  like to install FreeBSD 6.2.  I downloaded the disc 1 iso image and
  burned it to a disc in Win98.  I had to boot from my CDrom to
  reinstall Win98 so I know that my boot priority is correct and that my
  CDrom is working properly.  I looked at the burned cd with the
  6.2-RELEASE i386-disc1.iso file on it in FreeBSD 5.4 and everything
  appears to be there, including a folder called 'boot'.  But I just
  can't seem to boot from it.

  1.  Is there something simple I'm missing?
  2.  Should I just try downloading (it takes four hours) and burning
  more copies again?  (I've already done it three times...)
  3.  Is the fact that I'm burning it in Win98 a problem?
  4.  Is there anything I can do in FreeBSD 5.4 to see if the file is
  corrupted?

  BTW - I installed FreeBSD 5.4 from discs that I purchased through
  FreeBSD Mall.  I thought I would do it from the 6.2-RELEASE
  i386-disc1.iso file on FreeBSD's web site this time.

  Any suggestions, advice, or comments would be greatly appreciated.

  Thanks,
  Larry
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"