Mailinglist Archive: opensuse-project (169 mails)
| < Previous | Next > |
Re: [opensuse-project] opensuse upgrade: newer, faster, worse
- From: Maciej Pilichowski <macias@xxxxxxxxxxxxxxxx>
- Date: Sun, 14 Oct 2007 14:05:57 +0200
- Message-id: <200710141405.57832.macias@xxxxxxxxxxxxxxxx>
Hello,
> Well, Novell doesn't have to know about this one since isn't in his
> bugzilla.
Yes, and it is quite new :-) I posted it in samba bugzilla, since
everytime where I am not sure where to post a report I am told to
post it at original bug tracking system.
> But looks like there are really a lot of complains about
> cifs.
You can tell by looking at google. Also there is a lengthy report at
novell bugzilla about dropping smbfs (and comparing it to other
distributions).
> Still I don't think "is unsupported" should be such a big problem
> when keeping a module while the new one matures, at least no in a
> case like this one where so much people complains. If no inside the
> kernel package, yes like a KMP in the OSS repository... perhaps
> making clear someway it is unsupported.
Yes, that would be great.
> Ok, this is a real problem, but it's a very particular case.
Of course I have only one router/printserver but I guess it is related
to whole family of those models.
> I
> don't think there are so much (if any) problems like this one.
> That's a bug that should be fixed by USRobotics,
Yes.
> but... I would
> understand if you didn't tried to ask them.
The other reporter tried -- "we don't support linux". Companies really
awkwardly react when I am asking for linux support (when I was about
to buy Plustek scanner I got the answer, but when I asked about
linux... silence :-)).
> Novell hasn't any
> procedure for cases like this one? If Novell asks USRobotics would
> help, or I'm expecting too much from USR?
Probably you are :-) but it would be really nice to do so. Users who
bought routers from USR would surely benefit from that.
have a nice day
bye
--
Maciej Pilichowski
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
> Well, Novell doesn't have to know about this one since isn't in his
> bugzilla.
Yes, and it is quite new :-) I posted it in samba bugzilla, since
everytime where I am not sure where to post a report I am told to
post it at original bug tracking system.
> But looks like there are really a lot of complains about
> cifs.
You can tell by looking at google. Also there is a lengthy report at
novell bugzilla about dropping smbfs (and comparing it to other
distributions).
> Still I don't think "is unsupported" should be such a big problem
> when keeping a module while the new one matures, at least no in a
> case like this one where so much people complains. If no inside the
> kernel package, yes like a KMP in the OSS repository... perhaps
> making clear someway it is unsupported.
Yes, that would be great.
> Ok, this is a real problem, but it's a very particular case.
Of course I have only one router/printserver but I guess it is related
to whole family of those models.
> I
> don't think there are so much (if any) problems like this one.
> That's a bug that should be fixed by USRobotics,
Yes.
> but... I would
> understand if you didn't tried to ask them.
The other reporter tried -- "we don't support linux". Companies really
awkwardly react when I am asking for linux support (when I was about
to buy Plustek scanner I got the answer, but when I asked about
linux... silence :-)).
> Novell hasn't any
> procedure for cases like this one? If Novell asks USRobotics would
> help, or I'm expecting too much from USR?
Probably you are :-) but it would be really nice to do so. Users who
bought routers from USR would surely benefit from that.
have a nice day
bye
--
Maciej Pilichowski
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |