Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-07 Thread Francisco Paco Peralta
Where I can find those instructions?  I have googled around with no results.

Justice London [EMAIL PROTECTED] wrote: Just an FYI.. the upgrade from FC4 to 
CentOS 5 will work nearly
flawlessly (You can find instructions on how to do this via YUM online).

Justice

On Tue, 2008-03-04 at 14:40 -0800, Francisco Paco Peralta wrote:
 I agree 110% and will start planning the upgrade.  I have to check if
 the cms I am running for my website (also on the server) has any
 issues with centos.  I was just trying to see if the was a quick way
 of addressing this issue, but I certainly don't want to create any
 more work for you folks.
 
 Ericwe shall be in touch.  Thank You,
 
 Eric Shubert  wrote:
 Since FC4 has reached its EOL, I'm inclined to think that we
 shouldn't add
 yet another version of unionfs to qtp-newmodel just to support
 that one
 obsolete kernel.
 
 Paco, you really should get off of the FC track and on to
 CentOS at some
 point. Then you won't run into this problem again. When you're
 ready to do
 so, contact me off list and we can discuss what it would take.
 Otherwise,
 you can continue to use the copied or linked sandbox to
 upgrade your toaster
 packages.
 
 Justice London wrote:
  Okay.. you managed to find the one release/kernel combo that
 would
  require another union module just for it. Is there any way
 you can
  simply upgrade the kernel release or fedora release? The fc4
 release
  hasn't been supported for over a year, which means no
 security updates
  or anything.
  
  Justice
  
  On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
  Hey, Paco. Nice to hear from you.
 
  Indeed your observation is correct (afaict). Justice would
 know best though
  regarding the unionfs. That's a bit of a complicated
 situation, as there are
  4 module/versions which provide that capability, each for
 various kernel
  versions. I suppose that we might not have the right
 module/version paired
  up with the right kernel in your case (kernel 2.6.17), but
 Justice would
  need to make that call.
 
  If Justice can't help to get this resolved, you can always
 use a linked or
  copied sandbox to do the upgrade.
 
  Please keep us posted.
 
  Francisco Paco Peralta wrote:
  Well, I tried the unioned sandbox method and it didn't
 seem to work for me.
 
  I appears I have an unsupported kernel (fc4 vintage). The
 logs mention
  that I can add some extra flags to the command but I am
 unsure of the
  impact or repercussions. Comments are welcome.
 
  I have pasted some text from my session, any assistance
 would be greatly
  appreciated.
 
 
 
 
 
 
  Would you like a unioned sandbox (quicker, smaller, maybe
 less stable)
  [y]/n: y
 
  Using union filesystem ...
  qtp-mount-sandbox v0.2.6
  --No existing unionfs12 found. Continuing with build
 process
  --Testing for valid rpm install tool:
  yum -y install found!
 
  --Searching for valid kernel source/devel to build
 unionfs12:
  kernel-devel-2.6.17-1.2142_FC4
  --Looking at current kernel
  --You have the kernel source for the running kernel!
 
  --Building
  mv: cannot stat `unionfs.ko': No such file or directory
 
  --Something went wrong with the unionfs12 build
  --Please check /var/log/unionfs-build.log to see what
 happened
  qtp-build-unionfs failed,ure. Exiting!
 
  qtp-newmodel - qtp-mount-sandbox failed, exiting
 
  --- Hit ENTER to return to menu ---
 
  **
  my logs are as follows:
 
  **
 
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk
 clean
  make[1]: Entering directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  CLEAN /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
  make[1]: Leaving directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  rm -f subr.o dentry.o file.o inode.o main.o super.o
 stale_inode.o
  branchman.o xattr.o rdstate.o 

Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-07 Thread Lucian Cristian

Try this http://wiki.centos.org/HowTos/MigrationGuide/ServerCD_4.4_to_5
it should work (remember to backup!)


Francisco Paco Peralta wrote:
Where I can find those instructions?  I have googled around with no 
results.


*/Justice London [EMAIL PROTECTED]/* wrote:

Just an FYI.. the upgrade from FC4 to CentOS 5 will work nearly
flawlessly (You can find instructions on how to do this via YUM
online).

Justice

On Tue, 2008-03-04 at 14:40 -0800, Francisco Paco Peralta wrote:
 I agree 110% and will start planning the upgrade. I have to check if
 the cms I am running for my website (also on the server) has any
 issues with centos. I was just trying to see if the was a quick way
 of addressing this issue, but I certainly don't want to create any
 more work for you folks.

 Ericwe shall be in touch. Thank You,

 Eric Shubert wrote:
 Since FC4 has reached its EOL, I'm inclined to think that we
 shouldn't add
 yet another version of unionfs to qtp-newmodel just to support
 that one
 obsolete kernel.

 Paco, you really should get off of the FC track and on to
 CentOS at some
 point. Then you won't run into this problem again. When you're
 ready to do
 so, contact me off list and we can discuss what it would take.
 Otherwise,
 you can continue to use the copied or linked sandbox to
 upgrade your toaster
 packages.

 Justice London wrote:
  Okay.. you managed to find the one release/kernel combo that
 would
  require another union module just for it. Is there any way
 you can
  simply upgrade the kernel release or fedora release? The fc4
 release
  hasn't been supported for over a year, which means no
 security updates
  or anything.
 
  Justice
 
  On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
  Hey, Paco. Nice to hear from you.
 
  Indeed your observation is correct (afaict). Justice would
 know best though
  regarding the unionfs. That's a bit of a complicated
 situation, as there are
  4 module/versions which provide that capability, each for
 various kernel
  versions. I suppose that we might not have the right
 module/version paired
  up with the right kernel in your case (kernel 2.6.17), but
 Justice would
  need to make that call.
 
  If Justice can't help to get this resolved, you can always
 use a linked or
  copied sandbox to do the upgrade.
 
  Please keep us posted.
 
  Francisco Paco Peralta wrote:
  Well, I tried the unioned sandbox method and it didn't
 seem to work for me.
 
  I appears I have an unsupported kernel (fc4 vintage). The
 logs mention
  that I can add some extra flags to the command but I am
 unsure of the
  impact or repercussions. Comments are welcome.
 
  I have pasted some text from my session, any assistance
 would be greatly
  appreciated.
 
 



 
 
  Would you like a unioned sandbox (quicker, smaller, maybe
 less stable)
  [y]/n: y
 
  Using union filesystem ...
  qtp-mount-sandbox v0.2.6
  --No existing unionfs12 found. Continuing with build
 process
  --Testing for valid rpm install tool:
  yum -y install found!
 
  --Searching for valid kernel source/devel to build
 unionfs12:
  kernel-devel-2.6.17-1.2142_FC4
  --Looking at current kernel
  --You have the kernel source for the running kernel!
 
  --Building
  mv: cannot stat `unionfs.ko': No such file or directory
 
  --Something went wrong with the unionfs12 build
  --Please check /var/log/unionfs-build.log to see what
 happened
  qtp-build-unionfs failed,ure. Exiting!
 
  qtp-newmodel - qtp-mount-sandbox failed, exiting
 
  --- Hit ENTER to return to menu ---
 
  **
  my logs are as follows:
 
  **
 
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk
 clean
  make[1]: Entering directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  CLEAN /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
  make[1]: Leaving directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  rm -f subr.o dentry.o file.o inode.o main.o super.o
 stale_inode.o
  branchman.o xattr.o rdstate.o copyup.o dirhelper.o
 rename.o unlink.o
  lookup.o persistent_inode.o commonfops.o dirfops.o print.o
  malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags
 \#* *~
  rm -f TAGS tags
  rm -f unionfs-1.2.tar.gz
  make -C utils clean
  

Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-06 Thread Justice London
Just an FYI.. the upgrade from FC4 to CentOS 5 will work nearly
flawlessly (You can find instructions on how to do this via YUM online).

