The build service on SuSe Studio worked fine 2 weeks ago, but now it doesn’t compress the image any more
when compiling / building an iso install or iso live disk.
So instead of generating a 3.7 gigabyte iso image file, it generates a 14 gigabyte iso image file that I can’t do anything with.
I already made sure that nfs, bzip, and gzip packages are selected and added in, however it still won’t generate a compressed image.
Which I didn’t have this problem when building a 64 bit gnome live disk about 3 weeks ago.
I am trying to make a custom 32 bit KDE install disk, since I heard that 64 bit Linux won’t work on Intel processors.
So I was going to make a 32 bit KDE install disk for compatibility reasons, since most everyone else seems to
use Intel instead of the AMD black processor that I use. And because some of the packages I want to add
are not available in 64 bit.
> I heard that 64 bit Linux won’t work on Intel processors.
I’d just like to set the record straight. The SLES 11 Deployment guide
states:
> 2.2.3 Hardware for AMD64 and Intel 64
>
> The AMD64 and Intel 64 architectures support the simple migration of
> x86 software to 64 bits. Like the x86 architecture, they constitute a
> value-for-money alternative.
>
> CPU
>
> All CPUs available on the market to date are supported. This
> includes dual-core CPUs.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
On 2013-09-14 03:56, Trinton88 wrote:
> I am trying to make a custom 32 bit KDE install disk, since I heard that
> 64 bit Linux won’t work on Intel processors.
Not true.
AFAIK, all current (intel) processors are 64 bits. You have to look up
the characteristics of your processor: whoever said that was probably
talking about 20 years ago.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
That stems from an excuse I heard 2 years ago about why someone couldn’t install Linux Mint 8 on an HP laptop computer.
So I had to see that for myself, so I had them bring the laptop over for me to work on and I couldn’t install Linux on it either
because as it turned out that that brand of laptop had a proprietary BIOS that would prevent booting from any CD or DVD ROM
that was not either Windows XP or Windows Vista install disk. Which only confirmed my opinions about computers bought
‘off the shelf’ being inferior and ‘hobbled’ as opposed to computers that were custom built from individual parts bought
online or at an electronics store being a superior product. Since big name computer manufacturers often use such
‘dirty tricks’ and produce their manufactured computers as cheaply as possible with planed obsolescence.
Insufficient or missing cooling fans and proprietary BIOS cause such ‘off the shelf’ computers to burn out
or otherwise become unusable after only 3 or 4 years, shortly after the warranty expires.
However I did not want to get drawn in to anything even remotely resembling a political discussion.
I custom built my own computer for maximum durability, and carefully selected parts that would
be as compatible with Linux as possible given the limitations of what I can afford, and what is
available locally.
Gigabyte 890FXA-UD5 motherboard, AMD Phenom II x6 1075T 3 GHz, Crucial 8 GB memory, Nvidia eGeForce 7100 GS, Lite on DVD writer drive.
The build service on SuSe Studio worked fine 2 weeks ago, but now it doesn’t compress the image any more
when compiling / building an iso install or iso live disk.
So instead of generating a 3.7 gigabyte iso image file, it generates a 14 gigabyte iso image file that I can’t do anything with.
I already made sure that nfs, bzip, and gzip packages are selected and added in, however it still won’t generate a compressed image.
So what other packages do I need to include besides ‘nfs client’, ‘Yast2 nfs client’, ‘unionfs’, ‘gzip’, ‘bzip’, ‘zip’, ‘lzma’
to get SuSe Studio to generate a compressed iso image that will fit on a 4 GB or 8 GB DVD-R disk ?
Another problem related to the iso compression problem is that I am getting double entries for ‘glibc’
this has me worried that the packages are not being selected properly.
When the upgrade to 13.1 happened, it cleared out the corrupted cache.
From now on I will be a lot more careful about the integrity of the files I upload.
From now on I will test them out on my own system first to watch for unusual behavior.
Just because the antivirus scan says that the file is ok doesn’t necessarily mean that it is.
As for the iso compression problem, I found out the hard way that nfs, fuse, and zisofs
have to be included along with all the compression formats in order for that to work.
