Re: [opensuse-factory] cryptsetup, some old, big and fat disks with encryption=twofish256, ...
Jochen Hayek wrote: > > Ludwig Nussel writes: > LN> When migrating util-linux to util-linux-ng the loop-AES patch got > dropped. > > Did anybody at SUSE consider the consequences of that for enterprise users? > > But maybe I was the only one making use of that. > > LN> The itercountk option was part of that patch. > > LN> As quick workaround to be able to access your data > LN> you can install util-linux (or just mount/losetup) from 10.2. > > LN> The plan is to not reintroduce the loop-AES patch > LN> (yast never offered to use any of it's options right?) > > You are most probably right in that yast did not explicitly offer those > options, > but it *did* generate fstab (resp. crypttab ?!?) entries making use of that. > That's how I got to such encryption schemes. > That was a couple of years ago ... You are right. I just checked 9.2, yast indeed does use itercountk=100 if one chooses to not mount the image on boot. Ie different parameters depending on whether /etc/fstab or /etc/cryptotab is used. That means we need to support an upgrade path without hacks. Thanks for pointing that out! > I did not suspect then, that wasn't a good idea. > > If I had had the vague idea then, > that I depended on a pretty "off-road" patch resp. encryption scheme, > that SUSE would drop one day around 2007 ... I don't intend to drop support for encryption schemes yast once offered. > Excuse me, but is LUKS also such a quite "off-road" patch, > that I should better not make myself dependent on?!? Noone knows. It's supported on most distros with unmodified tools so chances are good that you won't end up with unreadable images :-) > LN> and also to get rid of the loop_fish2 kernel module for 10.3 though. > > >> Shall I just forget twofish256 and migrate all my encrypted disks? > > LN> If that's an option four you > LN> it certainly makes sense to use a more secure on-disk format. > LN> 10.3 should still be able to read old images though. > LN> Therefore cryptsetup/dm-crypt do suppport the loop_fish2 format > (twofish-cbc-null) in factory already. > LN> What's missing atm is the ability to generate keys compatible with > the loop-AES patch. > > You mean, the ability to cope with such encryption schemes, > is that identical to generating such keys?!? The itercountk parameter does not affect the format of the data on the disk (twofish-cbc-null). It just specifies a different method (sha512+aes instead of just sha512) to compute the binary key used for encryption. > LN> Please file a bug and assign it to me, > > I am not sure, we will really end there, but ... maybe. > (I personally, I am already migrating my encrypted disks ...) Looks like you are a brave man since you already tried to use your crypted images on factory :-) So I'd be glad if you could keep you old images around and verify that the new method to access them actually works. > Under http://en.opensuse.org/Submitting_Bug_Reports > I can find a list of "How to ..." -- which one applies? I've filed Bug #270833 myself. You may add yourself to CC if you are iterested. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE Labs V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] /etc/init.d/boot.crypto , LUKS extension, unattached devices
Jochen Hayek wrote: > > Ludwig Nussel writes: > > LN> Jochen Hayek wrote: > > >> I prepare my /etc/crypttab and my /etc/fstab for quite a few different > external encrypted disks. > >> And I don't attach them all at the same time, esp. not at boot time. > > >> /etc/init.d/boot.crypto shouldn't bother attempting to mount disks, > >> that are not currently attached. > >> [...] > > LN> Most current boot.crypto from factory already skips devices that > don't exist. > > I had installed (upgraded) SUSE Linux 10.3 from CD-ROMs, > then I upgraded certain parts from SUSE Factory, > and ... > > $ rpm --query -f /etc/init.d/boot.crypto > aaa_base-10.1-41 > > > In aaa_base-10.3-29.i586.rpm (currently on SUSE Factory) : > > $ rpm2cpio aaa_base-10.3-29.i586.rpm | cpio -tv | fgrep crypt > 630 blocks > -rw-r--r-- 1 root root 1232 Apr 27 17:31 > ./var/adm/fillup-templates/sysconfig.boot.crypto > > 1st: I find it a little risky to upgrade esp. aaa_base. > > 2nd: I cannot find boot.crypto in that package, > so I cannot verify, what you're saying, > and I would at least like to have a look at the new code in boot.crypto. boot.crypto is now in the util-linux-crypto package as it entirely depends on cryptsetup. You also need to upgrade the kernel, the 10.2 one does not support the on disk format you need via dm-crypt. cu Ludwig -- (o_ Ludwig Nussel //\ SUSE Labs V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
* M9. ([EMAIL PROTECTED]) [20070502 18:22]: > > You can download the source and binary kit from our webpage > > www.3m.com/touch. Click on the Touch Drivers link and then click on > > Linux Touchware Drivers. The source and object kit can be downloaded > > from this page. I downloaded the .src.rpm (wrapped in a zip archive ...) and checked it. It does indeed contain binary-only parts so there is no way this can be made part of openSUSE. Philipp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp Thomas schreef: > I downloaded the .src.rpm (wrapped in a zip archive ...) and checked it. It > does indeed contain binary-only parts so there is no way this can be made > part of openSUSE. > > Philipp Made part of openSUSE...hmmm... I was thinking more as a part of hardware detection, hardwaredriver installation, itc: touchware. If it can be compiled into the kernel, why cann't this be done at installtime? (if a touchscreen is detected offcourse..) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: [EMAIL PROTECTED] Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGObi2X5/X5X6LpDgRAnfNAJ9NqKsgjPFUgpyUvBcVLC3X7ZvGmgCeJror 1AyzAcjwTwUdT00BkakVCfw= =LnO5 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
"M9." <[EMAIL PROTECTED]> writes:
> Philipp Thomas schreef:
>
>> I downloaded the .src.rpm (wrapped in a zip archive ...) and checked it. It
>> does indeed contain binary-only parts so there is no way this can be made
>> part of openSUSE.
>>
>> Philipp
>
> Made part of openSUSE...hmmm...
>
> I was thinking more as a part of hardware detection, hardwaredriver
> installation, itc: touchware.
> If it can be compiled into the kernel, why cann't this be done at
> installtime? (if a touchscreen is detected offcourse..)
Did you check it?
The source RPM contains no sources - it contains lots of binary stuff:
tar tvzf TWDrvSources.tgz
drwxr-xr-x root/root 0 2006-04-11 21:47:06 bin/
-rwxr-xr-x root/root 12166 2006-04-11 21:48:39 bin/MultiMonitorTool
-rwxr-xr-x root/root 35075 2006-04-11 21:48:40 bin/TwCalib
drwxr-xr-x root/root 0 2006-04-11 21:48:39 common/
-rw-r--r-- root/root 7677 2006-04-11 21:48:39 common/tw_ioctl.h
-rw-r--r-- root/root 1497 2006-04-11 21:48:39 common/TWEvents.h
drwxr-xr-x root/root 0 2006-04-11 21:47:06 controlXInput/
-rw-r--r-- root/root 6439 2006-04-11 21:45:12 controlXInput/controlXInput.c
-rw-r--r-- root/root 344 2006-04-11 21:45:12 controlXInput/makefile
drwxr-xr-x root/root 0 2006-04-11 21:47:04 daemon/
-rwxr-xr-x root/root 19587 2006-04-11 21:48:39 daemon/TWDrvStartup
-rwxr-xr-x root/root 554 2006-04-11 21:48:37 install
drwxr-xr-x root/root 0 2006-04-11 21:47:06 lib/
-rwxr-xr-x root/root 14131 2006-04-11 21:48:39 lib/libMultiMonitor.so
-rwxr-xr-x root/root 40709 2006-04-11 21:48:40 lib/libTwCaliblib.so
-rwxr-xr-x root/root461488 2006-04-11 21:48:40 lib/libTwGraphics.so
-rw-r--r-- root/root 5887 2006-04-11 21:48:39 License.txt
drwxr-xr-x root/root 0 2006-04-11 21:47:06 mmtool/
-rw-r--r-- root/root 838 2006-04-11 21:48:39 mmtool/Makefile
-rw-r--r-- root/root 1725 2006-04-11 21:48:39 mmtool/TwMMTool.h
-rw-r--r-- root/root 414 2006-04-11 21:48:39 mmtool/Tool.cpp
-rw-r--r-- root/root 11376 2006-04-11 21:48:39 Readme.txt
drwxr-xr-x root/root 0 2006-04-11 21:47:06 TWCalib/
-rw-r--r-- root/root 926 2006-04-11 21:48:40 TWCalib/Makefile
-rw-r--r-- root/root 1700 2006-04-11 21:48:40 TWCalib/TwCalib.h
-rw-r--r-- root/root 391 2006-04-11 21:48:40 TWCalib/Calib.cpp
drwxr-xr-x root/root 0 2006-04-11 21:48:39 TwDrvKit/
-rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save
-rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c
-rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h
-rw-r--r-- root/root 736 2006-04-11 21:48:39 TwDrvKit/Makefile24
-rw-r--r-- root/root 916 2006-04-11 21:48:39 TwDrvKit/Makefile26
-rw-r--r-- root/root 1031 2006-04-11 21:48:39 TwDrvKit/makefile
-rwxr-xr-x root/root 1993 2006-04-11 21:48:37 TWDrvStartup
-rwxr-xr-x root/root 5882 2006-04-11 21:48:37 TWXinputInstall.perl
drwxr-xr-x root/root 0 2006-04-11 21:48:21 Xfree4.0.3/
-rw-r--r-- root/root 10158 2006-04-11 21:47:57 Xfree4.0.3/TWXinput_drv.o
The kernel parts are:
-rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save
-rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c
-rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h
So, there's a common.o binary file. We will never add such a driver to
our kernel.
It even does have:
#ifdef MODULE_LICENSE
MODULE_LICENSE("Proprietary");
#endif
So, this is not GPL compatible.
Sorry, no way, 3M is not providing a real source RPM for their kernel
driver,
Andreas
--
Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
pgp710N4gZULV.pgp
Description: PGP signature
Re: [opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jaeger schreef:
> "M9." <[EMAIL PROTECTED]> writes:
>
>> Philipp Thomas schreef:
>>
>>> I downloaded the .src.rpm (wrapped in a zip archive ...) and checked it. It
>>> does indeed contain binary-only parts so there is no way this can be made
>>> part of openSUSE.
>>>
>>> Philipp
>> Made part of openSUSE...hmmm...
>>
>> I was thinking more as a part of hardware detection, hardwaredriver
>> installation, itc: touchware.
>> If it can be compiled into the kernel, why cann't this be done at
>> installtime? (if a touchscreen is detected offcourse..)
>
> Did you check it?
>
> The source RPM contains no sources - it contains lots of binary stuff:
>
> [snip...lots of binary stuff]
>
> So, there's a common.o binary file. We will never add such a driver to
> our kernel.
>
> It even does have:
> #ifdef MODULE_LICENSE
> MODULE_LICENSE("Proprietary");
> #endif
>
> So, this is not GPL compatible.
>
> Sorry, no way, 3M is not providing a real source RPM for their kernel
> driver,
>
> Andreas
At this spot i am a complete noob...
What should 3M do, to provide a 'real' GPL compatible driver?
- --
Have a nice day,
M9. Now, is the only time that exists.
OS: Linux 2.6.18.8-01-default x86_64
Huidige gebruiker: [EMAIL PROTECTED]
Systeem: openSUSE 10.2 (X86-64)
KDE: 3.5.5 "release 45.4"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGOdKIX5/X5X6LpDgRAusrAJ9ff1u0ad2YI5SY9ZNWu0gKwKdK5QCdFGQW
TjC9jHYRmfiLLwZcjHjUUaU=
=EUVn
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
"M9." <[EMAIL PROTECTED]> writes: > At this spot i am a complete noob... > What should 3M do, to provide a 'real' GPL compatible driver? Complete source code - including sources for common.o - and everything licensed under the GPL. And then they should get it into the official Linux kernel instead of maintaining there drop in driver, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpmsFrD64KKk.pgp Description: PGP signature
Re: [opensuse-factory] Re: Answer 3M about touchscreendrivers...(touchware)echo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jaeger schreef: > "M9." <[EMAIL PROTECTED]> writes: > >> At this spot i am a complete noob... >> What should 3M do, to provide a 'real' GPL compatible driver? > > Complete source code - including sources for common.o - and everything > licensed under the GPL. And then they should get it into the official > Linux kernel instead of maintaining there drop in driver, > > Andreas OK, now i understand your point, i will now try to contact 3M again, and 'rub' this under their noses, (as a matter of speaking..) - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: [EMAIL PROTECTED] Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOdfPX5/X5X6LpDgRAiWWAJ9wXrT9a8JyLUyUsbHWZCOp+jAv9gCfaDos UiZ6Tvw1fK+5Jn2LV/PxZFk= =u4K6 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Touchware-drivers under GPL.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Letter, as sent to 3M.
> Good Day,
>
> The way your driver is maintained, it can not be inserted into the
> openSUSE kernel.
>
>> The source RPM contains no sources - it contains lots of binary stuff:
>>
>> tar tvzf TWDrvSources.tgz
>> drwxr-xr-x root/root 0 2006-04-11 21:47:06 bin/
>> -rwxr-xr-x root/root 12166 2006-04-11 21:48:39 bin/MultiMonitorTool
>> -rwxr-xr-x root/root 35075 2006-04-11 21:48:40 bin/TwCalib
>> drwxr-xr-x root/root 0 2006-04-11 21:48:39 common/
>> -rw-r--r-- root/root 7677 2006-04-11 21:48:39 common/tw_ioctl.h
>> -rw-r--r-- root/root 1497 2006-04-11 21:48:39 common/TWEvents.h
>> drwxr-xr-x root/root 0 2006-04-11 21:47:06 controlXInput/
>> -rw-r--r-- root/root 6439 2006-04-11 21:45:12
>> controlXInput/controlXInput.c
>> -rw-r--r-- root/root 344 2006-04-11 21:45:12 controlXInput/makefile
>> drwxr-xr-x root/root 0 2006-04-11 21:47:04 daemon/
>> -rwxr-xr-x root/root 19587 2006-04-11 21:48:39 daemon/TWDrvStartup
>> -rwxr-xr-x root/root 554 2006-04-11 21:48:37 install
>> drwxr-xr-x root/root 0 2006-04-11 21:47:06 lib/
>> -rwxr-xr-x root/root 14131 2006-04-11 21:48:39 lib/libMultiMonitor.so
>> -rwxr-xr-x root/root 40709 2006-04-11 21:48:40 lib/libTwCaliblib.so
>> -rwxr-xr-x root/root461488 2006-04-11 21:48:40 lib/libTwGraphics.so
>> -rw-r--r-- root/root 5887 2006-04-11 21:48:39 License.txt
>> drwxr-xr-x root/root 0 2006-04-11 21:47:06 mmtool/
>> -rw-r--r-- root/root 838 2006-04-11 21:48:39 mmtool/Makefile
>> -rw-r--r-- root/root 1725 2006-04-11 21:48:39 mmtool/TwMMTool.h
>> -rw-r--r-- root/root 414 2006-04-11 21:48:39 mmtool/Tool.cpp
>> -rw-r--r-- root/root 11376 2006-04-11 21:48:39 Readme.txt
>> drwxr-xr-x root/root 0 2006-04-11 21:47:06 TWCalib/
>> -rw-r--r-- root/root 926 2006-04-11 21:48:40 TWCalib/Makefile
>> -rw-r--r-- root/root 1700 2006-04-11 21:48:40 TWCalib/TwCalib.h
>> -rw-r--r-- root/root 391 2006-04-11 21:48:40 TWCalib/Calib.cpp
>> drwxr-xr-x root/root 0 2006-04-11 21:48:39 TwDrvKit/
>> -rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save
>> -rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c
>> -rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h
>> -rw-r--r-- root/root 736 2006-04-11 21:48:39 TwDrvKit/Makefile24
>> -rw-r--r-- root/root 916 2006-04-11 21:48:39 TwDrvKit/Makefile26
>> -rw-r--r-- root/root 1031 2006-04-11 21:48:39 TwDrvKit/makefile
>> -rwxr-xr-x root/root 1993 2006-04-11 21:48:37 TWDrvStartup
>> -rwxr-xr-x root/root 5882 2006-04-11 21:48:37 TWXinputInstall.perl
>> drwxr-xr-x root/root 0 2006-04-11 21:48:21 Xfree4.0.3/
>> -rw-r--r-- root/root 10158 2006-04-11 21:47:57 Xfree4.0.3/TWXinput_drv.o
>>
>> The kernel parts are:
>> -rw-r--r-- root/root 16894 2006-04-11 21:48:39 TwDrvKit/common.o.save
>> -rw-r--r-- root/root 48754 2006-04-11 21:48:39 TwDrvKit/TWDriver.c
>> -rw-r--r-- root/root 8663 2006-04-11 21:48:39 TwDrvKit/TWDriver.h
>>
>> So, there's a common.o binary file. We will never add such a driver to
>> our kernel.
>>
>> It even does have:
>> #ifdef MODULE_LICENSE
>> MODULE_LICENSE("Proprietary");
>> #endif
>>
>> So, this is not GPL compatible.
>>
>> Sorry, no way, 3M is not providing a real source RPM for their kernel
>> driver,
>
>
> What should 3M do, to provide a 'real' GPL compatible driver?
>
>> Complete source code - including sources for common.o - and everything
>> licensed under the GPL. And then they should get it into the official
>> Linux kernel instead of maintaining there drop in driver.
>
>
>
>
> Greetings, Rob Verberne.
>
>
> 30-04-07 20:22, [EMAIL PROTECTED] , [EMAIL PROTECTED] writes:
>
>
> Good Afternoon:
>
> We do not have a binary touch driver for Suse 10.2 or 10.3, however we
> do offer a source and binary kit that can be used to install the driver.
> Since Linux has a vast numbers of versions available, 3M Touch Systems
> provides the source and object kit to allow users to build our package
> for many versions of Linux . However, with every different version of
> Linux, it is possible to encountert a situation where the kernel module
> will not build or will not load on a target system. When this occurs
> the customer is responsible for finding the issues that prevent the
> driver from building as we do not have the resources to investigate and
> troubleshoot the many variations of Linux and kernels.
>
> You can download the source and binary kit from our webpage
> www.3m.com/touch. Click on the Touch Drivers link and then click on
> Linux Touchware Drivers. The source and object kit can be downloaded
> from this page.
>
> Thank you, Technical Support
> 3M Touch Systems, Methuen
> 978-659-9200
- --
Have a nice day,
M9. Now, is the only time that exists.
OS: Linux 2.6.18.8-01-default x86_64
H
[opensuse-factory] ntfs-3g.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, http://www.ntfs-3g.org/index.html Is this also something for 10.3? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.18.8-01-default x86_64 Huidige gebruiker: [EMAIL PROTECTED] Systeem: openSUSE 10.2 (X86-64) KDE: 3.5.5 "release 45.4" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGOloOX5/X5X6LpDgRAgzwAJ4hmhYjOVAdWvOEug0+GAtpadBr+wCfU/wb zjDXO6V4fOji0YnBsqtIVA0= =Xj70 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] ntfs-3g.
On Thu, May 03, 2007 at 11:54:22PM +0200, M9. wrote: > Hello, > > http://www.ntfs-3g.org/index.html > > Is this also something for 10.3? If it is in the main kernel.org tree, yes. If not, go bug the developer to submit it there. Also, you can easily build a KMP for it if you want. thanks, greg k-h - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] ntfs-3g.
Greg KH escribió: > If it is in the main kernel.org tree, yes. greg.. did you actually read the page !? it is a userspace driver!! it cannot be in the kernel because is not a kernel module ;-P signature.asc Description: OpenPGP digital signature
Re: [opensuse-factory] ntfs-3g.
On Thu, May 03, 2007 at 07:31:58PM -0400, Cristian Rodriguez R. wrote: > Greg KH escribi?: > > > If it is in the main kernel.org tree, yes. > > greg.. did you actually read the page !? it is a userspace driver!! it > cannot be in the kernel because is not a kernel module ;-P Ah, my apologies, you are correct. I have no idea about non-kernel related things :) greg k-h - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] ntfs-3g.
On Friday 04 May 2007 02:36:29 am Greg KH wrote: > On Thu, May 03, 2007 at 07:31:58PM -0400, Cristian Rodriguez R. wrote: > > Greg KH escribi?: > > > If it is in the main kernel.org tree, yes. > > > > greg.. did you actually read the page !? it is a userspace driver!! it > > cannot be in the kernel because is not a kernel module ;-P > > Ah, my apologies, you are correct. > > I have no idea about non-kernel related things :) Yep, but you do give consistent answers :-) Because this is bug https://bugzilla.novell.com/show_bug.cgi?id=247750 and you said the same thing there. Understandable, because a FS in normally in the kernel. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