Justice

On Tue, 2008-03-04 at 14:40 -0800, Francisco Paco Peralta wrote:
 I agree 110% and will start planning the upgrade.  I have to check if
 the cms I am running for my website (also on the server) has any
 issues with centos.  I was just trying to see if the was a quick way
 of addressing this issue, but I certainly don't want to create any
 more work for you folks.
 
 Ericwe shall be in touch.  Thank You,
 
 Eric Shubert [EMAIL PROTECTED] wrote:
 Since FC4 has reached its EOL, I'm inclined to think that we
 shouldn't add
 yet another version of unionfs to qtp-newmodel just to support
 that one
 obsolete kernel.
 
 Paco, you really should get off of the FC track and on to
 CentOS at some
 point. Then you won't run into this problem again. When you're
 ready to do
 so, contact me off list and we can discuss what it would take.
 Otherwise,
 you can continue to use the copied or linked sandbox to
 upgrade your toaster
 packages.
 
 Justice London wrote:
  Okay.. you managed to find the one release/kernel combo that
 would
  require another union module just for it. Is there any way
 you can
  simply upgrade the kernel release or fedora release? The fc4
 release
  hasn't been supported for over a year, which means no
 security updates
  or anything.
  
  Justice
  
  On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
  Hey, Paco. Nice to hear from you.
 
  Indeed your observation is correct (afaict). Justice would
 know best though
  regarding the unionfs. That's a bit of a complicated
 situation, as there are
  4 module/versions which provide that capability, each for
 various kernel
  versions. I suppose that we might not have the right
 module/version paired
  up with the right kernel in your case (kernel 2.6.17), but
 Justice would
  need to make that call.
 
  If Justice can't help to get this resolved, you can always
 use a linked or
  copied sandbox to do the upgrade.
 
  Please keep us posted.
 
  Francisco Paco Peralta wrote:
  Well, I tried the unioned sandbox method and it didn't
 seem to work for me.
 
  I appears I have an unsupported kernel (fc4 vintage). The
 logs mention
  that I can add some extra flags to the command but I am
 unsure of the
  impact or repercussions. Comments are welcome.
 
  I have pasted some text from my session, any assistance
 would be greatly
  appreciated.
 
 
 
 
 
 
  Would you like a unioned sandbox (quicker, smaller, maybe
 less stable)
  [y]/n: y
 
  Using union filesystem ...
  qtp-mount-sandbox v0.2.6
  --No existing unionfs12 found. Continuing with build
 process
  --Testing for valid rpm install tool:
  yum -y install found!
 
  --Searching for valid kernel source/devel to build
 unionfs12:
  kernel-devel-2.6.17-1.2142_FC4
  --Looking at current kernel
  --You have the kernel source for the running kernel!
 
  --Building
  mv: cannot stat `unionfs.ko': No such file or directory
 
  --Something went wrong with the unionfs12 build
  --Please check /var/log/unionfs-build.log to see what
 happened
  qtp-build-unionfs failed,ure. Exiting!
 
  qtp-newmodel - qtp-mount-sandbox failed, exiting
 
  --- Hit ENTER to return to menu ---
 
  **
  my logs are as follows:
 
  **
 
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk
 clean
  make[1]: Entering directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  CLEAN /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
  make[1]: Leaving directory
 `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  rm -f subr.o dentry.o file.o inode.o main.o super.o
 stale_inode.o
  branchman.o xattr.o rdstate.o copyup.o dirhelper.o
 rename.o unlink.o
  lookup.o persistent_inode.o commonfops.o 

Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-04 Thread Justice London
Okay.. you managed to find the one release/kernel combo that would
require another union module just for it.  Is there any way you can
simply upgrade the kernel release or fedora release?  The fc4 release
hasn't been supported for over a year, which means no security updates
or anything.

