Linux and spice

[jasen]

Right, checking on linuxpackages.net reveals that this version of wine is
meant for 2.6 kernels and the error occurs if you run with a 2.4 kernel. So
you could upgrade to a 2.6 kernel or roll back wine far enough to be 2.4
kernel compatible. I run 2.4 kernel so I have to make this decision too.Not
sure which way to go yet.

I've not heard of any downsides to 2.6( vs 2.4), the pre-teens were a bit
flakey, but since then it's been good

 

[Jamie]

Ian Bell wrote:




Right, checking on linuxpackages.net reveals that this version of wine is
meant for 2.6 kernels and the error occurs if you run with a 2.4 kernel. So
you could upgrade to a 2.6 kernel or roll back wine far enough to be 2.4
kernel compatible. I run 2.4 kernel so I have to make this decision too.Not
sure which way to go yet.

Ian

isn't always best to work with the newest ?

 

[Helmut Sennewald]

isn't always best to work with the newest ?

Hello,

There is no reason not to upgrade to a Linux with version 2.6 kernel.
I tried LTspice and Wine with the latest Ubuntu, Suse and Mandrake
and it worked, even with the latest Wine version. OK, it was a few
months ago, but I assume it's still true.

Best regards,
Helmut

 

[Ian Bell]

I've not heard of any downsides to 2.6( vs 2.4), the pre-teens were a bit
flakey, but since then it's been good

cdrecord does not get on well with with 2.6 kernels for starters and for
seconds the 2.6 install procedure is a tad hand driven (not a problem as
such for slackers but just a tad annoying).

Ian

 

[Ian Bell]

isn't always best to work with the newest ?

Definitely not.

Ian

 

[Ian Bell]

Hello,

There is no reason not to upgrade to a Linux with version 2.6 kernel.
I tried LTspice and Wine with the latest Ubuntu, Suse and Mandrake
and it worked, even with the latest Wine version. OK, it was a few
months ago, but I assume it's still true.

Best regards,
Helmut

Hi Helmut,

Not sure what you are saying here as the latest Ubuntu, Suse and mandrake
all use 2.6 kernels. The default slackware kernel is still 2.4

Ian

 

[Joerg Schilling]

jasen wrote:

cdrecord does not get on well with with 2.6 kernels for starters and for
seconds the 2.6 install procedure is a tad hand driven (not a problem as
such for slackers but just a tad annoying).

Not really true:

Linux-2.6 did introduce an incompatible kernel interface change at the
time when cdrtools-2.01 were in code freeze state. Recent original cdrtools
versions from:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

work, but there is a lot of missinformation from uninformed people.

Old Linux versions have been safe and did require cdrecord to run as root.

Late Linux-2.4 and early Linux-2.6 versions did introduce a bug that allowed
non-root processes to send SCSI commands.

Instead of fixing this bug, a filter was introduced in the Linux kernel that
did allow some of the SCSI commands to be issued without root privs. This makes
uninformed people believe that cdrecord does not need root privs and the filter
list on the other side is still insecure and still allows non-root processes
(e.g. the backup admin) to gain root privileges.

 

[JeffM]

Not really true:
Linux-2.6 did introduce an incompatible kernel interface change
at the time when cdrtools-2.01 were in code freeze state.
Recent original cdrtools versions from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
work, but there is a lot of missinformation from uninformed people.

Is there anything here you'd like to change?
http://66.102.9.104/search?q=cache:...Mkisofs+where-the-author-claims-to-have-fixed

 

[Joerg Schilling]

Is there anything here you'd like to change?
http://66.102.9.104/search?q=cache:...Mkisofs+where-the-author-claims-to-have-fixed

Well, there is a need to change almost everything.

Don't trust Wikipedia...... if there are too many malicious
people, it seems to be impossible to keep correct information
and the Wikipedia admins do not help against these lyers :-(

Well, you may help me to correct the content ;-)

 

[Rich Grise]

If you want to keep a 2.4 kernel try the 9.2.0 version of wine from
linuxpackages.net. This does work but has a bug with some dialog boxes -
leaves them blank. The workaround is to minimise then maximise them and the
content is restored.

Thanks for this - this sounds like a lot less rigamarole than changing
my kernel!

Thanks,
Rich

 

[Ian Bell]

Thanks for this - this sounds like a lot less rigamarole than changing
my kernel!

Thanks,
Rich

My pleasure. There's a very friendly yahoo group for LTSpice - definitely
worth joining .

Ian

 

[Rich Grise]

My pleasure. There's a very friendly yahoo group for LTSpice - definitely
worth joining .

Ian

Oopps! Guess I spoke too soon - what exactly does "9.2.0 version" mean?
There's no Slack 9.2 link, and wine itself is only up to 0.9.33.

So, could you be any more specific?

Thanks,
Rich

 

[John Voltz]

ngspice is a very mature and usable program, there is no need to run
spice in wine. But if you must, try http://158.132.148.166/

Also, if you can still find a copy, CircuitMaker 2000 runs PERFECTLY in
wine.

 

[Ian Bell]

Oopps! Guess I spoke too soon - what exactly does "9.2.0 version" mean?
There's no Slack 9.2 link, and wine itself is only up to 0.9.33.

So, could you be any more specific?

I mean the 9.2.0 version of wine for slackware. Go to the download page for
wine page at sourceforge and scroll down to the slackware packages. The
last item listed is ' View older releases from the Slackware Packages
package »'. Click this link and again scroll down and you will find wine
version 9.2.0 listed. This is the one you want to download and install.

Hope that helps

Ian