VectorLinux
General Announcements => Distro Releases => Topic started by: uelsk8s on September 06, 2007, 09:40:57 am
-
The VectorLinux Development team would like to announce the availability of these 2 development releases.
http://vectorlinux.osuosl.org/veclinux-5.9/iso-test/VL5.9-Pseudo-1.iso
http://vectorlinux.osuosl.org/VL64-5.9/iso-test/VL5.9-Pseudo64-0.1.iso
The main purpose of these releases is to facilitate packagers in packaging for the 5.9/6.0 releases
Packages built from these systems should be submitted with the vl59 designation.
we have modified a version of CruxPorts4Slack that will help wth package building.
you can get it here: http://vectorlinux.osuosl.org/Uelsk8s/cruxports4slack-20061113-i586-1vl59.tlz
Those submitting packages must have also include a source dir with source tarball and build instructions
Also we recommend using "--with-included-gettext" with ./configure
Thanks,
Uelsk8s
-
Is that a 64-bit version ?! :o :o
-
Is that a 64-bit version ?! :o :o
Yes it is ;)
-
I can't wait to get my 64 bit box back from repair. I'll try that baby for sure!
-
So does this mean that Vector is now going to have four different versions? VL SOHO 32bit, VL SOHO 64bit, VL Standard 32bit, and VL Standard 64bit. Or is there just going to be one VL but with a 64bit version?
-
So does this mean that Vector is now going to have four different versions? VL SOHO 32bit, VL SOHO 64bit, VL Standard 32bit, and VL Standard 64bit. Or is there just going to be one VL but with a 64bit version?
Vector will have VL Standard 32bit, and VL SOHO 32bit. If the VL community decides there is enough value in having 64bit versions to build the packages we need, then there will be 64bit versions as well.
-
YIKES this thing is slow to install! :o
Can we back away from using the max compression level for LZMA, please? I mean, I sat here watching a font extract! These things should be flying by way too quick for me to even read.
-
YIKES this thing is slow to install! :o
Can we back away from using the max compression level for LZMA, please? I mean, I sat here watching a font extract! These things should be flying by way too quick for me to even read.
LZMA decompresses faster than BZIP or GZIP, by the way...
VL 5.8 also uses -9 compression on the files in the ISO image, did those decompress fast on your box?
-
Okay, Xorg 7.3 looks waaay too sweet! Is it going to be included in VL 6? Oh, BTW, I absolutely love the HAL support. It's soo nice to be able to stick a cd in the drive and have it auto mount. Of course there's a lot of other things that it does to.
-
I agree it's painfully slow, but I think it's because there aren't any bulk packages. They are all individual. I'm sure that will change later right?
-
Where can I find the md5 or sha1 for the 64 bit version? The 32 bit installed beautifully on my test box, but I cannot get the 64 bit past the "boot: " screen.
I want to check the next download to make sure it's not corrupted.
Thanks.
Bill
-
sorry
it is in the folder with the iso now
2fbc5fd4235116bcbc86ce11d30b1232 VL5.9-Pseudo64-0.1.iso
-
Thanks uelsk8s.
-
LZMA decompresses faster than BZIP or GZIP, by the way...
Uh, put down the crack pipe, it ain't remotely close to being as fast as gzip, let alone faster. Gzip is around 3x faster to decompress than LZMA (http://tukaani.org/lzma/benchmarks).
VL 5.8 also uses -9 compression on the files in the ISO image, did those decompress fast on your box?
No, but I think this one feels even more painful with the lack of a single large base archive.
-
Uh, put down the crack pipe, it ain't remotely close to being as fast as gzip, let alone faster. Gzip is around 3x faster to decompress than LZMA
My bad, its only bzip. Crack pipe...hmmmm...
Don't know if we are also using squashfs with this ISO, might have something to do with this...?
-
who cares about 1 hour or ten minutes, is not a race. All the development versions were slower than gold before, in my experience.
-
Don't know if we are also using squashfs with this ISO, might have something to do with this...?
Yeah, if we're using a compressed filesystem and LZMA, that's a rather bad idea. If so, whoever did that can put down the crack pipe too. :D
-
I LOVE this new toolchain! 30 packages built without a hitch :)
(VL5.9-Pseudo-1)
-
I LOVE this new toolchain! 30 packages built without a hitch :)
(VL5.9-Pseudo-1)
Strange, I'm having problems with lots of packages on that same system. I was going to update to the packager one as soon as I can and see if that makes a difference.
-
Imagemagick is not included. I see the slack sources on the server. Was this overlooked or should I build and submit one? This is a dep for at least 2 packages I'm working on.
Edit: I guess I'm asking if this was an oversight or do we build imagemagick? I don't want to build my packages against the incorrect imagmagick package.
Edit again: gnutls-1.6.2-i486-1 also missing. Ghostscript complained about it.
Edit yet again: Thanks for helping me resolve this in IRC uelsk8s and easuter :)
-
I LOVE this new toolchain! 30 packages built without a hitch
*sigh* spoke too soon. The iconv thing got me.
-
Sorry, why are we still using 1.0.11 alsa in this release? Shouldn't we move for .14?
-
Sorry, why are we still using 1.0.11 alsa in this release? Shouldn't we move for .14?
We sure should!
-
So does this mean that Vector is now going to have four different versions? VL SOHO 32bit, VL SOHO 64bit, VL Standard 32bit, and VL Standard 64bit. Or is there just going to be one VL but with a 64bit version?
Vector will have VL Standard 32bit, and VL SOHO 32bit. If the VL community decides there is enough value in having 64bit versions to build the packages we need, then there will be 64bit versions as well.
Ummm.... The whole point is that there is a significant number of people who won't even look at VL without a 64 bit version. Oh, and yeah, I'll be testing both 32- and 64- bit versions and hopefully packaging for both. ;D
-
Imagemagick is not included. I see the slack sources on the server. Was this overlooked or should I build and submit one? This is a dep for at least 2 packages I'm working on.
Edit: I guess I'm asking if this was an oversight or do we build imagemagick? I don't want to build my packages against the incorrect imagmagick package.
Edit again: gnutls-1.6.2-i486-1 also missing. Ghostscript complained about it.
Edit yet again: Thanks for helping me resolve this in IRC uelsk8s and easuter :)
i built imagemagick quite a while ago for the pseudo vec. ::)
-
Hi together,
first i want to say hello - i am new to this forum and VL.
I work with several slackbased distributions like slax, slamd64 and bluewhite64.
Now a friend told me about a VL 64-Bit (live) version.
So, if i am right there is only a developer 64-Bit version.
Do you plan a 64-Bit version for the near future or is this only a test?
64-Bit VL would be great!
-
Sorry, why are we still using 1.0.11 alsa in this release? Shouldn't we move for .14?
We sure should!
We are using alsa 1.0.14, it's just that the version shown in valsaconf script is 1.0.11. If you check in gslapt it's 1.0.14.
-
That is because there is a copy of alsaconf used for VASM. That script should also be updated. Really, an upgraded alsaconf CAN make the difference between a working soundcard and a dead one. I think it's called something like "valsaconf" in the same directory as most of the other vasm utilities. Can't check now, I'm in winDOS.
-
Anybody planning on building KDE soon? I've been doing some test building and have got arts and kdelibs compiled based on Slack 12's KDE src. (I guess Slackware 12's KDE would do until someone packages it, but ...)
-
I personally don't have windows on my machines, but when you install VL your windows will be detected and a proper lilo is setup. But please be aware that VL5.9 is NOT ready. It's just a VERY basic setup. It's mainly for packagers/developers to have a base to work off of, and advanced users to play around with.
You really should be using VL5.8 Standard/SOHO :)
But if you would like to try VL5.9x, be warned, it has quite a while to go before it's user friendly. It is usable, but plenty of things do not work at this time. And.... since it's so young, the install is painfully slow. So run setup, and go mow the lawn or something. :D
-
VectorLinux 5.9-Pseudo-2 is available for download here:http://vectorlinux.osuosl.org/veclinux-5.9/iso-test/VL5.9-Pseudo-2.iso
md5sum: b06ca07b4111f256f9c4e205a58f0b5c VL5.9-Pseudo-2.iso
a delta from 1 to 2 is availabe here: http://vectorlinux.osuosl.org/veclinux-5.9/iso-test/VL5.9-Pseudo-1to2.delta
md5sum: e4565aa1f3003ee7543dbdd0ce6d3717 VL5.9-Pseudo-1to2.delta
We are almost ready to release a beta at this point.
We just need a few more packages and a little more polish.
The packages submitted so far are looking real good.
There are 2 installers in this release. You can get to the second one by typing "linux2" at the boot prompt.
If someone has the time and a stopwatch, I would appreciate Knowing the time it take to install using both of them.
Thanks,
Uelsk8s
-
I could help if you like. I'm new here but just installing it twice and
writing down the time it takes sounds simple enough.
I'd like to help. I feel like giving something to the creator(s) of this
excellent operating system.
-
Well.. I installed VL 5.9 pseudo 2 using both install methods.
The default method (without the "linux2" boot command) was apparently an all-text option.
It showed white text on black backround without the blue boxes.
The install took 23 minutes. From the "Here we go" message to the "Installation done" message.
The other method (the linux2 option) was showing the blue-boxes like seen on
vector 5.8. The install took 39 minutes... that's 16 minutes more than the other option...
could this be right :D ? hopefully I didn't do anything wrong :D
I'd say (yeah.. like someone cares what I think :D ) definately go with the "text only" method if it really
is that much faster. It's not like the "blue-boxes" are providing much extra eye-cande or anything :D
And anyway.. If - by just disabling some eye-candy - something can be made faster... always do it :D
Some notes (could be useless.. just posting to make sure) :
- The first install option seemed to be doing something wrong... because at the end
it claimed it was installing package 431 of 428. Where as the linux2 method did not seem to do this.
- Also the "show boot image 640x480" option did not work after the first installation method.
- There were two shortcuts for "vector docs" when logging in as root on runlevel 4.
- There were a shortcut for "gaim" on the desktop when logging in as root on runlevel 4 (which did not seem to work...
it opened somekind of text document)
Well... hopefully I was of some help here. Or - atleast - did not harm anyone(/thing). :D
-
Zakhary,
Thats exactly what i was after.
Thanks,
Uelsk8s
-
I found a mistake with Pseudo-2 that should only affect those with SATA drives.
a fixed ISO is here here: http://vectorlinux.osuosl.org/veclinux-5.9/iso-test/VL5.9-Pseudo-2.1.iso
a delta from 2 to 2.1 is availabe here: http://vectorlinux.osuosl.org/veclinux-5.9/iso-test/VL5.9-Pseudo-2to2.1.delta
Sorry for any inconvenience this may have caused,
Uelsk8s
-
How is the next release (beta???) coming along? :D
Any news?
Can't wait for a brand new VL standard *drool* ....
-
Hi folks,
I'm a French user playing with VL from 5.1 (I still have it working on a 166 MHz Compaq laptop!). When I've seen a 64 bits version, even as a test, I couldn't let it and install it, for my pleasure, because I'm an advanced user, but no packager, programmer or coder. I'm agree that it should give such a version of VL, just like all the others big one, because today there is a lot of 64 bits CPU outside.
So does it help you people of the dev' team if I give some feedback? I can provide you my .log files, dmesg, hardware list or whatever you need to give a little help getting that baby up and running = : )
For the moment, here what's happened with a fresh install on a AMD 64 3700+ on Asus K8N mainboard with 1 Go DDR-1 Ram, on a SATA-1 HD:
- quick and easy install, like always. I didn't take a stopwatch, but I would say between 20 and 30 minutes.
- Xorg configured itself good with the free driver (no problem with 1600x1200) and then I could install the NVidia proprietary driver without trouble, with Direct Rendering activated (sorry if you are shocked = ; )
- the onboard LAN (nForce) was not recognized at install time, but then just after the first boot: I've put my fixed IP adress, Gateway, DNS and done!
- Flash Player is working "out-of-the-box" with sound, thanks nspluginwrapper.
Now the "problems" (that are surely easy to fix, I just installed yesterday and don't have searched the answers for now...):
- in dmesg "i2c_adapter i2c-2: SMBus Quick command not supported, can't probe for chips".
---> It appears two times one after the other.
- in Terminal "xmodmap: unable to open file '/home/fvj/.Xmodmap' for reading
xmodmap: 1 error encountered, aborting."
----> the same appears if I su to root (... '/root/.Xmodmap' ...)
- if I put a CD or USB stick, an icon appears on the Desktop, but if I try to open it (double- or right-click), I got the following error message:
"mount failed - Unable to mount "Disk":
A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file
(rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")"
---> But the manual mounting is working anyway...
So that's all I've noticed for now, but I will test (and enjoy) it further & deeper.
Greetings from France.
-
fvj,
hello, and welcome.
thanks for the feedback on the 64bit VL.
Work on 64bit is continuing but it lags behind 32bit.
there will be a 64bit VL released.
Thanks,
Uelsk8s
-
Bonjour Uelsk8s,
it's a pleasure to send feedback on VL, because it's speed, slim and somehow easy (or logical like mr. Spock would say = : )
I've found some topics on the forum about the real interest of 64 or 32 bits, the benchmarks, the loads, calculs and everything... Very interesting to think about if one really need it or it's just that the publicity of the companies who made us want it... Anyway, I'm too busy testing various Operating System to really work with my computer and to notice any improvement = ; )
But long life to VL 64 bits if it goes further, and when it can't, because nobody can do the job for 32 AND 64 at the same time, then better a good working 32, that's MHO.... But the community here look like full of good will and possibilities.
So if anybody has the trouble that I've had, "mount failed - Unable to mount "Disk":, here is the solution
http://www.linuxforums.org/forum/slackware-linux-help/97981-usb-flash-disk-mount-problem.html
Just put your user to the plugdev group in /etc/group et voila! Now CD, DVD and USB are mounting, unmounting and ejecting. A double-click mounts and opens Thunar, a right-click unmounts or ejects, as it should....
Now I will try to get the two others "problems" I have and keep you people informed.
Salut,
FvJ
-
Salut à tous,
here is how to get rid of the error messages:
- in Terminal "xmodmap: unable to open file '/home/fvj/.Xmodmap' for reading
xmodmap: 1 error encountered, aborting."
----> the same appears if I su to root (... '/root/.Xmodmap' ...)
I have understood that Xmodmap allows to make land specific keyboard map ( like here for a french one http://www.linux-france.org/article/nation/Xmodmap.fr-saratxaga.gz), is old and now deprecated!
It is true that, in /etc/X11/xorg.conf, Option "XkbLayout" "fr" does the job really good.
So, if we don't use it, we don't need it and, because it is the Terminal which complains about that file, I've had a look in the Bash configuration file, in /home/(user)/.bashrc and /root/.bashrc.
Bingo, we see :
#use custom keymap
xmodmap ~/.Xmodmap
so
#use custom keymap
#xmodmap ~/.Xmodmap
It's surely not a 64 bits VL problem, perhaps a VL 5.9, I don't know, but I can't remember having seen it in VL5.8 Standard Gold and Live CD VL5.8-Beryl...
Ok à la prochaine
FvJ
-
I redownloaded and reinstalled and could now get X running.
However, as on all slackware distros having a Davicom external eth card the Internet connection has to be fiddled first.
rmmod tulip
modprobe dmfe
blacklist tulip
set yes to use dhcp in rc.inet1.conf
and finally
rc.inet1 start
Is there no way in slacks that this would not be necessary? Fedora, DSL and Ubuntu do it right.
Further as reported in another post leaving X via logout or Ctrl-Alt-Backspace blanks the screen and the only keys working are Ctrl-Alt-Del to reboot. This happens as well in slackware-12 and the clones slax and absolute-linux based on slack 12. It does not happen in slack-11 and its clones.
-
I redownloaded and reinstalled and could now get X running.
Further as reported in another post leaving X via logout or Ctrl-Alt-Backspace blanks the screen and the only keys working are Ctrl-Alt-Del to reboot. This happens as well in slackware-12 and the clones slax and absolute-linux based on slack 12. It does not happen in slack-11 and its clones.
Unquote
This was now solved by upgrading all the x*/X* from the slackware current/x as Uelsk had suggested. Thank you!
And yes all works well in VL-5.9, adding my VL-5.8 home and usr/local partitions I would not even know where I am. Nothing hangs all programs working properly.
On installation, however, when the program vlati was coming-up for installation the system would freeze. Happened twice so I did not install it anymore.