My First Step - Page 3

anticapitalista · posted: 2011-01-26 14:40

For the testing repo, change testing to squeeze

Or try advice at end of this thread.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://justlinux.com/forum/archive/index.php/t-144101.html"
linktext was:"http://justlinux.com/forum/archive/inde ... 44101.html"
====================================

TheForsaken · posted: 2011-01-26 15:32

anticapitalista wrote:For the testing repo, change testing to squeeze

Or try advice at end of this thread.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://justlinux.com/forum/archive/index.php/t-144101.html"
linktext was:"http://justlinux.com/forum/archive/inde ... 44101.html"
====================================

Attached is a screen shot for the repositories in Synaptic.

Sorry but I did not understand your post. Could you explain more please?

Thank you!

masinick · posted: 2011-01-26 16:50

When you select each of the repositories listed in synaptic, notice - as in your image - that"Distribution" is listed, and currently it is set to testing. If you want to continue with the rolling release of Debian, which is currently Squeeze, but will soon become Wheezy, then keep this as it is. But if you want to continue to use the Squeeze release as it moves from testing to stable, then replace the name testing where"Distribution" is listed with squeeze, and you will stay with the Squeeze release as it becomes stable (which, if all work out well, will be next week).

Do this for each repository currently containing a"testing" entry; change each of them to squeeze to follow the Squeeze release.

TheForsaken · posted: 2011-01-26 18:48

Thank you so much for your reply __{{emoticon}}__

masinick wrote:When you select each of the repositories listed in synaptic, notice - as in your image - that"Distribution" is listed, and currently it is set to testing.

Yes, I have noticed that and I realized immediately that it's because antiX is based on Debian Testing not Stable.

If you want to continue with the rolling release of Debian, which is currently Squeeze, but will soon become Wheezy, then keep this as it is. But if you want to continue to use the Squeeze release as it moves from testing to stable, then replace the name testing where"Distribution" is listed with squeeze, and you will stay with the Squeeze release as it becomes stable (which, if all work out well, will be next week).

I was about to ask whether I could choose"Stable" instead of"Testing" mirrors but still not sure if that possible. You're talking about replacing the name not to un-tick"Testing mirrors" and tick on"Stable" ones.

Is there any difference? which one is better? when you say"rolling release" does that mean new releases? new versions?
If I'm going to keep everything as it's, then the same error will occur again.
I guess in my case, there's no other option but to change it. Am I right? sorry but I'm still a bit confuse.

Do this for each repository currently containing a"testing" entry; change each of them to squeeze to follow the Squeeze release.

Ok, I have replaced"testing" with"squeeze" but ...

Code: Select all

Hit http://www.debian-multimedia.org squeeze Release.gpg
Ign http://www.debian-multimedia.org squeeze/main Translation-en_US            
Ign http://www.debian-multimedia.org squeeze/non-free Translation-en_US        
Hit http://www.debian-multimedia.org squeeze Release                           
Get:1 http://www.debian-multimedia.org squeeze/main Packages/DiffIndex [2,023B]
Get:2 http://www.debian-multimedia.org squeeze/non-free Packages/DiffIndex [2,023B]
Ign http://security.debian.org squeeze Release.gpg                             
Ign http://security.debian.org squeeze/main Translation-en_US                  
Ign http://security.debian.org squeeze/contrib Translation-en_US               
Ign http://security.debian.org squeeze/non-free Translation-en_US              
Ign http://security.debian.org squeeze Release                                 
Ign http://security.debian.org squeeze/main Packages                           
Ign http://security.debian.org squeeze/contrib Packages                        
Ign http://security.debian.org squeeze/non-free Packages                       
Ign http://security.debian.org squeeze/main Packages                           
Ign http://security.debian.org squeeze/contrib Packages
Ign http://security.debian.org squeeze/non-free Packages
Err http://security.debian.org squeeze/main Packages
  404  Not Found [IP: 195.20.242.89 80]
Err http://security.debian.org squeeze/contrib Packages
  404  Not Found [IP: 195.20.242.89 80]
Err http://security.debian.org squeeze/non-free Packages
  404  Not Found [IP: 195.20.242.89 80]
Hit http://ftp.us.debian.org squeeze Release.gpg
Ign http://ftp.us.debian.org squeeze/main Translation-en_US
Ign http://ftp.us.debian.org squeeze/contrib Translation-en_US
Ign http://ftp.us.debian.org squeeze/non-free Translation-en_US
Hit http://ftp.us.debian.org squeeze Release
Get:3 http://ftp.us.debian.org squeeze/main Packages/DiffIndex [2,038B]
Get:4 http://ftp.us.debian.org squeeze/contrib Packages/DiffIndex [2,023B]
Get:5 http://ftp.us.debian.org squeeze/non-free Packages/DiffIndex [2,023B]    
Fetched 10.1kB in 37s (270B/s)                                                 
W: Failed to fetch http://security.debian.org/dists/squeeze/main/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

W: Failed to fetch http://security.debian.org/dists/squeeze/contrib/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

W: Failed to fetch http://security.debian.org/dists/squeeze/non-free/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

E: Some index files failed to download, they have been ignored, or old ones used instead.

anticapitalista · posted: 2011-01-26 19:01

Leave this one as is.
deb
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://security.debian.org/"
linktext was:"http://security.debian.org/"
====================================
testing/updates main contrib non-free

Now do apt-get install debian-archive-keyring

Then change the squeeze back to testing and see if it updates ok

masinick · posted: 2011-01-26 19:07

For another week or two, the Security repository probably won't be available, but as soon as Squeeze actually becomes the stable Debian release, the Security repository will become active. Until then, you will want to disable (or uncheck) that repository, and in a couple of weeks, you can enable it again.

Right now, Squeeze still is in testing.

Stable always equals the stable repository. At the moment, it is still Lenny. Soon it will be Squeeze.

Stable always points to the stable repository.

Testing always points to the testing repository.

The release names always point to that particular release, but they may vary from testing (as Squeeze happens to be at the moment), to stable, once they become the stable release.

Sid always points to the unstable repository.

I hope that is helpful, but if not, please ask for further clarification and I will try to help.

The suggestion that anticapitalista made, of course, should also work, depending on what you need.

TheForsaken · posted: 2011-01-26 19:08

anticapitalista wrote:Leave this one as is.
deb
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://security.debian.org/"
linktext was:"http://security.debian.org/"
====================================
testing/updates main contrib non-free

Now do apt-get install debian-archive-keyring

Then change the squeeze back to testing and see if it updates ok

Before I do what you suggested, I'd like to tell you this __{{emoticon}}__

I got this:

Code: Select all

Get:1 http://www.debian-multimedia.org stable Release.gpg [198B]
Hit http://security.debian.org stable/updates Release.gpg                
Get:2 http://ftp.us.debian.org stable Release.gpg [1,033B]
Ign http://www.debian-multimedia.org stable/main Translation-en_US          
Ign http://security.debian.org stable/updates/main Translation-en_US 
Ign http://www.debian-multimedia.org stable/non-free Translation-en_US
Get:3 http://www.debian-multimedia.org stable Release [26.5kB]       
Ign http://security.debian.org stable/updates/contrib Translation-en_US    
Ign http://security.debian.org stable/updates/non-free Translation-en_US     
Hit http://security.debian.org stable/updates Release                  
Ign http://ftp.us.debian.org stable/main Translation-en_US             
Ign http://ftp.us.debian.org stable/contrib Translation-en_US        
Get:4 http://www.debian-multimedia.org stable/main Packages/DiffIndex [2,023B]
Get:5 http://www.debian-multimedia.org stable/non-free Packages/DiffIndex [2,023B]
Ign http://security.debian.org stable/updates/main Packages/DiffIndex         
Ign http://ftp.us.debian.org stable/non-free Translation-en_US
Ign http://security.debian.org stable/updates/contrib Packages/DiffIndex
Ign http://security.debian.org stable/updates/non-free Packages/DiffIndex
Hit http://security.debian.org stable/updates/main Packages
Hit http://security.debian.org stable/updates/contrib Packages                
Hit http://security.debian.org stable/updates/non-free Packages               
Get:6 http://ftp.us.debian.org stable Release [73.8kB]                         
Get:7 http://ftp.us.debian.org stable/main Packages [5,193kB]                  
Get:8 http://ftp.us.debian.org stable/contrib Packages [76.2kB]                
Get:9 http://ftp.us.debian.org stable/non-free Packages [100kB]                
Fetched 5,475kB in 3min 48s (24.0kB/s)                                         
Reading package lists... Done