Justice

On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
 Hey, Paco. Nice to hear from you.
 
 Indeed your observation is correct (afaict). Justice would know best though
 regarding the unionfs. That's a bit of a complicated situation, as there are
 4 module/versions which provide that capability, each for various kernel
 versions. I suppose that we might not have the right module/version paired
 up with the right kernel in your case (kernel 2.6.17), but Justice would
 need to make that call.
 
 If Justice can't help to get this resolved, you can always use a linked or
 copied sandbox to do the upgrade.
 
 Please keep us posted.
 
 Francisco Paco Peralta wrote:
  Well, I tried the unioned sandbox method and it didn't seem to work for me.
  
  I appears I have an unsupported kernel (fc4 vintage).  The logs mention
  that I can add some extra flags to the command but I am unsure of the
  impact or repercussions.  Comments are welcome.
  
  I have pasted some text from my session, any assistance would be greatly
  appreciated.
  
  
  
  
  Would you like a unioned sandbox (quicker, smaller, maybe less stable)
  [y]/n: y
  
  Using union filesystem ...
  qtp-mount-sandbox v0.2.6
  --No existing unionfs12 found.  Continuing with build process
  --Testing for valid rpm install tool:
  yum -y install found!
  
  --Searching for valid kernel source/devel to build unionfs12:
  kernel-devel-2.6.17-1.2142_FC4
  --Looking at current kernel
  --You have the kernel source for the running kernel!
  
  --Building
  mv: cannot stat `unionfs.ko': No such file or directory
  
  --Something went wrong with the unionfs12 build
  --Please check /var/log/unionfs-build.log to see what happened
  qtp-build-unionfs failed,ure.  Exiting!
  
  qtp-newmodel - qtp-mount-sandbox failed, exiting
  
   --- Hit ENTER to return to menu ---
  
  **
  my logs are as follows:
  
  **
  
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
  FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
  make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
  make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o
  branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o
  lookup.o persistent_inode.o commonfops.o dirfops.o print.o
  malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~
  rm -f TAGS tags
  rm -f unionfs-1.2.tar.gz
  make -C utils clean
  make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
  rm -f unionctl uniondbg unionimap TAGS tags
  make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
  **
  If you have questions about or problems building Unionfs, please read
  INSTALL.
  **
  
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
  FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
  make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
  In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning
  You are compiling Unionfs on an unsupported kernel version.
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning
  To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning
  Try adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk
  make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1
  make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2
  make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  make: *** [unionfs.ko] Error 2
  
  ***
  
  
  Francisco Paco Peralta
 
 


-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-04 Thread Eric Shubert
Since FC4 has reached its EOL, I'm inclined to think that we shouldn't add
yet another version of unionfs to qtp-newmodel just to support that one
obsolete kernel.

Paco, you really should get off of the FC track and on to CentOS at some
point. Then you won't run into this problem again. When you're ready to do
so, contact me off list and we can discuss what it would take. Otherwise,
you can continue to use the copied or linked sandbox to upgrade your toaster
packages.

Justice London wrote:
 Okay.. you managed to find the one release/kernel combo that would
 require another union module just for it.  Is there any way you can
 simply upgrade the kernel release or fedora release?  The fc4 release
 hasn't been supported for over a year, which means no security updates
 or anything.
 
 Justice
 
 On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
 Hey, Paco. Nice to hear from you.

 Indeed your observation is correct (afaict). Justice would know best though
 regarding the unionfs. That's a bit of a complicated situation, as there are
 4 module/versions which provide that capability, each for various kernel
 versions. I suppose that we might not have the right module/version paired
 up with the right kernel in your case (kernel 2.6.17), but Justice would
 need to make that call.

 If Justice can't help to get this resolved, you can always use a linked or
 copied sandbox to do the upgrade.

 Please keep us posted.

 Francisco Paco Peralta wrote:
 Well, I tried the unioned sandbox method and it didn't seem to work for me.

 I appears I have an unsupported kernel (fc4 vintage).  The logs mention
 that I can add some extra flags to the command but I am unsure of the
 impact or repercussions.  Comments are welcome.

 I have pasted some text from my session, any assistance would be greatly
 appreciated.

 


 Would you like a unioned sandbox (quicker, smaller, maybe less stable)
 [y]/n: y

 Using union filesystem ...
 qtp-mount-sandbox v0.2.6
 --No existing unionfs12 found.  Continuing with build process
 --Testing for valid rpm install tool:
 yum -y install found!

 --Searching for valid kernel source/devel to build unionfs12:
 kernel-devel-2.6.17-1.2142_FC4
 --Looking at current kernel
 --You have the kernel source for the running kernel!

 --Building
 mv: cannot stat `unionfs.ko': No such file or directory

 --Something went wrong with the unionfs12 build
 --Please check /var/log/unionfs-build.log to see what happened
 qtp-build-unionfs failed,ure.  Exiting!

 qtp-newmodel - qtp-mount-sandbox failed, exiting

  --- Hit ENTER to return to menu ---

 **
 my logs are as follows:

 **

 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
 rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o
 branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o
 lookup.o persistent_inode.o commonfops.o dirfops.o print.o
 malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~
 rm -f TAGS tags
 rm -f unionfs-1.2.tar.gz
 make -C utils clean
 make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 rm -f unionctl uniondbg unionimap TAGS tags
 make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 **
 If you have questions about or problems building Unionfs, please read
 INSTALL.
 **

 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
 In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning
 You are compiling Unionfs on an unsupported kernel version.
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning
 To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning
 Try adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk
 make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1
 make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2
 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
 make: *** [unionfs.ko] Error 2

 

Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-04 Thread Francisco Paco Peralta
I agree 110% and will start planning the upgrade.  I have to check if the cms I 
am running for my website (also on the server) has any issues with centos.  I 
was just trying to see if the was a quick way of addressing this issue, but I 
certainly don't want to create any more work for you folks.

