Hi, 1. About the path - see for you self: homesrv:~# pwd /root homesrv:~# cat .profile # ~/.profile: executed by Bourne-compatible login shells.
if [ -f ~/.bashrc ]; then . ~/.bashrc fi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X 11 export PATH mesg n homesrv:~# Notice that root's .profile sets the path not adding to the system path (/etc/profile) but over-writes it (security reasons). 2. As I said in my previous mail, I burned you the US version of the installation file. The one which you bought form the site is NON_US. Here are the file sizes (from mirrors.sunsite.dk): debian-30r1-i386-binary-1.iso 584M debian-30r1-i386-binary-1_NONUS.iso 647M 3. Under cdrecord it reports the amount of bytes burned from the total bytes of the ISO file. If they are qual, and I get no errors - I guess the burning process is ok. About your burning - I guess the same method will be ok. 4. I guess is worth a thought about sending people the NON_US version. Thanks for making me check that issue again. 5. Good luck (again) ! Regards, Lior Kaplan [EMAIL PROTECTED] http://www.Guides.co.il Come to write at the forums: http://www.guides.co.il/forums ----- Original Message ----- From: "avraham.rosenberg" <[EMAIL PROTECTED]> To: "Lior Kaplan" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 10, 2003 6:32 PM Subject: Re: path problems > First, thanks to all those who answered. > Now, specifically to Lior: > I'll answer in reverse order: > 4- Are you certain that the root path is undefined unless one define it in > the /root/.profile file? I am pretty sure it is devined, or built > gradually in the phases of the init process. I cannot swear for debian, > but I have a slackware 8.0 installation which I am only rarely using in > which there is no /root/.bashrc, /root/.profile, or /root/.bash_profile > file but echo $PATH gives the complete right answer. I checked it 10 > minutes ago. I remember that, when trying to find the cause of the problem > myself, in debian, I "grep-ed" in /etc some files which set or appended > directories to the path. I would "buy" gladly your explanation, but I am > affraid you are wrong. > 3-The output of the apt-cdrom ident, df /cdrom/ and find /cdrom/ -empty > for the two disks are: > for yours: > Identifying.. [7ca46d7ea14606c63fa4880088c78409-2] > Stored Label: 'Debian GNU/Linux 3.0 r1 _Woody_ > - Official i386 Binary-1 (20021218)' > /cdrom/dists/woody/contrib/binary-i386/Packages > /cdrom/dists/woody/contrib/source > /cdrom/dists/woody/main/source > /cdrom/dists/woody/non-US/contrib/binary-i386/Packages > /cdrom/dists/woody/non-US/contrib/source > /cdrom/dists/woody/non-US/main/binary-i386/Packages > /cdrom/dists/woody/non-US/main/source > /cdrom/.disk/base_installable > /cdrom/.disk/kernel_installable > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/cdrom 597728 597728 0 100% /cdrom > for the other: > Identifying.. [04c27238e58cc8e54279d0493834e204-2] > Stored Label: 'Debian GNU/Linux 3.0 r1 _Woody_ > - Official i386 Binary-1 (20021218)' > /cdrom/dists/woody/contrib/binary-i386/Packages > /cdrom/dists/woody/contrib/source > /cdrom/dists/woody/main/source > /cdrom/dists/woody/non-US/contrib/source > /cdrom/dists/woody/non-US/main/source > /cdrom/.disk/base_installable > /cdrom/.disk/kernel_installable > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/cdrom 662496 662496 0 100% /cdrom > > Seems to be the same disk, though yours is leaner, although find -empty > does not report anything suspect > > 2-I did not intend to assert, imply, suggest -chose your expression- that > you did not check your work. Being new to Debian, I wondered if there are > not different types of CDROM packages, so that your disk, which served for > the installation would not be completely compatible with those I used > later on. > 2b- Asd an aside, the checksum check verifies the download, but not the > roasting process. After getting the complete set, in order to avoid > carying them on my back to and from work, I decided to make a copy. As it > happened, I had only six verbatim blanks, so I used a "no brand name" one > for the seventh. As I had my doubts about their quality, I compared in a > for loop every corresponding pair of files from original and copy. Lo and > behold, three packages did not pass the test > 1-I can't answer that question yet. I am still trying. And a combination > of little spare time and lack of concentration which cause many mistakes, > will assure that the learning will take some time. I'll write you by then. > Bye, Avraham > > On Wed, 10 Sep 2003, Lior Kaplan wrote: > > > Hi Avraham, > > > > 1. How did you installed to offline packages? using dpkg or apt-get? Did you > > create your repository localy? > > 2. I checked the MD5 sum of the iso file from which I burned the cds. It's > > indentical to the one at > > http://mirrors.sunsite.dk/debian-cd/images/3.0_r1/i386/MD5SUMS > > (debian-30r1-i386-binary-1.iso) > > 3. You might have to the NON_US version of disc 1 > > (debian-30r1-i386-binary-1_NONUS.iso). Check it. > > 4. Please check to last modified date on file like /root/.profile to see if > > anything was done to them. Root's path is set there. You may also want to > > check the file content. > > > > Good Luck, > > > > Lior Kaplan > > [EMAIL PROTECTED] > > http://www.Guides.co.il > > > > Come to write at the forums: http://www.guides.co.il/forums > > > > ----- Original Message ----- > > From: "avraham.rosenberg" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, September 10, 2003 8:58 AM > > Subject: path problems > > > > > > > Hi, > > > I am using Debian 30r1 both at home and at work. In both cases the > > > system > > > was installed from a CDROM copy bought from Lior. At home, because the > > > computer is not connected directly to the internet and at work because I > > > am behind a firewall and it took me some time to find out the name of the > > > proxy server and to configure get-apt. In the meantime I bought the set of > > > 7 CDROMS from a site in the US, installed all that I needed and started > > > using it. > > > In the meantime I configured apt at work to fetch the files from some ftp > > > and http servers and started to learn how to obtain there the > > > packages that I need for my home computer (apt-get offline method). But > > > yesterday, without (knowingly) doing anything wrong, bash announced me > > > (root) that it does not know the command apt-get. > > > A rapid check showed that all sbin directories have disappeared from my > > > root path. A rapid fix was to add them manually, and insert this line also > > > in the .bash_profile of the root. But I would like to find out where the > > > init process changed, resulting in the mangled path. And why. > > > Any suggestions. > > > Maybe it is relevant to mention that the first CD from Lior -though > > > version 3.0r1 as well- has a different ID and a different content (less > > > packages) than the corresponding CD from the complete set. I also > > > bought from him CD-s 2 and 3. These are identical with those from the > > > complete set. > > > The same problem occured with my home home computer some time ago. But in > > > that case I cannot claim my innocence, as I was very tired and I may have > > > blundered somewhere. > > > The machine at home is a celeron 600 MHz. The one at work a Pentium 4 1600 > > > MHz. > > > Thanks, Avraham > > > > > > > > > > > > ================================================================= > > > To unsubscribe, send mail to [EMAIL PROTECTED] with > > > the word "unsubscribe" in the message body, e.g., run the command > > > echo unsubscribe | mail [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