After I choose the"stable" mirrors as shown in the screen shot.

Shall I keep everything as it's now or shall I try your suggestion?

Thank you so much __{{emoticon}}__

masinick · posted: 2011-01-26 19:18

That's one way to go, but right now, stable points to Debian Lenny, and except for bug fixes and security updates, it is mostly software from 2009. In a couple of weeks, when Squeeze gets moved to stable, they will be one and the same thing.

My suggestion would be to do what anticapitalista suggested, namely keep the security repo at testing until the release comes out, and rename the other repos from testing to Squeeze. You'll only have to change the security repo from testing to squeeze in a couple of weeks after the release; everything else will remain the same. That is, in a couple of weeks, it will all, in effect, become"stable". But right now, if you change everything to stable, what you will be getting are Lenny packages. If you have already installed antiX, you probably won't get any package changes at all, but there is a possibility of some confusion, and therefore I would recommend anti's approach.

TheForsaken · posted: 2011-01-26 19:20

masinick wrote:For another week or two, the Security repository probably won't be available, but as soon as Squeeze actually becomes the stable Debian release, the Security repository will become active. Until then, you will want to disable (or uncheck) that repository, and in a couple of weeks, you can enable it again.

Right now, Squeeze still is in testing.

Stable always equals the stable repository. At the moment, it is still Lenny. Soon it will be Squeeze.

Stable always points to the stable repository.

Testing always points to the testing repository.

The release names always point to that particular release, but they may vary from testing (as Squeeze happens to be at the moment), to stable, once they become the stable release.

Sid always points to the unstable repository.

I hope that is helpful, but if not, please ask for further clarification and I will try to help.

The suggestion that anticapitalista made, of course, should also work, depending on what you need.

Thanks again.
I just checked this:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.debian.org/releases/"
linktext was:"http://www.debian.org/releases/"
====================================

The current"stable" distribution of Debian GNU/Linux is version 5.0.8, codenamed lenny. It was released on January 22nd, 2011.

So, if Lenny is the"stable" distribution of Debian and it was released few days ago, how come another one"squeeze" is going to be released as"stable"? I thought it's 6 months-cycle right? perhaps I need to read more about Debian!

What about MEPIS? can't I choose its mirror and use that?

masinick · posted: 2011-01-26 19:39

Debian has not had a completely new stable release since February 2009, the original Debian Version 5.0, the"Lenny" release. It has had a number of"updates"; I believe they are up to 5.0.7 or 5.0.8, and one of those was only recently released. All that means it is is a updated image of the bug fixes and security changes since the original Version 5 release, which is called Lenny. Those who already have a Lenny based system do not need to get those systems, all they need to do is update their system with the current package changes for bug fixes and security related changes. Frankly there are not that many of them.

Squeeze is not yet stable; it is in"Release Candidate" stage, with the anticipated release some time near February 5-6, 2011.

I would recommend keeping with"testing" or"squeeze" for a couple more weeks. In the case of the main repositories, renaming them from testing to squeeze right now is a good idea; you won't have to change them again - that's if you are hoping to go with the soon to be released"stable" release, which is soon to become Squeeze. The security repository names, at the present time, are stable, Lenny, or testing. Squeeze, since it is not yet officially stable, does not have a security repository in place.

The Debian release calendar over the past few releases has been approximately a two year cycle, not a six month cycle. It is Ubuntu that has a six month release cycle, not Debian.

Going back, I'd recommend either leaving all the repos at testing until February 5-6. or change the main repository to squeeze now, and leave the security repo at testing until the release. That's if your intention, going forward, is to continue running the stable release. If you change your mind and decide to go with the testing release, then just set them all to testing and leave them that way indefinitely. By early to mid February, that could potentially result in a lot of package changes when the testing release changes from Squeeze to Wheezy. If you want stable, make the main repo squeeze now and keep the security repo testing until February 5-6, then change it to squeeze.

Hope this is not confusing you!

TheForsaken · posted: 2011-01-26 19:53

anticapitalista wrote:Leave this one as is.
deb
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://security.debian.org/"
linktext was:"http://security.debian.org/"
====================================
testing/updates main contrib non-free

Now do apt-get install debian-archive-keyring

Code: Select all