Ericwe shall be in touch.  Thank You,

Eric Shubert [EMAIL PROTECTED] wrote: Since FC4 has reached its EOL, I'm 
inclined to think that we shouldn't add
yet another version of unionfs to qtp-newmodel just to support that one
obsolete kernel.

Paco, you really should get off of the FC track and on to CentOS at some
point. Then you won't run into this problem again. When you're ready to do
so, contact me off list and we can discuss what it would take. Otherwise,
you can continue to use the copied or linked sandbox to upgrade your toaster
packages.

Justice London wrote:
 Okay.. you managed to find the one release/kernel combo that would
 require another union module just for it.  Is there any way you can
 simply upgrade the kernel release or fedora release?  The fc4 release
 hasn't been supported for over a year, which means no security updates
 or anything.
 
 Justice
 
 On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
 Hey, Paco. Nice to hear from you.

 Indeed your observation is correct (afaict). Justice would know best though
 regarding the unionfs. That's a bit of a complicated situation, as there are
 4 module/versions which provide that capability, each for various kernel
 versions. I suppose that we might not have the right module/version paired
 up with the right kernel in your case (kernel 2.6.17), but Justice would
 need to make that call.

 If Justice can't help to get this resolved, you can always use a linked or
 copied sandbox to do the upgrade.

 Please keep us posted.

 Francisco Paco Peralta wrote:
 Well, I tried the unioned sandbox method and it didn't seem to work for me.

 I appears I have an unsupported kernel (fc4 vintage).  The logs mention
 that I can add some extra flags to the command but I am unsure of the
 impact or repercussions.  Comments are welcome.

 I have pasted some text from my session, any assistance would be greatly
 appreciated.

 


 Would you like a unioned sandbox (quicker, smaller, maybe less stable)
 [y]/n: y

 Using union filesystem ...
 qtp-mount-sandbox v0.2.6
 --No existing unionfs12 found.  Continuing with build process
 --Testing for valid rpm install tool:
 yum -y install found!

 --Searching for valid kernel source/devel to build unionfs12:
 kernel-devel-2.6.17-1.2142_FC4
 --Looking at current kernel
 --You have the kernel source for the running kernel!

 --Building
 mv: cannot stat `unionfs.ko': No such file or directory

 --Something went wrong with the unionfs12 build
 --Please check /var/log/unionfs-build.log to see what happened
 qtp-build-unionfs failed,ure.  Exiting!

 qtp-newmodel - qtp-mount-sandbox failed, exiting

  --- Hit ENTER to return to menu ---

 **
 my logs are as follows:

 **

 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
 rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o
 branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o
 lookup.o persistent_inode.o commonfops.o dirfops.o print.o
 malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~
 rm -f TAGS tags
 rm -f unionfs-1.2.tar.gz
 make -C utils clean
 make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 rm -f unionctl uniondbg unionimap TAGS tags
 make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 **
 If you have questions about or problems building Unionfs, please read
 INSTALL.
 **

 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
 In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning
 You are compiling Unionfs on an unsupported kernel version.
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning
 To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
 

Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-03 Thread Eric Shubert
Hey, Paco. Nice to hear from you.

Indeed your observation is correct (afaict). Justice would know best though
regarding the unionfs. That's a bit of a complicated situation, as there are
4 module/versions which provide that capability, each for various kernel
versions. I suppose that we might not have the right module/version paired
up with the right kernel in your case (kernel 2.6.17), but Justice would
need to make that call.

If Justice can't help to get this resolved, you can always use a linked or
copied sandbox to do the upgrade.

Please keep us posted.

Francisco Paco Peralta wrote:
 Well, I tried the unioned sandbox method and it didn't seem to work for me.
 
 I appears I have an unsupported kernel (fc4 vintage).  The logs mention
 that I can add some extra flags to the command but I am unsure of the
 impact or repercussions.  Comments are welcome.
 
 I have pasted some text from my session, any assistance would be greatly
 appreciated.
 
 
 
 
 Would you like a unioned sandbox (quicker, smaller, maybe less stable)
 [y]/n: y
 
 Using union filesystem ...
 qtp-mount-sandbox v0.2.6
 --No existing unionfs12 found.  Continuing with build process
 --Testing for valid rpm install tool:
 yum -y install found!
 
 --Searching for valid kernel source/devel to build unionfs12:
 kernel-devel-2.6.17-1.2142_FC4
 --Looking at current kernel
 --You have the kernel source for the running kernel!
 
 --Building
 mv: cannot stat `unionfs.ko': No such file or directory
 
 --Something went wrong with the unionfs12 build
 --Please check /var/log/unionfs-build.log to see what happened
 qtp-build-unionfs failed,ure.  Exiting!
 
 qtp-newmodel - qtp-mount-sandbox failed, exiting
 
  --- Hit ENTER to return to menu ---
 
 **
 my logs are as follows:
 
 **
 
 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
 rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o
 branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o
 lookup.o persistent_inode.o commonfops.o dirfops.o print.o
 malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~
 rm -f TAGS tags
 rm -f unionfs-1.2.tar.gz
 make -C utils clean
 make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 rm -f unionctl uniondbg unionimap TAGS tags
 make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
 **
 If you have questions about or problems building Unionfs, please read
 INSTALL.
 **
 
 make -C /lib/modules/2.6.17-1.2142_FC4/build
 SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
 FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
 make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
   CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
 In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning
 You are compiling Unionfs on an unsupported kernel version.
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning
 To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
 /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning
 Try adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk
 make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1
 make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2
 make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
 make: *** [unionfs.ko] Error 2
 
 ***
 
 
 Francisco Paco Peralta


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] unionfs and fc4 trouble

