Re: how to update the DirectX/OpenGL driver
(Sorry, this should have gone to the list in the first place.) Please search the log for module nvidia. grep -i -C 3 nvidia /var/log/Xorg.0.log If you have installed package nvidia-driver in stable or testing, I can't imagine that it is too old for any software. Nouveau should be blacklisted by it automatically, IIRC. Regards, Christian Am 05.11.21 um 10:08 schrieb lina: > Hi all, > > I was told to "update the DirectX/OpenGL driver" when I tried to use > some software. > One example is > Renderer: Error creating Canvas3D graphics context > > I have general problems with the graphic rendering. > > > $ lspci | grep VGA > 01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT > 730] (rev a1) > > > x11-xserver-utils install > xserver-common install > xserver-xorg install > xserver-xorg-core install > xserver-xorg-input-all install > xserver-xorg-input-libinput install > xserver-xorg-input-wacom install > xserver-xorg-legacy install > xserver-xorg-video-intel deinstall > xserver-xorg-video-nvidia install > > > i965-va-driver:amd64 install > intel-media-va-driver:amd64 install > libreoffice-base-drivers install > mesa-va-drivers:amd64 install > mesa-vdpau-drivers:amd64 install > mesa-vulkan-drivers:amd64 install > nvidia-driver install > nvidia-driver-bin install > nvidia-driver-libs:amd64 install > nvidia-vdpau-driver:amd64 install > va-driver-all:amd64 install > vdpau-driver-all:amd64 install > > cat /var/log/Xorg.0.log | grep -e WW -e EE > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 5.484] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not > exist. > [ 5.728] (WW) Warning, couldn't open module nouveau > [ 5.728] (EE) Failed to load module "nouveau" (module does not exist, 0) > [ 5.728] (WW) Warning, couldn't open module nv > [ 5.728] (EE) Failed to load module "nv" (module does not exist, 0) > [ 5.729] (WW) Warning, couldn't open module fbdev > [ 5.729] (EE) Failed to load module "fbdev" (module does not exist, 0) > [ 5.729] (WW) Warning, couldn't open module vesa > [ 5.729] (EE) Failed to load module "vesa" (module does not exist, 0) > [ 5.768] (WW) Falling back to old probe method for modesetting > [ 6.091] (II) Initializing extension MIT-SCREEN-SAVER > [ 6.596] (WW) Option "xkb_variant" requires a string value > [ 6.596] (WW) Option "xkb_options" requires a string value > [ 9.230] (WW) Option "xkb_variant" requires a string value > [ 9.230] (WW) Option "xkb_options" requires a string value > [ 30.617] (EE) event2 - PixArt HP USB Optical Mouse: client bug: > event processing lagging behind by 18ms, your system is too slow > [ 31.043] (EE) event2 - PixArt HP USB Optical Mouse: client bug: > event processing lagging behind by 28ms, your system is too slow > [ 904.011] (EE) event2 - PixArt HP USB Optical Mouse: client bug: > event processing lagging behind by 27ms, your system is too slow > > Thanks very much for your advice about how to fix it. > >
how to update the DirectX/OpenGL driver
Hi all, I was told to "update the DirectX/OpenGL driver" when I tried to use some software. One example is Renderer: Error creating Canvas3D graphics context I have general problems with the graphic rendering. $ lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1) x11-xserver-utils install xserver-common install xserver-xorg install xserver-xorg-core install xserver-xorg-input-all install xserver-xorg-input-libinput install xserver-xorg-input-wacom install xserver-xorg-legacy install xserver-xorg-video-intel deinstall xserver-xorg-video-nvidia install i965-va-driver:amd64 install intel-media-va-driver:amd64 install libreoffice-base-drivers install mesa-va-drivers:amd64 install mesa-vdpau-drivers:amd64 install mesa-vulkan-drivers:amd64 install nvidia-driver install nvidia-driver-bin install nvidia-driver-libs:amd64 install nvidia-vdpau-driver:amd64 install va-driver-all:amd64 install vdpau-driver-all:amd64 install cat /var/log/Xorg.0.log | grep -e WW -e EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 5.484] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 5.728] (WW) Warning, couldn't open module nouveau [ 5.728] (EE) Failed to load module "nouveau" (module does not exist, 0) [ 5.728] (WW) Warning, couldn't open module nv [ 5.728] (EE) Failed to load module "nv" (module does not exist, 0) [ 5.729] (WW) Warning, couldn't open module fbdev [ 5.729] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 5.729] (WW) Warning, couldn't open module vesa [ 5.729] (EE) Failed to load module "vesa" (module does not exist, 0) [ 5.768] (WW) Falling back to old probe method for modesetting [ 6.091] (II) Initializing extension MIT-SCREEN-SAVER [ 6.596] (WW) Option "xkb_variant" requires a string value [ 6.596] (WW) Option "xkb_options" requires a string value [ 9.230] (WW) Option "xkb_variant" requires a string value [ 9.230] (WW) Option "xkb_options" requires a string value [30.617] (EE) event2 - PixArt HP USB Optical Mouse: client bug: event processing lagging behind by 18ms, your system is too slow [31.043] (EE) event2 - PixArt HP USB Optical Mouse: client bug: event processing lagging behind by 28ms, your system is too slow [ 904.011] (EE) event2 - PixArt HP USB Optical Mouse: client bug: event processing lagging behind by 27ms, your system is too slow Thanks very much for your advice about how to fix it.
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 10:17:21AM -0400, Roberto C. Sánchez wrote: > On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote: > > I just installed Debian using netinstall image. I thought I install testing > > version, but apparently it's Debian 11. So now my source.list looks like > > below: > > > > deb http://deb.debian.org/debian/ bullseye main non-free contrib > > deb-src http://deb.debian.org/debian/ bullseye main non-free contrib > > > > deb http://security.debian.org/debian-security bullseye-security main > > contrib non-free > > deb-src http://security.debian.org/debian-security bullseye-security > > main contrib non-free > > > > deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free > > deb-src http://deb.debian.org/debian/ bullseye-updates main contrib > > non-free > > > > I want to switch to testing version. In the past I just change the keyword > > from e.g. bullseye to testing, and generally there is no weird problem. But > > I read on the internet saying that the source.list should not mix up with > > different version. For instance, Debian 11 with testing. So I am wondering > > if there is a better way to switch to testing? Or reinstalling is the only > > way to go? > > > If you change all instances of bullseye -> testing, then you are not > mixing. Go ahead with that, modulo the standard caveats associated with > running testing. The problem would come if you tried to include both > bullseye *and* testing sources in your sources.list. Then you might > create very difficult to resolve problems. > > You might consider using bookwork rather than testing, however. That is > the name of the testing release and unless you specifically want to > continue tracking testing even after bookwork is released, it is > probably better for most use cases to use the specific release code name > rather than stable or testing. > > Regards, > > -Roberto > > -- > Roberto C. Sánchez > Small thing: the release that should eventually become Debian 12 - that is currently also referred to as testing is bookworm NOT bookwork. Given that even the CD release team were consistently mistyping it - and mental autocorrect will change it automatically - that's unsurprising. In general: referring to current/future releases by codeword is a good thing - it does keep you consistent. Mixing releases is having concurrent lines for stable AND testing in the same file (also testing and unstable). It's not a real sin, but you have to know which bits come from where and how to resolve breakages. With the passing of time, you're more or less guaranteed to be running testing in that scenario anyway. https://wiki.debian.org/DontBreakDebian is relevant here to most people who would want to install a random .deb from a third party vendor or random website. All the very best, as ever, Andy Cater
Re: How to update Debian 11 source.list to testing?
On 4/09/21 2:17 am, Roberto C. Sánchez wrote: You might consider using bookwork rather than testing, however. Or bookworm, even. Richard
Re: How to update Debian 11 source.list to testing?
I will change to testing with all keyword switched to testing because my case is more often needing to use newer version software compared to stable, which also works fine w/t a problem for most of time. Thanks for all your help, and advice! Appreciate it! Sep 4, 2021, 09:30 by riveravaldezm...@gmail.com: > On 9/3/21, The Wanderer wrote: > >> On 2021-09-03 at 15:16, Brian wrote: >> >>> On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote: >>> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: (...) In the absence of "pinning", using the two lines that The Wanderer posted would give you a testing system, with the option to pull in packages from stable if needed. It's a viable setup. Sensible. >>> (...) >>> >> >> Absence in testing is the specific reason why I still include that line: >> in case I need to install a package because I need its functionality, >> but it's been temporarily removed from testing for whatever reason. >> >> That scenario has actually arisen a handful of times over the years, and >> the rest of the time, having the line included doesn't seem to have done >> any harm. >> >> -- >> The Wanderer >> > > In fact, I'm just right now dealing with kinda situation. > > There's this `phwmon.py`[1] which I use with fluxbox to have a couple > of system monitors at hand, and that depends on some python2 packages. > I've just made it work, installing manually (# apt-get install packages.deb) > this packages that I've downloaded from OldStable official archives: > > python-psutil > python-is-python2 (this is in fact in Testing) > python-numpy > python-pkg-resources > python-cairo > libffi6 > python-gobject-2 > python-gtk2 > > Therefore, my question: > > Is it better to install them as I did, or adding the line in sources.list as > The Wanderer does? > > Thanks a lot in advance. > Kind regards! > > [1] https://gitlab.com/o9000/phwmon >
Re: How to update Debian 11 source.list to testing?
On 9/3/21, The Wanderer wrote: > On 2021-09-03 at 15:16, Brian wrote: > >> On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote: >> >>> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: > >>> (...) >>> In the absence of "pinning", using the two lines that The Wanderer >>> posted would give you a testing system, with the option to pull in >>> packages from stable if needed. It's a viable setup. Sensible. >> (...) > > Absence in testing is the specific reason why I still include that line: > in case I need to install a package because I need its functionality, > but it's been temporarily removed from testing for whatever reason. > > That scenario has actually arisen a handful of times over the years, and > the rest of the time, having the line included doesn't seem to have done > any harm. > > -- >The Wanderer In fact, I'm just right now dealing with kinda situation. There's this `phwmon.py`[1] which I use with fluxbox to have a couple of system monitors at hand, and that depends on some python2 packages. I've just made it work, installing manually (# apt-get install packages.deb) this packages that I've downloaded from OldStable official archives: python-psutil python-is-python2 (this is in fact in Testing) python-numpy python-pkg-resources python-cairo libffi6 python-gobject-2 python-gtk2 Therefore, my question: Is it better to install them as I did, or adding the line in sources.list as The Wanderer does? Thanks a lot in advance. Kind regards! [1] https://gitlab.com/o9000/phwmon
Re: How to update Debian 11 source.list to testing?
On 2021-09-03 at 15:16, Brian wrote: > On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote: > >> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: >>> Surely - if you have a package installed from a previous release, >>> it does not get removed simply because testing does not have it? >> >> Correct. >> >>> It looks to me that the first line in sources.list does not help >>> in this situation. >> >> Also correct, *but* it does help if you want to install something from >> stable that has been removed from testing. >> >> In the absence of "pinning", using the two lines that The Wanderer >> posted would give you a testing system, with the option to pull in >> packages from stable if needed. It's a viable setup. Sensible. > > The bit that neeeds emphasising is > > ...give you a testing system. > > That is what the second entry in sources.list does. > > It doesn't matter what the other line is, the user is working > with a testing system. That is where the packages come from. > > Having said that, the option to pull in packages from stable > as needed is moot, apart from security updates or absence on > testing. It looks like cargo cult. Absence in testing is the specific reason why I still include that line: in case I need to install a package because I need its functionality, but it's been temporarily removed from testing for whatever reason. That scenario has actually arisen a handful of times over the years, and the rest of the time, having the line included doesn't seem to have done any harm. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to update Debian 11 source.list to testing?
On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote: > On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: > > On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote: > > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib > > > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > > > Surely - if you have a package installed from a previous release, > > it does not get removed simply because testing does not have it? > > Correct. > > > It looks to me that the first line in sources.list does not help > > in this situation. > > Also correct, *but* it does help if you want to install something from > stable that has been removed from testing. > > In the absence of "pinning", using the two lines that The Wanderer > posted would give you a testing system, with the option to pull in > packages from stable if needed. It's a viable setup. Sensible. The bit that neeeds emphasising is ...give you a testing system. That is what the second entry in sources.list does. It doesn't matter what the other line is, the user is working with a testing system. That is where the packages come from. Having said that, the option to pull in packages from stable as needed is moot, apart from security updates or absence on testing. It looks like cargo cult. -- Brian.
Re: How to update Debian 11 source.list to testing?
On 2021-09-03 at 13:40, Greg Wooledge wrote: > On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: > >> On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote: >> >>> deb http://ftp.us.debian.org/debian/ stable main non-free >>> contrib deb http://ftp.us.debian.org/debian/ testing main >>> non-free contrib > >> Surely - if you have a package installed from a previous release, >> it does not get removed simply because testing does not have it? > > Correct. > >> It looks to me that the first line in sources.list does not help in >> this situation. > > Also correct, *but* it does help if you want to install something > from stable that has been removed from testing. Yep - and that's the main reason why I keep this arrangement. > In the absence of "pinning", using the two lines that The Wanderer > posted would give you a testing system, with the option to pull in > packages from stable if needed. It's a viable setup. Sensible. > > The problem is, sometimes people think it's the opposite of that. > They think they can run a "mostly stable" system with the option to > cherry-pick packages from testing. This is *NOT* the case. And no > amount of "pinning" will make it so. I hadn't even considered that angle, although now that it's been brought up I recall having seen it discussed in the past. No, indeed - that's not going to work, and it should not be anything close to recommended. I would not want my description of my own setup to be interpreted as an endorsement of trying to do that. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to update Debian 11 source.list to testing?
On 2021-09-03 at 13:06, Greg Wooledge wrote: > On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote: > >> I have been running with (e.g.) >> >> deb http://ftp.us.debian.org/debian/ stable main non-free contrib >> deb http://ftp.us.debian.org/debian/ testing main non-free contrib >> >> for over a decade, and [...] there have been some problems [...] > > This is *precisely* why we advise against doing this. A dedicated > expert in Debian may be equipped to handle the problems that arise. > If you think you're good enough, and you want to do this, we can't > stop you. But we also can't help you when it breaks. While I acknowledge the points raised thus far (that being why I haven't responded, since I wouldn't have had much to say but "That's fair"), I don't think this is entirely right. You snipped out the part where I pointed out that as far as I can tell, the problems which I had are the same ones which I'd have had from just tracking testing anyway. If that's correct, then the fact of tracking both will have had nothing to do with my having encountered those problems. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote: > On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote: > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib > > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > Surely - if you have a package installed from a previous release, > it does not get removed simply because testing does not have it? Correct. > It looks to me that the first line in sources.list does not help > in this situation. Also correct, *but* it does help if you want to install something from stable that has been removed from testing. In the absence of "pinning", using the two lines that The Wanderer posted would give you a testing system, with the option to pull in packages from stable if needed. It's a viable setup. Sensible. The problem is, sometimes people think it's the opposite of that. They think they can run a "mostly stable" system with the option to cherry-pick packages from testing. This is *NOT* the case. And no amount of "pinning" will make it so. (If you actually want such a system, use stable-backports. That's what they're for. Do not pull binary packages from testing. I know, we say this every 3 days, but that's because the issue *comes up* every 3 days. We can't stamp it out.)
Re: How to update Debian 11 source.list to testing?
On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote: [...] > Are you sure about that last part? > > I have been running with (e.g.) > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > > for over a decade, and while there have been some problems, I think > they've been basically the same ones I'd have seen from running testing > alone; none of them have seemed terribly difficult to resolve, either. > (At least not by my standards, although I'll admit that I may not be the > best or most representative example.) > > I don't particularly consider this mixing releases; it's more tracking > testing, while still keeping available any packages which were in stable > but have been removed from testing. > > IMO, if you're going to track testing at all on a production computer > (as opposed to, well, for the purpose of actually *testing the upcoming > release*), it only makes sense to also include stable; there's too much > chance of an important package being (temporarily or permanently) > unavailable, otherwise. Surely - if you have a package installed from a previous release, it does not get removed simply because testing does not have it? It looks to me that the first line in sources.list does not help in this situation. -- Brian.
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote: > I have been running with (e.g.) > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > > for over a decade, and [...] there have been some problems [...] This is *precisely* why we advise against doing this. A dedicated expert in Debian may be equipped to handle the problems that arise. If you think you're good enough, and you want to do this, we can't stop you. But we also can't help you when it breaks.
Re: How to update Debian 11 source.list to testing?
On 03/09/2021 11:40, The Wanderer wrote: On 2021-09-03 at 10:17, Roberto C. Sánchez wrote: On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote: If you change all instances of bullseye -> testing, then you are not mixing. Go ahead with that, modulo the standard caveats associated with running testing. The problem would come if you tried to include both bullseye *and* testing sources in your sources.list. Then you might create very difficult to resolve problems. Are you sure about that last part? I have been running with (e.g.) deb http://ftp.us.debian.org/debian/ stable main non-free contrib deb http://ftp.us.debian.org/debian/ testing main non-free contrib for over a decade, and while there have been some problems, I think they've been basically the same ones I'd have seen from running testing alone; none of them have seemed terribly difficult to resolve, either. (At least not by my standards, although I'll admit that I may not be the best or most representative example.) I don't particularly consider this mixing releases; it's more tracking testing, while still keeping available any packages which were in stable but have been removed from testing. IMO, if you're going to track testing at all on a production computer (as opposed to, well, for the purpose of actually *testing the upcoming release*), it only makes sense to also include stable; there's too much chance of an important package being (temporarily or permanently) unavailable, otherwise. But there's a chance that the version in stable is not installable anymore because it depends on packages that have been upgraded on testing and are incompatible with stable. That said, I agree with you that there's a bit of exaggeration about mixing releases. Sure, it's not something to be recommended to a beginner or someone who's used to just clicking "Next >" to install/upgrade software, but provided one knows what they are doing and are careful when running apt-get (or equivalents), it's certainly possible and won't lead to guaranteed breakage. -- Goes (Went) over like a lead balloon. Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 04:25:39PM +0100, piorunz wrote: > On 03/09/2021 15:17, Roberto C. Sánchez wrote: > > If you change all instances of bullseye -> testing, then you are not > > mixing. Go ahead with that (...) > > Yep, that's all there is to say. testing word instead of bullseye > everywhere in sources.list will do the trick. > > AFAIK, you may also disable "-security" entry, as testing doesn't have > dedicated security team and testing-security repository will be empty. > I actually would recommend leaving it. In the last months prior to the next release, particularly when the freeze goes into effect, there will be uploads into bookwork-security (or testing-security). It doesn't hurt anything to leave it. Regards, -Roberto -- Roberto C. Sánchez
Re: How to update Debian 11 source.list to testing?
On 03/09/2021 15:17, Roberto C. Sánchez wrote: If you change all instances of bullseye -> testing, then you are not mixing. Go ahead with that (...) Yep, that's all there is to say. testing word instead of bullseye everywhere in sources.list will do the trick. AFAIK, you may also disable "-security" entry, as testing doesn't have dedicated security team and testing-security repository will be empty. -- With kindest regards, piorunz. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote: > On 2021-09-03 at 10:17, Roberto C. Sánchez wrote: > > > On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote: > > > >> I just installed Debian using netinstall image. I thought I install > >> testing version, but apparently it's Debian 11. So now my > >> source.list looks like below: > >> > >> deb http://deb.debian.org/debian/ bullseye main non-free contrib > >> deb-src http://deb.debian.org/debian/ bullseye main non-free contrib > >> > >> deb http://security.debian.org/debian-security bullseye-security main > >> contrib non-free > >> deb-src http://security.debian.org/debian-security bullseye-security > >> main contrib non-free > >> > >> deb http://deb.debian.org/debian/ bullseye-updates main contrib > >> non-free > >> deb-src http://deb.debian.org/debian/ bullseye-updates main contrib > >> non-free > >> > >> I want to switch to testing version. In the past I just change the > >> keyword from e.g. bullseye to testing, and generally there is no > >> weird problem. But I read on the internet saying that the > >> source.list should not mix up with different version. For instance, > >> Debian 11 with testing. So I am wondering if there is a better way > >> to switch to testing? Or reinstalling is the only way to go? > > > > If you change all instances of bullseye -> testing, then you are not > > mixing. Go ahead with that, modulo the standard caveats associated > > with running testing. The problem would come if you tried to include > > both bullseye *and* testing sources in your sources.list. Then you > > might create very difficult to resolve problems. > > Are you sure about that last part? > Yes, I'm sure, that's why I used *might* :-) > I have been running with (e.g.) > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib > deb http://ftp.us.debian.org/debian/ testing main non-free contrib > > for over a decade, and while there have been some problems, I think > they've been basically the same ones I'd have seen from running testing > alone; none of them have seemed terribly difficult to resolve, either. > (At least not by my standards, although I'll admit that I may not be the > best or most representative example.) > I respect your experience as valid. However, the anecdotal "I haven't experienced this particular problem" does not automatically extend to "therefore nobody else should either". The people who have written the documentation have provided a great deal of user support over the years. It seems unlikely that they would invent phantom problems to try to frighten users. Having experienced problems precisely as those described associated with mixing releases, I can testify to the fact that it can happen. > I don't particularly consider this mixing releases; it's more tracking > testing, while still keeping available any packages which were in stable > but have been removed from testing. > Yet, the further way the stable release becomes from the present, the greater the divergence of things like library dependencies. It is, in fact, mixing releases. Depending on which particular set of packages you have installed, you might see no problems, only minor problems, or extraordinarily difficult problems. Hence, the caution. > IMO, if you're going to track testing at all on a production computer > (as opposed to, well, for the purpose of actually *testing the upcoming > release*), it only makes sense to also include stable; there's too much > chance of an important package being (temporarily or permanently) > unavailable, otherwise. > Note that the OP's concern was "I want to switch a just-installed system from bullseye to testing, but I'm concerned about mixing releases." The idea is that if everything is switched from bullseye to testing then it isn't mixing releases. However, I did feel the need to point out the nature of potential problems to be encountered. Regards, -Roberto -- Roberto C. Sánchez
Re: How to update Debian 11 source.list to testing?
On 2021-09-03 at 10:17, Roberto C. Sánchez wrote: > On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote: > >> I just installed Debian using netinstall image. I thought I install >> testing version, but apparently it's Debian 11. So now my >> source.list looks like below: >> >> deb http://deb.debian.org/debian/ bullseye main non-free contrib >> deb-src http://deb.debian.org/debian/ bullseye main non-free contrib >> >> deb http://security.debian.org/debian-security bullseye-security main >> contrib non-free >> deb-src http://security.debian.org/debian-security bullseye-security >> main contrib non-free >> >> deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free >> deb-src http://deb.debian.org/debian/ bullseye-updates main contrib >> non-free >> >> I want to switch to testing version. In the past I just change the >> keyword from e.g. bullseye to testing, and generally there is no >> weird problem. But I read on the internet saying that the >> source.list should not mix up with different version. For instance, >> Debian 11 with testing. So I am wondering if there is a better way >> to switch to testing? Or reinstalling is the only way to go? > > If you change all instances of bullseye -> testing, then you are not > mixing. Go ahead with that, modulo the standard caveats associated > with running testing. The problem would come if you tried to include > both bullseye *and* testing sources in your sources.list. Then you > might create very difficult to resolve problems. Are you sure about that last part? I have been running with (e.g.) deb http://ftp.us.debian.org/debian/ stable main non-free contrib deb http://ftp.us.debian.org/debian/ testing main non-free contrib for over a decade, and while there have been some problems, I think they've been basically the same ones I'd have seen from running testing alone; none of them have seemed terribly difficult to resolve, either. (At least not by my standards, although I'll admit that I may not be the best or most representative example.) I don't particularly consider this mixing releases; it's more tracking testing, while still keeping available any packages which were in stable but have been removed from testing. IMO, if you're going to track testing at all on a production computer (as opposed to, well, for the purpose of actually *testing the upcoming release*), it only makes sense to also include stable; there's too much chance of an important package being (temporarily or permanently) unavailable, otherwise. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to update Debian 11 source.list to testing?
On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote: > I just installed Debian using netinstall image. I thought I install testing > version, but apparently it's Debian 11. So now my source.list looks like > below: > > deb http://deb.debian.org/debian/ bullseye main non-free contrib > deb-src http://deb.debian.org/debian/ bullseye main non-free contrib > > deb http://security.debian.org/debian-security bullseye-security main > contrib non-free > deb-src http://security.debian.org/debian-security bullseye-security main > contrib non-free > > deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free > deb-src http://deb.debian.org/debian/ bullseye-updates main contrib > non-free > > I want to switch to testing version. In the past I just change the keyword > from e.g. bullseye to testing, and generally there is no weird problem. But I > read on the internet saying that the source.list should not mix up with > different version. For instance, Debian 11 with testing. So I am wondering if > there is a better way to switch to testing? Or reinstalling is the only way > to go? > If you change all instances of bullseye -> testing, then you are not mixing. Go ahead with that, modulo the standard caveats associated with running testing. The problem would come if you tried to include both bullseye *and* testing sources in your sources.list. Then you might create very difficult to resolve problems. You might consider using bookwork rather than testing, however. That is the name of the testing release and unless you specifically want to continue tracking testing even after bookwork is released, it is probably better for most use cases to use the specific release code name rather than stable or testing. Regards, -Roberto -- Roberto C. Sánchez
How to update Debian 11 source.list to testing?
I just installed Debian using netinstall image. I thought I install testing version, but apparently it's Debian 11. So now my source.list looks like below: deb http://deb.debian.org/debian/ bullseye main non-free contrib deb-src http://deb.debian.org/debian/ bullseye main non-free contrib deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free I want to switch to testing version. In the past I just change the keyword from e.g. bullseye to testing, and generally there is no weird problem. But I read on the internet saying that the source.list should not mix up with different version. For instance, Debian 11 with testing. So I am wondering if there is a better way to switch to testing? Or reinstalling is the only way to go? Thanks
Re: how to update Debian 9.4 to at least OpenGL 3.3
Sven, awesome! You were right, I already have them - using your glxinfo statement I get: > $ glxinfo |grep "OpenGL core profile version" > OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.6 > SOLVED Thank you! --Brian On Thu, Jun 28, 2018 at 12:20 PM, Sven Joachim wrote: > On 2018-06-28 11:11 -0400, Brian Cary wrote: > > > Greetings, > > New to Debian, long-time Ubuntu user. If is in the wrong place, > apologies, > > please point me in the right direction. > > > > QUESTION: > > Can some-one tell me how (or point me to updated step-by-step docs) to > > update > > my Debian 9.4 system (with Gnome) to at least OpenGL 3.3 mesa drivers? > > > > BACKGROUND: > > Avid Blender user. Those latest versions of Blender contain critically > > needed features. I would like to start working/learning on > not-yet-released > > Blender 2.8 which comes out late in 2018. > > > > Blender 2.8 requires OpenGL 3.3 > > (per here: https://www.blender.org/2-8/#viewport ) > > > > Debian 9.4 seems to have OpenGL 3.0 > > On my system: > > > > $ glxinfo |grep "OpenGL version" > >> OpenGL version string: 3.0 Mesa 13.0.6 > >> > > > > So how can I upgrade Mesa drivers to a level that supports > > at least OpenGL 3.3 (or higher)? > > You probably already have them. From the release notes: > > , > | Mesa 13.0.6 implements the OpenGL 4.4 API, but the version reported by > | glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) / > | glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being > | used. Some drivers don't support all the features required in OpenGL > | 4.4. OpenGL 4.4 is only available if requested at context creation > | because compatibility contexts are not supported. > ` > > IIUC the last sentence is why "OpenGL version string" is stuck at 3.0. > To see the maximum OpenGL version the driver supports, you need to look > at the "OpenGL core profile version" string. > > $ glxinfo | grep "OpenGL core profile version" > > It should report 3.3 or higher unless your graphics card is older than > ~10 years. > > Cheers, >Sven > > -- --Brian
Re: how to update Debian 9.4 to at least OpenGL 3.3
On 06/28/2018 12:20 PM, Sven Joachim wrote: glxinfo | grep "OpenGL core profile version" My system reports: ric@iam:/opt/ric/Downloads/warzone2100-2.3.8/src$ glxinfo | grep "OpenGL core profile version" OpenGL core profile version string: 4.6.0 NVIDIA 390.48 ric@iam:/opt/ric/Downloads/warzone2100-2.3.8/src$ So, a lot might depend on which video driver you use. FYI, Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: how to update Debian 9.4 to at least OpenGL 3.3
On 2018-06-28 11:11 -0400, Brian Cary wrote: > Greetings, > New to Debian, long-time Ubuntu user. If is in the wrong place, apologies, > please point me in the right direction. > > QUESTION: > Can some-one tell me how (or point me to updated step-by-step docs) to > update > my Debian 9.4 system (with Gnome) to at least OpenGL 3.3 mesa drivers? > > BACKGROUND: > Avid Blender user. Those latest versions of Blender contain critically > needed features. I would like to start working/learning on not-yet-released > Blender 2.8 which comes out late in 2018. > > Blender 2.8 requires OpenGL 3.3 > (per here: https://www.blender.org/2-8/#viewport ) > > Debian 9.4 seems to have OpenGL 3.0 > On my system: > > $ glxinfo |grep "OpenGL version" >> OpenGL version string: 3.0 Mesa 13.0.6 >> > > So how can I upgrade Mesa drivers to a level that supports > at least OpenGL 3.3 (or higher)? You probably already have them. From the release notes: , | Mesa 13.0.6 implements the OpenGL 4.4 API, but the version reported by | glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) / | glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being | used. Some drivers don't support all the features required in OpenGL | 4.4. OpenGL 4.4 is only available if requested at context creation | because compatibility contexts are not supported. ` IIUC the last sentence is why "OpenGL version string" is stuck at 3.0. To see the maximum OpenGL version the driver supports, you need to look at the "OpenGL core profile version" string. $ glxinfo | grep "OpenGL core profile version" It should report 3.3 or higher unless your graphics card is older than ~10 years. Cheers, Sven
how to update Debian 9.4 to at least OpenGL 3.3
Greetings, New to Debian, long-time Ubuntu user. If is in the wrong place, apologies, please point me in the right direction. QUESTION: Can some-one tell me how (or point me to updated step-by-step docs) to update my Debian 9.4 system (with Gnome) to at least OpenGL 3.3 mesa drivers? BACKGROUND: Avid Blender user. Those latest versions of Blender contain critically needed features. I would like to start working/learning on not-yet-released Blender 2.8 which comes out late in 2018. Blender 2.8 requires OpenGL 3.3 (per here: https://www.blender.org/2-8/#viewport ) Debian 9.4 seems to have OpenGL 3.0 On my system: $ glxinfo |grep "OpenGL version" > OpenGL version string: 3.0 Mesa 13.0.6 > So how can I upgrade Mesa drivers to a level that supports at least OpenGL 3.3 (or higher)? Thanks, --Brian
plasma5 - how to update menus
Hi folks, I installed a new application (not from repo), and there is a *.desktop file in /usr/share/applications. But I the new application does not appear in the menus of plasma5/kde. How can I force, to recreate the menus in plasma5? I tried "update-menus", "kbuildsycoca5 --noincremental" and "kbuildsycoca4 --noincremental" as well without any success. I also removed ~/.local/share/applications away - with no success. Is there any other way, to recreate the menus in plasma5? Thanks for any hints. Best regards Hans
Re: how to update TexLive 2014, apt-get or tlmgr?
On Fri, 08 Aug 2014, Sharon Kimble wrote: Thanks Norbert, that's the definitive answer that I was looking for, and I shall wait as suggested. :) Next upload is planned for about the 25 August, after the holidays here in Japan are over. All the best Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140811010447.gs5...@auth.logic.tuwien.ac.at
Re: how to update TexLive 2014, apt-get or tlmgr?
On Thu, Aug 07, 2014 at 09:18:08AM +0100, Sharon Kimble wrote: I'm using TexLive 2014 from the jessie repos, and also keeping a watching brief on comp.text.tex where it shows updates to packages as they occur. I'm interested in the tcolorbox and glossaries packages and see that they have recently been updated. What is the best way of getting the updated packages please? To update with tlmgr, and then hope that the ~/texmf/tex/latex/foo version overrides the texlive version, if that’s where they end up? I would ask on the Debian TeX Maintainers list: debian-tex-ma...@lists.debian.org In fact, to keep debian-user in the loop I may as well CC them. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140808130816.GF2128@tal
Re: how to update TexLive 2014, apt-get or tlmgr?
On Sat, 09 Aug 2014, Chris Bannister wrote: I'm using TexLive 2014 from the jessie repos, and also keeping a watching brief on comp.text.tex where it shows updates to packages as they occur. I'm interested in the tcolorbox and glossaries packages and see that they have recently been updated. What is the best way of getting the updated packages please? To update with tlmgr, and then hope that the ~/texmf/tex/latex/foo version overrides the texlive version, if that’s where they end up? Wait. I normally do updates of the texlive packages once a month. If you cannot wait, use tlmgr in self mode, install locally, and then make sure that after TL in Debina is updated to remove it again. These are the two options. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140808135832.gc5...@auth.logic.tuwien.ac.at
Re: how to update TexLive 2014, apt-get or tlmgr?
Norbert Preining prein...@logic.at writes: On Sat, 09 Aug 2014, Chris Bannister wrote: I'm using TexLive 2014 from the jessie repos, and also keeping a watching brief on comp.text.tex where it shows updates to packages as they occur. I'm interested in the tcolorbox and glossaries packages and see that they have recently been updated. What is the best way of getting the updated packages please? To update with tlmgr, and then hope that the ~/texmf/tex/latex/foo version overrides the texlive version, if that’s where they end up? Wait. I normally do updates of the texlive packages once a month. If you cannot wait, use tlmgr in self mode, install locally, and then make sure that after TL in Debina is updated to remove it again. These are the two options. Thanks Norbert, that's the definitive answer that I was looking for, and I shall wait as suggested. :) Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.5, emacs 24.3.92.1 signature.asc Description: PGP signature
how to update TexLive 2014, apt-get or tlmgr?
I'm using TexLive 2014 from the jessie repos, and also keeping a watching brief on comp.text.tex where it shows updates to packages as they occur. I'm interested in the tcolorbox and glossaries packages and see that they have recently been updated. What is the best way of getting the updated packages please? To update with tlmgr, and then hope that the ~/texmf/tex/latex/foo version overrides the texlive version, if that’s where they end up? Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.5, emacs 24.3.92.1 signature.asc Description: PGP signature
Re: How to update
On Thu, Oct 25, 2012 at 07:41:54PM +0100, Edwin Zarthrusz wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? 1. Edit your /etc/apt/sources.list and make sure there's a stanza for security.debian.org. 2. sudo apt-get install apticron 3. edit /etc/apticron/apticron.conf to have a reliable email address for you. Now you will get an email whenever there are security updates for your system, and a reminder of the single command necessary to apply them all. Read http://www.debian.org/security/ -dsr- -- http://randomstring.org/~dsr/eula.html is hereby incorporated by reference. You can't fight for freedom by taking away rights. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121025185050.gk2...@randomstring.org
Re: How to update
On Oct 25, 2012, at 12:41 PM, Edwin Zarthrusz wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? apticron is pretty close to automatic. There are no commands; you just install it (apt-get install apticron), and it checks for updates and stuff every night, downloads the .debs, and sends you an email saying that you need to do something (the command line command is in the email, and you can always bring up aptitude for more info). I think that Debian (like many other systems) tries not to do anything to your machine on its own -- it always asks first. There are pros and cons to this, but it's what I prefer. And it's not much trouble... -- Glenn English -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/13f8f834-2f04-4394-ae74-77500833e...@slsware.com
Re: How to update
On 10/25/2012 02:41 PM, Edwin Zarthrusz wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? TIA -- Be. Love. Ed. The information you require is in the following packages. 1. aptitude package man aptitude will display the commands 2. debian-reference A reference Doc that can be viewed in a a browser (html). These packages are a must have for any new user. HTH -- Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50898e80.1010...@gmail.com
Re: How to update
On 10/25/2012 02:09 PM, Wayne Topa wrote: On 10/25/2012 02:41 PM, Edwin Zarthrusz wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? apt-get and aptitude are the main tools used for updating a Debian system. They are similar tools, and the use of one or the other is largely a matter of preference. Google can tell you more about which tool to use; I almost always use aptitude, but in the examples below, you could use either aptitude or apt-get. #aptitude update aptitude dist-upgrade or # aptitude update aptitude safe-upgrade You can google for apt-get safe-upgrade vs dist-upgrade (dist-upgrade I think has now been renamed to full-upgrade) to get an idea of which method you might prefer. The short answer is that safe-upgrade is more conservative and less likely to break things, whereas dist-upgrade will upgrade things that safe-upgrade won't. I almost always use dist-upgrade. The simply means do the second command once the first command completes successfully. (If the first command is unsuccessful, the second command will not run.) You could also break the commands into two separate command lines if you prefer, like so: # aptitude update # aptitude dist-upgrade Or you could use a gui tool like Synaptic. You could build a cron job to automate the process, although you'd probably have to feed an extra parameter or two to apt-get/aptitude to tell it to assume Yes answers to any questions it asks, etc. I think simply adding -y to the end of the command will do the job. -- Kent West*))) http://kentwest.blogspot.com Praise Yah! \o/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/508993ac.9070...@acu.edu
Re: How to update
On Jo, 25 oct 12, 19:41:54, Edwin Zarthrusz wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? Additionally to what has been mentioned already I will add packages unattended-upgrades and cron-apt. However, please mind that simply upgrading your system automatically is not enough to keep it secure. Just two examples I just thought about (but there are probably many others): - programs affected by security updates need to be restarted, otherwise you will still be running the old version. For kernel upgrades a reboot is needed. - some security issues can/are not handled by upgrades. For example in the past it happened that some packages could not supported anymore from a security point of view. There was simply a mention on the debian-security-announce list, where users were advised to stop using the program. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: How to update
On Thu, Oct 25, 2012 at 2:41 PM, Edwin Zarthrusz zarthr...@yahoo.co.uk wrote: Can you send me a straight-forward list of commands for updating and applying any necessary security patches and such on my install? And is there a way of getting it to update automatically? Hi Ed, In addition to all of the other correspondents, I have to add that I generally don't let it automatically update. I have a small (15-20 hosts) network at home, and a larger one (250-300 hosts) at work. I never automatically update because every now and again, things can get broken, like APIs/ABIs. This is primarily when running testing or unstable (which I do on most of my machines). Automatically updating can leave you scrambling to get everything fixed. (Remember, MS forces auto-updates, and you can see how well that works out for them...:) ) What I do is similar to what Glenn suggested. Each of my hosts sends apticron updates to my email, and every day, I run through the list and see if I need to update. I check for a) applications affecting the purpose of the server, e.g. php or mediawiki or apache on my wiki, ruby or puppet on my puppetmaster, etc.; b) Urgency of the update. About 8 months ago, there was a kerberos patch that was listed as Emergency. I upgraded as quickly as I could. I also peruse the changes for the packages listed for upgrade. I'm more likely to upgrade if packages say Apply security patch for... than for ones that say new upstream release unless I need some piece of functionality. The final point is that you should get more hands on with your security if you are that concerned with it. Here are a few approaches that I suggest: * Only run services that you really need. If you're not using an app, either turn it off or deinstall it. * Run a firewall to keep all services from being exposed to the internet. * Run tools like nmap and nessus (the free version) or openvas against your machine in addition to patching what others think you need to patch. * Keep good backups. * Read the Debian security list (http://www.debian.org/security/). * Get familiar with your machine and how it normally behaves. That way, if something does go awry, you have that familiarity, which may allow you to find a problem in days or hours instead of weeks or months. Not only will this help you secure your machine, it can develop into marketable skills. Regards, --b -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakmzw+y3cwy02+dw0qporc9fddurojvyiyrjg6ugcva7aml...@mail.gmail.com
Re: how does update-grub choose the root filesystem
On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am trying to make this work on, and am worried that if I go too far without properly understanding what would happen I may end up with an unbootable system. -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff6848a.9040...@chandlerfamily.org.uk
Re: how does update-grub choose the root filesystem
On 06/07/12 07:24, Alan Chandler wrote: On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am trying to make this work on, and am worried that if I go too far without properly understanding what would happen I may end up with an unbootable system. I think the answer might be here. http://unix.stackexchange.com/questions/5297/debian-grub2-moving-root-partition-to-new-drive I have some other things to do right now, but I will try this out later. It looks as though update-grub and/or grub-install use the current root. So by chrooting into where you want to be you get them all set up. -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff6907e.5070...@chandlerfamily.org.uk
Re: how does update-grub choose the root filesystem
On 06/07/12 08:15, Alan Chandler wrote: On 06/07/12 07:24, Alan Chandler wrote: On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. I want to achieve the mimimum of downtime on the machine I am trying to make this work on, and am worried that if I go too far without properly understanding what would happen I may end up with an unbootable system. I think the answer might be here. http://unix.stackexchange.com/questions/5297/debian-grub2-moving-root-partition-to-new-drive I have some other things to do right now, but I will try this out later. It looks as though update-grub and/or grub-install use the current root. So by chrooting into where you want to be you get them all set up. Something went wrong - I am not sure what, but I ended up needing a rescue disk to reset root back to its old location. I wonder if its to do with trying to use a raid device as the root partition. Do you need to create a special initrd for that? -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff6d9b8.1080...@chandlerfamily.org.uk
Re: how does update-grub choose the root filesystem
On Fri, Jul 6, 2012 at 2:24 AM, Alan Chandler a...@chandlerfamily.org.uk wrote: On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. grub-install /dev/sdX uses grub-probe to find / and /boot. grub-install /dev/sdX installs grub in the MBR of sdX and grub-install -f /dev/sdXY installs grub in the PBR of of sdXY. The latter's not recommended in general and isn't necessarily possible when using mdraid. You have to install grub in the MBR of both drives in order to be able to boot from a degraded array. From a system of mine: = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. = Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. update-grub calls grub-mkconfig -o /boot/grub/grub.cfg and creates the grub menu configuration. It doesn't install grub on a disk. You shouldn't have to worry about the initramfs. It's built with md scripts and hooks in /usr/share/initramfs-tools. You can check that it's been done with lsinitramfs /boot/INITRAMFS | grep md | grep -v modules. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=Swews0hjj32QSFU3XrQQCxmco7xMMpHeGBBRehjN=h...@mail.gmail.com
Re: how does update-grub choose the root filesystem
On 06/07/12 01:43 PM, Tom H wrote: On Fri, Jul 6, 2012 at 2:24 AM, Alan Chandlera...@chandlerfamily.org.uk wrote: On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. grub-install /dev/sdX uses grub-probe to find / and /boot. grub-install /dev/sdX installs grub in the MBR of sdX and grub-install -f /dev/sdXY installs grub in the PBR of of sdXY. The latter's not recommended in general and isn't necessarily possible when using mdraid. You have to install grub in the MBR of both drives in order to be able to boot from a degraded array. From a system of mine: = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. = Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. update-grub calls grub-mkconfig -o /boot/grub/grub.cfg and creates the grub menu configuration. It doesn't install grub on a disk. You shouldn't have to worry about the initramfs. It's built with md scripts and hooks in /usr/share/initramfs-tools. You can check that it's been done with lsinitramfs /boot/INITRAMFS | grep md | grep -v modules. Grub-install is generally pretty good at installing on both drives in a RAID1 array or all drives in other RAID arrays. Update-grub also manages to find OS partitions in just about everything - including non-Linux partitions. When in doubt, if you've changed things, just run update-grub and update-initramfs -u. They only take a few seconds to run. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff726ba.5060...@rogers.com
Re: how does update-grub choose the root filesystem
On 06/07/12 18:56, Gary Dale wrote: On 06/07/12 01:43 PM, Tom H wrote: On Fri, Jul 6, 2012 at 2:24 AM, Alan Chandlera...@chandlerfamily.org.uk wrote: On 05/07/12 23:10, Tom H wrote: On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX Reading the man page for this doesn't say how it finds out where the root filesystem is. Thats the bit that is confusing me. I currently have a root filesystem on /dev/sdb1. I am not sure which disk contains the mbr - but it boots and then loads the root from there. I have created a partially degraded mdadm raid array /dev/md0 comprising /dev/sda1 and an empty slot. My desire is to install grub on both /dev/sda and /dev/sdb to boot up from /dev/md0. When that is working I will retire /dev/sdb1 and add it as the second component of /dev/md0. The magic appears to be in grub-mkconfig (wrapped with update-grub). But I am also confused as to whether I need to do anything about an initramfs. grub-install /dev/sdX uses grub-probe to find / and /boot. grub-install /dev/sdX installs grub in the MBR of sdX and grub-install -f /dev/sdXY installs grub in the PBR of of sdXY. The latter's not recommended in general and isn't necessarily possible when using mdraid. You have to install grub in the MBR of both drives in order to be able to boot from a degraded array. From a system of mine: = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. = Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 34 of the same hard drive for core.img. core.img is at this location and looks for (mduuid/801256bc800752eab5118583d15c4689)/boot/grub on this drive. update-grub calls grub-mkconfig -o /boot/grub/grub.cfg and creates the grub menu configuration. It doesn't install grub on a disk. You shouldn't have to worry about the initramfs. It's built with md scripts and hooks in /usr/share/initramfs-tools. You can check that it's been done with lsinitramfs /boot/INITRAMFS | grep md | grep -v modules. Grub-install is generally pretty good at installing on both drives in a RAID1 array or all drives in other RAID arrays. Update-grub also manages to find OS partitions in just about everything - including non-Linux partitions. When in doubt, if you've changed things, just run update-grub and update-initramfs -u. They only take a few seconds to run. I think you are simplifying things. update-grub needs to locate a root filesystem and seems to do that based on what it is running on at the moment. I you are changing that then you have to do all this is the context of that new root. This means setting up the environment as described in the link I left elsewhere in this thread -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff72eea.9010...@chandlerfamily.org.uk
Re: how does update-grub choose the root filesystem
On Wed, Jul 4, 2012 at 7:22 PM, Alan Chandler a...@chandlerfamily.org.uk wrote: I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. grub-install /dev/sdX -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxiswebfuy-ideckmaz8jtjruvsm9xlsjrjqthm9cz...@mail.gmail.com
how does update-grub choose the root filesystem
I am trying to figure out how to move my current rootfs to raid1 (its just a partition at the moment). The plan is to make a a raid device, copy the current root fs in to it - but I then need to tell grub to set up this up as the root for the boot. How do I do this? -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff4d03c.1070...@chandlerfamily.org.uk
Re: how to update Debian OS properly
On Lu, 28 mai 12, 02:21:39, Muhammad Yousuf Khan wrote: [snip] Must read: http://www.debian.org/doc/manuals/debian-reference/ (or as package debian-reference) Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: how to update Debian OS properly
On Sat, May 26, 2012 at 1:04 PM, Andrei POPESCU andreimpope...@gmail.com wrote: On Vi, 25 mai 12, 15:36:40, Ralf Mardorf wrote: On Fri, 2012-05-25 at 18:28 +0500, Muhammad Yousuf Khan wrote: In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package Yesno. I'll say yes, somebody else might recommend http://jaqque.sbih.org/kplug/apt-pinning.html That article, while still useful, - mentions non-US which has been discontinued long time ago (sarge?) - uses sources + pinning by release not code-name[1] [1] this may be due to a bug in apt where pinning by codename was not possible, fixed in the meantime (lenny?). I seem to remember the Debian Reference has a good guide to pinning and it is up-to-date (thanks to Osamu Aoki). I remember but I can't find a confirmation via google that apt-get has been patched so that, if you're running stable, apt-get package/testing now meets dependencies from testing just like apt-get -t testing package does (which contradicts the url above). Can anyone confirm or infirm this? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxG33vYkYiomRycpKQu6pTZXJKVwoBLojx0gyjy...@mail.gmail.com
Re: how to update Debian OS properly
On Sat, May 26, 2012 at 10:39 PM, Lisi lisi.re...@gmail.com wrote: On Saturday 26 May 2012 18:04:35 Andrei POPESCU wrote: I seem to remember the Debian Reference has a good guide to pinning and it is up-to-date (thanks to Osamu Aoki). Given the OP's confusion, and the fact that he states his main aim as not crashing, would he not do better to stick to pure Squeeze for now? Hopefully, more use of Linux will enable him to stop trying to mimic Windows - a job which Windows itself does rather well ;-) true :-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205261839.42048.lisi.re...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMn=D6FyArU1Ha6OWC0C=tLDq-2EPH=G09=a28uti1u...@mail.gmail.com
Re: how to update Debian OS properly
On Sat, May 26, 2012 at 7:17 PM, Lisi lisi.re...@gmail.com wrote: On Saturday 26 May 2012 12:43:45 you wrote: I prefer to use aptitude full-upgrade routinely - but I have the code name in my sources.list, not stable or testing. I then change the code name when I want to get the more recent version. So, Squeeze not stable, Muhammad. you could get in quite a mess at the changeover point from Squeeze to Wheezy if you have stable in your sources.list, as several people have pointed out. if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. I'm afraid that I don't understand you. Why should you have a system crash? I'm afraid that I don't understand you. Why should you have a system crash? i know my question regarding comparing Windows and Linux a bit annoying, but i had bad experiences with upgrading windows from one version to another one. and in linux i just run the command ap-get upgrade and after few minutes i was working in wheezy regardless of sid or testing (so the simplicity of the process left me very confuse). i know how patches and service packs in windows can turn people's life to nightmare. actually i am the only resource in system and network in my company and i am the only one who is motivating management to shift to linux. so i am a bit scared. because this is new world to me. however i learn too much from this thread and from this mailing list. i am thankful to everyone for sharing your views/thoughts/suggestions . i know remaining confusions will be clears after getting use to with linux. Thanks And what are you trying to achieve? Always use code names, and incidentally Sid is the code-name for unstable, a code-name which never changes. So choose which you want. From the sound of things you want Squeeze. Install Squeeze. Check that Squeeze is in your sources.list, and only Squeeze at this stage. No mention of stable or anything else. Update Squeeze. (aptitude update followed by aptitude full-upgrade or aptitude safe-upgrade.) From then on you will only basically get security updates, though there are periodic point releases for Squeeze to iron out some remaining bugs etc. For now, and while you bed down with Debian/Linux, simply ignore all mentions of Wheezy, stable, Sid, unstable, testing etc. Time enough to come to terms with those when you understand fully what is going on or when Wheezy has become Stable and Squeeze is Old Stable. apt is now preferred to aptitude by many on this list, but I am more familiar with aptitude, and might have got the commands slightly wrong had I attempted to give you them. (I did last time that I did so.) But for what you are doing now, either is fine, and when it comes to upgrading to a new release, the release notes will tell you which to use. But above all, keep things simple for now. And when you ask a question, try to express it without reference to Windows. Many of us do not use Windows, and in my case I have not done so since Windows 98, which I don't remember very well. HTH Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205261517.08770.lisi.re...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMmnt=secmo8vujuagi8qft6co5iptpj_ee-9krrrm4...@mail.gmail.com
Re: how to update Debian OS properly
On Sunday 27 May 2012 22:21:39 you wrote: On Sat, May 26, 2012 at 7:17 PM, Lisi lisi.re...@gmail.com wrote: On Saturday 26 May 2012 12:43:45 you wrote: I prefer to use aptitude full-upgrade routinely - but I have the code name in my sources.list, not stable or testing. I then change the code name when I want to get the more recent version. So, Squeeze not stable, Muhammad. you could get in quite a mess at the changeover point from Squeeze to Wheezy if you have stable in your sources.list, as several people have pointed out. if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. I'm afraid that I don't understand you. Why should you have a system crash? i know my question regarding comparing Windows and Linux a bit annoying, No, it is not annoying - merely somewhat difficult to follow. Here, we have been an all-Unix house for some years. We were all-Linux until recently, but my granddaughter has a new laptop, which is a Mac with OSX, so still Unix. So I am not very au fait with Windows problems. but i had bad experiences with upgrading windows from one version to another one. and in linux i just run the command ap-get upgrade and after few minutes i was working in wheezy regardless of sid or testing (so the simplicity of the process left me very confuse). i know how patches and service packs in windows can turn people's life to nightmare. actually i am the only resource in system and network in my company and i am the only one who is motivating management to shift to linux. so i am a bit scared. because this is new world to me. Your description of life under Windows shows why many of us simply don't use Windows. In your shoes most of us would be scared. Well, I certainly would be. It's a huge responsibility, and the buck stops with you! however i learn too much from this thread and from this mailing list. i am thankful to everyone for sharing your views/thoughts/suggestions . i know remaining confusions will be clears after getting use to with linux. Just ask whenever there is something you don't understand. One of the beauties of this list is that it is a) large and b) worldwide. So, what with all the different time zones there is always someone around. And yes, you will soon get used to Linux. But from what you say, I really would stick to Squeeze for now, provided that it is OK on your hardware. Get it going rock-solid and you will soon win converts. Time enough to fly in the rarefied regions of pinning and mixed systems when you have really found your feet. Good luck! Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205272257.19822.lisi.re...@gmail.com
Re: how to update Debian OS properly
On Sat, May 26, 2012 at 1:30 AM, Lisi lisi.re...@gmail.com wrote: On Friday 25 May 2012 18:23:37 Tom H wrote: On Fri, May 25, 2012 at 11:53 AM, Mika Suomalainen mika.henrik.mai...@hotmail.com wrote: On 25.05.2012 15:49, Ralf Mardorf wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. Is it safe to use stable instead of squeeze? Are there usually any conflicts or anything what would need full-upgrade whenever new stable is named? No. No need for aptitude full-upgrade, even apt-get upgrade/aptitude safe-upgrade will pull in wheezy (partially) when it becomes stable. I prefer to use aptitude full-upgrade routinely - but I have the code name in my sources.list, not stable or testing. I then change the code name when I want to get the more recent version. So, Squeeze not stable, Muhammad. you could get in quite a mess at the changeover point from Squeeze to Wheezy if you have stable in your sources.list, as several people have pointed out. if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. I can't comment on your Windows analogies as I don't use Windows. I think that you need to expect that Linux will be different from whatever you used in Windows. They are very different OSs. FWIW, I do most of my admin from the CLI, including updating and upgrading. So yes, it can be done from the CLI. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205252130.54213.lisi.re...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfM=s3FrC=yzgk+d3bvg7jm64kks_p_xvcy8mcfogj6v...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 6:36 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Fri, 2012-05-25 at 18:28 +0500, Muhammad Yousuf Khan wrote: In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package Yesno. I'll say yes, somebody else might recommend http://jaqque.sbih.org/kplug/apt-pinning.html i was reading this article and it is very helpful and something new that i learned but i am a bit confuse. how come i be safe in this technique because what this article is saying means if i wanted to install a specific package this would be helpful and if the package is not in the stable then apt will check in testing and finally in sid. but what if i run apt-get upgrade then my question is, would it be safe and will not upgrade my OS to sid or testing. Do you need src? Src repos provide source code only. You might need headers to compile src codes from sourceforge etc., but seldom a Debian src. Google if there is a stable stable-updates repository etc. too. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337953000.2251.114.camel@precise -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMnk2aSYbnfBQFgdowYOowmyRymrG5=q6qcelism_gm...@mail.gmail.com
Re: how to update Debian OS properly
On Sat, 26 May 2012 16:43:45 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. I can see you are getting confused; best practice suggests using the stable dist by name.(Currently Squeeze) When you want to upgrade to the next stable version, replace squeeze with wheezy, in your /etc/apt/sources.list. ~~ My sources.list on a clean installation of Debian Squeeze 6.0.5, with the addition of non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free deb http://ftp.debian.org/debian/ squeeze main contrib non-free deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526132531.a457ef470c1325f297b2e...@gmail.com
Re: how to update Debian OS properly
On Sat, 26 May 2012 17:06:04 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: i was reading this article and it is very helpful and something new that i learned but i am a bit confuse. how come i be safe in this technique because what this article is saying means if i wanted to install a specific package this would be helpful and if the package is not in the stable then apt will check in testing and finally in sid. but what if i run apt-get upgrade then my question is, would it be safe and will not upgrade my OS to sid or testing. When I upgraded squeeze to wheezy, i did - apt-get update; apt-get upgrade; apt-get dist-upgrade My understanding is - If you apt-get upgrade, you are updating your system (squeeze) When you use apt-get dist-upgrade you change your system from squeeze to wheezy If you install a package from wheezy/sid it won't be upgraded until the version number is reached in the stable (i.e. squeeze) version. -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526133926.85c6d542d64ad10f386a5...@gmail.com
Re: how to update Debian OS properly
On Sat, 26 May 2012 16:43:45 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. Usually when a version of Stable is upgraded to the next, there will be some things to do manually. If you have any software installed by other means than the apt system, or from other repositories than the official Debian ones, then that will need to be upgraded by hand, or maybe even removed if that software is now available in the new version. There may be some applications whose configuration files have changed significantly, and cannot be automatically upgraded. There may be some applications on hold, where you did not want them kept up to date even at the risk of security bugs. Such holds must be released before upgrading. So you don't want a version upgrade to happen without preparation, and certainly not automatically on the day of the new release. It's a bit like automatic updates in Windows: you wouldn't enable that on a server, you would want to check first and approve updates (and possibly wait a week to see who else has problems..). If you are installing a service pack, this is especially true, and a Debian version upgrade is broadly similar to an MS service pack. So if you use the codename of the distribution, the version upgrade will not happen automatically, and this is generally what you want. After the new version is released, you can take up to a year to prepare for the upgrade, and carry it out at a time of your own choosing. If you use the Stable distribution, with no apt sources other than the official Debian ones, and use the codename in your sources list, you should never expect to see any system disturbance. When you make the upgrade to the next version, you shouldn't expect to see any problems which have not been mentioned in the release notes for the upgrade. As to which upgrade to use routinely, it's not too important in Stable. Nothing should be removed under normal conditions, so aptitude safe-upgrade or apt-get upgrade should have the same effect as aptitude full-upgrade or apt-get dist-upgrade. The apt-get and aptitude actions are not absolutely identical, but very similar for routine upgrades, the differences are in how dependencies are handled. Routine upgrades of the Stable distribution do not normally involve any dependency changes. The release notes for a version upgrade will normally advise which of the two systems is preferred for the upgrade (e.g. apt-get for squeeze, aptitude for lenny). If you choose to run sid, the Unstable distribution, on a workstation, you will learn Debian a little bit quicker, but you should expect problems. You will need to look at upgrades before carrying them out, as routine upgrades applied without thinking can damage sid, and this happens once or twice a year. Much more often than that, sid will ask if you want half of your desktop environment removed, and it's usually safer to say no. There are typically 20-50 packages upgraded per day in an 'average' sid system, and at any time there are two or three needing upgrades but with problems preventing it happening. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526134351.26661...@jretrading.com
Re: how to update Debian OS properly
On Saturday 26 May 2012 12:43:45 you wrote: I prefer to use aptitude full-upgrade routinely - but I have the code name in my sources.list, not stable or testing. I then change the code name when I want to get the more recent version. So, Squeeze not stable, Muhammad. you could get in quite a mess at the changeover point from Squeeze to Wheezy if you have stable in your sources.list, as several people have pointed out. if i use Squeeze (the code name) instead stable, sid or anything. should i not to worry about system crash? is it what people here mean to say (who support code name squeeze ) that if i apt-get upgrade/full-upgrade/safe-upgrade will not crash my system if using squeeze. because what i am worried about here is system crash. I'm afraid that I don't understand you. Why should you have a system crash? And what are you trying to achieve? Always use code names, and incidentally Sid is the code-name for unstable, a code-name which never changes. So choose which you want. From the sound of things you want Squeeze. Install Squeeze. Check that Squeeze is in your sources.list, and only Squeeze at this stage. No mention of stable or anything else. Update Squeeze. (aptitude update followed by aptitude full-upgrade or aptitude safe-upgrade.) From then on you will only basically get security updates, though there are periodic point releases for Squeeze to iron out some remaining bugs etc. For now, and while you bed down with Debian/Linux, simply ignore all mentions of Wheezy, stable, Sid, unstable, testing etc. Time enough to come to terms with those when you understand fully what is going on or when Wheezy has become Stable and Squeeze is Old Stable. apt is now preferred to aptitude by many on this list, but I am more familiar with aptitude, and might have got the commands slightly wrong had I attempted to give you them. (I did last time that I did so.) But for what you are doing now, either is fine, and when it comes to upgrading to a new release, the release notes will tell you which to use. But above all, keep things simple for now. And when you ask a question, try to express it without reference to Windows. Many of us do not use Windows, and in my case I have not done so since Windows 98, which I don't remember very well. HTH Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205261517.08770.lisi.re...@gmail.com
Re: how to update Debian OS properly
On Sb, 26 mai 12, 13:39:26, keith wrote: My understanding is - If you apt-get upgrade, you are updating your system (squeeze) When you use apt-get dist-upgrade you change your system from squeeze to wheezy No, see 'man apt-get' for the difference between the two. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: how to update Debian OS properly
On Vi, 25 mai 12, 15:36:40, Ralf Mardorf wrote: On Fri, 2012-05-25 at 18:28 +0500, Muhammad Yousuf Khan wrote: In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package Yesno. I'll say yes, somebody else might recommend http://jaqque.sbih.org/kplug/apt-pinning.html That article, while still useful, - mentions non-US which has been discontinued long time ago (sarge?) - uses sources + pinning by release not code-name[1] [1] this may be due to a bug in apt where pinning by codename was not possible, fixed in the meantime (lenny?). I seem to remember the Debian Reference has a good guide to pinning and it is up-to-date (thanks to Osamu Aoki). Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: how to update Debian OS properly
On Saturday 26 May 2012 18:04:35 Andrei POPESCU wrote: I seem to remember the Debian Reference has a good guide to pinning and it is up-to-date (thanks to Osamu Aoki). Given the OP's confusion, and the fact that he states his main aim as not crashing, would he not do better to stick to pure Squeeze for now? Hopefully, more use of Linux will enable him to stop trying to mimic Windows - a job which Windows itself does rather well ;-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205261839.42048.lisi.re...@gmail.com
Re: how to update Debian OS properly
FWIW, sometime ago this book was announced here: http://debian-handbook.info/browse/stable/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1338053740.2316.0.camel@precise
Re: how to update Debian OS properly
On Sat, 26 May 2012 19:57:19 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 26 mai 12, 13:39:26, keith wrote: My understanding is - If you apt-get upgrade, you are updating your system (squeeze) When you use apt-get dist-upgrade you change your system from squeeze to wheezy No, see 'man apt-get' for the difference between the two. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic I was wrong about dist-upgrade, as has been pointed out above. (Sorry for the bum steer; but when I 'changed' from squeeze to wheezy I did use it.) -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120526191958.1a27c85fd316a03b7c8ca...@gmail.com
how to update Debian OS properly
well, I have questions about upgrading Linux. since i have been using Microsoft for years the concept of upgrade I think is different from Linux upgrade. in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmmuhv5e8frlde1e8_awkq34k8tte9rjtdcz2dhrvrf...@mail.gmail.com
Re: how to update Debian OS properly
PS: I like Synaptic, a GUI for the package management. It automatically set up an upgrade history. You manually can set up a history when using apt, however, Synaptic is very comfortable. A history provides information this way: package_name (1.11.4) to 1.12.0 Note, for the standard repository 1.11.4 is replaced by 1.12.0 too, so you can't simply downgrade using the same repository. You need another repository or to keep packages. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337946438.2251.82.camel@precise
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 15:57 +0500, Muhammad Yousuf Khan wrote: 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. If your repositories are explicit for stable, than there shouldn't happen an upgrade to testing or unstable. To restore your Debian stable in the future, IMO the easiest way is to do a backup before upgrading and to restore from such a backup if needed. You can backup any Linux from another Linux, e.g. from a live media, if you're root and run cd /path/to/debian_stable tar czf backup_name.tar.gz * Globbing (here using *) and following links shouldn't be an issue for your setup. And IMO having several backups/snapshots is more safe than syncing backups. Btw. some dirs can be excluded, but IMO this makes a backup unneeded complicated. - Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337945545.2251.74.camel@precise
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 11:57:28AM BST, Muhammad Yousuf Khan wrote: well, I have questions about upgrading Linux. since i have been using Microsoft for years the concept of upgrade I think is different from Linux upgrade. in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. Read below [0]. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? aptitude update aptitude safe-upgrade [1] 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. There are no patches like in Windows. Patches in free (open source) software are for source code [2]. Upgrading a package you effectively installing a new version of the software. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. You can always install an older version of the package. [0] It seems like you had several entries in your sources.list file(s) - post the content of your file here. [1] safe-upgrade will only upgrade packages and won't remove any other ones [2] yes, I know, you can have binary patches as well Cheers, -- rjc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525115409.ga13...@linuxstuff.pl
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 03:57:28PM +0500, Muhammad Yousuf Khan wrote: in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? If security is your concern, you ought to be running stable as opposed to testing. If you run stable, then ensuring that security.debian.org is listed in the /etc/apt/sources.list will fetch security updates. 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. I'd advise you to subscribe to the security mailing list of the projects which you run on your machine whose security issues you are concerned about. Read this for further details and ideas: http://www.debian.org/security/ 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. This is a little complicated and one could end up hosing one's system. I'd advise you to back up things and do a fresh install of squeeze. HTH. Kumar -- We use Linux for all our mission-critical applications. Having the source code means that we are not held hostage by anyone's support department. -- Russell Nelson, President of Crynwr Software -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525114253.gb5...@bluemoon.alumni.iitm.ac.in
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 06:42 -0500, Kumar Appaiah wrote: I'd advise you to back up things and do a fresh install of squeeze. things for your current install might be /home only. Perhaps xorg.conf and some other files, using cp -pr while you're root. But in the future completely backup using e.g. tar. Note, if you sync, you anyway might lose data, since you might notice some issues after doing several backups and not already with the backup that did cause an issue. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337948255.2251.89.camel@precise
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 4:32 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Fri, 2012-05-25 at 15:57 +0500, Muhammad Yousuf Khan wrote: 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. If your repositories are explicit for stable, than there shouldn't happen an upgrade to testing or unstable. To restore your Debian stable in the future, IMO the easiest way is to do a backup before upgrading and to restore from such a backup if needed. You can backup any Linux from another Linux, e.g. from a live media, if you're root and run cd /path/to/debian_stable tar czf backup_name.tar.gz * will clonezilla live CD work in this case? as i am using it very often and a bit useto with it. Globbing (here using *) and following links shouldn't be an issue for your setup. And IMO having several backups/snapshots is more safe than now this snapshots point raising one more question in my mind. did you means snapshots like XP and Other windows OS supports. for example. i can make a snapshot before installing any service like apache , samba or anything. and after installing , at the end i realize that i messed up the whole box then i can revert my system back to that particular snapshot and i will be at the old stage. can i use snapshot in this context ( sorry for the newbie Questions but i am confused with Microsoft and Linux as there are same services in both OS and working entirely in different way) syncing backups. Btw. some dirs can be excluded, but IMO this makes a backup unneeded complicated. - Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337945545.2251.74.camel@precise -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMk8mzQ+5r=58e-L0TRfUA-M7DX4ojp5Ab=jz6f4ad8...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 4:42 PM, Kumar Appaiah a.ku...@alumni.iitm.ac.in wrote: On Fri, May 25, 2012 at 03:57:28PM +0500, Muhammad Yousuf Khan wrote: in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? If security is your concern, you ought to be running stable as opposed to testing. If you run stable, then ensuring that security.debian.org is listed in the /etc/apt/sources.list will fetch security updates. thanks for the response, but more i concern was a patch like fix patches in Microsoft. i thought it would be working in same way :P as i am already behind the firewall and actively monitoring things so security from outside is not a concern for me. but securing the debian box is also a target to achieve and security should not be neglected. ill subscribe for the mailing list ASAP thanks for the advice. 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. I'd advise you to subscribe to the security mailing list of the projects which you run on your machine whose security issues you are concerned about. Read this for further details and ideas: http://www.debian.org/security/ 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. This is a little complicated and one could end up hosing one's system. I'd advise you to back up things and do a fresh install of squeeze. HTH. Kumar -- We use Linux for all our mission-critical applications. Having the source code means that we are not held hostage by anyone's support department. -- Russell Nelson, President of Crynwr Software -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525114253.gb5...@bluemoon.alumni.iitm.ac.in -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmndqijonpyoejzjwx2x-s-ufrjqnzpry1raqzhaxtn...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 17:19 +0500, Muhammad Yousuf Khan wrote: cd /path/to/debian_stable tar czf backup_name.tar.gz * will clonezilla live CD work in this case? as i am using it very often and a bit useto with it. AFAIK yes, Clonezilla should be ok. now this snapshots point raising one more question in my mind. did you means snapshots like XP and Other windows OS supports. for example. i can make a snapshot before installing any service like apache , samba or anything. and after installing , at the end i realize that i messed up the whole box then i can revert my system back to that particular snapshot and i will be at the old stage. can i use snapshot in this context ( sorry for the newbie Questions but i am confused with Microsoft and Linux as there are same services in both OS and working entirely in different way) If you don't sync, than yes, at least for Linux you'll restore exactly what you had before, at a explicit date. I suspect XP does a kind of sync and I suspect it will be possible for Linux too, but if you tar your Debian or use Clonezilla to do a complete image, nothing could go wrong. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337948846.2251.94.camel@precise
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 4:54 PM, rjc r...@linuxstuff.pl wrote: On Fri, May 25, 2012 at 11:57:28AM BST, Muhammad Yousuf Khan wrote: well, I have questions about upgrading Linux. since i have been using Microsoft for years the concept of upgrade I think is different from Linux upgrade. in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. Read below [0]. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? aptitude update aptitude safe-upgrade [1] ok it will only update the security patches, no matter if what ever i write in source.list? one more question. for example. if i wanted to upgrade. but only to stable version not to unstable or testing. then what could be done to achieve this. if there is no stable version update then it shouldn’t download anything from servers. what i want is not just security patch but also OS to OS upgrade but only stable releases for, example. lenny to new lenny (but stable version) for,example Lenny to Squeez (but stable squeez version) how it is possible? 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. There are no patches like in Windows. Patches in free (open source) software are for source code [2]. Upgrading a package you effectively installing a new version of the software. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. You can always install an older version of the package. [0] It seems like you had several entries in your sources.list file(s) - post the content of your file here. deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main [1] safe-upgrade will only upgrade packages and won't remove any other ones [2] yes, I know, you can have binary patches as well Cheers, -- rjc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525115409.ga13...@linuxstuff.pl -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMí2vyNrwYn+iq5gFem68PfOFj'cJbsCG1DvdeSF=w...@mail.gmail.com
Re: how to update Debian OS properly
On Fri 25 May 2012 at 15:57:28 +0500, Muhammad Yousuf Khan wrote: So the question are 1. how to upgrade only the security patches? Install stable and stick with it. Do not be tempted to alter sources.list in /etc/apt/ 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. This is very, very unlikely to happen. If it did, someone would notice and provide you with a fixed package. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. Forget about it. Re-install stable. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525124214.GD2847@desktop
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337950166.2251.102.camel@precise
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 5:49 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. ok ill comment the sid repo. but would you please give me a hint what do you mean by naming squeeze to stable. Thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337950166.2251.102.camel@precise -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMmCQz20uPBye6tLKU1=-NP97ATAU=tjalh_+wghuey...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 01:37:16PM BST, Muhammad Yousuf Khan wrote: 1. how to upgrade only the security patches? aptitude update aptitude safe-upgrade [1] ok it will only update the security patches, no matter if what ever i write in source.list? No, this will upgrade any upgradeable packages - be it a security update or not. one more question. for example. if i wanted to upgrade. but only to stable version not to unstable or testing. then what could be done to achieve this. if there is no stable version update then it shouldn’t download anything from servers. You don't upgrade stable to stable, you upgrade certain packages within the stable distribution - the above command will achieve just that. what i want is not just security patch but also OS to OS upgrade but only stable releases for, example. lenny to new lenny (but stable version) I don't quite get what you mean by Lenny to new Lenny? Lenny is an unsupported old-stable release. for,example Lenny to Squeez (but stable squeez version) how it is possible? Lenny to squeeze upgrade is somewhat different, you need to have entries for both of these releases in you sources.list file(s). aptitude update aptitude full-upgrade will do what you want here. Bear in mind that full-upgrade will remove packages, i.e. the ones which are in conflict with the new ones. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. You can always install an older version of the package. [0] It seems like you had several entries in your sources.list file(s) - post the content of your file here. deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main This is the mistake you made, you've mixed both squeeze (stable) with sid (unstable release) adding squeeze-backports on top of it. I'd recommend reading about mixing of stable, testing unstable - stay away from experimental ;^) - releases and what can you do with APT pinning. Until then, stick with stable. Cheers, -- rjc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525130609.ga15...@linuxstuff.pl
Re: how to update Debian OS properly
On Fri, 25 May 2012 17:37:16 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: [...] [0] It seems like you had several entries in your sources.list file(s) - post the content of your file here. deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main Delete the last line from your /etc/apt/sources.list (# deb http://ftp.de.debian.org/debian sid main) And, I believe you can change 'squeeze' to 'stable', remain updating the stable version, whatever the name. Just as an aside; to make it easy on yourself, if you need to re-install again, make your partitioning scheme friendly. i.e. One partition for swap, One partition for the / (system), at least another for your /home (/or data); then if you have to re-install, only overwrite your / partition. You should, of course, still have backups of your data as well. -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525141048.181b7356179f064614743...@gmail.com
Re: how to update Debian OS properly
ok found a website for which generates source.list http://debgen.simplylinux.ch/ deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb-src http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free please confirm if above repositories are good to go with, In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package On Fri, May 25, 2012 at 6:10 PM, keith km3...@gmail.com wrote: On Fri, 25 May 2012 17:37:16 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: [...] [0] It seems like you had several entries in your sources.list file(s) - post the content of your file here. deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main Delete the last line from your /etc/apt/sources.list (# deb http://ftp.de.debian.org/debian sid main) And, I believe you can change 'squeeze' to 'stable', remain updating the stable version, whatever the name. Just as an aside; to make it easy on yourself, if you need to re-install again, make your partitioning scheme friendly. i.e. One partition for swap, One partition for the / (system), at least another for your /home (/or data); then if you have to re-install, only overwrite your / partition. You should, of course, still have backups of your data as well. -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMmf36qZOXps0LuG1mxukC6kfJU4aszEN7TtsQ4=U=q...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 14:06 +0100, rjc wrote: Lenny to squeeze upgrade is somewhat different, you need to have entries for both of these releases in you sources.list file(s). On Fri, 2012-05-25 at 17:58 +0500, Muhammad Yousuf Khan wrote: ok ill comment the sid repo. but would you please give me a hint what do you mean by naming squeeze to stable. Comment out the backports too. Instead of e.g. deb http://ftp.us.debian.org/debian squeeze main non-free contrib use deb http://ftp.us.debian.org/debian stable main non-free contrib Than you'll get stable, what ever it's named. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337951764.2251.110.camel@precise
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 4:47 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: PS: I like Synaptic, a GUI for the package management. It automatically set up an upgrade history. You manually can set up a history when using apt, however, Synaptic is very comfortable. A history provides information this way: package_name (1.11.4) to 1.12.0 do you know any CLI work in same way. i am not using GUI. Note, for the standard repository 1.11.4 is replaced by 1.12.0 too, so you can't simply downgrade using the same repository. You need another repository or to keep packages. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337946438.2251.82.camel@precise -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmntk9fntne7s8mvs4mthsxybhr+uysqmnicsov9r4m...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 18:28 +0500, Muhammad Yousuf Khan wrote: In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package Yesno. I'll say yes, somebody else might recommend http://jaqque.sbih.org/kplug/apt-pinning.html Do you need src? Src repos provide source code only. You might need headers to compile src codes from sourceforge etc., but seldom a Debian src. Google if there is a stable stable-updates repository etc. too. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337953000.2251.114.camel@precise
Re: how to update Debian OS properly
On Vi, 25 mai 12, 14:49:26, Ralf Mardorf wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. I don't agree. IMNSHO pinning (or simply setting Default-Release in apt.conf) is the correct way to use a mixed environment, because: - installing even one package from the other repository can have unwanted side effects without pinning. Use correct pinning and the '-t' switch instead - one will not be aware of any possibly security related updates[1] [1] even unstable has some degree of security support, because the maintainer is usually aware of any stable security updates and will in most cases update the package in unstable too. Such packages are uploaded with 'urgency=high' and will also migrate faster to testing if possible. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 8:49 AM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. That means that the OP'll be upgraded automatically to wheezy when it becomes stable! No one wants to do that. You want to choose when to upgrade, if at all... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=Sy6p0zjWA-9ePzfwpygAxnTFGPuBfOiCW4kG0=nzej...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 18:36 +0500, Muhammad Yousuf Khan wrote: A history provides information this way: package_name (1.11.4) to 1.12.0 do you know any CLI work in same way. i am not using GUI. A script using apt, aptitude or dpkg might be able to generate a history too. I once used one of those commands to do this. Can't remember what command I used. Man pages and --help should help. Writing shell scripts in a naive way is easy to learn. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337953530.2251.120.camel@precise
Re: how to update Debian OS properly
On Vi, 25 mai 12, 15:16:04, Ralf Mardorf wrote: Instead of e.g. deb http://ftp.us.debian.org/debian squeeze main non-free contrib use deb http://ftp.us.debian.org/debian stable main non-free contrib Than you'll get stable, what ever it's named. ... but it might catch you unprepared if you don't follow release announcements. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 16:50 +0300, Andrei POPESCU wrote: On Vi, 25 mai 12, 15:16:04, Ralf Mardorf wrote: Instead of e.g. deb http://ftp.us.debian.org/debian squeeze main non-free contrib use deb http://ftp.us.debian.org/debian stable main non-free contrib Than you'll get stable, what ever it's named. ... but it might catch you unprepared if you don't follow release announcements. Again a good point and in this case I prefer using version names such as squeeze too. I should have mentioned this too, instead of simply answering the question, without further explanation. Apologize to the OP. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337954181.2251.125.camel@precise
Re: how to update Debian OS properly
On Vi, 25 mai 12, 15:45:30, Ralf Mardorf wrote: On Fri, 2012-05-25 at 18:36 +0500, Muhammad Yousuf Khan wrote: A history provides information this way: package_name (1.11.4) to 1.12.0 do you know any CLI work in same way. i am not using GUI. A script using apt, aptitude or dpkg might be able to generate a history too. I once used one of those commands to do this. Can't remember what command I used. Man pages and --help should help. Writing shell scripts in a naive way is easy to learn. dpkg, apt and aptitude have their own log files under /var/log/ (of course). Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
RE: how to update Debian OS properly
Hi, Instead of e.g. deb http://ftp.us.debian.org/debian squeeze main non-free contrib use deb http://ftp.us.debian.org/debian stable main non-free contrib Than you'll get stable, what ever it's named. ... but it might catch you unprepared if you don't follow release announcements. And just as with Microsoft upgrades it never realy quite workst just the way you thought it would work so Allways update the way described in the upgrade notes and that means one needs to have the release name like lenny, squeeze, etc. in the sources list and not stable so one can do a proper upgrade at the time of ones choosing. Bonno Bloksma -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d70ac34...@hglexch-01.tio.nl
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 02:46:50PM BST, Tom H wrote: On Fri, May 25, 2012 at 8:49 AM, Ralf Mardorf You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. That means that the OP'll be upgraded automatically to wheezy when it becomes stable! No one wants to do that. You want to choose when to upgrade, if at all... I agree here, don't change squeeze to stable if you don't want to get into trouble when wheezy comes out. -- rjc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525135946.ga18...@linuxstuff.pl
Re: how to update Debian OS properly
On Fri, 2012-05-25 at 16:45 +0300, Andrei POPESCU wrote: - one will not be aware of any possibly security related updates Good point -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1337953797.2251.121.camel@precise
Re: how to update Debian OS properly
On Fri, 25 May 2012 15:57:28 +0500, Muhammad Yousuf Khan wrote: well, I have questions about upgrading Linux. since i have been using Microsoft for years the concept of upgrade I think is different from Linux upgrade. in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. Mmm, you should run first apt-get update to refresh the available packages. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. The first thing you have to look at is the sources (/etc/apt/ sources.list). This is _the key_ for having a happy system :-) The second thing is knowing what's what you want to get: 1/ Having a stable system 2/ Having a testing/sid system For 1/ you have to point your sources to squeeze and add a security repo. That's all. For 2/ well, you have to point your sources to a testing or sid version and you have to update the whole system on a regular basis to avoid breaking things. In my case, I only use apt-get update apt-get dist-upgrade in both, stable and testing distributions: the sources will make the difference here. So the question are 1. how to upgrade only the security patches? Stable versions only get security pathes (and a few of enhancements) so this is not a problem here. For testing/sid you have to update the whole system. 2. if the upgrade patch trigger any critical issue. Like any service like hosting, filesharing or squid got effected by the update, how come we know which patch cause this problem and how to remove that specific patch because in Microsoft I have seen that security patches and OS patches some time make problems when run along with ongoing services. You can remove/revert any package by reading the apt logs and using synaptic or aptitude to uninstall a specific package version and stick to the desired one. 3. how to revert back to old OS, for example, in my case i upgraded my system from 6.0.4 to Wheezy/SID now want to revert things back. I'm not sure if that will work, at least not flawlessly; you can fall into a dependency hell and lots of broken packages. Anyway, by the kind of questions you ask, I would suggest first a careful reading of the FAQ: http://www.debian.org/doc/manuals/debian-faq/ Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jpo450$4v3$6...@dough.gmane.org
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 06:42:53AM -0500, Kumar Appaiah wrote: On Fri, May 25, 2012 at 03:57:28PM +0500, Muhammad Yousuf Khan wrote: in a testing environment I was trying to upgrade the security patches and I run the command apt-get upgrade. It ran fine, but at the end it upgraded my whole OS, first my test machine was showing Debian version 6.0.4 now after the upgrade it shifted to Wheezy/SID which I think is unstable. In Microsoft when we upgrade the OS. it downloads only the security and OS patches. So the question are 1. how to upgrade only the security patches? If security is your concern, you ought to be running stable as opposed to testing. If you run stable, then ensuring that security.debian.org is listed in the /etc/apt/sources.list will fetch security updates. Or, you could run testing and put in sources.list: deb http://security.debian.org/ wheezy/updates main contrib non-free Still, I do consider stable to be safer, and do stick with it... -- ❤ ♫ ❤ ♫ ❤ ♫ ❤ Indulekha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525145453.GA13504@radhesyama
Re: Re: how to update Debian OS properly
deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb-src http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free please confirm if above repositories are good to go with, There is a problem because you have mixed stable and squeeze. It will work from now until wheezy is released, then your system will partly upgrade itself to wheezy and something will likely break. To fix that, use either stable or squeeze exclusively. I prefer to use squeeze, as recommended by most of the people who have commented here, so I can choose a convenient time to perform the upgrade to the next release. I hope this helps. -- Cheers, Clive -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525150915.GA5209@lister.localdomain
Re: how to update Debian OS properly
On 25.05.2012 15:49, Ralf Mardorf wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. Is it safe to use stable instead of squeeze? Are there usually any conflicts or anything what would need full-upgrade whenever new stable is named? I am asking just for curiosity, I am Sid user. -- [Mika Suomalainen](https://mkaysi.github.com/) || [gpg --keyserver pool.sks-keyservers.net --recv-keys 4DB53CFE82A46728](http://mkaysi.github.com/PGP/key.txt) || [Why do I sign my emails?](http://mkaysi.github.com/PGP/WhyDoISignEmails.html) || [Please don't send HTML.](http://mkaysi.github.com/articles/complaining/HTML.html) || [Please don't toppost](http://mkaysi.github.com/articles/complaining/topposting.html) || [This signature](https://gist.github.com/2643070) || signature.asc Description: OpenPGP digital signature
Re: how to update Debian OS properly
On 2012-05-25 17:53 +0200, Mika Suomalainen wrote: Is it safe to use stable instead of squeeze? No, this is very much not recommended. Are there usually any conflicts or anything what would need full-upgrade whenever new stable is named? Yes, about every two years when a new major Debian stable release is made. With stable in sources.list, you may find yourself upgrading to the new release when you're not expecting it and are unprepared, similar to the situation the OP has got himself into. Using the codename avoids such surprises at the cost of having to alter the sources.list file every two years (with a time window of one year where more than one release is supported). Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871um8nrjd@turtle.gmx.de
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 11:53 AM, Mika Suomalainen mika.henrik.mai...@hotmail.com wrote: On 25.05.2012 15:49, Ralf Mardorf wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. Is it safe to use stable instead of squeeze? Are there usually any conflicts or anything what would need full-upgrade whenever new stable is named? No. No need for aptitude full-upgrade, even apt-get upgrade/aptitude safe-upgrade will pull in wheezy (partially) when it becomes stable. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sxbfo9v909tyot1g2o8zyvufo6fvz6bmd6zld2cgsg...@mail.gmail.com
Re: how to update Debian OS properly
On Fri, 25 May 2012 18:28:29 +0500 Muhammad Yousuf Khan sir...@gmail.com wrote: ok found a website for which generates source.list http://debgen.simplylinux.ch/ deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb-src http://ftp.debian.org/debian/ squeeze-updates main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free please confirm if above repositories are good to go with, In conclusion i found out that i should stick to stable and should not play with the source list until unless it is necessary. even if i add a repo then i must comment it after installing the whatever package I think that sources.list will work OK (I believe it will prioritize the us sites if they come first) With regard to using stable as a designation; I don't, I use Squeeze, but I thought I would just mention it. -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525193831.31d79b1641243dd1030f5...@gmail.com
Re: how to update Debian OS properly
On Fri, 25 May 2012 19:38:31 +0100 keith km3...@gmail.com wrote: deb http://ftp.us.debian.org/debian stable main contrib non-free deb-src http://ftp.us.debian.org/debian stable main contrib non-free My apologies, I somehow missed that, as someone else has pointed out. Use squeeze not stable. (I know it's no excuse but I was distracted by someone whilst I was in the middle of replying, again sorry for missing that.) -- keith keith...@yahoo.co.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/361072.18951...@smtp151.mail.ukl.yahoo.com
Re: how to update Debian OS properly
On Friday 25 May 2012 18:23:37 Tom H wrote: On Fri, May 25, 2012 at 11:53 AM, Mika Suomalainen mika.henrik.mai...@hotmail.com wrote: On 25.05.2012 15:49, Ralf Mardorf wrote: On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote: deb http://security.debian.org/ squeeze/updates main deb-src http://security.debian.org/ squeeze/updates main deb http://backports.debian.org/debian-backports squeeze-backports main deb http://ftp.de.debian.org/debian sid main You're issue is related to the sid repository. If you need something from sid, then uncomment it and after that comment it. Don't feel secure using pinning. You can name the repositories stable instead of squeeze, so it will use stable what ever Debian stable is named. Is it safe to use stable instead of squeeze? Are there usually any conflicts or anything what would need full-upgrade whenever new stable is named? No. No need for aptitude full-upgrade, even apt-get upgrade/aptitude safe-upgrade will pull in wheezy (partially) when it becomes stable. I prefer to use aptitude full-upgrade routinely - but I have the code name in my sources.list, not stable or testing. I then change the code name when I want to get the more recent version. So, Squeeze not stable, Muhammad. you could get in quite a mess at the changeover point from Squeeze to Wheezy if you have stable in your sources.list, as several people have pointed out. I can't comment on your Windows analogies as I don't use Windows. I think that you need to expect that Linux will be different from whatever you used in Windows. They are very different OSs. FWIW, I do most of my admin from the CLI, including updating and upgrading. So yes, it can be done from the CLI. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205252130.54213.lisi.re...@gmail.com
Re: how to update Debian OS properly
On Fri, May 25, 2012 at 02:17:35PM +0200, Ralf Mardorf wrote: things for your current install might be /home only. Perhaps xorg.conf and some other files, using cp -pr while you're root. But in the future completely backup using e.g. tar. Note, if you sync, you anyway might lose data, since you might notice some issues after doing several backups and not already with the backup that did cause an issue. Yes, sync is not backup (that is, an rsync by itself is not adequate coverage). But neither is tar! A proper backup solution is something that covers the seven points listed at http://www.taobackup.com/. You can build a solution using parts like tar, or rsync, or higher level tools like rdiff-backup, or bacula. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525220506.GE31519@debian
How to update bios to support 64-bit cpu in Debian?
I have a intel dual-core cpu which supports 64-bit mode, and I want to install a IA64 etch on it, so i burn the etch IA64 iso CD, but i cannot boot from it! I guess it's caused by my bios not supporting 64-bit mode, it's a ami bios v02.57 which has neither information about 64bit nor hyper threading features, so i want to update the bios. Is there any tool to update the ami bios on a msi motherboard in debian? thanks! - Buddha Debian GNU/Linux MSN/aMSN: [EMAIL PROTECTED] -
Re: How to update bios to support 64-bit cpu in Debian?
Try the amd64 disk. The IA64 disk is for Itanium CPUs, which are different from most 64-bit CPUs. On Fri, Jun 20, 2008 at 8:53 PM, Star Liu [EMAIL PROTECTED] wrote: I have a intel dual-core cpu which supports 64-bit mode, and I want to install a IA64 etch on it, so i burn the etch IA64 iso CD, but i cannot boot from it! I guess it's caused by my bios not supporting 64-bit mode, it's a ami bios v02.57 which has neither information about 64bit nor hyper threading features, so i want to update the bios. Is there any tool to update the ami bios on a msi motherboard in debian? thanks! - Buddha Debian GNU/Linux MSN/aMSN: [EMAIL PROTECTED] -