apt-get install debian-archive-keyring

Reading package lists... Done
Building dependency tree       
Reading state information... Done
debian-archive-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Then change the squeeze back to testing and see if it updates ok

Code: Select all

apt-get update

Get:1 http://www.debian-multimedia.org testing Release.gpg [198B]
Ign http://security.debian.org testing Release.gpg                             
Ign http://www.debian-multimedia.org testing/main Translation-en_US            
Ign http://www.debian-multimedia.org testing/non-free Translation-en_US        
Hit http://www.debian-multimedia.org testing Release                           
Err http://www.debian-multimedia.org testing Release                           
  
Get:2 http://www.debian-multimedia.org testing Release [26.7kB]                
Ign http://www.debian-multimedia.org testing Release                           
Get:3 http://www.debian-multimedia.org testing/main Packages/DiffIndex [2,023B]
Ign http://security.debian.org testing/main Translation-en_US                  
Ign http://security.debian.org testing/contrib Translation-en_US
Get:4 http://www.debian-multimedia.org testing/non-free Packages/DiffIndex [2,023B]
Ign http://security.debian.org testing/non-free Translation-en_US              
Ign http://security.debian.org testing Release             
Ign http://security.debian.org testing/main Packages       
Ign http://security.debian.org testing/contrib Packages
Ign http://security.debian.org testing/non-free Packages   
Ign http://security.debian.org testing/main Packages       
Ign http://security.debian.org testing/contrib Packages    
Ign http://security.debian.org testing/non-free Packages   
Err http://security.debian.org testing/main Packages                                                                        
  404  Not Found [IP: 195.20.242.89 80]
Err http://security.debian.org testing/contrib Packages                                                                     
  404  Not Found [IP: 195.20.242.89 80]
Err http://security.debian.org testing/non-free Packages                                                                    
  404  Not Found [IP: 195.20.242.89 80]
Err http://ftp.us.debian.org testing Release.gpg                                                                            
  Temporary failure resolving 'ftp.us.debian.org'
Err http://ftp.us.debian.org testing/main Translation-en_US
  Temporary failure resolving 'ftp.us.debian.org'
Err http://ftp.us.debian.org testing/contrib Translation-en_US
  Temporary failure resolving 'ftp.us.debian.org'
Ign http://ftp.us.debian.org testing/non-free Translation-en_US
Fetched 31.0kB in 1min 7s (456B/s)
Reading package lists... Done
W: GPG error: http://www.debian-multimedia.org testing Release: The following signatures were invalid: BADSIG 07DC563D1F41B907 Christian Marillat <marillat@debian.org>
W: Failed to fetch http://ftp.us.debian.org/debian/dists/testing/Release.gpg  Temporary failure resolving 'ftp.us.debian.org'

W: Failed to fetch http://ftp.us.debian.org/debian/dists/testing/main/i18n/Translation-en_US.bz2  Temporary failure resolving 'ftp.us.debian.org'

W: Failed to fetch http://ftp.us.debian.org/debian/dists/testing/contrib/i18n/Translation-en_US.bz2  Temporary failure resolving 'ftp.us.debian.org'

W: Failed to fetch http://security.debian.org/dists/testing/main/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

W: Failed to fetch http://security.debian.org/dists/testing/contrib/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

W: Failed to fetch http://security.debian.org/dists/testing/non-free/binary-i386/Packages.gz  404  Not Found [IP: 195.20.242.89 80]

W: Some index files failed to download, they have been ignored, or old ones used instead.

__{{emoticon}}__
I don't know what more shall we try?

masinick · posted: 2011-01-26 21:22

Go back to my first suggestion then; uncheck or comment out the security repo until Squeeze becomes the stable release. While you have testing enabled, you will get all of the latest packages anyway. If you stay with testing, don't worry about Security updates; you will get the changes as they come in. If you decide to go with Stable once the release comes out, just change everything to squeeze once released, and meanwhile just stick with testing and the security repo disabled, and you should be good to go.

TheForsaken · posted: 2011-01-26 23:33

TheForsaken wrote:Kernel Panic __{{emoticon}}__

SliTaz: /boot/grub/menu.lst
Code: Select all
# /boot/grub/menu.lst: GRUB boot loader configuration.
#

# By default, boot the first entry.
default 0

# Boot automatically after 8 secs.
timeout 8

# Change the colors.
color yellow/brown light-green/black

# For booting SliTaz from : /dev/hdb6
#
title SliTaz GNU/Linux (cooking) (Kernel vmlinuz-2.6.30.6-slitaz)
root (hd1,5)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/hdb6
The output of the command
Code: Select all
ls -l /dev/disk/by-uuid
is:
Code: Select all
total 0
lrwxrwxrwx 1 root root 10 2011-01-26 10:36 2f42dc15-6728-4961-b176-7824f9f80dab -> ../../sda6
antiX: /boot/grub/menu.lst
Code: Select all
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title antiX at sda1, kernel 2.6.32-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/sda1 nomce quiet nosplash vga=791 
initrd /boot/initrd.img-2.6.32-1-mepis-smp
boot

title SliTaz at sda6 (Kernel vmlinuz-2.6.30.6-slitaz)
root (hd0,5)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=UUID=2f42dc15-6728-4961-b176-7824f9f80dab
I'm not sure if there's a solution for this problem.
Problem is here: root (hd0,5)

Before it's a problem here: kernel /boot/vmlinuz-2.6.30.6-slitaz root=UUID=2f42dc15-6728-4961-b176-7824f9f80dab

When GRUB pass the control to SliTaz to boot, the entries are not the same as GRUB passing"(hd0,5)" while SliTaz doesn't understand anything but"(hd1,5)".

Why SliTaz is doing that?
Because I'm using a SLAVE HDD as I mentioned in my first post regarding this issue.

SliTaz is using /dev/hdX so hd system detects Master and Slave thus it is"hdb" not even"hda".

On the other hand, antiX is using"/dev/sdX" system so it doesn't matter whether the HDD is Master or Slave, it's"sda" in all cases.

That's the problem. I know it but I have no clue how to fix it?!

I know the problem could be solved with GRUB2 but not really sure whether that's possible to do in antiX or not?
I'll try to install GRUB2 in antiX hopefully it will work and hopefully that would fix the issue. Otherwise, I'm not sure what more we could try here?

Thanks!

Sorry to go back to this problem but I'd like to let you know that I have managed to fix it.
Now, I can login to both antiX and SliTaz without any problems at all __{{emoticon}}__ HOOHAA __{{emoticon}}__

I knew it. GRUB2 is the only solution and the easiest solution for this issue. NO, I did not install a third OS, I just upgraded GRUB Legacy in antiX and I have now GRUB2 UP and RUNNING __{{emoticon}}__

GRUB2 ROCKS, period __{{emoticon}}__

Now, back to my other issue with Synaptic __{{emoticon}}__

TheForsaken · posted: 2011-01-26 23:36

masinick wrote:Go back to my first suggestion then; uncheck or comment out the security repo until Squeeze becomes the stable release. While you have testing enabled, you will get all of the latest packages anyway. If you stay with testing, don't worry about Security updates; you will get the changes as they come in. If you decide to go with Stable once the release comes out, just change everything to squeeze once released, and meanwhile just stick with testing and the security repo disabled, and you should be good to go.

I'm going to try again tomorrow. It's too late here and I feel so exhausted. I was trying to fix that for many hours beside doing other stuff so I need to sleep now.

I'll let you know what will happen __{{emoticon}}__

Thank you so much!

masinick · posted: 2011-01-27 03:12

Well, you have made some progress, that's for sure. Good luck with it; I hope you are learning a lot! On the GRUB thing, yes, GRUB 2 can recognize systems. It is certainly possible (and in some ways easier) to edit entries with GRUB Legacy, so that is the trade-off: GRUB Legacy, once you become familiar with it, is very easy to edit - you edit the file /boot/grub/menu.lst. With GRUB 2, you run update-grub and let it edit the entries. That works unless you have systems that are using GRUB Legacy, which also have initrd lines containing device specs, such as initrd (hd0,7)/boot/initrd-2.6.32.7-mdk.img. The (hd0,7) info will get carried into GRUB 2, but that's incorrect syntax for GRUB 2, so you have to know how to correct it. Hopefully you will not run into this issue, but if you do, at least you have a rough idea where to look - and you can ping me if you need help with it.

Rest well, keep learning, and have fun! You will feel a great sense of accomplishment when you conquer all of this! __{{emoticon}}__