Menu
▾
▴
vectorlinux-devel — Vector Linux developer's list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(40) |
Apr
(76) |
May
(31) |
Jun
(39) |
Jul
(44) |
Aug
(87) |
Sep
(32) |
Oct
(23) |
Nov
(36) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(49) |
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(63) |
Aug
(95) |
Sep
(39) |
Oct
(61) |
Nov
(75) |
Dec
(118) |
| 2009 |
Jan
(25) |
Feb
(37) |
Mar
(20) |
Apr
(15) |
May
(14) |
Jun
(48) |
Jul
(82) |
Aug
(160) |
Sep
(94) |
Oct
(55) |
Nov
(59) |
Dec
(4) |
| 2010 |
Jan
(5) |
Feb
(17) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: M0E L. <m0...@gm...> - 2009-09-01 03:50:00
|
I was under the impression that the initrd did not need to be copied.. that it would be provided by vlconfig2 along with theming customizations and things of that sort. If it is not currently in vlconfig2, we need to supply something for the time being in case the themes are not ready yet. |
|
From: Newt <gen...@gm...> - 2009-09-01 00:01:01
|
Hello, Default installer that came with 1.19 (r752, I think). I don't know if this is any help at all but just in case it is. Running in debug mode I see: "MdlBootMngr.Get_Initrd_List.99: Looking for initrds in /mnt/sda1/boot" A quick listing of /mnt/sda1/boot reveals no files. Manually 'cp /mnt/source/isolinux/initrd.img /mnt/target/boot/initrd' works. Once the initrd image is in-place, lilo installs correctly to mbr and bootsector. Grub also installs correctly to mbr, and since installing grub to bootsector is highly suggested against doing, I would say that the bootloader installation seems to be working correctly. As M0E has already suggested, we just need to figure out why initrd is not being copied over correctly (if at all). Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 31, 2009, 3:10:54 PM, M0E wrote: ML> LILO keeps failing because we have an empty initrd in the target. ML> I'm not sure how or why this is happening, but doing ls -al ML> /mnt/target/boot clearly shows a 0 size for the initrd file. The 0 ML> initrd will report a "empty map section" error on the installer, ML> according to google, LILO produces this error when it tries to access ML> a referenced file with a 0 sector size. |
|
From: M0E L. <m0...@gm...> - 2009-08-31 21:11:07
|
Ok guys, I've managed to offer a way for the user to stay at the booloader configuration if it fails. Basically, if it fails, it will ask you wether to continue or not. click yes, moves on, click no, stays there to let you figure out the problem. On other notes, other things we need to figure out. LILO keeps failing because we have an empty initrd in the target. I'm not sure how or why this is happening, but doing ls -al /mnt/target/boot clearly shows a 0 size for the initrd file. The 0 initrd will report a "empty map section" error on the installer, according to google, LILO produces this error when it tries to access a referenced file with a 0 sector size. KDM Got tired of looking at the plain KDM login greeter last night, and I thought to myself, there has to be a way to make it show the face icons. And there is. The only problem is, we need to modify the kdmrc to make it look like this http://vlcore.vectorlinux.com/trac/vlcore/attachment/ticket/14/kdmrc Not sure what the best way to do this would be, but I'm thinking maybe rip the kdebase-workspace package apart and patch the file or something. After patching the file, kdm will show the uers login face icons on the greeter, just a little nice touch that means nothing, but is nice to have. .bash_profile Linking $USER/.bash_profile to $USER/.bashrc works for sourcing the .bashrc. Apparently KDE expects this file instead of the .bashrc, however, if linked, then when you open a termina, you get the prompt this prompt twice: Frequently used programs: Configuration : vasm Package manager: slapt-get, pkg Network tools : ifconfig, host, ping, nmap, iptables File manager : mc (press F2 for useful menu) Editor : mcedit, nano, vi Multimedia : alsamixer, play |
|
From: Masta M. <mas...@gm...> - 2009-08-30 03:34:58
|
Found the java issue to be a java directory with the jre files in it, and a symlink named jre_version-number pointing to that java directory. This is a bit backwards. I downloded latest jre and installed the jre_version-number directory and made a java symlink pointing to it, solved the pogo games issues. |
|
From: Newt <gen...@gm...> - 2009-08-29 04:55:13
|
Hello All,
Just an added bit of info:
During the install I resorted to manually installing the bootloaders in this fashion:
Lilo to /dev/sda (mbr)
grub to /dev/sda1 (partition bootsector)
...with the intentions of chainloading grub from lilo; primarily as a test to see
if it would be successful and it seems that it is. I am able to chain load grub
from lilo and continue to boot into the system.
First I had to chroot /mnt/target. Next, to get lilo installed I had to completely
remove the 'initrd=/boot/initrd' line from /etc/lilo.conf, and to get grub
installed to the bootsector I had to use the '--force' option (grub-install
--force /dev/sda1).
Cheers, newt
|
|
From: Newt <gen...@gm...> - 2009-08-29 04:39:40
|
Hello All, Noticed a few bootloader issues in the installer - submitted bug reports on these. And another minor 'text under running box' issue - also submitted. Otherwise the installer seems to be functional at this revision. It seems like the bootloader section is giving a run for our money. No worries, given time I'm sure we'll get it figured out and working correctly. First boot of installed system: wifi-radar service has always failed since I started testing soho, and still is. When all of the 'Starting such_and_such...' messages go by during boot, I notice that the 'starting slapt_update_notified_d' message begins with a lowercase 's' rather than a capital 'S' like all of the other 'Starting.....' messages. Totally minor, just an observation. Nepomuk strigi is awfully verbose on the first login to KDE. Told me three times it was indexing some files, and then several seconds later it told me how long it took to index said files. No harm though, just a chatty service. Ooo page color is back to white - yipee!! I prefer that to the grayish color is was before. Ooo styles, fonts, font size selection boxes are now showing the entire text rather than cropped on top and bottom - yipee!! Ooo Extension Manager is working again. I've never used it but it's working so now I can start :D I cannot determine if slapt-update-notifier-d is actually running or not. I don't see it listed in my processes, but maybe I just overlooked it. VasmCC/Utilities still give a fatal error - [-1] Unable to load image. Mfiles.?.0 Overall it seems to running pretty darn good. Great work to all!! Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Friday, August 28, 2009, 7:41:18 PM, you wrote: ua> new ISO's up ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.19.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.19-CD2.iso |
|
From: uel a. <ue...@gm...> - 2009-08-29 02:09:52
|
new ISO's up ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.19.iso ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.19-CD2.iso |
|
From: M0E L. <m0...@gm...> - 2009-08-28 18:22:09
|
Ok... So we are at A1.18 and I'm still having issues with my user accounts ~/.bashrc not being sourced. First effect of this is not being able to run gui apps when you su to root. I'm trying to add multi language support, and I noticed I'm setting up my variables correctly in ~/.bashrc, but the dang t hing doesn't get sources, so no effect whats so ever. I did an ugly quick hack to get this going for me ATM. in /etc/profile, at the very end of the file, there is an if statement, so I added a line there to make it look like this if [ ! "`id -u`" = "0" ]; then PATH="$PATH:." . /home/$USER/.bashrc fi That fixes the issue for me, and gives me interationalization support because the regional variables are set in ~/.bashrc Can you guys figure out how to fix this or use this fix for it or whatever... I just need it working |
|
From: John B <joh...@gm...> - 2009-08-28 02:22:42
|
The java-related problem is due to the fact that the JRE package is a very old one. We should really put the latest JRE in there - it will solve your problems with Pogo (I had similar problems with Yahoo games and found the latest JRE solved them). Cheers, John Masta MCF wrote: > Tested this today on another machine. Results: > Selected bootsplash-high and ended up with standard text bootup, > however on shut down, the graphical verbose screen is displayed. > > Lilo errors out with selecting "init" or "none", either choice gives > an error, and I didn't see any other option. > > Desktop Issues: > Desktop seems to work ok, but there is a problem with java in Firefox. > I could only get one game to actually load on pogo.com > <http://pogo.com>, most of the time the window would show up and stay > grey with nothing in it, sometimes the game window reported text at > the bottom saying applet done, but still no part of the game. Other > times it would just shut off the applet window. Thought maybe it was > server connection with pogo, but switched back to the original HD > installation and seems to run normal. > > Grub: > Doesn't let you change the displayed text during installer, > shows "Slackware...." but when the actual Grub menu comes on at > bootup, it shows "VectorLinux". If there will be no editing of the > menu's displayed text, why is it there? and Why say SLackware then > switch to saying VectorLinux? > Maybe confusing to fresh users. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > ------------------------------------------------------------------------ > > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Masta M. <mas...@gm...> - 2009-08-28 00:03:50
|
Tested this today on another machine. Results: Selected bootsplash-high and ended up with standard text bootup, however on shut down, the graphical verbose screen is displayed. Lilo errors out with selecting "init" or "none", either choice gives an error, and I didn't see any other option. Desktop Issues: Desktop seems to work ok, but there is a problem with java in Firefox. I could only get one game to actually load on pogo.com, most of the time the window would show up and stay grey with nothing in it, sometimes the game window reported text at the bottom saying applet done, but still no part of the game. Other times it would just shut off the applet window. Thought maybe it was server connection with pogo, but switched back to the original HD installation and seems to run normal. Grub: Doesn't let you change the displayed text during installer, shows "Slackware...." but when the actual Grub menu comes on at bootup, it shows "VectorLinux". If there will be no editing of the menu's displayed text, why is it there? and Why say SLackware then switch to saying VectorLinux? Maybe confusing to fresh users. |
|
From: M0E L. <m0...@gm...> - 2009-08-27 21:32:31
|
1.18 is up there... and new installer also. try the new ISO and update the installer in it by refreshing the svn branch in it. Thanks |
|
From: Sergey P. <fa...@gm...> - 2009-08-27 21:22:01
|
Hi, installing 117 now. Couldn't install LILO properly. The "Reboot" button on selecting services screen has transferred me to "details of your vectorlinux install". I pressed "Back" and pressed "Reboot" again and it succesfully rebooted. |
|
From: Newt <gen...@gm...> - 2009-08-27 17:46:32
|
Hello Uel, No 1.17 does not work with my nvidia/kvm box. I think the issue is more related to the X video driver (i.e. vesa) than anything else. I will try this system again tonight directly connected (i.e. no kvm) to see if there's any change. I also notice 1.18 is ready so I'll try that one tonight. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thursday, August 27, 2009, 10:43:34 AM, you wrote: ua> newt, ua> does this installer work with your nvidia/kvm box? |
|
From: uel a. <ue...@gm...> - 2009-08-27 16:43:45
|
newt, does this installer work with your nvidia/kvm box? On 8/27/09, Newt <gen...@gm...> wrote: > > Hello, > > Any relevant installer issues will be filed in vlcore bugs: > > >> -language, keyboard layout, mouse type screen is gone. I think it was a > nice addition. If it > >> can be added back that would be nice;. > >> > >> Bootloader: > >> The 'Saving Configuration...Please Wait' message only appears once > the bootloader has been > >> installed rather than the moment the button is clicked. The same is > true for the lower half > >> of the screen - it only disables once the bootloader is successfully > installed. This should > >> be adjusted because it's a nice informational message and indicates > something is happening. > >> > >> Bootloader: > >> Lilo Bootsplash Medium fails to install because it leaves the 'vga > =' line empty like that. > >> Maybe it should be 'vga = 788' (800x600 64k) > >> > >> Bootloader/Bootsector: > >> -bootloader lists correct bootsector (hda1), but fails to install > lilo or grub. > >> -The lilo failed message reads: "Unable to successfully install LILO > on" (seems either > >> incomplete or has the extra word 'on') > >> > >> LILO bootsector help: > >> I chrooted to /mnt/target and looked at lilo.conf after the failed > bootsector installation. > >> I contains an empty string where the boot device is specified (i.e. > 'boot ='). I tried > >> installing lilo with this and it gave an error at or above line > 7. I then removed that line > >> from lilo.conf and tried installing lilo again and it worked. I > don't know if this is the > >> proper fix but it works for installing to /dev/sda1. > >> > >> GRUB bootsector help: > >> I chrooted to /mnt/target. I attempted a 'grub-install /dev/sda' and > it completed with no error > >> reported. I then tried 'grub-install /dev/sda1' and it gave this > message: > >> grub-setup: warn: Attempting to install GRUB to a partition > instead of the MBR. This is a > >> BAD idea. > >> grub-setup: warn: Embedding is not possible. GRUB can only be > installed in this setup by > >> using blocklists. However, blocklists are > UNRELIABLE and its use is > >> discouraged. > >> grub-setup: error: If you really want blocklists, use --force. > >> I then tried a 'grub-install --force /dev/sda1' and it gave the same > 'warn' message but completed > >> successfully. > >> > >> -I ended up going with GRUB installed to bootsector and LILO installed > to MBR. I will attempt to > >> chainload them to test the GRUB installation. I've never tried > chainloading like this using lilo so > >> we'll see. > >> > >> Root password: > >> -Everything seems to be working correctly. I cannot bypass this. > AWESOME!! > >> > >> > >> First boot: > >> -No bootsplash - I see the scrolling text (tui) boot with black > background. > >> -wifi-radar service fails > > Cheers, newt > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Monday, August 24, 2009, 10:59:48 PM, you wrote: > > ua> New ISO's > ua> new kde pkgs > ua> new installer > ua> > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso > ua> > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso > > >> > >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso > ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso > > ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso > ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Newt <gen...@gm...> - 2009-08-27 16:32:38
|
Hello, Any relevant installer issues will be filed in vlcore bugs: >> -language, keyboard layout, mouse type screen is gone. I think it was a nice addition. If it >> can be added back that would be nice;. >> >> Bootloader: >> The 'Saving Configuration...Please Wait' message only appears once the bootloader has been >> installed rather than the moment the button is clicked. The same is true for the lower half >> of the screen - it only disables once the bootloader is successfully installed. This should >> be adjusted because it's a nice informational message and indicates something is happening. >> >> Bootloader: >> Lilo Bootsplash Medium fails to install because it leaves the 'vga =' line empty like that. >> Maybe it should be 'vga = 788' (800x600 64k) >> >> Bootloader/Bootsector: >> -bootloader lists correct bootsector (hda1), but fails to install lilo or grub. >> -The lilo failed message reads: "Unable to successfully install LILO on" (seems either >> incomplete or has the extra word 'on') >> >> LILO bootsector help: >> I chrooted to /mnt/target and looked at lilo.conf after the failed bootsector installation. >> I contains an empty string where the boot device is specified (i.e. 'boot ='). I tried >> installing lilo with this and it gave an error at or above line 7. I then removed that line >> from lilo.conf and tried installing lilo again and it worked. I don't know if this is the >> proper fix but it works for installing to /dev/sda1. >> >> GRUB bootsector help: >> I chrooted to /mnt/target. I attempted a 'grub-install /dev/sda' and it completed with no error >> reported. I then tried 'grub-install /dev/sda1' and it gave this message: >> grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a >> BAD idea. >> grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by >> using blocklists. However, blocklists are UNRELIABLE and its use is >> discouraged. >> grub-setup: error: If you really want blocklists, use --force. >> I then tried a 'grub-install --force /dev/sda1' and it gave the same 'warn' message but completed >> successfully. >> >> -I ended up going with GRUB installed to bootsector and LILO installed to MBR. I will attempt to >> chainload them to test the GRUB installation. I've never tried chainloading like this using lilo so >> we'll see. >> >> Root password: >> -Everything seems to be working correctly. I cannot bypass this. AWESOME!! >> >> >> First boot: >> -No bootsplash - I see the scrolling text (tui) boot with black background. >> -wifi-radar service fails Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 24, 2009, 10:59:48 PM, you wrote: ua> New ISO's ua> new kde pkgs ua> new installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso >> >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |
|
From: Newt <gen...@gm...> - 2009-08-26 17:52:14
|
Hello All, Just tested booting soho117alpha using new option and it worked perfectly - very nice! All boot options work over here in VM testing along with most menu options. I did not run through them all again, but they were working before and of the ones I tried again they worked. I have never tested the vlinstall, vlusb, vlmakiso, etc options so I cannot confirm that they ever worked. I'll try to give this a shot tonight in a virtual machine. Probe, autoprobe, and alternative autoprobe all provide scroll mouse functionality without any additional work on my part. Fantastic LIVE distro! Thanks to all involved for the hard work!! Just some general ideas and thoughts below: I wonder if the 'autoprobe' option would make the better default option (i.e. the first listed) followed by the 'vesa' option. I like the idea of users having scroll mouse functionality working without any additional effort. Also, I know I'm kind of unique in this aspect, but 'vesa' does not work with my Abit Siluro Nvidia Geforce FX5200 and the 'autoprobe' selects a working driver plus give me scroll wheel functionality. A few more seconds on the boot menu would be nice. Unless I'm reading really fast I can only get down to the third or fourth option before the time runs out. I know it's about finding a nice balance and 20 is probably too much but even 3-5 more seconds would help. At least it would give the user time to realize that their time is running out and to make a choice quickly. VGA=791 and VGA=normal boot options boot to TUI login, but nowhere is it mentioned what users actually exist on the system. Granted, everyone should expect 'root' to exist and it works but user 'vl' in not mentioned anywhere and since it's not an intuitive username I feel like it should be mentioned somewhere; perhaps above the password. Logging in as root and starting X brings up a red-background desktop which is to be expected, but having the user login as 'vl' and then starting X would provide a more desirable experience with the pretty background. Cheers, newt |
|
From: M0E L. <m0...@gm...> - 2009-08-26 14:29:19
|
STOP DO NOT BUILD ANOTHER ISO WITH MY 3RD KDE BUILD This build did not work at all. I ended up with a KDM screen, but I can't log in with either user account or root This has to be the PAM problem I have removed the package from the CHROOT and i'm building again without it I'll upload later on today and let you guys know when it's done On 8/26/09, uel archuletta <ue...@gm...> wrote: > The new boost package is here: > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/boost/boost-1.38.0-i586-3vl60.tlz > we should get it into next ISO with rebuilt kde and see if it causes any > problems > > > On Tue, Aug 25, 2009 at 10:18 AM, John B <joh...@gm...> wrote: > >> If the person who maintains the boost package for the VL repo is >> subscribed >> to this list, please rebuild the package that is in the repository, adding >> the patch from the Fedora bugtracker in the e-mail below. >> >> It is my understanding that Papa Slack will include the patch in the boost >> package that will be part of Slack13.0, so let's do the right thing. ;-) >> >> Thanks, >> John >> >> ---------- Forwarded message ---------- >> From: Rene Engelhard <re...@de...> >> Date: Sun, Aug 23, 2009 at 11:31 AM >> Subject: Re: [ooo-build] ooo-build-3.1.0.99.3 fails building sddll0.hxx >> To: ooo...@li... >> >> >> On Sun, Aug 23, 2009 at 08:49:34AM -0400, John B wrote: >> > I wonder whether other subscribers to this list have run into the same >> > error with boost 1.38, regardless of distro. If that's the case, then >> > there is a coding issue needing fixing. >> >> Yes. Inside boost. Since 1.37 >> https://bugzilla.redhat.com/show_bug.cgi?id=477131 >> >> Grüße/Regards, >> >> Rene >> -- >> .''`. René Engelhard -- Debian GNU/Linux Developer >> : :' : http://www.debian.org | >> http://people.debian.org/~rene/<http://people.debian.org/%7Erene/> >> `. `' re...@de... | GnuPG-Key ID: D03E3E70 >> `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 >> _______________________________________________ >> ooo-build mailing list >> ooo...@li... >> http://lists.freedesktop.org/mailman/listinfo/ooo-build >> >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Vectorlinux-devel mailing list >> Vec...@li... >> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel >> >> > |
|
From: uel a. <ue...@gm...> - 2009-08-26 13:14:18
|
The new boost package is here: ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/boost/boost-1.38.0-i586-3vl60.tlz we should get it into next ISO with rebuilt kde and see if it causes any problems On Tue, Aug 25, 2009 at 10:18 AM, John B <joh...@gm...> wrote: > If the person who maintains the boost package for the VL repo is subscribed > to this list, please rebuild the package that is in the repository, adding > the patch from the Fedora bugtracker in the e-mail below. > > It is my understanding that Papa Slack will include the patch in the boost > package that will be part of Slack13.0, so let's do the right thing. ;-) > > Thanks, > John > > ---------- Forwarded message ---------- > From: Rene Engelhard <re...@de...> > Date: Sun, Aug 23, 2009 at 11:31 AM > Subject: Re: [ooo-build] ooo-build-3.1.0.99.3 fails building sddll0.hxx > To: ooo...@li... > > > On Sun, Aug 23, 2009 at 08:49:34AM -0400, John B wrote: > > I wonder whether other subscribers to this list have run into the same > > error with boost 1.38, regardless of distro. If that's the case, then > > there is a coding issue needing fixing. > > Yes. Inside boost. Since 1.37 > https://bugzilla.redhat.com/show_bug.cgi?id=477131 > > Grüße/Regards, > > Rene > -- > .''`. René Engelhard -- Debian GNU/Linux Developer > : :' : http://www.debian.org | http://people.debian.org/~rene/<http://people.debian.org/%7Erene/> > `. `' re...@de... | GnuPG-Key ID: D03E3E70 > `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 > _______________________________________________ > ooo-build mailing list > ooo...@li... > http://lists.freedesktop.org/mailman/listinfo/ooo-build > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: Roy S. <nig...@ci...> - 2009-08-26 04:05:31
|
Alrighty guys. VL 6.0 Light LIVE final is here: http://vectorlinux.osuosl.org/veclinux-6.0/iso-release/VL6.0-Light-LIVE.iso md5sum 9a44c0de69f525178a2a48522945b1a3 VL6.0-Light-LIVE.iso The changes in this version are: Removed vlati Added an entry for booting previously installed VL (credits to Granny and those who helped her) Made acceptance of Opera EULA mandatory (thank you newt) Made xkill terminal window smaller (credit: pita) Changed default browser to Firefox I would like a final round of internal testing before official announcement. Your feedback is much appreciated, as always. Roy |
|
From: M0E L. <m0...@gm...> - 2009-08-25 19:31:08
|
Newt, our of curiosity, are you using xfs as a filesystem for your target / ? bootsector is not an option when you use xfs. On the other issues you're having, could you fill out bug reports at http://vlcore.vectorlinux.com/trac/vinstall please? These get lost in my quite populated inbox so I keep forgetting about them. If you do not have an account yet @ the installer devel page, you should sign up. |
|
From: Newt <gen...@gm...> - 2009-08-25 18:43:30
|
Hello All, Here are my notes on 1.17, install r733 (I think): >> Bootloader Installation: >> -The bootsector option is still only offering the bootsector of my /home (sda2) >> directory, rather than my / directory (sda1). Aside from that, the bootsector >> option fails to install. >> -I like the added message about clicking back to try again on a failed bootloader >> installation, however this message is only presented when Grub fails to install. >> If you could implement the same message when lilo fails then that should be >> sufficient. >> -When installing grub, even though it only shows one entry that will be added to >> the boot options it adds the 'recovery mode' boot option by default. Lilo does >> not do this and it would be nice if it did to give the user a way back into a TUI >> interface in case they borked their xorg/gui. >> -When clicking back after a failed installation the bootloader configuration >> screen is still frozen. The 'Saving Configuration...Please Wait' message is >> still display, and nothing below that message can be edited. However, the user >> CAN chose a different location to install the bootloader and switch between >> loaders so, effectively, the bootloader installation can still take place. It >> would be nice to have this screen reset to default when going back to it. >> >> System Administrator Account: >> -There's still some kind of wierdness going on with the 'Next' button. There >> are still instances where it will enable (or stay enabled) allowing the user to >> bypass root password creation. However, it's slightly different that before. >> Let's see if I can describe what I'm seeing: >> -User clicks 'next' from regional settings and gets to system administrator >> account page. The 'next' button initially disables for about 1/2 second, but >> then it enables and will stay enabled until the mouse is moved into the System >> Administrator Account region. You can however move you mouse along the >> horizontal lower button plane, up the process overview area, and across the >> vectorlinux banner and the 'next' button will stay enabled. I hope that all >> makes sense. >> >> First boot: >> -wifi-rader service fails to start (perhaps a conflict with another service? e.g. wicd) >> -VasmCC start, however when I simply click on 'UTILITIES' I get a fatal error: >> [-1]Unable to load image. Mfiles.?.0 >> -VasmCC - Filesystem/Bootloader only offers lilo - needs updated to include grub >> -VasmCC - ALSASound doesn't seem to do anything - or does it just take a really long time? >> -VasmCC - Hardware Config message cannot be read (the lower 3/4 is cut off) >> -VasmCC - SAMBA Networking - Should we start Samba SWAT? Yes. Failed, cannot start SWAT. >> -VasmCC - CUPS Printing - Same deal as Samba SWAT. Tries to start it but cannot - failed. >> -Ooo - Extension Manager problem persists Hope this helps. Again, mostly minor things. No show stoppers by any means, just some normal bugs - most are minor but a couple are bigger than that. Still a great release and speedy too (pun intended). Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 24, 2009, 10:59:48 PM, you wrote: ua> New ISO's ua> new kde pkgs ua> new installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso >> >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |
|
From: Newt <gen...@gm...> - 2009-08-25 17:12:01
|
Hello, Quote-Newt> "Overall a very good install with new problems. Hope this is useful." You must all think I'm a real as*. That is not what I meant to write. That sentence should have read: "Overall a very good install with _few_ problems. Hope this is useful." Damn, one mistyped letter changes the entire feel of the sentence. Sorry about that. Cheers, newt |
|
From: John B <joh...@gm...> - 2009-08-25 16:18:41
|
If the person who maintains the boost package for the VL repo is subscribed to this list, please rebuild the package that is in the repository, adding the patch from the Fedora bugtracker in the e-mail below. It is my understanding that Papa Slack will include the patch in the boost package that will be part of Slack13.0, so let's do the right thing. ;-) Thanks, John ---------- Forwarded message ---------- From: Rene Engelhard <re...@de...> Date: Sun, Aug 23, 2009 at 11:31 AM Subject: Re: [ooo-build] ooo-build-3.1.0.99.3 fails building sddll0.hxx To: ooo...@li... On Sun, Aug 23, 2009 at 08:49:34AM -0400, John B wrote: > I wonder whether other subscribers to this list have run into the same > error with boost 1.38, regardless of distro. If that's the case, then > there is a coding issue needing fixing. Yes. Inside boost. Since 1.37 https://bugzilla.redhat.com/show_bug.cgi?id=477131 Grüße/Regards, Rene -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/<http://people.debian.org/%7Erene/> `. `' re...@de... | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 _______________________________________________ ooo-build mailing list ooo...@li... http://lists.freedesktop.org/mailman/listinfo/ooo-build |
|
From: Roy S. <nig...@ci...> - 2009-08-25 14:06:33
|
On Tuesday 25 August 2009 01:38:46 Masta MCF wrote: > Tested this on the Saphire X550 Radeon card. There were errors during > installation of the fglrx driver. I suspected as much. ATI is going in the right direction with their drivers, but fglrx is still troublesome. I have one old Radeon 9500, which I did test, and it would not work for me either. My son modded and overclocked this card back in the days when it was the hot thing around, so I hesitated to blame the driver without further testing. If it needs tweaking and fiddling to get working, it's out of the LiveCD. Making final ISO now. |
|
From: Paul M. <pa...@wa...> - 2009-08-25 05:42:52
|
uel archuletta wrote: > New ISO's up: > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.16.iso > <ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.15.iso> > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.16-CD2.iso > <ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.15-CD2.iso> > > There is a delta for CD1 and CD2 is an exact copy of > VL6.0-SOHO-A1.15-CD2.iso so if you have that iso still you can save the > bandwidth and rename it. > > new QT new vasmCC hopefully found workaround for KVM? > > vectorlinux:$ md5sum VL6.0-SOHO-A1.16.iso > 36b4ac06d6c4b709285a2e069cc99e84 VL6.0-SOHO-A1.16.iso Install was fine. A few problems. First, screen resolution was completely off - running at 1024x768 instead of 1280x800. Looked _very_ strange.... Second, even though I selected the UK keyboard layout, it defaulted to US in both X and console. To correct the resolution problem, I had to run Vasm from init 3. That allowed me to get the correct resolution and correct the keyboard layout problem in X (haven't checked console yet). Fails to mount an NTFS formatted USB drive. Attempting to run VasmCC from the menu gets me a popup box with 'sorry, command /usr/bin/vasmCC not found'. Running from the command line gets me this: root:$ vasmCC gbr2: error while loading shared libraries: libgnuintl.so.8: cannot open shared object file: No such file or directory More later.... paul. |
14 messages has been excluded from this view by a project administrator.