2008-03-03 Thread Justice London
I should be able to take a look at this mid-week.

Justice

On Mon, 2008-03-03 at 09:34 -0700, Eric Shubert wrote:
 Hey, Paco. Nice to hear from you.
 
 Indeed your observation is correct (afaict). Justice would know best though
 regarding the unionfs. That's a bit of a complicated situation, as there are
 4 module/versions which provide that capability, each for various kernel
 versions. I suppose that we might not have the right module/version paired
 up with the right kernel in your case (kernel 2.6.17), but Justice would
 need to make that call.
 
 If Justice can't help to get this resolved, you can always use a linked or
 copied sandbox to do the upgrade.
 
 Please keep us posted.
 
 Francisco Paco Peralta wrote:
  Well, I tried the unioned sandbox method and it didn't seem to work for me.
  
  I appears I have an unsupported kernel (fc4 vintage).  The logs mention
  that I can add some extra flags to the command but I am unsure of the
  impact or repercussions.  Comments are welcome.
  
  I have pasted some text from my session, any assistance would be greatly
  appreciated.
  
  
  
  
  Would you like a unioned sandbox (quicker, smaller, maybe less stable)
  [y]/n: y
  
  Using union filesystem ...
  qtp-mount-sandbox v0.2.6
  --No existing unionfs12 found.  Continuing with build process
  --Testing for valid rpm install tool:
  yum -y install found!
  
  --Searching for valid kernel source/devel to build unionfs12:
  kernel-devel-2.6.17-1.2142_FC4
  --Looking at current kernel
  --You have the kernel source for the running kernel!
  
  --Building
  mv: cannot stat `unionfs.ko': No such file or directory
  
  --Something went wrong with the unionfs12 build
  --Please check /var/log/unionfs-build.log to see what happened
  qtp-build-unionfs failed,ure.  Exiting!
  
  qtp-newmodel - qtp-mount-sandbox failed, exiting
  
   --- Hit ENTER to return to menu ---
  
  **
  my logs are as follows:
  
  **
  
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
  FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
  make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
  make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o
  branchman.o xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o
  lookup.o persistent_inode.o commonfops.o dirfops.o print.o
  malloc_debug.o mmap.o unionfs.o unionfs.ko *.d .*.flags \#* *~
  rm -f TAGS tags
  rm -f unionfs-1.2.tar.gz
  make -C utils clean
  make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
  rm -f unionctl uniondbg unionimap TAGS tags
  make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
  **
  If you have questions about or problems building Unionfs, please read
  INSTALL.
  **
  
  make -C /lib/modules/2.6.17-1.2142_FC4/build
  SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2
  FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
  make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
  In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning
  You are compiling Unionfs on an unsupported kernel version.
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning
  To compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
  /opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning
  Try adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk
  make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1
  make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2
  make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  make: *** [unionfs.ko] Error 2
  
  ***
  
  
  Francisco Paco Peralta
 
 


-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[qmailtoaster] unionfs and fc4 trouble

2008-03-01 Thread Francisco Paco Peralta
Well, I tried the unioned sandbox method and it didn't seem to work for me. 

I appears I have an unsupported kernel (fc4 vintage).  The logs mention that I 
can add some extra flags to the command but I am unsure of the impact or 
repercussions.  Comments are welcome.

I have pasted some text from my session, any assistance would be greatly 
appreciated.




Would you like a unioned sandbox (quicker, smaller, maybe less stable) [y]/n: y

Using union filesystem ...
qtp-mount-sandbox v0.2.6
--No existing unionfs12 found.  Continuing with build process
--Testing for valid rpm install tool:
yum -y install found!

--Searching for valid kernel source/devel to build unionfs12:
kernel-devel-2.6.17-1.2142_FC4
--Looking at current kernel
--You have the kernel source for the running kernel!

--Building
mv: cannot stat `unionfs.ko': No such file or directory

