Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Chris == Chris Menzel [EMAIL PROTECTED] writes: Chris On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes Chris wrote: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. Chris Does anyone know if this bug affects the configure script in Chris the fink OS X port of LyX with version number 1.2.2-1 (which I Chris believe is the most current version available)? The -1 Chris suggests that perhaps the script has been modified to remove Chris the bug. The patch that one can see at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/fink/dists/10.2/unstable/main/finkinfo/editors/lyx-1.2.2-1.patch?rev=1.1 seems to indicate that this is not the case. JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
> "Chris" == Chris Menzel <[EMAIL PROTECTED]> writes: Chris> On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes Chris> wrote: >> There is a very nasty bug in LyX 1.2.2 configure script: if you >> configure as root and an error occurs during the configure step >> (e.g. xforms not found), the the script will delete the /dev/null >> device. This undoubtly leads to very bad effect, since /dev/null is >> a very basic device in any unix system. Chris> Does anyone know if this bug affects the configure script in Chris> the fink OS X port of LyX with version number 1.2.2-1 (which I Chris> believe is the most current version available)? The "-1" Chris> suggests that perhaps the script has been modified to remove Chris> the bug. The patch that one can see at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/fink/dists/10.2/unstable/main/finkinfo/editors/lyx-1.2.2-1.patch?rev=1.1 seems to indicate that this is not the case. JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes wrote: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. Does anyone know if this bug affects the configure script in the fink OS X port of LyX with version number 1.2.2-1 (which I believe is the most current version available)? The -1 suggests that perhaps the script has been modified to remove the bug. Chris Menzel
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes wrote: > > There is a very nasty bug in LyX 1.2.2 configure script: if you > configure as root and an error occurs during the configure step > (e.g. xforms not found), the the script will delete the /dev/null > device. This undoubtly leads to very bad effect, since /dev/null is a > very basic device in any unix system. Does anyone know if this bug affects the configure script in the fink OS X port of LyX with version number 1.2.2-1 (which I believe is the most current version available)? The "-1" suggests that perhaps the script has been modified to remove the bug. Chris Menzel
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, 2003-01-08 at 22:02, Jean-Marc Lasgouttes wrote: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. Not possible if using devfs under Linux of course. So I'm safe ;) Devfs pretends to be a filesystem mounted at /dev, with devices coming and going as modules are inserted or removed. JMarc Darren
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, 2003-01-08 at 22:02, Jean-Marc Lasgouttes wrote: > There is a very nasty bug in LyX 1.2.2 configure script: if you > configure as root and an error occurs during the configure step > (e.g. xforms not found), the the script will delete the /dev/null > device. This undoubtly leads to very bad effect, since /dev/null is a > very basic device in any unix system. Not possible if using devfs under Linux of course. So I'm safe ;) Devfs pretends to be a filesystem mounted at /dev, with devices coming and going as modules are inserted or removed. > JMarc Darren
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Jean-Marc Lasgouttes wrote: Michael == Michael Abshoff [EMAIL PROTECTED] writes: Michael This bug bit me couple of times when I set up my new Laptop. Michael I never suspected the configure-script and chased the bug for Michael a week. Yes, it is ugly. Note that kudos for spotting this should go to Dominik Vogt. JMarc Ofcourse this isn't an excuse for this bug, but... Once upon a time there was a rule: Never configure and compile software as root! After a succesful build you should become root with su (without hyphen!) and do a make install, if you tested this piece of software and trust it. I'm working without the magic power of root as much as possible. And on my laptop and my home box there it is the same. Stephan
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Michael == Michael Abshoff [EMAIL PROTECTED] writes: Michael This bug bit me couple of times when I set up my new Laptop. Michael I never suspected the configure-script and chased the bug for Michael a week. Yes, it is ugly. Note that kudos for spotting this should go to Dominik Vogt. JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Stephan Witt wrote: Ofcourse this isn't an excuse for this bug, but... Once upon a time there was a rule: Never configure and compile software as root! After a succesful build you should become root with su (without hyphen!) and do a make install, if you tested this piece of software and trust it. I'm working without the magic power of root as much as possible. And on my laptop and my home box there it is the same. Stephan You are right about build software, but it was a fresh install without users. The funny thing is, that in my case /dev/null still existed, but somehow it couldn't be used. Are you guys still interested in bugreports fpr lyx 1.2.2? I am compiling a list of oddities and unexpected behaviours, but I won't be done till late friday. Michael -- Michael Abshoff - MRB - Universität Dortmund - Telefon 755-3463 (intern) Where do you want to RTFM today?
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Thu, Jan 09, 2003 at 12:51:09PM +0100, Michael Abshoff wrote: Are you guys still interested in bugreports fpr lyx 1.2.2? I am compiling a list of oddities and unexpected behaviours, but I won't be done till late friday. Especially if they are present in 1.3.0cvs, too: Yes. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Jean-Marc Lasgouttes wrote: "Michael" == Michael Abshoff <[EMAIL PROTECTED]> writes: Michael> This bug bit me couple of times when I set up my new Laptop. Michael> I never suspected the configure-script and chased the bug for Michael> a week. Yes, it is ugly. Note that kudos for spotting this should go to Dominik Vogt. JMarc Ofcourse this isn't an excuse for this bug, but... Once upon a time there was a rule: Never configure and compile software as root! After a succesful build you should become root with su (without hyphen!) and do a make install, if you tested this piece of software and trust it. I'm working without the magic power of root as much as possible. And on my laptop and my home box there it is the same. Stephan
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
> "Michael" == Michael Abshoff <[EMAIL PROTECTED]> writes: Michael> This bug bit me couple of times when I set up my new Laptop. Michael> I never suspected the configure-script and chased the bug for Michael> a week. Yes, it is ugly. Note that kudos for spotting this should go to Dominik Vogt. JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Stephan Witt wrote: Ofcourse this isn't an excuse for this bug, but... Once upon a time there was a rule: Never configure and compile software as root! After a succesful build you should become root with su (without hyphen!) and do a make install, if you tested this piece of software and trust it. I'm working without the magic power of root as much as possible. And on my laptop and my home box there it is the same. Stephan You are right about build software, but it was a fresh install without users. The funny thing is, that in my case /dev/null still existed, but somehow it couldn't be used. Are you guys still interested in bugreports fpr lyx 1.2.2? I am compiling a list of oddities and unexpected behaviours, but I won't be done till late friday. Michael -- Michael Abshoff - MRB - Universität Dortmund - Telefon 755-3463 (intern) Where do you want to RTFM today?
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Thu, Jan 09, 2003 at 12:51:09PM +0100, Michael Abshoff wrote: > Are you guys still interested in bugreports fpr lyx 1.2.2? I am compiling > a list of oddities and unexpected behaviours, but I won't be done > till late friday. Especially if they are present in 1.3.0cvs, too: Yes. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
[WARNING] Bad bug in lyx 1.2.2 configure script
There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. If you have been victim of this problem, please complain here and I'll try to find out how to reconstruct it (some magic command that I do not know yet). I plan to release a 1.2.3 version that does not have this problem very soon. The same problem occurs in 1.3.0cvs (and 1.3.0pre1 I guess) but is fixed now in cvs. A bit of background: there has been for a long time some code in LyX configure script that removed the config.cache file (that keep tracks of tests results) when an error has occured. This allows to re-run the script once you have made correction without seeing the old results. However, starting with autoconf 2.5x, the cache file now defaults to /dev/null (i.e. no cache). Since LyX 1.2.2 was the first version distributed with an autoconf script generated with autoconf 2.52, this triggered this awful behaviour. Sorry for the problems that this may cause to your systems... JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | If you have been victim of this problem, please complain here and I'll | try to find out how to reconstruct it (some magic command that I do | not know yet). On linux: mknod /dev/null c 1 3 (also use the -m switch to set permissons correctly rw-rw-rw-, or chmod the char device after creation chmod a=rw /dev/null) -- Lgb
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Am Mittwoch, 8. Januar 2003 12:32 schrieb Jean-Marc Lasgouttes: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. If you have been victim of this problem, please complain here and I'll try to find out how to reconstruct it (some magic command that I do not know yet). mknod -m666 /dev/null c 1 3 as root, of course -- ronny
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
For anyone who needs to recover, On my RedHat 8.0 machine /dev/null is a character device with major mode 1, minor mode 3 and mode a+rw - use mknod to make a new one. On Solaris, it's a soft link to /devices/pseudo/mm@0:null - use ln to recreate. Bill. On 8 Jan 2003, Jean-Marc Lasgouttes wrote: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. If you have been victim of this problem, please complain here and I'll try to find out how to reconstruct it (some magic command that I do not know yet). I plan to release a 1.2.3 version that does not have this problem very soon. The same problem occurs in 1.3.0cvs (and 1.3.0pre1 I guess) but is fixed now in cvs. A bit of background: there has been for a long time some code in LyX configure script that removed the config.cache file (that keep tracks of tests results) when an error has occured. This allows to re-run the script once you have made correction without seeing the old results. However, starting with autoconf 2.5x, the cache file now defaults to /dev/null (i.e. no cache). Since LyX 1.2.2 was the first version distributed with an autoconf script generated with autoconf 2.52, this triggered this awful behaviour. Sorry for the problems that this may cause to your systems... JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On most Linux-distros you won't be able to properly boot since the root filesystem ist usually mounted read-only. Remounting it as read-write will fail when /dev/null is not present (at least in SuSE). So start you system in single user mode, log in as root on the console, do a 'mount -o remount /' an then recreate /dev/null. then you can reboot or use init to go to your preferred runlevel. This bug bit me couple of times when I set up my new Laptop. I never suspected the configure-script and chased the bug for a week. Michael [EMAIL PROTECTED] wrote: For anyone who needs to recover, On my RedHat 8.0 machine /dev/null is a character device with major mode 1, minor mode 3 and mode a+rw - use mknod to make a new one. On Solaris, it's a soft link to /devices/pseudo/mm@0:null - use ln to recreate. Bill. -- Michael Abshoff - MRB - Universität Dortmund - Telefon 755-3463 (intern) Where do you want to RTFM today?
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes wrote: There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. Oh, /dev/null isn't much of a loss; I've never been able to get anything out of it, anyway :) hawk -- Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
[WARNING] Bad bug in lyx 1.2.2 configure script
There is a very nasty bug in LyX 1.2.2 configure script: if you configure as root and an error occurs during the configure step (e.g. xforms not found), the the script will delete the /dev/null device. This undoubtly leads to very bad effect, since /dev/null is a very basic device in any unix system. If you have been victim of this problem, please complain here and I'll try to find out how to reconstruct it (some magic command that I do not know yet). I plan to release a 1.2.3 version that does not have this problem very soon. The same problem occurs in 1.3.0cvs (and 1.3.0pre1 I guess) but is fixed now in cvs. A bit of background: there has been for a long time some code in LyX configure script that removed the config.cache file (that keep tracks of tests results) when an error has occured. This allows to re-run the script once you have made correction without seeing the old results. However, starting with autoconf 2.5x, the cache file now defaults to /dev/null (i.e. no cache). Since LyX 1.2.2 was the first version distributed with an autoconf script generated with autoconf 2.52, this triggered this awful behaviour. Sorry for the problems that this may cause to your systems... JMarc
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | If you have been victim of this problem, please complain here and I'll | try to find out how to reconstruct it (some magic command that I do | not know yet). On linux: mknod /dev/null c 1 3 (also use the -m switch to set permissons correctly "rw-rw-rw-", or chmod the char device after creation "chmod a=rw /dev/null") -- Lgb
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
Am Mittwoch, 8. Januar 2003 12:32 schrieb Jean-Marc Lasgouttes: > There is a very nasty bug in LyX 1.2.2 configure script: if you > configure as root and an error occurs during the configure step > (e.g. xforms not found), the the script will delete the /dev/null > device. This undoubtly leads to very bad effect, since /dev/null is a > very basic device in any unix system. > > If you have been victim of this problem, please complain here and I'll > try to find out how to reconstruct it (some magic command that I do > not know yet). mknod -m666 /dev/null c 1 3 as root, of course -- ronny
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
For anyone who needs to recover, On my RedHat 8.0 machine /dev/null is a character device with major mode 1, minor mode 3 and mode a+rw - use mknod to make a new one. On Solaris, it's a soft link to /devices/pseudo/mm@0:null - use ln to recreate. Bill. On 8 Jan 2003, Jean-Marc Lasgouttes wrote: > > There is a very nasty bug in LyX 1.2.2 configure script: if you > configure as root and an error occurs during the configure step > (e.g. xforms not found), the the script will delete the /dev/null > device. This undoubtly leads to very bad effect, since /dev/null is a > very basic device in any unix system. > > If you have been victim of this problem, please complain here and I'll > try to find out how to reconstruct it (some magic command that I do > not know yet). > > I plan to release a 1.2.3 version that does not have this problem very > soon. The same problem occurs in 1.3.0cvs (and 1.3.0pre1 I guess) but > is fixed now in cvs. > > A bit of background: there has been for a long time some code in > LyX configure script that removed the config.cache file (that keep > tracks of tests results) when an error has occured. This allows to > re-run the script once you have made correction without seeing the old > results. However, starting with autoconf 2.5x, the cache file now > defaults to /dev/null (i.e. no cache). Since LyX 1.2.2 was the first > version distributed with an autoconf script generated with autoconf > 2.52, this triggered this awful behaviour. > > Sorry for the problems that this may cause to your systems... > > JMarc >
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On most Linux-distros you won't be able to properly boot since the root filesystem ist usually mounted read-only. Remounting it as read-write will fail when /dev/null is not present (at least in SuSE). So start you system in single user mode, log in as root on the console, do a 'mount -o remount /' an then recreate /dev/null. then you can reboot or use init to go to your preferred runlevel. This bug bit me couple of times when I set up my new Laptop. I never suspected the configure-script and chased the bug for a week. Michael [EMAIL PROTECTED] wrote: For anyone who needs to recover, On my RedHat 8.0 machine /dev/null is a character device with major mode 1, minor mode 3 and mode a+rw - use mknod to make a new one. On Solaris, it's a soft link to /devices/pseudo/mm@0:null - use ln to recreate. Bill. -- Michael Abshoff - MRB - Universität Dortmund - Telefon 755-3463 (intern) Where do you want to RTFM today?
Re: [WARNING] Bad bug in lyx 1.2.2 configure script
On Wed, Jan 08, 2003 at 12:32:24PM +0100, Jean-Marc Lasgouttes wrote: > > There is a very nasty bug in LyX 1.2.2 configure script: if you > configure as root and an error occurs during the configure step > (e.g. xforms not found), the the script will delete the /dev/null > device. This undoubtly leads to very bad effect, since /dev/null is a > very basic device in any unix system. Oh, /dev/null isn't much of a loss; I've never been able to get anything out of it, anyway :) hawk -- Richard E. Hawkins, Asst. Prof. of Economics/"\ ASCII ribbon campaign [EMAIL PROTECTED] Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of Xand postings. Penn State until it pays my retainer. / \
