Re: Upgrade from woody to sarge - ssh strangeness
Probably more suited to debian-user, so I have Cc'd and set MFT
accordingly.
On Mon, Jan 15, 2007 at 02:43:09PM +0100, Turbo Fredriksson wrote:
[...]
Everything works linux (woody, sarge and dapper) to linux, but from
windows (SecureCRT) to linux, I don't even get the option to enter
a password...
[...]
[SSH LOCAL ONLY] : RECV : USERAUTH_FAILURE, continuations
[publickey,keyboard-interactive]
[SSH LOCAL ONLY] : SEND: Disconnect packet: Unable to authenticate using any
of the configured authentication methods.
[...]
Received disconnect from windows_machine_behind_linux_NAT_firewall: 14:
Unable to authenticate using any of the configured authentication methods.
[...]
If memory serves, you need to edit /etc/ssh/sshd_config, uncomment
the PasswordAuthentication yes line, and reload ssh.
The SecureCRT version is a little old, but...
[...]
Yeah, I believe newer versions of SecureCRT support not only
password but also the newer keyboard-interactive authentication.
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP([EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]);
MUD([EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
On Tue, Aug 08, 2006 at 11:23:38PM -0500, Russell L. Harris wrote: Go to another machine and Make yourself a GRUB boot CD (or, if you prefer, a boot floppy). You can boot from the GRUB CD, and then repair your system. Everybody ought to keep a GRUB boot CD handy! How do you make a grub boot CD or floppy? And how do you use it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
[EMAIL PROTECTED] wrote: How do you make a grub boot CD or floppy? And how do you use it? /usr/share/doc/grub/README contains a link to grub's home page. This contains an excellent manual with all the information you require - and much more... alternatively you could install grub-doc and then find the information in /usr/share/doc/grub-doc chapter 3, Installation describes to install grub on hard disk, floppy, or cd-rom To use it: just set your bios to boot from floppy/CD-rom. Johannes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
On Wed, 2006-09-08 at 08:08 -0400, [EMAIL PROTECTED] wrote: On Tue, Aug 08, 2006 at 11:23:38PM -0500, Russell L. Harris wrote: Go to another machine and Make yourself a GRUB boot CD (or, if you prefer, a boot floppy). You can boot from the GRUB CD, and then repair your system. Everybody ought to keep a GRUB boot CD handy! How do you make a grub boot CD or floppy? And how do you use it? This might help: http://www.linuxjournal.com/article/4622 Also, googling for grub boot floppy gives a whole days worth reading. Grab a beverage and enjoy! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
[EMAIL PROTECTED] writes: On Tue, Aug 08, 2006 at 11:23:38PM -0500, Russell L. Harris wrote: Go to another machine and Make yourself a GRUB boot CD (or, if you prefer, a boot floppy). You can boot from the GRUB CD, and then repair your system. Everybody ought to keep a GRUB boot CD handy! How do you make a grub boot CD or floppy? And how do you use it? If you have a CD burner and can access the Internet, simply download the CD ISO image for the GRUB boot CD. Use Google to search for the image, or go to the GRUB web site. Once you have burned the ISO image to CD, go to the machine you wish to boot, set the BIOS to boot from CD, insert the CD, and press the RESET button. The fact that you already have LILO installed as a boot manager on the machine doesn't matter. If you read the GRUB manual, you can learn how to use GRUB to explore your drives and find and boot any of the operating systems you have installed. GRUB can boot anything. You can boot from the GRUB CD, or you can use the GRUB CD to install GRUB as a replacement for LILO. GRUB is really nice and easy to install, configure, and use. One of the first things you may wish to do after you install GRUB is to go to the configuration file, which is '/boot/grub/menu.lst' and place a '#' at the beginning of the line which reads 'timeout 5'. This comments-out the timeout parameter, so that GRUB waits until you make a selection; otherwise, GRUB automatically boots the default selection once the timeout expires. Or you may wish to increase the timeout parameter from 5 (seconds) to 15 or so; 5 seconds is a little short. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
help with upgrade from woody to sarge...
Hi, I have upgraded from woody to sarge and after a very long list of packages being installed, my system is a mess: Right after the upgrade, I launched X and kdm (I had kdm and kde working fine prior to the upgrade) and at log in, it tried to launch gnome, and it could not create a desktop. I managed to log out. Then I restarted the system and found that it could not boot again. The computer is stuck at lilo (it only prints out the first two letters: LI) and then it hungs. I don't have any important stuff on it so I can re-format the HD and do a clean install. However, if there's something else I can do that would not take all that time, I would like to try it. But first, what can I do to make it bootable again? or at least boot from a cd? Thanks, Mario Flores [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
On Tue, Aug 08, 2006 at 10:48:10PM -0400, Mario Flores wrote: Hi, I have upgraded from woody to sarge and after a very long list of packages being installed, my system is a mess: Right after the upgrade, I launched X and kdm (I had kdm and kde working fine prior to the upgrade) and at log in, it tried to launch gnome, and it could not create a desktop. I managed to log out. Then I restarted the system and found that it could not boot again. The computer is stuck at lilo (it only prints out the first two letters: LI) and then it hungs. I don't have any important stuff on it so I can re-format the HD and do a clean install. However, if there's something else I can do that would not take all that time, I would like to try it. But first, what can I do to make it bootable again? or at least boot from a cd? boot from knoppix and chroot in to redo your lilo might work. A signature.asc Description: Digital signature
Re: help with upgrade from woody to sarge...
On 08/08/2006 09:48 PM, Mario Flores wrote: Hi, I have upgraded from woody to sarge and after a very long list of packages being installed, my system is a mess: Right after the upgrade, I launched X and kdm (I had kdm and kde working fine prior to the upgrade) and at log in, it tried to launch gnome, and it could not create a desktop. I managed to log out. Then I restarted the system and found that it could not boot again. The computer is stuck at lilo (it only prints out the first two letters: LI) and then it hungs. Use a bootable Linux CD to fix your /etc/lilo.conf. LILO and lilo.conf have man-pages: man lilo man lilo.conf After you have put the right stuff into /etc/lilo.conf, you'll have to tell lilo to install the bootloader and rebuild its map file. I've you've booted from a CD, and your Debian installation does _not_ use udev, and you've mounted your root partition under /mnt/myroot/, then you can probably do this: lilo -v -r /mnt/myroot This tells lilo to chroot into your Debian installation's root directory before reading the /etc/lilo.conf file and accessing the device notes /dev. If you use udev, /dev might not be populated properly, and so all bets are off. I don't have any important stuff on it so I can re-format the HD and do a clean install. However, if there's something else I can do that would not take all that time, I would like to try it. But first, what can I do to make it bootable again? or at least boot from a cd? Knoppix and Kanotix are the best boot CDs probably, but you can also probably use the first Debian installation CD to boot. However, AFAIK, that CD wants to install GRUB as the bootloader--not LILO. And allowing it to do that might not be such a bad idea since Sarge's default boot loader is GRUB. Thanks, [...] You're welcome and good luck. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with upgrade from woody to sarge...
Andrew Sackville-West [EMAIL PROTECTED] writes: On Tue, Aug 08, 2006 at 10:48:10PM -0400, Mario Flores wrote: I have upgraded from woody to sarge and after a very long list of packages being installed, my system is a mess: Right after the upgrade, I launched X and kdm (I had kdm and kde working fine prior to the upgrade) and at log in, it tried to launch gnome, and it could not create a desktop. I managed to log out. Then I restarted the system and found that it could not boot again. The computer is stuck at lilo (it only prints out the first two letters: LI) and then it hungs. I don't have any important stuff on it so I can re-format the HD and do a clean install. However, if there's something else I can do that would not take all that time, I would like to try it. But first, what can I do to make it bootable again? or at least boot from a cd? Why are you messing around with LILO? LILO is obsolescent, if not obsolete. (I've forgotten; perhaps LILO still was an option with Woody.) You should be using GRUB, which is the boot loader which newer Debian systems install by default. Go to another machine and Make yourself a GRUB boot CD (or, if you prefer, a boot floppy). You can boot from the GRUB CD, and then repair your system. Everybody ought to keep a GRUB boot CD handy! RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
James Haskell wrote: my /etc/inputrc (without comments) is: set input-meta on set output-meta on so, i don't think my readline configuration is the cause. That looks normal. The problem now is that what you describe sounds really normal to me. And apparently to the other responders. But what you described as your previous behavior is what I can't explain. I don't see that on my old woody machines. I can't explain your previous behavior. just curious, what version(s) of bash and libreadline do you have installed on your sarge machine. i have bash (version 2.05b-26) libreadline4 (version 4.3-11) libreadline5 (version 5.0-10) As much as possible I run released stable systems. So I am running the Sarge versions, the same as you show here. I just looked and Bash actually uses a statically compiled in version of libreadline. So that will be the same if the bash version is the same. Bob signature.asc Description: Digital signature
pager changed after upgrade from woody to sarge:
hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? __ Click here to donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
--- James Haskell [EMAIL PROTECTED] wrote: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. As root: update-alternatives --config pager -- Thomas Adam Send instant messages to your online friends http://uk.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
On Mon, 05 Sep 2005 the mental interface of James Haskell told: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? echo export PAGER=less .bashrc echo export aCeiMs=LESS .bashrc #Change less options to your needs. Elimar -- what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
James Haskell wrote: i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. Are you sure that it is /bin/more and not the bash readline built-in pager? The documentation for readline which is used by bash says this: page-completions (On) If set to On, readline uses an internal more-like pager to display a screenful of possible completions at a time. I believe you are seeing the built-in pager and not the external one. I do not think bash spawns an external pager for this operation. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. No need to chase. Just use ask the system. update-alternatives --display pager how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? I think you are incorrect. I do not believe bash is using an external pager. I just now tested a woody and a sarge system and could not see any noticeable difference in how bash operates with regards to completion. If you are seeing differences I am guessing it has to do with bash and libreadline upgrades combined with your own personal readline configuration. For me both used the bash readline internal built-in pager. It says --more-- but that does not mean it is using the /bin/more external program. It is using the built-in. You can verify this for yourself by looking at the 'ps -efH' output and seeing that your command shell is not spawning any external commands while in the built-in pager. (Hint: Use the tty to find the other bash shell.) Bob signature.asc Description: Digital signature
Re: pager changed after upgrade from woody to sarge:
James Haskell wrote: i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. Not really, it's an internal pager similar to /bin/more. Differs from the system pager that programs like man use. Previously bash didn't page at all, if I recall correctly. $ man bash /pager # use the search function page-completions (On) If set to On, readline uses an internal more-like pager to display a screenful of possible completions at a time. Edit or create ~/.inputrc to contain the line: set page-completions off and new instances of bash will no longer use the internal pager. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
James Vahn wrote: Edit or create ~/.inputrc to contain the line: set page-completions off and new instances of bash will no longer use the internal pager. I think you knew this but just did not say it explicitly. But for the original poster... But then no pager will be used at all. All of the output will scroll. This still will not cause bash to use an external pager. It just won't say --more-- ever again. But I don't think that is what is really wanted. :-) Bob signature.asc Description: Digital signature
Re: pager changed after upgrade from woody to sarge:
On Mon, Sep 05, 2005 at 06:55:09AM -0700, James Haskell wrote: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. AFAIK, it shouldn't be using an external pager at all; it should simply write to stdout. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. That seems right. how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? It seems that less *is* your default pager. What happens if you try $ ls /usr/include/ | pager ? -- PJR :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
Thomas, as root, i ran: update-alternatives --config pager here is the output: There are 4 alternatives which provide `pager'. SelectionAlternative --- 1/bin/more *+2/usr/bin/less 3/usr/bin/most 4/usr/bin/w3m Press enter to keep the default[*], or type selection number: 2 Using `/usr/bin/less' to provide `pager'. unfortunately, this did not fix my problem. looks like less is already my default pager; i do not override this in ~/.bash_profile or ~/.bashrc. --- Thomas Adam [EMAIL PROTECTED] wrote: --- James Haskell [EMAIL PROTECTED] wrote: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. As root: update-alternatives --config pager -- Thomas Adam Send instant messages to your online friends http://uk.messenger.yahoo.com __ Click here to donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
Peter, the result of running: ls /usr/include/ | pager is that the output of ls is piped to less. i think your're right in that less is already my default pager. --- Peter J Ross [EMAIL PROTECTED] wrote: On Mon, Sep 05, 2005 at 06:55:09AM -0700, James Haskell wrote: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. AFAIK, it shouldn't be using an external pager at all; it should simply write to stdout. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. That seems right. how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? It seems that less *is* your default pager. What happens if you try $ ls /usr/include/ | pager ? -- PJR :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
Bob, you're right. after trying the 'ps -efH', i can verify that bash is using the built-in pager and not /bin/more. If you are seeing differences I am guessing it has to do with bash and libreadline upgrades combined with your own personal readline configuration. my /etc/inputrc (without comments) is: set input-meta on set output-meta on so, i don't think my readline configuration is the cause. just curious, what version(s) of bash and libreadline do you have installed on your sarge machine. i have bash (version 2.05b-26) libreadline4 (version 4.3-11) libreadline5 (version 5.0-10) thanks. --- Bob Proulx [EMAIL PROTECTED] wrote: James Haskell wrote: i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. Are you sure that it is /bin/more and not the bash readline built-in pager? The documentation for readline which is used by bash says this: page-completions (On) If set to On, readline uses an internal more-like pager to display a screenful of possible completions at a time. I believe you are seeing the built-in pager and not the external one. I do not think bash spawns an external pager for this operation. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. No need to chase. Just use ask the system. update-alternatives --display pager how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? I think you are incorrect. I do not believe bash is using an external pager. I just now tested a woody and a sarge system and could not see any noticeable difference in how bash operates with regards to completion. If you are seeing differences I am guessing it has to do with bash and libreadline upgrades combined with your own personal readline configuration. For me both used the bash readline internal built-in pager. It says --more-- but that does not mean it is using the /bin/more external program. It is using the built-in. You can verify this for yourself by looking at the 'ps -efH' output and seeing that your command shell is not spawning any external commands while in the built-in pager. (Hint: Use the tty to find the other bash shell.) Bob __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
Bob, in my previous post, i forgot to mention that i have no ~/.inputrc file. --- Bob Proulx [EMAIL PROTECTED] wrote: James Haskell wrote: i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. Are you sure that it is /bin/more and not the bash readline built-in pager? The documentation for readline which is used by bash says this: page-completions (On) If set to On, readline uses an internal more-like pager to display a screenful of possible completions at a time. I believe you are seeing the built-in pager and not the external one. I do not think bash spawns an external pager for this operation. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. No need to chase. Just use ask the system. update-alternatives --display pager how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? I think you are incorrect. I do not believe bash is using an external pager. I just now tested a woody and a sarge system and could not see any noticeable difference in how bash operates with regards to completion. If you are seeing differences I am guessing it has to do with bash and libreadline upgrades combined with your own personal readline configuration. For me both used the bash readline internal built-in pager. It says --more-- but that does not mean it is using the /bin/more external program. It is using the built-in. You can verify this for yourself by looking at the 'ps -efH' output and seeing that your command shell is not spawning any external commands while in the built-in pager. (Hint: Use the tty to find the other bash shell.) Bob __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pager changed after upgrade from woody to sarge:
elimar, i tried: echo export PAGER=less ~/.bashrc echo export aCeiMs=LESS ~/.bashrc not sure about the second line; shouldn't it be echo export LESS=aCeiMs ~/.bashrc anyway i tried both ways -- unfortunately, neither of these work. if you follow this thread, it seems that less is already my default pager; bash is using an internal more-like pager. --- Elimar Riesebieter [EMAIL PROTECTED] wrote: On Mon, 05 Sep 2005 the mental interface of James Haskell told: hello all, i just upgraded from woody to sarge, and it *seems* that in the process, my pager has changed from /usr/bin/less to /bin/more. e.g. if i type: cd /usr/include/ tab tab bash displays: Display all 370 possibilities? (y or n) when i type y, bash lists the files using /bin/more. chase `which pager` says that /usr/bin/pager points to /usr/bin/less. how do i get less to be my default pager? and am i correct in concluding that the upgrade changed my pager? echo export PAGER=less .bashrc echo export aCeiMs=LESS .bashrc #Change less options to your needs. Elimar -- what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Click here to donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Name resolver problem after upgrade from woody to sarge
Hi, (sorry if you receive this twice, I sent it a couple of days ago but the email has still not appeared in the archives, so I try again) I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Name resolver problem after upgrade from woody to sarge
Hi, I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. /Mats -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Name resolver problem after upgrade from woody to sarge
[This message has also been posted to linux.debian.user.] In article [EMAIL PROTECTED], Mats Bengtsson wrote: Hi, I have just upgraded my machine at home from woody to sarge and now the name resolution doesn't work anymore. To be more precise, programs such as Mozilla or lynx don't manage to lookup any names, but i can use host or dig or nslookup (or even socket.gethostbyname(...) in Python) without My impression is Mozilla only reads /etc/resolv.conf once, when it's launched. If you change resolv.conf, you have to exit mozilla and start a new one. I haven't seen Lynx have that problem. problems. Also, once I have looked up a name using host, for example, then Mozilla can also find it, at least for some minutes of time. In that case, I would look for a problem with the forwarder (dns cache) that you're pointing at with resolv.conf. I have tried looking in different documents and HOWTO:s and Google but haven't found anything really related. Also, I don't know the inner workings of name resolution in Linux, so I may have missed something obvious. Some facts on my setup: - I use an ADSL connection with a combined ADSL modem/router configured as a DNS relay. - ifup seems to detect this setup correctly and writes nameserver 192.168.1.1 in /etc/resolv.conf Is there really a name server at 192.168.1.1? Does it work? Try host kernel.org 192.168.1.1 and see. - Since I only have 2 machines connected to the router, I haven't setup any DNS for my private network and have simply added a line 192.168.1.2 MatsPC in /etc/hosts At the moment, I don't really have any clue on where to search, so any hints are welcome. While you're working on your home network, routers, resolv.conf, ifup/down, etc, use a reliable name server on the public Internet. After everything else is working, *then* worry about a local forwarder. Maybe you don't need one. Don't assume the name server you're told about by DHCP actually works. There are still a lot of name servers around that answer all queries from everywhere. They'll die (or be secured) if somebody publishes software that uses them by default, but short of that the potential for abuse isn't too bad. Pick half a dozen of your favorite ISPs and look up their name servers in whois. Try all the listed name servers. Some will work, some won't. Chances are you'll find at least two that answer queries about unrelated domains as well. A certain large telco on the West coast of the US, that doesn't have any network tech support for its residential DSL customers, has one. Perhaps the last technical person forgot to shut it off when they laid her or him off. The largest cable TV operator in the US, who happens also to be #2 on the Spamhaus.org list, has another. And the #1 spam supporter worldwide (see spamhaus top 10) has two more. Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem with upgrade from Woody to Sarge
hello, i got a problem during the upgrade from Woody to Sarge with apache (Version 1) and the module libapache-mod-php4. I get the error: Setting up libapache-mod-php4 (4.3.10-15) ... Error: mod_webapp.so does not have a corresponding .info file. what can i do to fix this? thanks a lots for some help. Pierre log file: Errors were encountered while processing: fetchmail libapache-mod-php4 php4 E: Sub-process /usr/bin/dpkg returned an error code (1) Ack! Something bad happened while installing packages. Trying to recover: Setting up fetchmail (6.2.5-12) ... Starting mail retrieval agent: fetchmail (failed). dpkg: error processing fetchmail (--configure): subprocess post-installation script returned error exit status 1 Setting up libapache-mod-php4 (4.3.10-15) ... Error: mod_webapp.so does not have a corresponding .info file. The above errors might cause apache to not work properly or start Please refer to the documentation on how to fix it or report it to Debian Apache Mailing List debian-apache@lists.debian.org if in doubt on how to proceed dpkg: error processing libapache-mod-php4 (--configure): subprocess post-installation script returned error exit status 128 dpkg: dependency problems prevent configuration of php4: php4 depends on libapache-mod-php4 (= 4:4.3.10-15) | libapache2-mod-php4 (= 4:4.3.10-15); however: Package libapache-mod-php4 is not configured yet. Package libapache2-mod-php4 is not installed. dpkg: error processing php4 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: fetchmail libapache-mod-php4 php4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Can't upgrade from woody to sarge (sources.list problem?)
I have Debian installed on my xbox. It's Xebian 1.01, or something like that. As nearly as I can tell, it's exactly the same as woody except that the kernel is a 2.4 kernel with xbox patches, and a backported version of XFree86 4.3.0, and some customized configuration files. xbox:/# cat /etc/debian_version 3.0 xbox:/# gcc -v Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20011002 (Debian prerelease) Anyway, my point being that I'm pretty sure it's almost pure woody and looks a lot more like a customized Debian than a derived distribution. So, my sources list looks like this: deb-src http://ftp.us.debian.org/debian/ sarge main non-free contrib deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US sarge//non-US main contrib non-free deb http://security.debian.org/ sarge/updates main contrib non-free deb ftp://ftp.nerim.net/debian-marillat/ sarge main deb-src http://perso.wanadoo.fr/debian/ unstable main Then I type: xbox:/# apt-get update [snip] Hit http://ftp.us.debian.org sarge/main Release [snip] xbox:/# echo $? 0 (In other words, everything appears successful.) xbox:/# apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages have been kept back lame liblame0 libpostproc0 mplayer-586 2 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 1145kB of archives. After unpacking 4096B will be freed. Do you want to continue? [Y/n] I expected that a lot more packages would need upgrading (like, say, gcc). How can I upgrade? I don't want to mess with the kernel package, so I guess I should pin it or something. There might be some configuration file holding everything in place. -- Adam Fabian [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't upgrade from woody to sarge (sources.list problem?)
Adam Fabian wrote: I have Debian installed on my xbox. It's Xebian 1.01, or something like that. As nearly as I can tell, it's exactly the same as woody except that the kernel is a 2.4 kernel with xbox patches, and a backported version of XFree86 4.3.0, and some customized configuration files. Anyway, my point being that I'm pretty sure it's almost pure woody and looks a lot more like a customized Debian than a derived distribution. So, my sources list looks like this: deb-src http://ftp.us.debian.org/debian/ sarge main non-free contrib Lines with deb-src point to the source code for the packages, not to the packages. You need them only if you want to build your own packages. If you just want to install the packages from the debian mirror you have to use deb instead of deb-src. -- Thomas Weinbrenner pgp47FS7ml94C.pgp Description: PGP signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Florian Ernst wrote: MicheleM wrote: all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. [...] But what did it happen? I think there is a bug somewhere. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? I upgraded a machine running lilo and debconf mailed me the following information: Subject: Debconf: Configuring lilo -- Deprecated parameters in LILO configuration Deprecated files have been found on your system. You must update the 'install=' parameter in your LILO configuration file (/etc/lilo.conf) in order to properly upgrade the package. The new 'install=' options are: new: install=bmp old: install=/boot/boot-bmp.b new: install=text old: install=/boot/boot-text.b new: install=menu old: install=/boot/boot-menu.b or boot.b -- Debconf, running at discord.proulx.com [ Debconf was not configured to display this note, so it mailed it to you. ] Reading that message I took care of the problem (by installing grub) before rebooting the system. But I can't help but wonder if something similar occurred with the original poster? It was mailed to me because I had set my debconf to 'critical' only and so it was prevented from showing me a dialog box. Although for something like this it would justify a critical rating. Bob signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello again, On Thu, Jun 09, 2005 at 02:54:32PM -0700, MicheleM wrote: this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo [...] no more. Hm, strange, to me it looks like this question was never asked. I guess it's best to ask the lilo maintainers [EMAIL PROTECTED] about this, or you could send a bugreport against upgrade-reports... I personally don't use lilo myself, so I wouldn't dare venture any deeper into this problem. Cheers, Flo signature.asc Description: Digital signature
Release upgrade from Woody to Sarge failed reboot lilo problem
Hi there, yesterday I tried to upgrade my Woody production server to Sarge after reading and following step by step the relase notes under: http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. I post my ls -l /boot: total 4513 -rw-r--r-- 1 root root 512 2005-01-25 00:50 boot.0800 lrwxrwxrwx 1 root root 11 2005-01-25 00:48 boot.b - boot-menu.b -rw-r--r-- 1 root root 308326 2005-06-09 01:00 coffee.bmp -rw-r--r-- 1 root root3342 2005-01-25 00:45 config-2.4.28-bf2.4 -rw-r--r-- 1 root root 26684 2005-02-08 20:06 config-2.4.29 lrwxrwxrwx 1 root root 15 2005-06-09 01:00 debian.bmp - /boot/sarge.bmp -rw-r--r-- 1 root root 153720 2005-06-09 01:00 debianlilo.bmp -rw--- 1 root root 46080 2005-06-09 14:19 map -rw-r--r-- 1 root root 23662 2005-06-09 01:00 sarge.bmp -rw-r--r-- 1 root root 24116 2005-06-09 01:00 sid.bmp -rw-r--r-- 1 root root 568549 2005-01-25 00:45 System.map-2.4.28-bf2.4 -rw-r--r-- 1 root root 668419 2005-02-08 20:11 System.map-2.4.29 -rw-r--r-- 1 root root 1298076 2005-01-25 00:45 vmlinuz-2.4.28-bf2.4 -rw-r--r-- 1 root root 1477532 2005-02-08 20:11 vmlinuz-2.4.29 and the /etc/lilo.conf # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---+ # |!! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde #bios=0x81 #disk=/dev/sda #bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/sda # Specifies the device that should be mounted as root. (`/') # root=/dev/sda4 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 08:23:39AM -0700, MicheleM wrote: yesterday I tried to upgrade my Woody production server to Sarge after reading and following step by step the relase notes under: http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
On Thu, Jun 09, 2005 at 08:08:08PM +0200, Florian Ernst wrote: Hello *, all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Why do people insist on using LILO? Just install grub, set it up once with symlinks and *never* mess with it again. In case anyone cares, here is my configuration: default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux (recovery mode) root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD (recovery mode) root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot I installed it *one* time to the MBR. I have only since had to mess with it to replace the failed harddrive in the machine. If you have /boot on a separate partition, as I do, you will want to add 'do_symlinks = No' to /etc/kernel-img.conf. Trust me on this. It is really nice to have a boot loader that can actually read your filesystem. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpOSyrM8YMun.pgp Description: PGP signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 04:46:32PM -0400, Roberto C. Sanchez wrote: Why do people insist on using LILO? Just install grub, [...] Advocacy is one thing, trying to find out why a bug has occurred another. Let's try not to mix things up. Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hi Flo, this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo Name: lilo/upgrade Template: lilo/upgrade Owners: lilo I grep the upgrade's typescript searching for the lilo prompt but this is what I found: anjuna:~# cat /backup/typescript |grep lilo libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr Get:493 http://debian.fastweb.it sarge/main lilo 1:22.6.1-6.2 [343kB] Get:494 http://debian.fastweb.it sarge/main mbr 1.1.5-2 [20.4kB] Preparing to replace lilo 1:22.2-3 (using .../lilo_1%3a22.6.1-6.2_i386.deb) ... Unpacking replacement lilo ... Setting up lilo (22.6.1-6.2) ... no more. thanks Flo Mik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: On your upgrade from woody to sarge
On Sun, 12 Dec 2004 23:27:46 -0600 (CST), Gayle Lee Fairless [EMAIL PROTECTED] wrote: [...] I was wondering if the apt-get dist-upgrade would also upgrade the kernel, too. Sourceforge makes it sound easy. Only if there are updated Debian revision of your kernel version. Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: On your upgrade from woody to sarge
On Sun, Dec 12, 2004 at 11:27:46PM -0600, Gayle Lee Fairless wrote: I was wondering if the apt-get dist-upgrade would also upgrade the kernel, too. Sourceforge makes it sound easy. In Debian, kernel upgrades are special. They only happen if you specifically request them. This is intentional. It is the considered opinion of the Debian leadership that it should not be automatic. But it is really easy. Once you have done a dist-upgrade to get to Sarge, you can, in a speparate step, download and install a new kernel. But, you need to read the directions. A new kernel does require restarting your computer. It does require making sure that lilo or grub is properly changed to startup using the new kernel. And it is important to have them set up to allow you to boot back into your old kernel. All this is covered in the instructions. Read them first. Then it is easy. And _don't_ read instructions for another distribution and think they apply to Debian. -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: On your upgrade from woody to sarge
On Sun, 12 Dec 2004 23:27:46 -0600 (CST), Gayle Lee Fairless [EMAIL PROTECTED] wrote: [...] I was wondering if the apt-get dist-upgrade would also upgrade the kernel, too. Sourceforge makes it sound easy. Only if there are updated Debian revision of your kernel version. Andrea Does that mean that a change from a 2.4 kernel to a 2.6 kernel has to be a separate operation? (In which case, I guess I had better really study that Sourceforge document very seriously!) -- (Mr.) Gayle Lee Fairless -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: On your upgrade from woody to sarge
On Mon, 13 Dec 2004 11:16:28 -0600 (CST), Gayle Lee Fairless [EMAIL PROTECTED] wrote: On Sun, 12 Dec 2004 23:27:46 -0600 (CST), Gayle Lee Fairless [EMAIL PROTECTED] wrote: [...] I was wondering if the apt-get dist-upgrade would also upgrade the kernel, too. Sourceforge makes it sound easy. Only if there are updated Debian revision of your kernel version. Andrea Does that mean that a change from a 2.4 kernel to a 2.6 kernel has to be a separate operation? (In which case, I guess I had better really study that Sourceforge document very seriously!) It's easy but not automatic, and you can keep them both installed, or better, with Debian you can have how many kernels installed as you want... Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: On your upgrade from woody to sarge
On Sun, 12 Dec 2004, Leonard Chatagnier wrote: Not sure what you mean. I put testing in the sources.list which I thought would get the Sarge. Running upgrade several times never got away from 2.4.18-bf2.4 Woody. Now trying using pkg-upgrade as apt conditioner but my /var directory isn't large enough to contain the download. Attempting to use a symlnk to a partition with enough free space but its not working either. Leonard Chatagnier - Original Message - From: Gayle Lee Fairless [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, December 12, 2004 5:57 PM Subject: On your upgrade from woody to sarge Did you change your kernel version? I'm asking because I'll probably upgrade from woody to sarge when sarge finally goes stable. I guess that upgrading the kernel to a 2.6 might also be an improvement. Right now I tend to use KDE with gdm. I hope that the resolution can be more easily managed, too. And I hope to use my usb HP psc1210 better as well as the HP 697C on my parallel port. -- (Mr.) Gayle Lee Fairless Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown PS. I am subscribed to the digest but not the list. I was wondering if the apt-get dist-upgrade would also upgrade the kernel, too. Sourceforge makes it sound easy. -- Gayle Lee Fairless -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On your upgrade from woody to sarge
Did you change your kernel version? I'm asking because I'll probably upgrade from woody to sarge when sarge finally goes stable. I guess that upgrading the kernel to a 2.6 might also be an improvement. Right now I tend to use KDE with gdm. I hope that the resolution can be more easily managed, too. And I hope to use my usb HP psc1210 better as well as the HP 697C on my parallel port. -- (Mr.) Gayle Lee Fairless Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown PS. I am subscribed to the digest but not the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dodgy sudo upgrade on woody ppc - echos processing
Hi I don't think this is a ppc specific problem and so I'm posting here. In response to the sudo security alert I've upgraded 1 sid workstation and 3 woody servers (2 i386 and 1 ppc). All are fine except for the woody ppc upgrade. During aptitude upgrade dpkg couldn't write to its file because /var was at 100% no room left. The package installed but something was awry. When running sudo I get the following before commands are executed: Looking at PWD=/var/mail... Looking at [EMAIL PROTECTED]:\w\$ ... Looking at USER=clive... Looking at MAIL=/var/mail/clive... Looking at LANG=C... Looking at SSH_CLIENT=192.168.1.11 37884 22... Looking at LOGNAME=clive... Looking at SHLVL=1... Looking at SHELL=/bin/bash... Looking at HOME=/home/clive... Looking at TERM=xterm... Looking at PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games... Looking at SSH_TTY=/dev/pts/0... Looking at _=/usr/bin/sudo... Looking at OLDPWD=/home/clive... Other than this sudo works fine AFAICT. I tried removing sudo and purging the configuration files (dpkg -P sudo) and then reinstalling (having cleaned /var to make room) but the problem remains. I tried to find a configuration file for sudo but only came up with: /etc/init.d/sudo /etc/pam.d/sudo neither of which seem a likely source of remedy. Nothing is showing up in BUGS and I'm puzzled as to where to go from here ;) Thanks Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dodgy sudo upgrade on woody ppc - echos processing
On Wed, 24 Nov 2004, Clive Menzies wrote: I don't think this is a ppc specific problem and so I'm posting here. In response to the sudo security alert I've upgraded 1 sid workstation and 3 woody servers (2 i386 and 1 ppc). All are fine except for the woody ppc upgrade. During aptitude upgrade dpkg couldn't write to its file because /var was at 100% no room left. The package installed but something was awry. When running sudo I get the following before commands are executed: [snip debugging info rest of message] Same results here on woody i386. As I write this, it's been reported as bugs #282777, #282778, and #282786. - Aaron -- Aaron Hall : If UNIX is the heroin of operating systems, [EMAIL PROTECTED] : then...Windows is filling your sinuses with : lucite and letting it set. : -- The Usenet Oracle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Want to upgrade from Woody to Sarge. [Source.list]
I want to upgrade from woody to sarge. Can someone post the appropriate source.list. Thank you. Then aren't you supposed to run apt-get dist-upgrade or something? Moving to sarge is to new to me. I feel lost. Any help will be appreciated. Thanks
Re: Want to upgrade from Woody to Sarge. [Source.list]
Hi On Sat, Nov 20, 2004 at 08:56:13AM +, [EMAIL PROTECTED] wrote: I want to upgrade from woody to sarge. Can someone post the appropriate source.list. Thank you. You can change all entries from woody to sarge in your /etc/apt/sources.list Then aren't you supposed to run apt-get dist-upgrade or something? Moving to sarge is to new to me. I feel lost. Any help will be appreciated. Thanks Then, when changing the sources.list, run apt-get update and then finally: apt-get dist-upgrade. Maybe the APT-Howto on www.debian.org/doc could also be interessting for you: http://www.debian.org/doc/manuals/apt-howto/ http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html Greetings Salvatore -- Linux arda 2.6.9-1-686 #1 Tue Nov 16 17:52:21 JST 2004 i686 GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please help: upgrade from woody to sarge; postfix broken
I hope someone can help me.. Im desperate.. Recently I changed my /etc/apt/sources.list to upgrade from woody to sarge. All in all it went reasonably well. This is my current sources.list: SOURCES.LIST - deb ftp://ftp.debian.nl/debian/ sarge main non-free contrib deb-src ftp://ftp.debian.nl/debian/ sarge main non-free contrib deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free #php5 etc.. deb http://packages.dotdeb.org ./ - Before the upgrade I used the backports.org version of postfix. It was the same version as in sarge. I didn't change any config files and this is what postfix puts in mail.log after I start it: ERROR - Nov 17 22:36:55 server01 postfix/master[15177]: fatal: getaddrinfo: Servname not supported for ai_socktype - Probably some problem with libresolv? Anyway.. I simply upgraded and libresolv is now nicely at version 2.3.2 (/lib/libresolv*). Also master nicely is linked to it: - server01:/usr/lib/postfix# ldd /usr/lib/postfix/master libpostfix-global.so.1 = /usr/lib/libpostfix-global.so.1 (0x4002) libpostfix-util.so.1 = /usr/lib/libpostfix-util.so.1 (0x40043000) libdb-4.2.so = /usr/lib/libdb-4.2.so (0x40068000) libnsl.so.1 = /lib/tls/libnsl.so.1 (0x4013e000) libresolv.so.2 = /lib/tls/libresolv.so.2 (0x40153000) libgdbm_compat.so.3 = /usr/lib/libgdbm_compat.so.3 (0x40165000) libc.so.6 = /lib/tls/libc.so.6 (0x40168000) libdl.so.2 = /lib/tls/libdl.so.2 (0x402a3000) libgdbm.so.3 = /usr/lib/libgdbm.so.3 (0x402a7000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) - This is my postconf -n output: - server01:/usr/lib/postfix# postconf -n alias_database = hash:/etc/aliases alias_maps = pgsql:/etc/postfix/pgsql-aliases.cf append_dot_mydomain = yes biff = no broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix content_filter = smtp:127.0.0.1:10024 daemon_directory = /usr/lib/postfix default_destination_recipient_limit = 100 delay_warning_time = 4 disable_vrfy_command = yes header_checks = pcre:/etc/postfix/headercheck home_mailbox = Maildir/ in_flow_delay = 5s local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname mailbox_command = procmail -a $EXTENSION mailbox_size_limit = 0 message_size_limit = 2048 mydestination = $myhostname, $transport_maps, localhost.infogateway.org, localhost mydomain = infogateway.org myhostname = server01.infogateway.org mynetworks = 127.0.0.0/8, 192.168.0.0/16, 212.45.53.2/32, 212.142.6.228/32, 213.233.209.62/32, 217.128.103.29/32, 213.92.131.53/32,62.73.241.146/32,64.23.55.49/32 myorigin = $mydomain notify_classes = resource,software,2bounce recipient_delimiter = + relocated_maps = pgsql:/etc/postfix/pgsql-relocated.cf setgid_group = postdrop smtp_use_tls = yes smtpd_banner = $myhostname ESMTP (Debian/GNU). We intend to block/report all spam! smtpd_client_restrictions = smtpd_data_restrictions = smtpd_helo_required = yes smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_unauth_destination, check_recipient_access pcre:/etc/postfix/recipient_checks.pcre, check_sender_access pcre:/etc/postfix/sender_checks.pcre, check_client_access pcre:/etc/postfix/client_checks.pcre, reject_rbl_client relays.ordb.org, reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client xbl.spamhaus.org, reject_rbl_client bl.spamcop.net, reject_rbl_client cbl.abuseat.org, reject_rbl_client dnsbl.njabl.org, permit smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sender_restrictions = smtpd_tls_CAfile = /etc/postfix/cacert-comodo.pem smtpd_tls_CApath = /etc/postfix/certs/ smtpd_tls_ask_ccert = no smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/postfix/smtp_infogateway_org.crt smtpd_tls_key_file = /etc/postfix/smtp_infogateway_org.key smtpd_tls_loglevel = 0 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = sdbm:/etc/postfix/smtpd_scache smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes strict_rfc821_envelopes = yes tls_random_source = dev:/dev/urandom transport_maps = pgsql:/etc/postfix/pgsql-transport.cf unknown_address_reject_code = 554 unknown_client_reject_code = 550 unknown_hostname_reject_code = 554 virtual_gid_maps = pgsql:/etc/postfix/pgsql-virtual-gid.cf virtual_mailbox_base = /rdfs/postfix-vmail virtual_mailbox_maps = pgsql:/etc/postfix/pgsql-virtual-maps.cf virtual_uid_maps = pgsql:/etc/postfix/pgsql-virtual-uid.cf - And again: I hope someone can help me.. Im desperate.. Jacco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe
please help: upgrade from woody to sarge; postfix broken
I hope someone can help me.. Im desperate.. Recently I changed my /etc/apt/sources.list to upgrade from woody to sarge. All in all it went reasonably well. This is my current sources.list: SOURCES.LIST - deb ftp://ftp.debian.nl/debian/ sarge main non-free contrib deb-src ftp://ftp.debian.nl/debian/ sarge main non-free contrib deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free #php5 etc.. deb http://packages.dotdeb.org ./ - Before the upgrade I used the backports.org version of postfix. It was the same version as in sarge. I didn't change any config files and this is what postfix puts in mail.log after I start it: ERROR - Nov 17 22:36:55 server01 postfix/master[15177]: fatal: getaddrinfo: Servname not supported for ai_socktype - Probably some problem with libresolv? Anyway.. I simply upgraded and libresolv is now nicely at version 2.3.2 (/lib/libresolv*). Also master nicely is linked to it: - server01:/usr/lib/postfix# ldd /usr/lib/postfix/master libpostfix-global.so.1 = /usr/lib/libpostfix-global.so.1 (0x4002) libpostfix-util.so.1 = /usr/lib/libpostfix-util.so.1 (0x40043000) libdb-4.2.so = /usr/lib/libdb-4.2.so (0x40068000) libnsl.so.1 = /lib/tls/libnsl.so.1 (0x4013e000) libresolv.so.2 = /lib/tls/libresolv.so.2 (0x40153000) libgdbm_compat.so.3 = /usr/lib/libgdbm_compat.so.3 (0x40165000) libc.so.6 = /lib/tls/libc.so.6 (0x40168000) libdl.so.2 = /lib/tls/libdl.so.2 (0x402a3000) libgdbm.so.3 = /usr/lib/libgdbm.so.3 (0x402a7000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) - This is my postconf -n output: - server01:/usr/lib/postfix# postconf -n alias_database = hash:/etc/aliases alias_maps = pgsql:/etc/postfix/pgsql-aliases.cf append_dot_mydomain = yes biff = no broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix content_filter = smtp:127.0.0.1:10024 daemon_directory = /usr/lib/postfix default_destination_recipient_limit = 100 delay_warning_time = 4 disable_vrfy_command = yes header_checks = pcre:/etc/postfix/headercheck home_mailbox = Maildir/ in_flow_delay = 5s local_recipient_maps = $alias_maps $virtual_mailbox_maps unix:passwd.byname mailbox_command = procmail -a $EXTENSION mailbox_size_limit = 0 message_size_limit = 2048 mydestination = $myhostname, $transport_maps, localhost.infogateway.org, localhost mydomain = infogateway.org myhostname = server01.infogateway.org mynetworks = 127.0.0.0/8, 192.168.0.0/16, 212.45.53.2/32, 212.142.6.228/32, 213.233.209.62/32, 217.128.103.29/32, 213.92.131.53/32,62.73.241.146/32,64.23.55.49/32 myorigin = $mydomain notify_classes = resource,software,2bounce recipient_delimiter = + relocated_maps = pgsql:/etc/postfix/pgsql-relocated.cf setgid_group = postdrop smtp_use_tls = yes smtpd_banner = $myhostname ESMTP (Debian/GNU). We intend to block/report all spam! smtpd_client_restrictions = smtpd_data_restrictions = smtpd_helo_required = yes smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_unauth_destination, check_recipient_access pcre:/etc/postfix/recipient_checks.pcre, check_sender_access pcre:/etc/postfix/sender_checks.pcre, check_client_access pcre:/etc/postfix/client_checks.pcre, reject_rbl_client relays.ordb.org, reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client xbl.spamhaus.org, reject_rbl_client bl.spamcop.net, reject_rbl_client cbl.abuseat.org, reject_rbl_client dnsbl.njabl.org, permit smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sender_restrictions = smtpd_tls_CAfile = /etc/postfix/cacert-comodo.pem smtpd_tls_CApath = /etc/postfix/certs/ smtpd_tls_ask_ccert = no smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/postfix/smtp_infogateway_org.crt smtpd_tls_key_file = /etc/postfix/smtp_infogateway_org.key smtpd_tls_loglevel = 0 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = sdbm:/etc/postfix/smtpd_scache smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes strict_rfc821_envelopes = yes tls_random_source = dev:/dev/urandom transport_maps = pgsql:/etc/postfix/pgsql-transport.cf unknown_address_reject_code = 554 unknown_client_reject_code = 550 unknown_hostname_reject_code = 554 virtual_gid_maps = pgsql:/etc/postfix/pgsql-virtual-gid.cf virtual_mailbox_base = /rdfs/postfix-vmail virtual_mailbox_maps = pgsql:/etc/postfix/pgsql-virtual-maps.cf virtual_uid_maps = pgsql:/etc/postfix/pgsql-virtual-uid.cf - And again: I hope someone can help me.. Im desperate.. Jacco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe
Re: please help: upgrade from woody to sarge; postfix broken
On Wed, 17 Nov 2004, Jacco Hoeve wrote: ERROR - Nov 17 22:36:55 server01 postfix/master[15177]: fatal: getaddrinfo: Servname not supported for ai_socktype Translation: You're missing something in /etc/services. In other words, you're telling postfix to connect to something like 192.0.2.1:blah, and blah is not in /etc/services. It could be in a transport map, or anywhere. Are you using lmtp as a service name (i.e. like in 192.0.2.1:lmtp) somewhere, per chance? lmtp has no defined port, so it was dully removed from /etc/services. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: please help: upgrade from woody to sarge; postfix broken
On Wed, 17 Nov 2004, Jacco Hoeve wrote: ERROR - Nov 17 22:36:55 server01 postfix/master[15177]: fatal: getaddrinfo: Servname not supported for ai_socktype Translation: You're missing something in /etc/services. In other words, you're telling postfix to connect to something like 192.0.2.1:blah, and blah is not in /etc/services. It could be in a transport map, or anywhere. Are you using lmtp as a service name (i.e. like in 192.0.2.1:lmtp) somewhere, per chance? lmtp has no defined port, so it was dully removed from /etc/services. Thanks!! That worked.. I was missing 2 services (smtp-backdoor and vexira). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please help: upgrade from woody to sarge; postfix broken
On Wed, 17 Nov 2004, Henrique de Moraes Holschuh wrote: On Wed, 17 Nov 2004, Jacco Hoeve wrote: ERROR - Nov 17 22:36:55 server01 postfix/master[15177]: fatal: getaddrinfo: Servname not supported for ai_socktype Translation: You're missing something in /etc/services. Reported as #281815. This is one of those error messages that are way, way too obscure. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upgrade von woody zu sarge und Internal error couldn t config a pre-depend
Hallo Liste, habe wie mir empfohlen wurde ein upgrade von woody 3.0 auf sarge auf meinem Laptop gestartet. UNd zwar nach dem einlesen von 14 CD images (hat auch nach plan geklappt; sources.list kontrolliert, alles ok ) dann: apt-get update apt-get dist-upgrade lilo -v ES kommt die Meldung über die zu installierenden Pakete, jene zu entferneden usw. Dann einlegen der 1. CD und folgende Meldung: E: INternal error, could not perform immediate configuration (2) on libac1l. und ABBRUCH ok dann hab ich mit: apt-get install libacl1 das Paket einzeln installiert und es wurden einige zusätzliche pakete u.a. libc6 neu installiert bzw. konfiguriert. (jedenfalls schien mir so) dann wieder apt-get dist-upgrade lilo -v. folgende Meldung: Internal error couldn t config a pre-depend. ABBRUCH NIx weiteres , kein Hinweis welche pre-depend ! Hat jemand hier im Forum ne Ahnung davon ? Gruss und Danke JJ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: upgrade von woody zu sarge und Internal error couldn t config a pre-depend
On 24.Oct 2004 - 19:06:23, Ulrich Pedri wrote: Hallo Liste, habe wie mir empfohlen wurde ein upgrade von woody 3.0 auf sarge auf meinem Laptop gestartet. UNd zwar nach dem einlesen von 14 CD images (hat auch nach plan geklappt; sources.list kontrolliert, alles ok ) dann: apt-get update apt-get dist-upgrade lilo -v Auf etlichen Seiten bzgl. Debian DistributionsUpgrade ist angemerkt man solle zuerst! die Pakettools (also dpkg und apt) updaten und erst danach das dist-upgrade durchfuehren. Bei meinem Minimalsystem klappts auch ohne, aber grade wenn man ein voll installiertes System hat, duerfte diese Vorgehensweise besser sein. Ich kann dir allerdings nicht sagen ob das in deinem speziellen Fall das Problem loest... Wenn nicht muesstest du zumindestens rauskriegen bei welchem Paket er abbricht. Andreas -- It is impossible for an optimist to be pleasantly surprised. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Segfault after dist-upgrade on woody
On Mon, Sep 27, 2004 at 11:58:12AM +0200, Stefan Goessling-Reisemann wrote: Hello List! I have not gotten any response to my problem (see below), so I take the liberty to ask my questions once more. I hope you do not feel offended. Best regards, STefan -- Forwarded message -- Date: Wed, 22 Sep 2004 11:09:04 +0200 From: Stefan Gößling-Reisemann [EMAIL PROTECTED] Dear List, at the beginning of September I did an apt-get update and apt-get upgrade on a Woody installation. The upgraded packages were (IIRC) libpng2/3 and rsync. Exactly on that day tripwire stopped working, i.e. it delivers a segmentation fault. The rest of the system seemed to work fine at first, until I discovered recently that also dpkg creates a segfault. The system was setup by two CS students at our university, so I don't know all the details of the installation. I know that they have compiled their own kernel (2.4.19). They claim to have added two extra drivers (as modules) (via-rhine.c:v1.10-LK1.1.14 and sundance.c:v1.01b 17-Jan-2002). But aren't these part of the 2.4.19 source?? Hi, are you aware that many of these packages are awailable IN debian or at most available as backports. The whole point of using debian is the quality assurance. And most packages(samba,kernel and maybe the rhine module) have adequet default configurations. This would make upgrades easiser and assure that you can track further problems. Also, check the debian-user archives and the bug track system (bugs.debian.org/PKGNAME) for hints. Also, give a trace of the command like with 'script' or 'CMD logfile'. -Kev The tripwire package is also compiled from sources (version 2.3.1.2), as is the samba suite (version 2.2.9). All the rest is standard Woody, as far as I know. I have done an strace of a call to tripwire and dpkg, they end with the following lines: strace of tripwire == read(3, # /etc/nsswitch.conf\n#\n# Example..., 4096) = 465 read(3, , 4096) = 0 close(3)= 0 munmap(0x40076000, 4096)= 0 --- SIGSEGV (Segmentation fault) --- write(2, Software interrupt forced exit: ..., 51) = 51 munmap(0x40077000, 4096)= 0 _exit(8)= ? strace of dpkg == mremap(0x4018f000, 1007616, 1011712, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1011712, 1015808, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1015808, 1019904, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1019904, 1024000, MREMAP_MAYMOVE) = 0x402b2000 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ I have run memcheck for around 3 hours (6 passes) with no errors. I have also done an fsck on all partitions (except swap). Any ideas where to look? How would I further analyse the problem? Best regards and thanks to everyone willing to help, Stefan (debian @ goessling . de) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- (__) (oo) /--\/ / ||| * /\---/\ ~~ ~~ Have you mooed today?... signature.asc Description: Digital signature
Segfault aufter dist-upgrade on woody
Dear List, at the beginning of September I did an apt-get update and apt-get upgrade on a Woody installation. The upgraded packages were (IIRC) libpng2/3 and rsync. Exactly on that day tripwire stopped working, i.e. it delivers a segmentation fault. The rest of the system seemed to work fine at first, until I discovered recently that also dpkg creates a segfault. The system was setup by two CS students at our university, so I don't know all the details of the installation. I know that they have compiled their own kernel (2.4.19). They claim to have added two extra drivers (as modules) (via-rhine.c:v1.10-LK1.1.14 and sundance.c:v1.01b 17-Jan-2002). But aren't these part of the 2.4.19 source?? The tripwire package is also compiled from sources (version 2.3.1.2), as is the samba suite (version 2.2.9). All the rest is standard Woody, as far as I know. I have done an strace of a call to tripwire and dpkg, they end with the following lines: strace of tripwire == read(3, # /etc/nsswitch.conf\n#\n# Example..., 4096) = 465 read(3, , 4096) = 0 close(3)= 0 munmap(0x40076000, 4096)= 0 --- SIGSEGV (Segmentation fault) --- write(2, Software interrupt forced exit: ..., 51) = 51 munmap(0x40077000, 4096)= 0 _exit(8)= ? strace of dpkg == mremap(0x4018f000, 1007616, 1011712, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1011712, 1015808, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1015808, 1019904, MREMAP_MAYMOVE) = 0x4018f000 mremap(0x4018f000, 1019904, 1024000, MREMAP_MAYMOVE) = 0x402b2000 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ I have run memcheck for around 3 hours (6 passes) with no errors. I have also done an fsck on all partitions (except swap). Any ideas where to look? How would I further analyse the problem? Best regards and thanks to everyone willing to help, Stefan (debian @ goessling . de) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrade slapd woody / testing
Bonjour Je voudrais faire une upgrade en testing d'un serveur en prod, mais je me pose une petite question: Lors de la mise à jour, slapd va passer de la version 2.0.23-6.3 (stable) à la version 2.1.23-1 (testing), or entre ces deux versions (et 2.0.X / 2.1.X) il y a eds différences au niveau de la gestion des fichiers de schema (notemment core.schema).. Il va donc falloir les retravailler. Comment faire ce changement le plus efficacement? Quelqun a-t-il déjà effectué une upgrade de slapd 2.0.x à 2.1.x en apt-get? Y a-t-il un outil pour modifier automatiquement mes fichiers schema? (à coup de slapcat/LDIF ?) Merci beaucoup! Bonne journée Cordialement Ruben -- Ruben - [gnupg key Ox8E91859]
Re: After upgrade from woody stable to unstable xserver starts at boot again
Btw please start a new thread instead of making an off-topic reply to a thread about alsa. On Fri, 30 Apr 2004, Jens Simmoleit wrote: Hi, well heck, I can't explain why there's a X-server starting on my machine at boot up. I removed the init.d Entries in webmin. After the update the xserver came up again, and now I don't know how to stop this godd*mn thing. Which entry do I need to modify to prevent that the xserver is started. Take a look what webmin says (pretty funny story!): Action Start at boot? Description xdm No /etc/init.d/xdm: start or stop the X display manager xfree86-common No /etc/init.d/xfree86-common: set up the X server socket directory 10-4-2003: Now sets up .ICE-unix ICE IPC directory. -DS xfs No /etc/init.d/xfs: start or stop the X font server I think that's quite interesting as I've choosen to use kdm, which isn't running at all, not even mentioned :-/ It seems to me that you have xdm installed. Do you? If so just remove it if you don't need it. # dpkg --purge xdm -- Jaldhar H. Vyas [EMAIL PROTECTED] La Salle Debain - http://www.braincells.com/debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ssh problem after upgrade from woody to sarge
I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Any help appreciated. Thanks Pete = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Did you find your problem in the BTS? The new ssh uses PAM, and there seems to be some problem with the config file updates from different versions. You should look at your /etc/ssh/sshd_config and verify the following settings: PasswordAuthentication no ChallengeResponseAuthentication yes UsePAM yes Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/| | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | signature.asc Description: Digital signature
Re: ssh problem after upgrade from woody to sarge
I've tried that and now i can't login at all i get access denied. PasswordAuthentication no (was yes) ChallengeResponseAuthentication yes (was no) UsePAM yes (was yes) Could'nt find it on BTS, i'll check again. Thanks Pete --- Stephan Seitz [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). Is there anything wrong with the new version of the ssh server or is there anything more i need to do to get ssh to work ? Did you find your problem in the BTS? The new ssh uses PAM, and there seems to be some problem with the config file updates from different versions. You should look at your /etc/ssh/sshd_config and verify the following settings: PasswordAuthentication no ChallengeResponseAuthentication yes UsePAM yes Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/ | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | ATTACHMENT part 2 application/pgp-signature name=signature.asc = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. What errors? It's impossible to help without seeing those. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Sorry. What happens is that i get the usual window when an application crashes saying putty.exe generated errors and is being closed by windows, you need to restart the program (it's something like this i had to translate since my windows is not english. Also if i open an ssh connection to a woody server everything works ok, only to these two servers upgraded to sarge generate this error in putty. Windows doesn't log anything in the event log. The only thing i get is a 15.5Mb user.dmp. --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote: I've upgraded two Debian Woody boxes to testing (sarge). I use putty from a windows 2000 PC to login to these linux boxes, but after the upgrade i can't login anymore. What happens is that after typing the username and password putty generates errors. What errors? It's impossible to help without seeing those. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Thanks for your help Pete --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 04:43:48AM -0700, Pete RedHair wrote: What happens is that i get the usual window when an application crashes saying putty.exe generated errors and is being closed by windows, you need to restart the program (it's something like this i had to translate since my windows is not english. Best report that to the PuTTY team, then. Whether or not a current OpenSSH server triggers it, it's still a bug in PuTTY and should be fixed there. Are you using a recent version? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 06:11:07AM -0700, Pete RedHair wrote: Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Aha, right. http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html indeed lists some crash bugs fixed after 0.51. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
Yep, it's writen there, thanks for your help. It is now working without any problems. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be default in sarge ? Thanks again Colin, and Stephan Pete --- Colin Watson [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 06:11:07AM -0700, Pete RedHair wrote: Thanks for your reply . I was forgetting putty since it worked fine with woody, however i did upgraded putty and now it works ok, even after the changes i made in sshd_config which didn't let me login. Guess i missed the problem tracking when i assumed everything was ok with my old version of putty (0.5.1), sorry. Aha, right. http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html indeed lists some crash bugs fixed after 0.51. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh problem after upgrade from woody to sarge
On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete RedHair wrote: It is now working without any problems. Fine. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be You'll need them, if you don't have your passwords in /etc/shadow but in LDAP or Samba. At least, I needed them. default in sarge ? ChallengeResponseAuthentication is yes in new versions. I seemed to have an really old config file. The other options are, too, yes in new installations. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/| | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | signature.asc Description: Digital signature
Re: ssh problem after upgrade from woody to sarge
I'm using shadow so i guess i need the other config. Anyway it's working. Thanks Pete --- Stephan Seitz [EMAIL PROTECTED] wrote: On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete RedHair wrote: It is now working without any problems. Fine. Stephan reported about some changes needed to do in the sshd_config, should i keep them, are they to be You'll need them, if you don't have your passwords in /etc/shadow but in LDAP or Samba. At least, I needed them. default in sarge ? ChallengeResponseAuthentication is yes in new versions. I seemed to have an really old config file. The other options are, too, yes in new installations. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.rootsland.net/~stse/ | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | ATTACHMENT part 2 application/pgp-signature name=signature.asc = --- Thanks Pete __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anyone used Backports.org to upgrade a woody to 2.6?
On Wed, Apr 14, 2004 at 02:36:13PM -0700, Bill Moseley wrote: I see that there's both module-init-tools and a kernel-image-2.6.5 (kernel-image-2.6.5-1-k7_2.6.5-0.backports.org.1_i386.deb) available. There's another modules deb in the folder - make sure you have it if you need to drop back to 2.4 Anyone have success using those packages to update a Woody box? One is an Athlon XP 1800+, which I assume is should use the k7 kernel. I also have a P4 and a PIII. Yes. I roll my own kernel from vanilla. Athlon 1200. Any notes? Did you add backports to source.list or download the .deb and use dpkg -i for the modules and kernel? dpkg -i I normally build the kernels, but would really like to start using kernel-image packages to make upgrading easier. Try make-kpkg. Some problems I encountered: I use devfs and devpts wasn't mounted(fun with ssh). Modules names changed. Lots of them. Programs in procps no longer work. I'm considering dropping back to 2.4 until I can go to Sarge. Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Anyone used Backports.org to upgrade a woody to 2.6?
I see that there's both module-init-tools and a kernel-image-2.6.5 (kernel-image-2.6.5-1-k7_2.6.5-0.backports.org.1_i386.deb) available. Anyone have success using those packages to update a Woody box? One is an Athlon XP 1800+, which I assume is should use the k7 kernel. I also have a P4 and a PIII. Any notes? Did you add backports to source.list or download the .deb and use dpkg -i for the modules and kernel? I have xfs file systems so I guess I'd need to use initrd since XFS is included as a module -- is there any additional setup required? I normally build the kernels, but would really like to start using kernel-image packages to make upgrading easier. -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Latest kernel security upgrade in woody is BROKEN! DO NOT INSTALL!
Dear all, It seems that at least on ix86, the latest woody security updates for the kernel packages are completely broken. The kernel packages named kernel-image-2.4.18-1-subflavor with version 2.4.18-13 contain only one module. DO NOT upgrade to these packages or your system will be broken when you reboot. hoping this warning is timely and not _too_ redundant, -- Kevin B. McCarty [EMAIL PROTECTED] Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Latest kernel security upgrade in woody is BROKEN! DO NOT INSTALL!
kernel packages named kernel-image-2.4.18-1-subflavor with version 2.4.18-13 contain only one module. That and it expects the modules at 2.4.18-1 instead of 2.4.18-1-686-smp! hoping this warning is timely and not _too_ redundant, :-) Found out the hard way there is a 13.1 now tho' ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Anyone used Backports.org to upgrade a woody to 2.6?
On Wed, 2004-04-14 at 14:36 -0700, Bill Moseley wrote: Anyone have success using those packages to update a Woody box? Working great for my main mail/web server, and a postgres server at work. Any notes? Did you add backports to source.list or download the .deb and use dpkg -i for the modules and kernel? I added the source. I have xfs file systems so I guess I'd need to use initrd since XFS is included as a module -- is there any additional setup required? Shouldn't be anything special needed. The stock kernels are initrd kernels. It should Just Work. -Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrade de woody a SID i KDE
Hola a tothom: Avui he intentat fer un upgrade de woody (amb KDE 2.2)a SID. EL problema es que quan ja a baixat tot els paquets i comença a configurar em pregunta quin gestor de X vull, però nomes em dona dues opcions: gdm i xdm (no estic segur dels noms peraquè no els he apuntat quan tocaba...). El tema es que li dic gdm (deu ser gnome suposo) i just despres em comença a borrar paquets de kde (lògic suposo, si creu que no es faran servir). La pregunta es: Hi alguna manera de que al fer la instalacio de SID em doni la opcio de "kdm". ¿Que faig malament? I ja posats, suposem que vull intsl·lar kde despres de que m'ho borri tot, per on haig de començar? Moltes gracies per endavant! Toni P.D: Per cer, els meus source-list es: deb http://ftp.fi.debian.org/debian/ sid main non-free contribdeb-src http://ftp.fi.debian.org/debian/ sid main non-free contribdeb http://non-us.debian.org/debian-non-US/ sid/non-US main contribnon-freedeb-src http://non-us.debian.org/debian-non-US/ sid/non-US main contrib non-free
Re: Upgrade von Woody auf Sarge
On Thu, 18 Dec 2003, Andreas Pakulat wrote: Hae, ich halte es fuer ein Geruecht das das Archiv von debian-user-german keine Eintraege der juengeren Vergangenheit beherbergt. Oft sind Posts eher im Archiv als bei mir auf'm Rechner. Ups, du hast Recht. Ich hab grad noch mal nachgeschaut ... ich hatte bei user.de aufgehoert, weiter zu suchen, und hintendran in Klammer steht (dead list, see user-german) ... tschuldigung R. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Upgrade von Woody auf Sarge
Hallo, in einer Antwort, erst vor ein paar Tagen, war ein Link genannt, wo ich Anleitung dazu finden kann, direkt ueber das Netz von Woody auf Sarge einen upgrade zu machen. Leider habe ich diese Mail nicht mehr. Und das Archiv der Mailingliste reicht nicht bis in die juengere Vergangenheit. Kann mir jemand diesen Link noch mal nennen? Danke, Raimund -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Upgrade von Woody auf Sarge
On 18.Dec 2003 - 23:59:49, Raimund Kohl-Fuechsle wrote: Hallo, in einer Antwort, erst vor ein paar Tagen, war ein Link genannt, wo ich Anleitung dazu finden kann, direkt ueber das Netz von Woody auf Sarge einen upgrade zu machen. Leider habe ich diese Mail nicht mehr. Und das Archiv der Mailingliste reicht nicht bis in die juengere Vergangenheit. Kann mir jemand diesen Link noch mal nennen? Hae, ich halte es fuer ein Geruecht das das Archiv von debian-user-german keine Eintraege der juengeren Vergangenheit beherbergt. Oft sind Posts eher im Archiv als bei mir auf'm Rechner. Zu deinem Problem: Sofern du keine! Backports installiert hast ist ein einfaches austauschen vonn woody bzw. stable durch sarge bzw. testing in der /etc/apt/sources.list ausreichend. Danach natuerlich noch ein apt-get update um die neuen Paketlisten zu laden. Dann kannst du mit einem apt-get -u dist-upgrade das ganze System auf testing Level bringen. Guck dir dazu auch noch die Optionen zu apt-get in der Manpage an, speziell die nichts tun Option, bei der er nur so tut als ob. Und wie gesagt: Wenn du Backports drauf hast, wirds u.U. schwierig ein Upgrade auf Sarge durchzuefuehren. Andreas -- There's no point in being grown up if you can't be childish sometimes. -- Dr. Who -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid mglich?
On Thu, Nov 13, 2003 at 10:21:57PM +0100, Sven 'Rae the Git' Grounsell wrote: On Thu, 13 Nov 2003 21:56:30 +0100 abo [EMAIL PROTECTED] wrote: hallo, gerade wollte ich von stable auf unstable upgraden ich habe sources.list and apt.conf angepasst und 'apt-get update' ausgeführt. mit 'apt-get -u dist-upgrade' würde ich folgende packete verlieren: The following packages will be REMOVED: console-tools-libs igerman kdebase kdebase-libs kdelibs3 kdelibs3-bin konsole libdigest-md5-perl libfam0 libkonq3 liblcms libmemoize-perl libmime-base64-perl libvorbis0 libweakref-perl libxml-twig-perl libxmltv-perl mp3blaster mythtv mythtv-backend mythtv-frontend wgerman xmltv-util Ich habe ausschliesslich woody packete auf dem rechner. wie soll ich weiter vorgehen? freu mich über jeden hinweis! andreas am einfachsten geht das, indem du ein frontend wie aptitude benutzt (ncurses), dir die pakete anzeigen laesst, die er installieren, updaten und deinstallieren will und da die pakete, die du auf jeden fall behalten willst, auf hold setzt (=, shift+0). aptitude sollte dann automatisch die abhaengigkeiten und moegliche broken packets so loesen, dass der gewuenschte effekt eintritt, wenn das technisch moeglich ist. nur ein weg von wahrscheinlich unzaehligen :o) Moin, ich würde keine Pakete auf hold setzen. Wenn ein dist-upgrade einige Pakete deinstallieren möchte, dann wird es seine Gründe dafür haben. Ich würde zunächst die sources.list von allen woody Einträgen befreien. Dann würde ich an Deiner Stelle die Namen der Pakete die deinstalliert wurden aufschreiben und nach dem dist-upgrade neu installieren. Die KDE-Pakete z.B. muss er eh komplett neu holen, da sie zu den alten nicht mehr kompatibel sind. Gruß, Sven -- +--+ | .''`. Sven Bergner E-Mail: [EMAIL PROTECTED] | | : :' : | | `. `'Debian GNU/Linux User - http://www.debian.org/ | | `- Registered Linux-User #65111 | +--+ -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-- s+: a- C++ UL++ P+++ L++ E W++ N+ o K w--- O- M- V PS+ PE Y+ PGP++ t+ 5-- X+++ R+ tv++ b++ DI D++ G e++ h--- r+++ y+++ --END GEEK CODE BLOCK-- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid moeglich?
On Fri, 14 Nov 2003 09:48:54 +0100 Sven Bergner [EMAIL PROTECTED] wrote: Moin, ich würde keine Pakete auf hold setzen. Wenn ein dist-upgrade einige Pakete deinstallieren möchte, dann wird es seine Gründe dafür haben. ja, z.b. den grund, dass die version eines pakets in unstable oder testing dependencies hat, die entweder momentan ungeloest sind, oder die voruebergehende zwischenversionen sind, mit denen eines oder mehrere der anderen installierten pakete nix anfangen koennen. wenn man auf diesen rat hoert, nichts auf hold zu setzen, erlebt man des oefteren, dass man z.b. ne zeitlang ohne mplayer auskommen soll, oder sein lieblingsspiel gerade nicht zu den aktuellen paketversionen passt :o) gruss Sven ps: Subject: Re: sauberer upgrade von woody auf sid möglich? -- genau aus dem grund haben umlaute und sonderzeichen jenseits von der regulaeren interpunktion im mailheader nix zu suchen ;o) -- http://www.tuxhilfe.de.vu/ sven at schnuffs dot de sgrounsell at sectoor dot de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid moeglich?
On Fri, Nov 14, 2003 at 12:06:41PM +0100, Sven 'Rae the Git' Grounsell wrote: On Fri, 14 Nov 2003 09:48:54 +0100 Sven Bergner [EMAIL PROTECTED] wrote: Moin, ich würde keine Pakete auf hold setzen. Wenn ein dist-upgrade einige Pakete deinstallieren möchte, dann wird es seine Gründe dafür haben. ja, z.b. den grund, dass die version eines pakets in unstable oder testing dependencies hat, die entweder momentan ungeloest sind, oder die voruebergehende zwischenversionen sind, mit denen eines oder mehrere der anderen installierten pakete nix anfangen koennen. wenn man auf diesen rat hoert, nichts auf hold zu setzen, erlebt man des oefteren, dass man z.b. ne zeitlang ohne mplayer auskommen soll, oder sein lieblingsspiel gerade nicht zu den aktuellen paketversionen passt :o) Wenn man diese Dinge nicht in den Griff bekommt, sollte man vielleicht die Finger von SID lassen. Ich benutze jetzt seit geraumer Zeit SID und habe alles was ich brauche. gruss Sven ps: Subject: Re: sauberer upgrade von woody auf sid möglich? -- genau aus dem grund haben umlaute und sonderzeichen jenseits von der regulaeren interpunktion im mailheader nix zu suchen ;o) Das Subjekt stammt nicht von mir. Gruß, Sven -- +--+ | .''`. Sven Bergner E-Mail: [EMAIL PROTECTED] | | : :' : | | `. `'Debian GNU/Linux User - http://www.debian.org/ | | `- Registered Linux-User #65111 | +--+ -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-- s+: a- C++ UL++ P+++ L++ E W++ N+ o K w--- O- M- V PS+ PE Y+ PGP++ t+ 5-- X+++ R+ tv++ b++ DI D++ G e++ h--- r+++ y+++ --END GEEK CODE BLOCK-- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid moeglich?
On Fri, 14 Nov 2003 12:26:46 +0100 Sven Bergner [EMAIL PROTECTED] wrote: On Fri, Nov 14, 2003 at 12:06:41PM +0100, Sven 'Rae the Git' Grounsell wrote: On Fri, 14 Nov 2003 09:48:54 +0100 Sven Bergner [EMAIL PROTECTED] wrote: Moin, ich würde keine Pakete auf hold setzen. Wenn ein dist-upgrade einige Pakete deinstallieren möchte, dann wird es seine Gründe dafür haben. ja, z.b. den grund, dass die version eines pakets in unstable oder testing dependencies hat, die entweder momentan ungeloest sind, oder die voruebergehende zwischenversionen sind, mit denen eines oder mehrere der anderen installierten pakete nix anfangen koennen. wenn man auf diesen rat hoert, nichts auf hold zu setzen, erlebt man des oefteren, dass man z.b. ne zeitlang ohne mplayer auskommen soll, oder sein lieblingsspiel gerade nicht zu den aktuellen paketversionen passt :o) Wenn man diese Dinge nicht in den Griff bekommt, sollte man vielleicht die Finger von SID lassen. Ich benutze jetzt seit geraumer Zeit SID und habe alles was ich brauche. das steht nochmal auf nem anderen blatt ... ich bin eh erstaunt, wie oft immernoch debian als einsteiger-linux empfohlen wird. das schafft IMO nur unnoetigen frust... ketz debian installieren ist was fuer linuxer mit zuviel freizeit, debian aktuell halten ist was fuer kinder, und einsteiger nehmen lieber gleich suse. /ketz *vorsorglich in deckung geh* ;o) ps: Subject: Re: sauberer upgrade von woody auf sid möglich? -- genau aus dem grund haben umlaute und sonderzeichen jenseits von der regulaeren interpunktion im mailheader nix zu suchen ;o) Das Subjekt stammt nicht von mir. wer sagt, dass das von dir sei? :o) gruss auch Sven -- http://www.tuxhilfe.de.vu/ sven at schnuffs dot de sgrounsell at sectoor dot de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid moeglich?
On Fri, Nov 14, 2003 at 12:49:24PM +0100, Sven 'Rae the Git' Grounsell wrote: On Fri, 14 Nov 2003 12:26:46 +0100 Sven Bergner [EMAIL PROTECTED] wrote: On Fri, Nov 14, 2003 at 12:06:41PM +0100, Sven 'Rae the Git' Grounsell wrote: On Fri, 14 Nov 2003 09:48:54 +0100 Sven Bergner [EMAIL PROTECTED] wrote: Moin, ich würde keine Pakete auf hold setzen. Wenn ein dist-upgrade einige Pakete deinstallieren möchte, dann wird es seine Gründe dafür haben. ja, z.b. den grund, dass die version eines pakets in unstable oder testing dependencies hat, die entweder momentan ungeloest sind, oder die voruebergehende zwischenversionen sind, mit denen eines oder mehrere der anderen installierten pakete nix anfangen koennen. wenn man auf diesen rat hoert, nichts auf hold zu setzen, erlebt man des oefteren, dass man z.b. ne zeitlang ohne mplayer auskommen soll, oder sein lieblingsspiel gerade nicht zu den aktuellen paketversionen passt :o) Wenn man diese Dinge nicht in den Griff bekommt, sollte man vielleicht die Finger von SID lassen. Ich benutze jetzt seit geraumer Zeit SID und habe alles was ich brauche. das steht nochmal auf nem anderen blatt ... ich bin eh erstaunt, wie oft immernoch debian als einsteiger-linux empfohlen wird. das schafft IMO nur unnoetigen frust... ketz debian installieren ist was fuer linuxer mit zuviel freizeit, debian aktuell halten ist was fuer kinder, und einsteiger nehmen lieber gleich suse. /ketz Für mich ist der Thread hier zu Ende. Wir sind ja nicht im Heise Forum. Gruß, Sven -- +--+ | .''`. Sven Bergner E-Mail: [EMAIL PROTECTED] | | : :' : | | `. `'Debian GNU/Linux User - http://www.debian.org/ | | `- Registered Linux-User #65111 | +--+ -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-- s+: a- C++ UL++ P+++ L++ E W++ N+ o K w--- O- M- V PS+ PE Y+ PGP++ t+ 5-- X+++ R+ tv++ b++ DI D++ G e++ h--- r+++ y+++ --END GEEK CODE BLOCK-- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid moeglich?
On Fri, 14 Nov 2003 13:01:44 +0100 Sven Bergner [EMAIL PROTECTED] wrote: Für mich ist der Thread hier zu Ende. Wir sind ja nicht im Heise Forum. das stimmt, denn im heise-forum wird zu 99% geflamed, sprich unfundierte kommentare werden abgelassen, die a) keinerlei realitaetsbezug haben und b) auch auf nachfrage hin keinerlei rechtfertigung jenseits von persoenlicher sympathie oder antipathie bekommen. selbstkritik faellt AFAIK jedoch nicht unter o.g. kriterien. gruss Sven -- http://www.tuxhilfe.de.vu/ sven at schnuffs dot de sgrounsell at sectoor dot de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
sauberer upgrade von woody auf sid möglich?
hallo, gerade wollte ich von stable auf unstable upgraden ich habe sources.list and apt.conf angepasst und 'apt-get update' ausgeführt. mit 'apt-get -u dist-upgrade' würde ich folgende packete verlieren: The following packages will be REMOVED: console-tools-libs igerman kdebase kdebase-libs kdelibs3 kdelibs3-bin konsole libdigest-md5-perl libfam0 libkonq3 liblcms libmemoize-perl libmime-base64-perl libvorbis0 libweakref-perl libxml-twig-perl libxmltv-perl mp3blaster mythtv mythtv-backend mythtv-frontend wgerman xmltv-util Ich habe ausschliesslich woody packete auf dem rechner. wie soll ich weiter vorgehen? freu mich über jeden hinweis! andreas -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sauberer upgrade von woody auf sid mglich?
On Thu, 13 Nov 2003 21:56:30 +0100 abo [EMAIL PROTECTED] wrote: hallo, gerade wollte ich von stable auf unstable upgraden ich habe sources.list and apt.conf angepasst und 'apt-get update' ausgeführt. mit 'apt-get -u dist-upgrade' würde ich folgende packete verlieren: The following packages will be REMOVED: console-tools-libs igerman kdebase kdebase-libs kdelibs3 kdelibs3-bin konsole libdigest-md5-perl libfam0 libkonq3 liblcms libmemoize-perl libmime-base64-perl libvorbis0 libweakref-perl libxml-twig-perl libxmltv-perl mp3blaster mythtv mythtv-backend mythtv-frontend wgerman xmltv-util Ich habe ausschliesslich woody packete auf dem rechner. wie soll ich weiter vorgehen? freu mich über jeden hinweis! andreas am einfachsten geht das, indem du ein frontend wie aptitude benutzt (ncurses), dir die pakete anzeigen laesst, die er installieren, updaten und deinstallieren will und da die pakete, die du auf jeden fall behalten willst, auf hold setzt (=, shift+0). aptitude sollte dann automatisch die abhaengigkeiten und moegliche broken packets so loesen, dass der gewuenschte effekt eintritt, wenn das technisch moeglich ist. nur ein weg von wahrscheinlich unzaehligen :o) gruss Sven -- http://www.tuxhilfe.de.vu/ sven at schnuffs dot de sgrounsell at sectoor dot de -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Upgrade desde Woody a Testing
Hola, estoy migrando desde Mandrake a Debian; conseguí los 3 primeros cds de Woody 3.0r1, y lo instalé perfectamente. Aprendí a utilizar apt-get, y bajé las actualizaciones. Todo muy bien. Ahora, tengo entendido que lo que tengo hasta ahora es lo más estable (la distribución estable), pero es algo viejito, porque quiero utilizar cosas un poco más actualizadas, como KDE 3.1.3 y Gnome 2.25, ya que mi máquina es una máquina de escritorio. Mi pregunta es: teniendo Woody instalado y al día, como hago para upgradear a la versión Testing (Sarge) de Debian vía Internet? Con Apt-Get? o directamente me tengo que bajar las ISOs de la versión Sarge? Me animé a tocar el archivo /etc/apt/aptlists (o algo así) y cambié los sources, en donde decía stable lo cambié por testing... Bajó unos 60 MB, pero me parece que pisé algunas cosas, y algunos paquetes se negaron a instalar (error en el dpkg). En consecuencia, asumo que este no es el método, entonces, cuál es? Muchas Gracias
Upgrade desde Woody a Testing
Hola, estoy migrando desde Mandrake a Debian; conseguí los 3 primeros cds de Woody 3.0r1, y lo instalé perfectamente. Aprendí a utilizar apt-get, y bajé las actualizaciones. Todo muy bien. Ahora, tengo entendido que lo que tengo hasta ahora es lo más estable (la distribución estable), pero es algo viejito, porque quiero utilizar cosas un poco más actualizadas, como KDE 3.1.3 y Gnome 2.25, ya que mi máquina es una máquina de escritorio. Mi pregunta es: teniendo Woody instalado y al día, como hago para upgradear a la versión Testing (Sarge) de Debian vía Internet? Con Apt-Get? o directamente me tengo que bajar las ISOs de la versión Sarge? Me animé a tocar el archivo /etc/apt/aptlists (o algo así) y cambié los sources, en donde decía stable lo cambié por testing... Bajó unos 60 MB, pero me parece que pisé algunas cosas, y algunos paquetes se negaron a instalar (error en el dpkg). En consecuencia, asumo que este no es el método, entonces, cuál es? Muchas Gracias
Re: Upgrade desde Woody a Testing
Coordenadas temporales: Tue, Sep 09, 2003 at 03:04:05AM -0300 Sujeto: Marcelo Fernandez Comunicaba sobre: Upgrade desde Woody a Testing Me animé a tocar el archivo /etc/apt/aptlists (o algo así) y cambié los /etc/apt/sources.list sources, en donde decía stable lo cambié por testing... Bajó unos 60 Bien. MB, pero me parece que pisé algunas cosas, y algunos paquetes se negaron a instalar (error en el dpkg). En consecuencia, asumo que este no es el método, entonces, cuál es? Bajo 60 Mb... ¿Cuando, con que orden? Porque solo por cambiar ese fichero, no actualizas nada. El procedimiento es: -Cambiar el fichero, como has hecho. -Ejecutar apt-get update -Ejecutar apt-get dist-upgrade Todo esto como root y ya tienes Sarge. Más información: man apt-get man sources.list Salu2 -- Windows 95: Ahora para Mega Drive y Nintendo! -- Www.frases.com. pgpIBUqi4QoSt.pgp Description: PGP signature
Re: Upgrade desde Woody a Testing
Si, habia hecho lo que me has dicho: cambié el archivo de sources de apt y luego hice un apt-get upgrade (alli bajó 60 MB). Ahí es donde me dice que unos paquetes de console (common-console creo) no se pueden instalar... Aunque estoy dispuesto a instalar el Debian de nuevo, ya que tengo que reparar algunos errores de la instalación... Muchas Gracias! Saludos Marcelo El mar, 09-09-2003 a las 03:23, Emilio Santos escribió: Coordenadas temporales: Tue, Sep 09, 2003 at 03:04:05AM -0300 Sujeto: Marcelo Fernandez Comunicaba sobre: Upgrade desde Woody a Testing Me animé a tocar el archivo /etc/apt/aptlists (o algo así) y cambié los /etc/apt/sources.list sources, en donde decía stable lo cambié por testing... Bajó unos 60 Bien. MB, pero me parece que pisé algunas cosas, y algunos paquetes se negaron a instalar (error en el dpkg). En consecuencia, asumo que este no es el método, entonces, cuál es? Bajo 60 Mb... ¿Cuando, con que orden? Porque solo por cambiar ese fichero, no actualizas nada. El procedimiento es: -Cambiar el fichero, como has hecho. -Ejecutar apt-get update -Ejecutar apt-get dist-upgrade Todo esto como root y ya tienes Sarge. Más información: man apt-get man sources.list Salu2
RE: Upgrade desde Woody a Testing
Hola, Yo tenia problemas para actualizarme tambien y siguiendo esto tengo actualizado mi Debian a Sarge y el Kde 3.1.3 ... solo me falta el GNOME ... tiempo al tiempo : PASAR DE WOODY A SARGE http://es.kde.org/modules/newbb/viewtopic.php?topic_id=415forum=6jump= 1 INSTALAR KDE 3.1.3 http://es.kde.org/modules/news/article.php?storyid=81 Espero que te sirva ... por cierto si alguien tiene lo de GNOME que nos ayude. Saludos Miguel Corbella -Mensaje original- De: Marcelo Fernandez [mailto:[EMAIL PROTECTED] Enviado el: martes, 09 de septiembre de 2003 8:03 Para: Foro Debian Asunto: Upgrade desde Woody a Testing Hola, estoy migrando desde Mandrake a Debian; conseguí los 3 primeros cds de Woody 3.0r1, y lo instalé perfectamente. Aprendí a utilizar apt-get, y bajé las actualizaciones. Todo muy bien. Ahora, tengo entendido que lo que tengo hasta ahora es lo más estable (la distribución estable), pero es algo viejito, porque quiero utilizar cosas un poco más actualizadas, como KDE 3.1.3 y Gnome 2.25, ya que mi máquina es una máquina de escritorio. Mi pregunta es: teniendo Woody instalado y al día, como hago para upgradear a la versión Testing (Sarge) de Debian vía Internet? Con Apt-Get? o directamente me tengo que bajar las ISOs de la versión Sarge? Me animé a tocar el archivo /etc/apt/aptlists (o algo así) y cambié los sources, en donde decía stable lo cambié por testing... Bajó unos 60 MB, pero me parece que pisé algunas cosas, y algunos paquetes se negaron a instalar (error en el dpkg). En consecuencia, asumo que este no es el método, entonces, cuál es? Muchas Gracias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrade desde Woody a Testing
De todas formas el kde 3.1.x no esta en sarge, solo los paquetes de traduccion kde-i18n-xx, yo me he actualizado ayer mismo de woody a sarge, y he tenído que conservar los paquetes del kde 3.1.x que tenía de woody bajados de kde, en debian, estan en sid... puede que en unas semanas se pasen a sarge, pero eso yo, ya no lo sé. Así que, creo que tendrás que tener sarge, con los paquetes creados para woody en kde, mientras en debian no se pongan en sarge.
Re: Upgrade desde Woody a Testing
Hola, Yo tenia problemas para actualizarme tambien y siguiendo esto tengo actualizado mi Debian a Sarge y el Kde 3.1.3 ... solo me falta el GNOME... tiempo al tiempo : PASAR DE WOODY A SARGE http://es.kde.org/modules/newbb/viewtopic.php?topic_id=415forum=6jump= 1 INSTALAR KDE 3.1.3 http://es.kde.org/modules/news/article.php?storyid=81 Espero que te sirva ... por cierto si alguien tiene lo de GNOME que nos ayude. Facil, simplemente puse deb http://mirror.raw.no/ gnome2.2/ en el sources.list y listo, o si no deb http://ftp.acc.umu.se/mirror/mirrors.evilgeniuses.org.uk/debian/backports/woody/ gnome2.2/. Todo esto para Woody. Hasta ahora no he tenido problemas. Saludos
RE: Upgrade desde Woody a Testing
Eso he visto que no hay metapackages para KDE 3.1.3, tengo que seleccionar paquete a paquete los que quiero instalar Sl2 -Mensaje original- De: Borxa Varela Bouzas [mailto:[EMAIL PROTECTED] Enviado el: martes, 09 de septiembre de 2003 11:32 Para: [EMAIL PROTECTED]; debian-user-spanish@lists.debian.org Asunto: Re: Upgrade desde Woody a Testing De todas formas el kde 3.1.x no esta en sarge, solo los paquetes de traduccion kde-i18n-xx, yo me he actualizado ayer mismo de woody a sarge, y he tenído que conservar los paquetes del kde 3.1.x que tenía de woody bajados de kde, en debian, estan en sid... puede que en unas semanas se pasen a sarge, pero eso yo, ya no lo sé. Así que, creo que tendrás que tener sarge, con los paquetes creados para woody en kde, mientras en debian no se pongan en sarge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upgrade to woody - screen sessions without BACKSPACE
Hi all, since I upgraded Debian 2.2. machines to Debian Woody I always have some problems when I log in to older Debian machines and start screen. Within that screen session I cannot use BACKSPACE or DEL. I can emulate BACKSPACE with ctrlh. What can I do to get BACKPSACE back to work in screen-sessions on Debian 2.2. machines? When I press BACKSPACE then I get [3~. Regards Holger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade fvwm (woody)
Cesar Rincon [EMAIL PROTECTED] wrote: On Tue, 2003-07-22 at 03:12, Ignacio García Fernández wrote: Argh!! no estoy solo en el mundo!! Alguien más usa fvwm!! :-D Un día de estos intercambiamos ficheros de configuración :op ¡Yo! ¡Yo también! ¡Yo! Otro usuario satisfecho de FVWM, aquí :-) [...] Supongo que ya habrás resuelto tu problema con la versión, así que sólo preguntaré: ¿porqué quieres actualizar? ¿Algún beneficio específico en la nueva versión? Es básicamente por algunas mejoras estéticas, como por ejemplo el manejo de Transparencias. En lo que respecta a funcionalidad, 2.4.x está ok. saludos -ejg
Re: upgrade fvwm (woody)
On Mon, Jul 21, 2003 at 02:50:22PM -0400, Eduardo Gargiulo wrote: Hola a todos. Actualmente estoy corriendo debian 3.0_r1 y todo funciona ok. Ahora quiero actualizar la versión de fvwm a 2.5.7. Qué es lo mas Argh!! no estoy solo en el mundo!! Alguien más usa fvwm!! :-D Un día de estos intercambiamos ficheros de configuración :op recomendable, cambiar mis sources y pasarme a testing/unstable (no se en qué estado se encuentra) o bajarme los fuentes y compilarlos por separado? Cambiar tu source.list y editar el fichero preferences que hay en el mismo directorio Hay alguna forma debian de manejarme en estos casos? Esa. En el fichero preferences le puedes decir que ignore todas las entradas del sourcees list de testing o unstable, salvo para ciertos paquetes, que es lo que tu quieres Pero mira antes las dependencias de fvwm, porque tal vez la versión 2.5 no la puedas usar en woody porque necesites versiones más nuevas de bibliotecas del sistema o algo. gracias por adelantado ... -ejg -- May the source be with you NO A LA GUERRA - NOT TO WAR Ignacio García Fernández Instituto de Robótica ignacio.garcia_at_uv.esUniversidad de Valencia http://robotica.uv.es/~ignacio/ Tlf. 96 354 3564 pgpBuVsOT9uEJ.pgp Description: PGP signature
Re: upgrade fvwm (woody)
Ignacio García Fernández wrote:
On Mon, Jul 21, 2003 at 02:50:22PM -0400, Eduardo Gargiulo wrote:
Hola a todos.
Actualmente estoy corriendo debian 3.0_r1 y todo funciona ok.
Ahora quiero actualizar la versión de fvwm a 2.5.7. Qué es lo mas
Argh!! no estoy solo en el mundo!! Alguien más usa fvwm!! :-D
Un día de estos intercambiamos ficheros de configuración
:op
Somos muchos los que usamos fvwm, yo lo he probado incluso con Gnome.
Parece muy simple cuando lo instalas pero tiene muchas posibilidades y
una vez personalizado uno ya no lo cambia por nada.
Es muy configuralble, a mi me encanta por ejemplo usar el
escritorio virtual en el que al alcanzar el borde de la pantalla
se mueve un poco el área de visualización como si movieras una ventana
sobre 9 monitores en mi caso.
(Hay gente a la que esto le marea, pero yo no se vivir sin ello)
#
# DeskTopSize sets the size of the desktop in units of physical screen
# `pages'. I prefer to use a single desktop with multiple pages,
# but many people like having multiple desktops. I thinks its
confusing.
#
DeskTopSize 3x3
#
# I like to be able to move between pages or desks simply by moving
# the mouse against the screen border. I find it very useful. The
# following command enables this behaviour. To disable it, the
# command EdgeScroll 0 0 could be placed in the post.hook.
#
EdgeScroll 100 100
#(Cuando se alcanza el borde se desplaza 100 puntos)
Otras opciones que me gustan:
- permite maximizar las ventanas en vertical y horizontal, que mara
mi
es de lo mas útil
- permite mimimizar la pantalla dejando solo la barra de título.
(en mi caso lo tengo con el botón derecho del ratón sobre el título)
- permite asignar las acciones a los botones del ratón en las
distintas situaciones.
- Tiene un monton de modulos adicionales para hacer multitud de cosas
desde una barra de tareas hasta...
En fin que sobre todo para maquinas pequeñas es una maravilla
May the source be with you NO A LA GUERRA - NOT TO WAR
--
Fernando.
{:-{D
Hackers do it with fewer instructions.
Re: upgrade fvwm (woody)
Ignacio García Fernández [EMAIL PROTECTED] wrote: On Mon, Jul 21, 2003 at 02:50:22PM -0400, Eduardo Gargiulo wrote: Hola a todos. Actualmente estoy corriendo debian 3.0_r1 y todo funciona ok. Ahora quiero actualizar la versión de fvwm a 2.5.7. Qué es lo mas Argh!! no estoy solo en el mundo!! Alguien más usa fvwm!! :-D Un día de estos intercambiamos ficheros de configuración :op recomendable, cambiar mis sources y pasarme a testing/unstable (no se en qué estado se encuentra) o bajarme los fuentes y compilarlos por separado? Cambiar tu source.list y editar el fichero preferences que hay en el mismo directorio Hay alguna forma debian de manejarme en estos casos? Esa. En el fichero preferences le puedes decir que ignore todas las entradas del sourcees list de testing o unstable, salvo para ciertos paquetes, que es lo que tu quieres Pero mira antes las dependencias de fvwm, porque tal vez la versión 2.5 no la puedas usar en woody porque necesites versiones más nuevas de bibliotecas del sistema o algo. Y cómo debería hacer para bajarme los fuentes de fvwm-2.5.7 con apt-get? En este caso, apt actualizaría las dependencias o debería hacerlo a mano? Muchas gracias por responder. Soy un usuario mas que satisfecho con fvwm y cada día me sorprende mas con todas las posibilidades que ofrece, aunque hay que reconocer que lleva su tiempo aprender a customizarlo. saludos -ejg pgpbKlj2wLTg7.pgp Description: PGP signature
Re: upgrade fvwm (woody)
On Tue, 2003-07-22 at 03:12, Ignacio García Fernández wrote: Argh!! no estoy solo en el mundo!! Alguien más usa fvwm!! :-D Un día de estos intercambiamos ficheros de configuración :op ¡Yo! ¡Yo también! ¡Yo! Otro usuario satisfecho de FVWM, aquí :-) Yo tengo configurados teclazos y strokes (trazos con el mouse) para disparar aplicaciones y comandos. Ejemplos: PgUp/PgDn retrocede y avanza la canción en XMMS; los botones de scroll en mi touchpad suben y bajan el volumen; dibujar una 'e' sobre el background lanza Emacs... (ésto último es presumir, nada más... no es que lo use mucho, siendo que presionar la letra 'e' sobre el background hace lo mismo, y yo soy más de teclado que de mouse :-) Supongo que ya habrás resuelto tu problema con la versión, así que sólo preguntaré: ¿porqué quieres actualizar? ¿Algún beneficio específico en la nueva versión? -CR