--Something went wrong with the unionfs12 build
--Please check /var/log/unionfs-build.log to see what happened
qtp-build-unionfs failed,ure.  Exiting!

qtp-newmodel - qtp-mount-sandbox failed, exiting

 --- Hit ENTER to return to menu ---

**
my logs are as follows:

**

make -C /lib/modules/2.6.17-1.2142_FC4/build 
SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2 
FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk clean
make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  CLEAN   /opt/qmailtoaster-plus/src/unionfs-1.2/.tmp_versions
make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
rm -f subr.o dentry.o file.o inode.o main.o super.o stale_inode.o branchman.o 
xattr.o rdstate.o copyup.o dirhelper.o rename.o unlink.o lookup.o 
persistent_inode.o commonfops.o dirfops.o print.o malloc_debug.o mmap.o 
unionfs.o unionfs.ko *.d .*.flags \#* *~
rm -f TAGS tags
rm -f unionfs-1.2.tar.gz
make -C utils clean
make[1]: Entering directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
rm -f unionctl uniondbg unionimap TAGS tags
make[1]: Leaving directory `/opt/qmailtoaster-plus/src/unionfs-1.2/utils'
**
If you have questions about or problems building Unionfs, please read INSTALL.
**

make -C /lib/modules/2.6.17-1.2142_FC4/build 
SUBDIRS=/opt/qmailtoaster-plus/src/unionfs-1.2 
FISTDEVMK=/opt/qmailtoaster-plus/src/unionfs-1.2/fistdev.mk modules
make[1]: Entering directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
  CC [M]  /opt/qmailtoaster-plus/src/unionfs-1.2/subr.o
In file included from /opt/qmailtoaster-plus/src/unionfs-1.2/subr.c:22:
/opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:50:2: error: #warning You are 
compiling Unionfs on an unsupported kernel version.
/opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:51:2: error: #warning To 
compile Unionfs, you will need to define UNIONFS_UNSUPPORTED.
/opt/qmailtoaster-plus/src/unionfs-1.2/unionfs.h:52:2: error: #warning Try 
adding: EXTRACFLAGS=-DUNIONFS_UNSUPPORTED to fistdev.mk
make[2]: *** [/opt/qmailtoaster-plus/src/unionfs-1.2/subr.o] Error 1
make[1]: *** [_module_/opt/qmailtoaster-plus/src/unionfs-1.2] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2142_FC4-i686'
make: *** [unionfs.ko] Error 2

***


Francisco Paco Peralta