View previous topic :: View next topic |
Author |
Message |
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Thu Mar 17, 2005 3:17 am Post subject: |
|
|
semijoyful wrote: | I thank you for the code, but it's not working:
Code: | [root@localhost freshjoy]# groupadd -g 250 portage
bash: groupadd: command not found
[root@localhost freshjoy]# useradd -d /var/tmp/portage -g portage -u 250 portage |
Any ideas?
-Semijoyful | [/quote]that explains why the script didn't create it. your user 'root' is pretty much screwed because he doesn't have /usr/sbin and /sbin in his path and that's where most of the admin utilities are...I will update the script to use /usr/sbin/useradd instead of depend on the PATH to find useradd etc. |
|
Back to top |
|
|
semijoyful n00b
Joined: 27 Jan 2005 Posts: 11 Location: Sacramento
|
Posted: Thu Mar 17, 2005 9:30 am Post subject: |
|
|
devsk and others, thank you for helping me through this. I think I just about got it. I am curious about some stuff that showed up towards the end of the code:
Code: | [root@localhost sbin]# emerge -O portage
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/portage-2.0.51.19 to /
>>> md5 src_uri ;-) portage-2.0.51.19.tar.bz2
>>> Merging sys-apps/portage-2.0.51.19 to /
find: /var/tmp/portage/portage-2.0.51.19/image//: No such file or directory
find: /var/tmp/portage/portage-2.0.51.19/image//: No such file or directory
* Checking //var/lib/portage for bad/illegal files:
* Feature additions are noted in help and make.conf descriptions.
* Update configs using 'etc-update' please. Maintaining current configs
* for portage and other system packages is fairly important for the
* continued health of your system.
* NOTICE: There have been changes in the location of some internal files
* to better match the FHS. The changes do not directly affect users
* but please be advised that changing between versions of portage
* with and without these changes may introduce some inconsistencies
* in package data regarding 'world' and 'virtuals' (provides).
* /var/cache/edb/world has moved to /var/lib/portage/world
* /var/cache/edb/virtuals has been deprecated and is now calculated
* on demand. Strictly _USER_ modifications to virtuals may go into
* /etc/portage/profile/virtuals and will not be modified by portage.
Recalculating the counter... Counter updated successfully.
* Compiling python modules...
* You may run 'emerge metadata' to perform cache updates if you have
* changed versions of portage. This will provide a fairly dramatic
* speedup. Alternatively, you may 'emerge sync' if it has been more
* than 30 minutes since your last sync.
>>> Regenerating /etc/ld.so.cache...
* Caching service dependencies...
gawk: /lib/rcscripts/awk/cachedepends.awk:73: fatal: extension: cannot open `/lib/rcscripts/filefuncs.so' (/lib/rcscripts/filefuncs.so: cannot open shared object file: No such file or directory)
bash: /var/lib/init.d/depcache: No such file or directory
>>> sys-apps/portage-2.0.51.19 merged.
>>> clean: No packages selected for removal.
>>> Auto-cleaning packages ...
>>> No outdated packages were found on your system. |
Should I be concerned about any of this?
Obrigado!
-Semijoyful |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Thu Mar 17, 2005 4:59 pm Post subject: |
|
|
semijoyful wrote: |
Should I be concerned about any of this?
Obrigado!
-Semijoyful |
find problem, yes!
do this :
Code: | emerge -O gawk
emerge -O findutils
emerge -O portage |
|
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sat Mar 19, 2005 7:42 pm Post subject: |
|
|
kimchi_sg wrote: |
[list=1][*]emerge --sync refuses to go to updating the cache for some reason. I have set Code: | RSYNC_TIMEOUT=1800
RSYNC_RETRIES=30 | but when I try to sync it ends up retrying and retrying with the following message (it has been doing this for 3 hours already):
Code: | Number of files: 111825
Number of files transferred: 61
Total file size: 87180631 bytes
Total transferred file size: 19764 bytes
Literal data: 19764 bytes
Matched data: 0 bytes
File list size: 2650351
Total bytes sent: 1370
Total bytes received: 2673590
sent 1370 bytes received 2673590 bytes 3312.64 bytes/sec
total size is 87180631 speedup is 32.59
rsync error: some files could not be transferred (code 23) at /home/lapo/packagi
ng/tmp/rsync-2.6.3/main.c(1146)
>>> retry ... |
I will try to compile rsync from source to see if this fixes the problem.
|
its not rsync, but the portage tree which is corrupt with filenames which don't make sense inside of cygwin. The files in question are:
Code: | /usr/portage/dev-lang/ruby/files/ruby-1.8.0-CGI::Session.patch
/usr/portage/dev-ruby/shim-ruby18/files/shim-ruby18-CGI::Session.patch |
':' can't be escaped either. So, file creation will always fail with 'Invalid argument'. emerge-webrsync will also fail because even tar can't create this file.
And because rsync fails to to copy these files, emerge thinks that rsync failed and hence restarts it.
I made a custom portage tree sans these files on another system and 'emerge metadata' went fine. I can emerge programs normally(I updated less, patch just for kicks) but there are lot of porting issues like filename "//var/db" is not valid on cygwin because it starts searching network path, while on linux its same as "/var/db". Then there are tonnes of file locking issues and there are some bugs in portage python code. And I am not sure if people at gentoo are very receptive of bug fixes for operating systems outside of Linux(I faced lot of problems fixing issues for solaris for example).
Currently, I don't have much time otherwise I could peruse it further. May be later sometime.
If they fix issues with "//" in pathnames, this port seems easier than solaris.
PS: you can create root:root, portage:portage on cygwin. Following assumes that you know passwd/group file formats.
Create root user, portage group, wheel group, portage2 user in windows 2000. Assign groups to newer users as needed. Then do mkpasswd -l > /etc/passwd and mkgroup -l > /etc/group to create /etc/passwd and /etc/group. Edit /etc/group to COPY PASTE (NOT cut paste) line containing Administrators and change Administrators to root and last field to '0'. Make wheel's group id be 10 and portage groupid be 250. Edit /etc/passwd to assign userid '0' to root. 'id -a root' should now list 0 for userid and 0 for gid. Also manually edit entry for portage2 user and make it portage and assign userid '250'. Remember that you should NOT touch fields starting with "S-", those are SIDs used by cygwin to map to real user/group in windows system.
after re-login, you should essentially end up with linux like users for portage and root. Make sure to make a copy of these files somewhere because mkpasswd/mkgroup again and these changes are history. |
|
Back to top |
|
|
mrnegitoro Tux's lil' helper
Joined: 30 Jun 2003 Posts: 77 Location: Vancouver, BC.
|
Posted: Mon Mar 21, 2005 9:46 pm Post subject: Most recent script |
|
|
Hi,
Is the most recent version of your script at the very beginning of this topic? I'm running Slackware 10.1 and I don't really want to do a whole reinstall with Gentoo or be bother to back up all my data. Portage is a much better system than slapt-get (I find). Will my Slackware box basically become a Gentoo box? Is this a stupid question?
Thanks for such an excellent script! |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Mon Mar 21, 2005 11:41 pm Post subject: |
|
|
Quote: | Is the most recent version of your script at the very beginning of this topic? | that's pretty much it.
Quote: | Will my Slackware box basically become a Gentoo box? |
no, your box will become a hybrid... gendora or slackgen or whatever you wanna call it. There are issues with startup/shutdown scripts for daemons/services, because they are essentially different on different distros. If you threads 7,8,9 you will get a wealth of knowledge about fedora integration, which you can probably apply to slackware. |
|
Back to top |
|
|
mrnegitoro Tux's lil' helper
Joined: 30 Jun 2003 Posts: 77 Location: Vancouver, BC.
|
Posted: Tue Mar 22, 2005 3:56 am Post subject: Slacker Generation |
|
|
Hi again,
I have a Slackgen box now! Thanks!
However, I can't help myself, I must ask another "newbie" question. On your Fedora Red Hat box are you emerging over all your rpm binary installs? I assume I should uninstall any Slackware packages I have that I might wish to then reinstall using portage?
Thanks again! |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Tue Mar 22, 2005 8:19 am Post subject: Re: Slacker Generation |
|
|
mrnegitoro wrote: | Hi again,
I have a Slackgen box now! Thanks!
However, I can't help myself, I must ask another "newbie" question. On your Fedora Red Hat box are you emerging over all your rpm binary installs? I assume I should uninstall any Slackware packages I have that I might wish to then reinstall using portage?
Thanks again! | its fine to overwrite because portage resolves dependencies and will install lowest level packages first. So, you won't get into situations where your emerge will fail because of existing old install files. Morever, whenever applicable, portage points newer packages to its own installed packages for builds.
there is some cruft left from rpm install. So, usually I would recommend un-install the app if it is safe to do so and then emerge. |
|
Back to top |
|
|
rush_ad l33t
Joined: 22 Jul 2004 Posts: 863 Location: New Jersey, USA
|
Posted: Tue Mar 22, 2005 7:15 pm Post subject: |
|
|
anybody had luck installing this on SuSE? does it conflict with YaST? |
|
Back to top |
|
|
rush_ad l33t
Joined: 22 Jul 2004 Posts: 863 Location: New Jersey, USA
|
Posted: Tue Mar 29, 2005 1:48 am Post subject: |
|
|
i am going to try it on suse 9.3 when it is released, it will be soon. |
|
Back to top |
|
|
dearborn98 n00b
Joined: 30 Nov 2004 Posts: 19
|
Posted: Sat Apr 02, 2005 2:05 am Post subject: |
|
|
Was able to install portage on SUSE 9.1 . Had problems with this part of the script:
cd ../src/python-missingos
./setup.py install
Showed errors relating to python, even after changing the python2.2 to python2.3 in the setup.py script. I dug up a python2.2-src.rpm from an older version of SUSE, installed it with YAST. I also used devsk export:
export PYTHONPATH=/usr/lib/python2.3/site-packages:/usr/lib/python2.2/site-packages
Script worked fine afterwords.
When I installed portage on SuSE 9.2, I pasted the script line for line. I had to change a few lines in order to get emerge --sync to work without any errors.
To make this script work, I also had to change the python2.2 to python2.3 in the /python-missingos setup.py file. I do not know how to add this change to the script so as to make the whole script work from start to finish.
This is the part of the script that I had to change to get portage to work on my SuSE 9.2 (along with python2.2 to python2.3 in setup.py) :
#!/bin/bash
#
if [ "`id -u`" != "0" ]; then
echo ""
echo "Su as root and try again."
echo ""
exit 1
fi
pythonV=`python -V 2>&1`
if [ "$pythonV" \< "Python 2.2.0" ];then
echo ""
echo "Install python 2.2 and then try again"
echo ""
exit 1
fi
mkdir -p /usr/lib/portage/bin
mkdir -p /usr/lib/portage/pym
mkdir -p /usr/portage/profiles
mkdir -p /usr/local/portage
mkdir -p /etc/env.d
mkdir -p /etc/portage/profile
mkdir -p /var/log/portage
mkdir -p /var/tmp/portage
mkdir -p /etc/config-archive
mkdir -p /var/lib/init.d
mkdir -p /var/lib/portage
mkdir -p /usr/man/man1
mkdir -p /usr/man/man5
mkdir -p /usr/portage/sys-apps/portage/files
cd /usr/portage/sys-apps/portage/files
wget http://dev.gentoo.org/~carpaski/portage_rescue/portage-rescue-2.0.51-r14-x86.tbz2
cd /tmp
rm -rf portage-2.0.51.18
wget ftp://gentoo.mirrors.pair.com/distfiles/portage-2.0.51.18.tar.bz2 -O /tmp/portage-2.0.51.18.tar.bz2
if [ ! -f portage-2.0.51.18.tar.bz2 ];then
echo ""
echo "Mirror error. Try this script again after a while without any args".
echo ""
exit 1
fi
tar jxf portage-2.0.51.18.tar.bz2
export PYTHONPATH=/usr/lib/python2.3/site-packages:/usr/lib/python2.2/site-packages
cd portage-2.0.51.18/bin
cp * /usr/lib/portage/bin
export PATH=/usr/lib/portage/bin:$PATH
cd ../pym ; cp * /usr/lib/portage/pym/
cd ../man ;cp *.1 /usr/man/man1 ;cp *.5 /usr/man/man5
cd /usr/portage/sys-apps/portage/files
tar xjpUvf portage-rescue-2.0.51-r14-x86.tbz2
cd /tmp/portage-2.0.51.18/src/python-missingos
./setup.py install
cd ../sandbox-1.1
make && make install
cd ../../cnf; cp * /etc
I Didn't like SUSE 9.2 as much as 9.1, to me it seemed to run slower than SUSE 9.1.
SUSE 9.1 and 9.2 seems to be stable with portage.
YAST still works good. Still able to install programs with YAST. The SUSE updater (susewatcher) is still updating the system via internet. |
|
Back to top |
|
|
rush_ad l33t
Joined: 22 Jul 2004 Posts: 863 Location: New Jersey, USA
|
Posted: Fri Apr 15, 2005 2:19 pm Post subject: |
|
|
this is what i get on suse 9.3\\
EDIT: using the above script. i also get erros using the scipt on the first page.
Code: | linux:/home/pankaj # /tmp/install-portage.sh
--10:17:48-- http://dev.gentoo.org/%7Ecarpaski/portage_rescue/portage-rescue-2.0.51-r14-x86.tbz2
=> `portage-rescue-2.0.51-r14-x86.tbz2'
Resolving dev.gentoo.org... 134.68.220.30
Connecting to dev.gentoo.org[134.68.220.30]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 330,151 [text/plain]
100%[====================================>] 330,151 453.97K/s
10:17:49 (452.86 KB/s) - `portage-rescue-2.0.51-r14-x86.tbz2' saved [330151/330151]
--10:17:49-- ftp://gentoo.mirrors.pair.com/distfiles/portage-2.0.51.18.tar.bz2
=> `/tmp/portage-2.0.51.18.tar.bz2'
Resolving gentoo.mirrors.pair.com... 216.92.2.140
Connecting to gentoo.mirrors.pair.com[216.92.2.140]:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /distfiles ... done.
==> PASV ... done. ==> RETR portage-2.0.51.18.tar.bz2 ...
No such file `portage-2.0.51.18.tar.bz2'.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Child returned status 2
tar: Error exit delayed from previous errors
/tmp/install-portage.sh: line 49: cd: portage-2.0.51.18/bin: No such file or directory
cp: omitting directory `gconfd-pankaj'
cp: omitting directory `gconfd-root'
cp: omitting directory `hsperfdata_pankaj'
cp: omitting directory `kde-pankaj'
cp: omitting directory `ksocket-pankaj'
cp: omitting directory `orbit-pankaj'
cp: cannot open `OSL_PIPE_1000_SingleOfficeIPC_3f2f44c6e7b6dbc1b90d8f6eac2d389' for reading: No such device or address
/tmp/install-portage.sh: line 52: cd: ../pym: No such file or directory
cp: omitting directory `gconfd-pankaj'
cp: omitting directory `gconfd-root'
cp: omitting directory `hsperfdata_pankaj'
cp: omitting directory `kde-pankaj'
cp: omitting directory `ksocket-pankaj'
cp: omitting directory `orbit-pankaj'
cp: cannot open `OSL_PIPE_1000_SingleOfficeIPC_3f2f44c6e7b6dbc1b90d8f6eac2d389' for reading: No such device or address
/tmp/install-portage.sh: line 53: cd: ../man: No such file or directory
cp: cannot stat `*.1': No such file or directory
cp: cannot stat `*.5': No such file or directory
./
tar: .: Cannot mkdir: No such file or directory
./etc/
./etc/make.globals
./etc/etc-update.conf
./etc/dispatch-conf.conf
./etc/make.conf.example
./lib/
./lib/libsandbox.so
./var/
./var/tmp/
./var/tmp/.keep
./usr/
./usr/bin/
./usr/bin/xpak
./usr/bin/repoman
./usr/bin/g-cpan.pl
./usr/bin/portageq
./usr/bin/ebuild
./usr/bin/emerge
./usr/bin/quickpkg
./usr/bin/tbz2tool
./usr/lib/
./usr/lib/portage/
./usr/lib/portage/bin/
./usr/lib/portage/bin/fixpackages
./usr/lib/portage/bin/dispatch-conf-dialog
./usr/lib/portage/bin/domo
./usr/lib/portage/bin/xpak
./usr/lib/portage/bin/queryhost.sh
./usr/lib/portage/bin/fix-db.py
./usr/lib/portage/bin/dolib.so
./usr/lib/portage/bin/donewins
./usr/lib/portage/bin/mirror.py
./usr/lib/portage/bin/env-update
./usr/lib/portage/bin/fixdbentries
./usr/lib/portage/bin/repoman
./usr/lib/portage/bin/dopython
./usr/lib/portage/bin/dobin
./usr/lib/portage/bin/dodir
./usr/lib/portage/bin/dodoc
./usr/lib/portage/bin/doexe
./usr/lib/portage/bin/dojar
./usr/lib/portage/bin/doins
./usr/lib/portage/bin/dolib
./usr/lib/portage/bin/doman
./usr/lib/portage/bin/dosed
./usr/lib/portage/bin/dosym
./usr/lib/portage/bin/emake
./usr/lib/portage/bin/etc-update
./usr/lib/portage/bin/portage_gpg_update.sh
./usr/lib/portage/bin/doconfd
./usr/lib/portage/bin/doinitd
./usr/lib/portage/bin/dolib.a
./usr/lib/portage/bin/sandbox
./usr/lib/portage/bin/g-cpan.pl
./usr/lib/portage/bin/emerge-webrsync
./usr/lib/portage/bin/regenworld
./usr/lib/portage/bin/chkcontents
./usr/lib/portage/bin/portageq
./usr/lib/portage/bin/clean_locks
./usr/lib/portage/bin/prepstrip
./usr/lib/portage/bin/archive-conf
./usr/lib/portage/bin/ebuild
./usr/lib/portage/bin/doenvd
./usr/lib/portage/bin/dohard
./usr/lib/portage/bin/dohtml
./usr/lib/portage/bin/doinfo
./usr/lib/portage/bin/dosbin
./usr/lib/portage/bin/emerge
./usr/lib/portage/bin/fowners
./usr/lib/portage/bin/fperms
./usr/lib/portage/bin/newenvd
./usr/lib/portage/bin/newsbin
./usr/lib/portage/bin/prepallman
./usr/lib/portage/bin/pkgmerge.new
./usr/lib/portage/bin/db-update.py
./usr/lib/portage/bin/newbin
./usr/lib/portage/bin/newdoc
./usr/lib/portage/bin/newexe
./usr/lib/portage/bin/newins
./usr/lib/portage/bin/newman
./usr/lib/portage/bin/fixvardbentries
./usr/lib/portage/bin/dispatch-conf
./usr/lib/portage/bin/md5check.py
./usr/lib/portage/bin/md5check.sh
./usr/lib/portage/bin/ebuild.sh
./usr/lib/portage/bin/preplib.so
./usr/lib/portage/bin/pkgmerge
./usr/lib/portage/bin/prepinfo
./usr/lib/portage/bin/prepallstrip
./usr/lib/portage/bin/newconfd
./usr/lib/portage/bin/newinitd
./usr/lib/portage/bin/newlib.a
./usr/lib/portage/bin/quickpkg
./usr/lib/portage/bin/prepalldocs
./usr/lib/portage/bin/prepallinfo
./usr/lib/portage/bin/env-update.sh
./usr/lib/portage/bin/pkgname
./usr/lib/portage/bin/newlib.so
./usr/lib/portage/bin/find-requires
./usr/lib/portage/bin/tbz2tool
./usr/lib/portage/bin/fixvirtuals
./usr/lib/portage/bin/prepall
./usr/lib/portage/bin/preplib
./usr/lib/portage/bin/prepman
./usr/lib/portage/lib/
./usr/lib/portage/lib/sandbox.bashrc
./usr/lib/portage/pym/
./usr/lib/portage/pym/portage_const.py
./usr/lib/portage/pym/portage_db_anydbm.py
./usr/lib/portage/pym/xpak.py
./usr/lib/portage/pym/portage.py
./usr/lib/portage/pym/portage_dep.py
./usr/lib/portage/pym/portage_db_test.py
./usr/lib/portage/pym/portage_exception.py
./usr/lib/portage/pym/portage_data.py
./usr/lib/portage/pym/portage_db_flat.py
./usr/lib/portage/pym/portage_gpg.py
./usr/lib/portage/pym/portage_locks.py
./usr/lib/portage/pym/portage_checksum.py
./usr/lib/portage/pym/dispatch_conf.py
./usr/lib/portage/pym/dcdialog.py
./usr/lib/portage/pym/portage_contents.py
./usr/lib/portage/pym/portage_localization.py
./usr/lib/portage/pym/portage_db_cpickle.py
./usr/lib/portage/pym/portage_file.py
./usr/lib/portage/pym/getbinpkg.py
./usr/lib/portage/pym/portage_exec.py
./usr/lib/portage/pym/cvstree.py
./usr/lib/portage/pym/output.py
./usr/lib/portage/pym/emergehelp.py
./usr/lib/portage/pym/portage_db_template.py
./usr/lib/portage/pym/portage_util.py
./usr/sbin/
./usr/sbin/fixpackages
./usr/sbin/env-update
./usr/sbin/etc-update
./usr/sbin/emerge-webrsync
./usr/sbin/regenworld
./usr/sbin/archive-conf
./usr/sbin/ebuild
./usr/sbin/dispatch-conf
./usr/sbin/ebuild.sh
./usr/sbin/pkgmerge
./usr/share/
./usr/share/doc/
./usr/share/doc/portage-2.0.51-r14/
./usr/share/doc/portage-2.0.51-r14/ChangeLog.gz
./usr/share/man/
./usr/share/man/man1/
./usr/share/man/man1/ebuild.1.gz
./usr/share/man/man1/repoman.1.gz
./usr/share/man/man1/etc-update.1.gz
./usr/share/man/man1/emerge.1.gz
./usr/share/man/man1/quickpkg.1.gz
./usr/share/man/man1/env-update.1.gz
./usr/share/man/man1/dispatch-conf.1.gz
./usr/share/man/man1/g-cpan.pl.1.gz
./usr/share/man/man5/
./usr/share/man/man5/ebuild.5.gz
./usr/share/man/man5/portage.5.gz
./usr/share/man/man5/make.conf.5.gz
bzip2: (stdin): trailing garbage after EOF ignored
tar: Error exit delayed from previous errors
/tmp/install-portage.sh: line 56: cd: /tmp/portage-2.0.51.18/src/python-missingos: No such file or directory
/tmp/install-portage.sh: line 57: ./setup.py: No such file or directory
/tmp/install-portage.sh: line 58: cd: ../sandbox-1.1: No such file or directory
make: *** No targets specified and no makefile found. Stop.
/tmp/install-portage.sh: line 60: cd: ../../cnf: No such file or directory
cp: omitting directory `etc'
cp: omitting directory `lib'
cp: omitting directory `usr'
cp: omitting directory `var'
linux:/home/pankaj # |
any idea? |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Fri Apr 15, 2005 2:37 pm Post subject: |
|
|
dearborn98 wrote: | Was able to install portage on SUSE 9.1 . Had problems with this part of the script:
cd ../src/python-missingos
./setup.py install
Showed errors relating to python, even after changing the python2.2 to python2.3 in the setup.py script. |
those errors are fine. if you have python2.3 installed, you don't even need python-missingos. that's the reason script ignores these errors. You didn't need to change the script and include rescue tar in it for that.
rush_ad, try to run the script from page 1 of this thread. |
|
Back to top |
|
|
dearborn98 n00b
Joined: 30 Nov 2004 Posts: 19
|
Posted: Thu Apr 28, 2005 12:01 am Post subject: |
|
|
Devsk:
Had problems running your script on pre-SuSE 9.2 versions as a bash script. Other versions of SuSE would stop in the middle of the script with errors, and then the system was broke. Because of this, I had been pasting it line for line (with some modifications) to get portage installed successfully on SuSE.
Decided to try to run your script again as a bash script on SuSE 9.2 (as you suggested to rush_ad.) The script ran all the way through with SuSE 9.2 successfully.
As you said, the python-2.3 did made the difference. Thanks for all the info. |
|
Back to top |
|
|
raid517 l33t
Joined: 06 Mar 2003 Posts: 946
|
Posted: Thu Apr 28, 2005 12:27 am Post subject: |
|
|
A much simpler way to do this is just to install Gentoo in a chroot environment and run gentoo applications directly from your chroot directory. I do this with both Debian and Gentoo. Indeed you can have any package manager you want if you do things this way.And you have less danger of breaking things.
GJ |
|
Back to top |
|
|
dlong500 n00b
Joined: 11 Jun 2004 Posts: 17 Location: Midlothian, VA
|
Posted: Thu May 05, 2005 5:52 am Post subject: |
|
|
raid517 wrote: | A much simpler way to do this is just to install Gentoo in a chroot environment and run gentoo applications directly from your chroot directory. I do this with both Debian and Gentoo. Indeed you can have any package manager you want if you do things this way.And you have less danger of breaking things. |
That may work for many cases, but I would be concerned with the overhead of essentially running two operating systems especially for things like web servers. However, in my specific case I am locked into a Redhat system running a Virtuozzo VPS (Virtual Private Server). It is not possible (at least at the current time) to install another kernel in a chrooted environment on a VPS, so that is why I wanted to be able to use portage natively within the Redhat OS. If I wasn't locked into Redhat on the base system I would most certainly choose Gentoo as my OS anyway and forego all this complication, but alas, I cannot as of yet... |
|
Back to top |
|
|
raid517 l33t
Joined: 06 Mar 2003 Posts: 946
|
Posted: Thu May 05, 2005 6:12 am Post subject: |
|
|
You don't 'run two operating systems.' You only run one. The chroot simply runs using your installed kernel and is only active when installing applications. You cannot run 'two kernels simultaniously' - not unless you are using a virtual machine, or some other kind of exotic set up. All you are doing is using chroot to install applications from one distribution into another. You want Debian in Gentoo, Gentoo in Debian, Red Hat in Suse? No problem. The choice is yours.
You really ought to read up on chroot. It requires none of this complicated messing about - nor will it risk harming your original OS install - as most of these other methods always (in time) eventually do.
GJ |
|
Back to top |
|
|
rush_ad l33t
Joined: 22 Jul 2004 Posts: 863 Location: New Jersey, USA
|
Posted: Sun May 15, 2005 12:18 pm Post subject: |
|
|
i installed portage on suse 9.3 using the script on first page. everything was fine.
then i tried "emerge vlc" and it told me that it needs to install 101 packages. what do i do? and when i tried "emerge -O vlc" it worked. |
|
Back to top |
|
|
raid517 l33t
Joined: 06 Mar 2003 Posts: 946
|
Posted: Sun May 15, 2005 12:42 pm Post subject: |
|
|
You do it at your own risk. However my experience of these kinds of scripts is that eventually they all seriously screw something up.
GJ |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sun May 15, 2005 6:35 pm Post subject: |
|
|
rush_ad wrote: | i installed portage on suse 9.3 using the script on first page. everything was fine.
then i tried "emerge vlc" and it told me that it needs to install 101 packages. what do i do? and when i tried "emerge -O vlc" it worked. | portage doesn't know about the packages which are already installed in suse. you have two options: 1. overwrite those packages with the ones from portage OR 2. let portage know about them. You can use the following to create /etc/portage/profile/package.provided file which is a plain list of packages which you don't want portage to install.
Code: |
mkdir -p /etc/portage/profile
emerge -pv --nocolor vlc|grep "ebuild "|awk '{print $4}' >> /etc/portage/profile/package.provided
|
then have a look at the file /etc/portage/profile/package.provided and remove the packages which you want portage to install/overwrite.
raid517: you need to qualify your statement: they can seriously screw something up if you don't know what they or YOU are doing. |
|
Back to top |
|
|
raid517 l33t
Joined: 06 Mar 2003 Posts: 946
|
Posted: Sun May 15, 2005 8:15 pm Post subject: |
|
|
I'll qualify it with this... They can lead to sometimes seemingly unresolvable conflicts that are often way too much more hassle to resolve than the effort to fix them is worth. Sure they can be overcome, sure they can be fixed - but it's a bit like in the world of Debian. It's not considered safe to even mix packages from different repositories or Debian based distributions - let alone mix entirely different Linux versions.
In any case as I have said I personally have a preference for chroot - like I said, I can keep my 'other OS' in a sandpit and prevent them from interacting with my main OS almost completely. Yet I can still run any application I want from them at will. I of course acknowledge that this may not be everyone else's preference.
Best regards,
GJ |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sun May 15, 2005 9:31 pm Post subject: |
|
|
I have yet to see an example of such inconsistency so far. I have been running nitro2 kernel emerged from portage on FC2 for a year, with working suspend to disk, bootsplash and some other very bleeding edge features. most of the other stuff I use also comes from portage. no problems so far. Otherwise I would be looking at FC3 by now. It all depends on how much one knows about what's happening when one emerges a package. |
|
Back to top |
|
|
raid517 l33t
Joined: 06 Mar 2003 Posts: 946
|
Posted: Sun May 15, 2005 10:21 pm Post subject: |
|
|
Like I said, you can fix most things. But don't underestimate the level of knowledge that is required. Not everone has this immediately to hand. A competant hacker can fix almost anything - but that isn't true of everyone.
You can take your pick I guess. A chroot can be set up, installed and run by a n00b in a matter of a few minutes - but like I said too, a serious hacker might prefer a more 'intergrated approach.' The end result in any case is the same.
Besides which, after a year of running your install, I doubt there will be very much left of your original Fedora install? Isn't it pretty much just pure Gentoo by now?
I only suggested this method as a quick and safe way to run packages for one OS inside another. I didn't mean to ruffle anyone's feathers in doing so.
I guess it is just all about choice.
GJ |
|
Back to top |
|
|
devsk Advocate
Joined: 24 Oct 2003 Posts: 2995 Location: Bay Area, CA
|
Posted: Sun May 15, 2005 10:30 pm Post subject: |
|
|
I think we are both right.... |
|
Back to top |
|
|
chakkaradeepcc n00b
Joined: 25 Feb 2005 Posts: 25
|
Posted: Sat May 28, 2005 9:33 am Post subject: |
|
|
hi all,
am using LFS as my base system..when i ran the script i was able to "emerge rsync" and i do have my "/usr/portage" files....but stll am not able to perform any step after that becoz it is telling there is no symlink to "/etc/make.profile"...what is this file and it also tells "your ARCH is not set"........how do i rectify this error??...
i would be happy if somebdy help me out..
with regards,
C.C.Chakkaradeep |
|
Back to top |
|
|
|