vectorlinux-devel Mailing List for vectorlinux (Page 5)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Just installed it on my laptop.
Seems fine, I not sure that default wallpaper says "VectorLinux" though.

Other than that, it's good

Hey Everyone,
Proud to announce our first beta iso's are up and ready to test. We want to announce this on forum and Distrowatch but would like a few internal tests prior so if you could asap please!!!! Let us know if there are any show stoppers. The theme has been updated we have fixed reported bugs (Paul, sorry the uid situation is still there for your info) Please report back as soon as possible so we know if we have the green light to go public with this.
download links below:
ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-B1.iso
ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-B1-CD2.iso

Cheers,
vec

Robert Lange
vec...@ya...
http://www.vectorlinux.com

      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/

The installer has been completely rewritten. I don't think most users will
have this type of problem.  Every time I have tried this, has created all
kinds of problems for me.

On Oct 31, 2009 5:30 PM, "paul marwick" <pa...@wa...> wrote:

M0E Lnx wrote: > I will fix the installer to start the user count @ 1000,
however, > the installer h...
Thanks....

> In the case of a shared /home with other distros, this will prevent
problems.
It never did with the 6.0 installer. What has changed in that regard?

paul.
------------------------------------------------------------------------------
Come build w...

M0E Lnx wrote:
> I will fix the installer to start the user count @ 1000, however,
> the installer has to validate these uid's before creating the user account.

Thanks....

> In the case of a shared /home with other distros, this will prevent problems.

It never did with the 6.0 installer. What has changed in that regard?

paul.

I will fix the installer to start the user count @ 1000, however,
the installer has to validate these uid's before creating the user account.

In the case of a shared /home with other distros, this will prevent problems.

I think moe is working on fixing the GUI installer to start at  1000.
there are 2 ways currently change the UID of the first user to 1000:
1) create the user from vasm on first boot
2) on first boot, edit /etc/passwd, /etc/group and change the UID to 1000,
then chown -R 1000 /home/usrname, and chgrp -R 1000 /home/username

Uel

On Fri, Oct 30, 2009 at 2:28 PM, Paul Marwick <pa...@wa...> wrote:

> uel archuletta wrote:
> > paul,
> > do you have any directories in /home?
>
> :) I sure do. At the moment, my home partition has a user for Zenwalk, a
> user for VL6.0 standard, a user for VL5.9 standard, a user for Salix and
> a couple of leftovers which that I can't remember what they were for...
>
> > I remember talking about reserving UID's for home folders that were
> > found owned by UID's not in passwd, so if you imported a user they could
> > keep that dir and UID.
> > I am not sure if that is what is going on or not.
>
> I wondered about something like that, but didn't think the number being
> used made much sense if that was the case...
>
> I use a separate home partition. Since all the distributions I'm
> currently using start UIDs from 1000, I can then use a common area for
> documents, downloads, etc. Having SOHO assign 1002 breaks its ability to
> use the shared resources, which is a real pain....
>
> > is there a reason you are not importing old user?
>
> At the moment, mainly because I didn't want to carry over any problems
> from earlier alphas, and since the user accounts haven't been used much,
> it has been easier to simply use a new user account.
>
> Is there any way of forcing the correct UID? That would solve the
> problem for me, and I'm not sure how many others would find it as much
> of a stopper as I do. Though I do know a few people who do set things up
> in a similar manner.
>
> Regards, Paul.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

uel archuletta wrote:
> paul,
> do you have any directories in /home?

:) I sure do. At the moment, my home partition has a user for Zenwalk, a 
user for VL6.0 standard, a user for VL5.9 standard, a user for Salix and 
a couple of leftovers which that I can't remember what they were for...

> I remember talking about reserving UID's for home folders that were
> found owned by UID's not in passwd, so if you imported a user they could
> keep that dir and UID.
> I am not sure if that is what is going on or not.

I wondered about something like that, but didn't think the number being 
used made much sense if that was the case...

I use a separate home partition. Since all the distributions I'm 
currently using start UIDs from 1000, I can then use a common area for 
documents, downloads, etc. Having SOHO assign 1002 breaks its ability to 
use the shared resources, which is a real pain....

> is there a reason you are not importing old user?

At the moment, mainly because I didn't want to carry over any problems 
from earlier alphas, and since the user accounts haven't been used much, 
it has been easier to simply use a new user account.

Is there any way of forcing the correct UID? That would solve the 
problem for me, and I'm not sure how many others would find it as much 
of a stopper as I do. Though I do know a few people who do set things up 
in a similar manner.

Regards, Paul.

paul,
do you have any directories in /home?
I remember talking about reserving UID's for home folders that were found
owned by UID's not in passwd, so if you imported a user they could keep that
dir and UID.
I am not sure if that is what is going on or not.
is there a reason you are not importing old user?

Uel

On 10/30/09, Paul Marwick <pa...@wa...> wrote:
>
> Just installed.
>
> Install was fine. The installer came up much faster than it has in most
> of the other alphas. Also nice to see Seamonkey 2.0 installed.
>
> Other problems from 2.1 are not fixed. Console font is still not
> following selection made during install. VasmCC is cleaner, but still
> suffering from some video problems.
>
> The biggie for me is first user - this is still being set to UID 1002. I
> don't know whether this is an installer or base system problem, but it
> really needs to be fixed. For me, it makes SOHO effectively unusable.
>
> I still have to fiddle with the mixer to get sound working - use
> configure, go to the bottom of the list, tick the speaker box, then
> unmute it.
>
> paul.
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

Just installed.

Install was fine. The installer came up much faster than it has in most 
of the other alphas. Also nice to see Seamonkey 2.0 installed.

Other problems from 2.1 are not fixed. Console font is still not 
following selection made during install. VasmCC is cleaner, but still 
suffering from some video problems.

The biggie for me is first user - this is still being set to UID 1002. I 
don't know whether this is an installer or base system problem, but it 
really needs to be fixed. For me, it makes SOHO effectively unusable.

I still have to fiddle with the mixer to get sound working - use 
configure, go to the bottom of the list, tick the speaker box, then 
unmute it.

paul.

uel archuletta wrote:
> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A2.1.iso
> 6db2741885a7f01f91f3761879790fba  VL6.0-SOHO-A2.1.iso
> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A2.1-CD2.iso
> f54e51cb69d4240ae094d1ad31a5e762  VL6.0-SOHO-A2.1-CD2.iso

Downloaded and installed without problems.

> The primary reason for this release is preperation for a B1 public release.
> I think all the bugs that have been reported from A2 are fixed in this one.
> Let me know if I missed anything.

:( A few things....

First user on the system is now being added as UID 1002. This makes it 
almost unusable for me. Can we PLEASE go back to UID 1000 for first user?

Keyboard layout settings are set correctly (from the selection made 
during install) for X, but not for console.

In the KDE system settings/advanced section, anything that requires root 
access is greyed out, no option to enter root password to get access.

Seamonkey is offered as an install choice in the selective install, but 
is not installed.

The KDE powermanagement section reports problems, complaining that 
consolekit is not installed.

While I've been able to get the screen effects to work, I made the 
mistake of activating them, making a change to the settings and then 
clicking on 'apply'. That locked X up completely - had to use 
Ctrl-Alt-Bkspace to kill X and start again.

VasmCC has some video problems. See the attached images - the problem 
occurs after clicking on different selections from the left hand bar.

ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A2.1.iso
6db2741885a7f01f91f3761879790fba  VL6.0-SOHO-A2.1.iso
ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A2.1-CD2.iso
f54e51cb69d4240ae094d1ad31a5e762  VL6.0-SOHO-A2.1-CD2.iso

The primary reason for this release is preperation for a B1 public release.
I think all the bugs that have been reported from A2 are fixed in this one.
Let me know if I missed anything.

Thanks,
Uel

Hi John,
 Could you please provide me with an account to upload test packages of ghc
and Haskell platform for VL6.0 ?
they are very huge and it is very inconvenient to share through email or
external file sharing sites.

It would be great if the user name is cintyram or performance

Thank you
Cheers
Ram

Hello All,

Just some notes from an A2 test install:

Before installer:
-F1 (boot) menu could use updating - seems a little dated with the 'ide' option
-vxconf resolution selection now includes 1680x1050 - great!

Installer:
-still can reproduce the ISO fail to find media issue. I doubt that anyone will actually
 try the same sequence while using ISOs for install so the issue really is pretty minor
-the installer still shows 'fuseblk' for ntfs partitions if Gparted has been run; again,
 probably a minor issue. As far as I can tell, it does not affect functionality
-I did notice this time that my hsf+ partition shows up if gparted has not been run,
 however once gparted is run then it will not show up. Kind of relates to the 'fuseblk'
 issue mentioned above. Does not affect functionality of the installer.
-Development Crew changes took place when scroller was moved to main installer. Some
 observations are: there are extra spaces (top/bottom) around Vector/Moe/Uel (deservedly so),
 and stretchedthin was lost from the list. There may have been more changes that took
 place but these were items I could identify.
-My windows partition will still not boot from lilo entry, but I'm going to chalk it up
 as an issue related solely to my unique setup and hardware configuration. Unless anyone
 else has this same issue then I don't think it's worth investing much time into.

After Installation:
-post-install configuration: vxconf resolution does not include 1680x1050
-gambas2 is missing from kde menu
-gslapt, system upgrade, selects like 20 packages that are actually downgrades
 (i.e. lesser version numbers).

I think having the vxconf resolution options show up in order by first resolution size
would be a nice change. Perhaps just keep a top option of 'default (1024x768)' and then
the rest could go in order. It not a functional issue but an aesthetic one, and
certainly not a major one at that (just a convenience).

Cheers, newt

Actually, what you attached shows more of what happens when it scans
for CD media. Still fixed a typo there ;)

I believe your problem is going to be this

"ls: cannot access /mnt/sda1: Transport endpoint is not connected"

Can you try to manually mount your /dev/sda1 partition and see what happens?

I googled for that error, and a lot of interesting things came up.

http://www.google.com/linux?hl=en&q=Transport+endpoint+is+not+connected%22&btnG=Search

M0E,

I meant to send this yesterday with my other attachments but totally forgot.
Attached is the snippet from the Gambas2 Console showing what happens when the ISO
media finding fails (i.e. next, next, back, search again, search again). You can
see the sequence of events of searching for media and the final failure at the
end. Hope this helps.

The issue persists in A2 as well.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Monday, October 12, 2009, 2:58:20 PM, you wrote:

ML> I can't reproduce the ISO failure.
ML> I dont know which installer revision you tried, but I fixed an issue
ML> in this area this morning. r911 is up there and works for me. I'm
ML> unable to reproduce the issue using your instructions with this
ML> version. Hope this issue is gone ;)

Thanks for that explanation, Uel. I guess that settles it. It would essentially
take a person with advanced knowledge of the apple boot process and bootloaders in
order to even install VL along side osx, such that it would not be a concern
whether our installer identifies an osx system during the bootloader stage. That
means less work! :D

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Monday, October 12, 2009, 9:38:31 PM, you wrote:

ua> A "relatively novice osx user" could not even boot the VL install cdrom.
ua> Apple hardware has a "firmware" that loads the OS.
ua> Without replacing it you cant boot anything but an OSX HD or DVD.
ua> LILO/GRUB will not boot by itself at all.

ua> So to install VL on an intel mac you have to replace the firmware by
ua> installing REFIT, then use REFIT to boot the CDROM, and install VL.

ua> HTH,
ua> Uel

ua> On Mon, Oct 12, 2009 at 9:16 PM, Newt <gen...@gm...> wrote:

>> Hello,
>>
>> Uel: How does this affect a relatively novice osx user? Could they
>> accidentally
>> leave themselves without an easy way to boot back into osx using LILO?
>>
>> I'm just trying to determine if (for instance) lilo could leave someone
>> locked out
>> of osx without an easy way to fix the situation.
>>
>> Example: User installs VL on their mac for dual-booting. Installer does not
>> detect
>> osx partition. They choose LILO as the bootloader. Lilo installs
>> successfully with
>> only 'VL' and 'VL-cli' boot options. 1) Is this even possible on a mac?,
>> and 2) if
>> so, is it in our best interest to have our installer probe for and include
>> osx
>> partitions in the bootloader phase?
>>
>> Since you have the hardware I imagine you know the answer or can determine
>> it
>> pretty easily. This is probably not the most important issue but just
>> something
>> that came to mind a couple days ago.
>>
>> Cheers, newt
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>
>> Monday, October 12, 2009, 5:35:17 PM, you wrote:
>>
>> ua> 3 of my computers here are Intel macs. they do not have a BIOS, and
>> need
>> ua> something to load grub/lilo. REFIT works best for this IMO, and adds an
>> ua> option to boot OSX, so adding it to LILO or grub is redundant.
>>
>> ua> Grub will not install to any of the HD that are partitioned GPT without
>> the
>> ua> --force argument.
>>
>>
>>
>> ua> On Mon, Oct 12, 2009 at 4:19 PM, Newt <gen...@gm...> wrote:
>>
>> >> Hello,
>> >>
>> >> Thanks for the info on REFIt. It sounds like an interesting project
>> though
>> >> I'm not
>> >> sure I want to venture down that path at the present time.
>> >>
>> >> Personally, I'm not concerned with lilo automatically picking up my osx
>> >> installation as I can easily add it to lilo; plus, it's non-standard
>> >> implementation of osx for testing purposes. I was more thinking of other
>> >> standard
>> >> osx users who might end up "locked out" of their systems if a boot
>> option
>> >> is not
>> >> included by default.
>> >>
>> >> Then again, it's entirely possible that apple already has a forced
>> scenario
>> >> whereby a non-apple bootloader always comes second in the boot process
>> >> regardless
>> >> of user wants. Example: Perhaps efi always loads prior to mbr providing
>> >> options of
>> >> 'osx' and other bootloaders (lilo/grub/etc). This kind of scenario would
>> >> alleviate
>> >> any necessity to detect and provide a boot option for osx since apple
>> would
>> >> already have their users "protected". I don't have any true apple
>> hardware
>> >> so I
>> >> cannot say for sure.
>> >>
>> >> Cheers, newt
>> >>
>> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> >>
>> >> Monday, October 12, 2009, 3:36:29 PM, you wrote:
>> >>
>> >> JB> Moe and all,
>> >>
>> >> JB> Google may well be our friend on resolving Newt's problem in getting
>> >> his OS
>> >> JB> X entry to show in the LILO menu. The REFIt project on sf.net may
>> or
>> >> may not
>> >> JB> be helpful to Newt:
>> >>
>> >> JB> http://refit.sourceforge.net/ - rEFIt is a boot menu and
>> maintenance
>> >> toolkit
>> >> JB> for EFI <http://www.intel.com/technology/efi/>-based machines like
>> the
>> >> Intel
>> >> JB> Macs <http://www.apple.com/hardware/>. You can use it to boot
>> multiple
>> >> JB> operating systems easily, including triple-boot setups with Boot
>> Camp.
>> >> It
>> >> JB> also provides an easy way to enter and explore the EFI pre-boot
>> >> environment.
>> >>
>> >>
>> >>
>> >> JB> Cheers,
>> >> JB> John

A "relatively novice osx user" could not even boot the VL install cdrom.
Apple hardware has a "firmware" that loads the OS.
Without replacing it you cant boot anything but an OSX HD or DVD.
LILO/GRUB will not boot by itself at all.

So to install VL on an intel mac you have to replace the firmware by
installing REFIT, then use REFIT to boot the CDROM, and install VL.

HTH,
Uel

On Mon, Oct 12, 2009 at 9:16 PM, Newt <gen...@gm...> wrote:

> Hello,
>
> Uel: How does this affect a relatively novice osx user? Could they
> accidentally
> leave themselves without an easy way to boot back into osx using LILO?
>
> I'm just trying to determine if (for instance) lilo could leave someone
> locked out
> of osx without an easy way to fix the situation.
>
> Example: User installs VL on their mac for dual-booting. Installer does not
> detect
> osx partition. They choose LILO as the bootloader. Lilo installs
> successfully with
> only 'VL' and 'VL-cli' boot options. 1) Is this even possible on a mac?,
> and 2) if
> so, is it in our best interest to have our installer probe for and include
> osx
> partitions in the bootloader phase?
>
> Since you have the hardware I imagine you know the answer or can determine
> it
> pretty easily. This is probably not the most important issue but just
> something
> that came to mind a couple days ago.
>
> Cheers, newt
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> Monday, October 12, 2009, 5:35:17 PM, you wrote:
>
> ua> 3 of my computers here are Intel macs. they do not have a BIOS, and
> need
> ua> something to load grub/lilo. REFIT works best for this IMO, and adds an
> ua> option to boot OSX, so adding it to LILO or grub is redundant.
>
> ua> Grub will not install to any of the HD that are partitioned GPT without
> the
> ua> --force argument.
>
>
>
> ua> On Mon, Oct 12, 2009 at 4:19 PM, Newt <gen...@gm...> wrote:
>
> >> Hello,
> >>
> >> Thanks for the info on REFIt. It sounds like an interesting project
> though
> >> I'm not
> >> sure I want to venture down that path at the present time.
> >>
> >> Personally, I'm not concerned with lilo automatically picking up my osx
> >> installation as I can easily add it to lilo; plus, it's non-standard
> >> implementation of osx for testing purposes. I was more thinking of other
> >> standard
> >> osx users who might end up "locked out" of their systems if a boot
> option
> >> is not
> >> included by default.
> >>
> >> Then again, it's entirely possible that apple already has a forced
> scenario
> >> whereby a non-apple bootloader always comes second in the boot process
> >> regardless
> >> of user wants. Example: Perhaps efi always loads prior to mbr providing
> >> options of
> >> 'osx' and other bootloaders (lilo/grub/etc). This kind of scenario would
> >> alleviate
> >> any necessity to detect and provide a boot option for osx since apple
> would
> >> already have their users "protected". I don't have any true apple
> hardware
> >> so I
> >> cannot say for sure.
> >>
> >> Cheers, newt
> >>
> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >>
> >> Monday, October 12, 2009, 3:36:29 PM, you wrote:
> >>
> >> JB> Moe and all,
> >>
> >> JB> Google may well be our friend on resolving Newt's problem in getting
> >> his OS
> >> JB> X entry to show in the LILO menu. The REFIt project on sf.net may
> or
> >> may not
> >> JB> be helpful to Newt:
> >>
> >> JB> http://refit.sourceforge.net/ - rEFIt is a boot menu and
> maintenance
> >> toolkit
> >> JB> for EFI <http://www.intel.com/technology/efi/>-based machines like
> the
> >> Intel
> >> JB> Macs <http://www.apple.com/hardware/>. You can use it to boot
> multiple
> >> JB> operating systems easily, including triple-boot setups with Boot
> Camp.
> >> It
> >> JB> also provides an easy way to enter and explore the EFI pre-boot
> >> environment.
> >>
> >>
> >>
> >> JB> Cheers,
> >> JB> John
> >>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is the only developer event you need to attend this year. Jumpstart your
> >> developing skills, take BlackBerry mobile applications to market and
> stay
> >> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> Vectorlinux-devel mailing list
> >> Vec...@li...
> >> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
> >>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

Hello,

Uel: How does this affect a relatively novice osx user? Could they accidentally
leave themselves without an easy way to boot back into osx using LILO?

I'm just trying to determine if (for instance) lilo could leave someone locked out
of osx without an easy way to fix the situation.

Example: User installs VL on their mac for dual-booting. Installer does not detect
osx partition. They choose LILO as the bootloader. Lilo installs successfully with
only 'VL' and 'VL-cli' boot options. 1) Is this even possible on a mac?, and 2) if
so, is it in our best interest to have our installer probe for and include osx
partitions in the bootloader phase?

Since you have the hardware I imagine you know the answer or can determine it
pretty easily. This is probably not the most important issue but just something
that came to mind a couple days ago.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Monday, October 12, 2009, 5:35:17 PM, you wrote:

ua> 3 of my computers here are Intel macs. they do not have a BIOS, and need
ua> something to load grub/lilo. REFIT works best for this IMO, and adds an
ua> option to boot OSX, so adding it to LILO or grub is redundant.

ua> Grub will not install to any of the HD that are partitioned GPT without the
ua> --force argument.

ua> On Mon, Oct 12, 2009 at 4:19 PM, Newt <gen...@gm...> wrote:

>> Hello,
>>
>> Thanks for the info on REFIt. It sounds like an interesting project though
>> I'm not
>> sure I want to venture down that path at the present time.
>>
>> Personally, I'm not concerned with lilo automatically picking up my osx
>> installation as I can easily add it to lilo; plus, it's non-standard
>> implementation of osx for testing purposes. I was more thinking of other
>> standard
>> osx users who might end up "locked out" of their systems if a boot option
>> is not
>> included by default.
>>
>> Then again, it's entirely possible that apple already has a forced scenario
>> whereby a non-apple bootloader always comes second in the boot process
>> regardless
>> of user wants. Example: Perhaps efi always loads prior to mbr providing
>> options of
>> 'osx' and other bootloaders (lilo/grub/etc). This kind of scenario would
>> alleviate
>> any necessity to detect and provide a boot option for osx since apple would
>> already have their users "protected". I don't have any true apple hardware
>> so I
>> cannot say for sure.
>>
>> Cheers, newt
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>
>> Monday, October 12, 2009, 3:36:29 PM, you wrote:
>>
>> JB> Moe and all,
>>
>> JB> Google may well be our friend on resolving Newt's problem in getting
>> his OS
>> JB> X entry to show in the LILO menu. The REFIt project on sf.net may or
>> may not
>> JB> be helpful to Newt:
>>
>> JB> http://refit.sourceforge.net/ - rEFIt is a boot menu and maintenance
>> toolkit
>> JB> for EFI <http://www.intel.com/technology/efi/>-based machines like the
>> Intel
>> JB> Macs <http://www.apple.com/hardware/>. You can use it to boot multiple
>> JB> operating systems easily, including triple-boot setups with Boot Camp.
>> It
>> JB> also provides an easy way to enter and explore the EFI pre-boot
>> environment.
>>
>>
>>
>> JB> Cheers,
>> JB> John
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Vectorlinux-devel mailing list
>> Vec...@li...
>> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>>

Hello,

Attached is the lilo.conf that will not boot winxp (M0E requested). Everything
except for the last menu entry (osx) is generated by installer.

I am able to reproduce the ISO problem using the sequence that I mentioned before
and this is using r912 (next, next, back, search again, search again). Of course,
this is using the ISO install method (not virtualized cdroms, but actual isos).

I've attached an image with hopefully enough clarity to see the 'fuseblk'
identifier that's shown for ntfs drives. I was able to determine that this issue
crops up only after using Gparted. You don't actually need to do anything with
gparted but start it, exit it, and hit next to see ntfs show as fuseblk. The image
shows that the installs picks up 'fuseblk' but in terminal 'parted -l' shows ntfs.

I was able to use gparted to create a small ntfs partition without any problems.

I did a minimal install and these are just a few notes:
-no X installed
-no display manager
-chose lilo very high and ended up with lilo standard (black/white/red text)

Hope this is useful.

Cheers, newt
So what does this mean then? I guess not worth spending any time to try to
get this in line then

On Oct 12, 2009 6:35 PM, "uel archuletta" <ue...@gm...> wrote:

3 of my computers here are Intel macs. they do not have a BIOS, and need
something to load grub/lilo. REFIT works best for this IMO, and adds an
option to boot OSX, so adding it to LILO or grub is redundant.

Grub will not install to any of the HD that are partitioned GPT without the
--force argument.

On Mon, Oct 12, 2009 at 4:19 PM, Newt <gen...@gm...> wrote: > > Hello,
> > Thanks for the i...

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Vectorlinux-devel mailing list
Vec...@li...
https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel

3 of my computers here are Intel macs. they do not have a BIOS, and need
something to load grub/lilo. REFIT works best for this IMO, and adds an
option to boot OSX, so adding it to LILO or grub is redundant.

Grub will not install to any of the HD that are partitioned GPT without the
--force argument.

On Mon, Oct 12, 2009 at 4:19 PM, Newt <gen...@gm...> wrote:

> Hello,
>
> Thanks for the info on REFIt. It sounds like an interesting project though
> I'm not
> sure I want to venture down that path at the present time.
>
> Personally, I'm not concerned with lilo automatically picking up my osx
> installation as I can easily add it to lilo; plus, it's non-standard
> implementation of osx for testing purposes. I was more thinking of other
> standard
> osx users who might end up "locked out" of their systems if a boot option
> is not
> included by default.
>
> Then again, it's entirely possible that apple already has a forced scenario
> whereby a non-apple bootloader always comes second in the boot process
> regardless
> of user wants. Example: Perhaps efi always loads prior to mbr providing
> options of
> 'osx' and other bootloaders (lilo/grub/etc). This kind of scenario would
> alleviate
> any necessity to detect and provide a boot option for osx since apple would
> already have their users "protected". I don't have any true apple hardware
> so I
> cannot say for sure.
>
> Cheers, newt
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> Monday, October 12, 2009, 3:36:29 PM, you wrote:
>
> JB> Moe and all,
>
> JB> Google may well be our friend on resolving Newt's problem in getting
> his OS
> JB> X entry to show in the LILO menu. The REFIt project on sf.net may or
> may not
> JB> be helpful to Newt:
>
> JB> http://refit.sourceforge.net/ - rEFIt is a boot menu and maintenance
> toolkit
> JB> for EFI <http://www.intel.com/technology/efi/>-based machines like the
> Intel
> JB> Macs <http://www.apple.com/hardware/>. You can use it to boot multiple
> JB> operating systems easily, including triple-boot setups with Boot Camp.
> It
> JB> also provides an easy way to enter and explore the EFI pre-boot
> environment.
>
>
>
> JB> Cheers,
> JB> John
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

Hello,

Thanks for the info on REFIt. It sounds like an interesting project though I'm not
sure I want to venture down that path at the present time.

Personally, I'm not concerned with lilo automatically picking up my osx
installation as I can easily add it to lilo; plus, it's non-standard
implementation of osx for testing purposes. I was more thinking of other standard
osx users who might end up "locked out" of their systems if a boot option is not
included by default.

Then again, it's entirely possible that apple already has a forced scenario
whereby a non-apple bootloader always comes second in the boot process regardless
of user wants. Example: Perhaps efi always loads prior to mbr providing options of
'osx' and other bootloaders (lilo/grub/etc). This kind of scenario would alleviate
any necessity to detect and provide a boot option for osx since apple would
already have their users "protected". I don't have any true apple hardware so I
cannot say for sure.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Monday, October 12, 2009, 3:36:29 PM, you wrote:

JB> Moe and all,

JB> Google may well be our friend on resolving Newt's problem in getting his OS
JB> X entry to show in the LILO menu. The REFIt project on sf.net may or may not
JB> be helpful to Newt:

JB> http://refit.sourceforge.net/ - rEFIt is a boot menu and maintenance toolkit
JB> for EFI <http://www.intel.com/technology/efi/>-based machines like the Intel
JB> Macs <http://www.apple.com/hardware/>. You can use it to boot multiple
JB> operating systems easily, including triple-boot setups with Boot Camp. It
JB> also provides an easy way to enter and explore the EFI pre-boot environment.

JB> Cheers,
JB> John

Hello,

If we can't do anything in the osx area, it's fine by me. I was just coming at it
from the perspective of an apple osx user who might want to try installing VL
alongside their osx installation. I'm not even certain how lilo and/or grub might
install on true-apple hardware - it may not, in which case it would be left up to
the user to implement a boot option using osx tools. All in all, no worries on my
end. If we have any apple/osx users in the forum then perhaps trying to get them
to test an alpha or beta build could prove useful.

I'll get you a copy of my lilo.conf as soon as I can reboot. May take a few hours
though.

I was trying the most up-to-date installer which I believe was r912 - if not then
it was r911. Regardless, I'll give it another shot and see if I can reproduce the
issue. I'll let you know either way.

Thanks for the reasoning on why my ntfs show up as fuseblk. I'm going to see if
this same thing happens again on a new install. I have spare room on hda so I can
certainly try creating an ntfs partition on it. I'll let you know how it goes.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Monday, October 12, 2009, 2:58:20 PM, you wrote:

ML> I Presume this OSX thing is going to be a problem because of the fact
ML> the os-prober does not pick it up, and I'm afraid there is not much I
ML> can do in that area, as I dont own any mac software or hardware.

ML> My windows XP entry does work here though. Can you send me or post a
ML> copy of your lilo.conf to see what it came out with?

ML> I can't reproduce the ISO failure.
ML> I dont know which installer revision you tried, but I fixed an issue
ML> in this area this morning. r911 is up there and works for me. I'm
ML> unable to reproduce the issue using your instructions with this
ML> version. Hope this issue is gone ;)

ML> As for the partition listing, that is straight from parted. Whatever
ML> parted reports will be shown in the installer. The parted listings
ML> depend on the kernel modules, so I presume something with the fuse or
ML> ntfsprogs in the initrd are causing this behaviour. Might need to try
ML> to resize or create a ntfs partition with the current initrd (maybe
ML> gparted from the installer) to make sure everything is fine there.

ML> On 10/12/09, Newt <gen...@gm...> wrote:
>> Hello,
>>
>> Things are definitely getting better - not that they were bad before - but
>> they're
>> even better now!! Here's my list of little notes:
>>
>> During Install:
>> -Lilo installs correctly to bootsector with VL and WinXP (good job!!) (but
>> problems, see below)
>>      -OSX bootable partition is not detected
>>      -osprober and fdisk-l identify the partition as 'unknown'
>>      -parted-l identify the partition as 'hsf+'
>>      -I manually added an 'other' option to lilo.conf and it works correctly
>> -ISO 'Search Again' problem persists
>>      -try: next, next, back, search again, search again
>>      -Cannot find ISO after that
>> -Partition selection shows ntfs drives as 'fuseblk' (maybe by design?)
>>
>> After Install:
>> -Lilo cannot boot the WindowsXP boot entry
>>      -just sits at lilo message saying 'booting WindowsXP' with a cursor
>> below
>> -KDM starts/runs correctly with proprietary nvidia driver (good job!!)
>>      -the backdrop for KDM leaves black sides on widescreen 1400x900
>> -Analog clock issue will persist for small resolution screens (1024x768 and
>> below)
>>      -the clock will be out of viewable range at these lower resolution
>> screens
>> -KDE taskbar/panel could be configured as 'centered' and would look better
>> at
>>  resolutions higher than 1280. As it stands, the panel is left-aligned and
>> anything
>>  higher than 1280 wide leaves a gap on the right-hand side of the panel. I
>> think a
>>  "centered" config is more aesthetically pleasing (opinion of course).
>> -vburn-iso does not start and has no icon
>> -opera, wpa_gui, and browser have no icons
>>      -I noticed that opera.desktop points to wrong location for icon
>> (hicolor)
>> -Icons added to desktop from KDE menu show up different than existing icons.
>>      -maybe they are configured in 'desktop view' because they appear
>> over-top of
>>       existing icons and have the fly-out options. Plus, they can't be
>> drag/drop into
>>       trash with this configuration.
>>
>> Most of these points are pretty minor and don't actually affect
>> functionality. The
>> only major item on my list is the fact that WinXP would not start from the
>> lilo
>> menu option. During installation, I quickly glanced at the lilo entry and it
>> seemed correct but I wasn't paying a lot of attention to the winxp lilo
>> entry
>> (I'll have to have another look to confirm).
>>
>> It very well could be my boot setup. I'm trying to leave the sda mbr alone
>> (sda is
>> my first bootable device), as well as create the ability to boot directly
>> from
>> ISO, so I'm using various techniques to accomplish this. However, my feeling
>> is
>> that once LILO actually boots, my system should effectively be ignorant to
>> the
>> complex nature of my boot scenario (perhaps not??).
>>
>> sda_mbr: windows bootloader (boot.ini) with following options:
>>          -windowsxp (works)
>>          -osx (chainloads to sdc) (works)
>>          -grub4dos (boots grldr at sda1 root partition) (works)
>>
>> grub4dos with following options:
>>          -vector iso (located at sda1 root partition) (works)
>>          -lilo on hda1 (works)
>>
>> VectorLilo (hda1) options:
>>          -windowsxp (does not work)
>>          -vector-cli (untested, but likely works)
>>          -vector (works)
>>          -osx (works)
>>
>> Cheers, newt

Moe and all,

Google may well be our friend on resolving Newt's problem in getting his OS
X entry to show in the LILO menu. The REFIt project on sf.net may or may not
be helpful to Newt:

http://refit.sourceforge.net/ - rEFIt is a boot menu and maintenance toolkit
for EFI <http://www.intel.com/technology/efi/>-based machines like the Intel
Macs <http://www.apple.com/hardware/>. You can use it to boot multiple
operating systems easily, including triple-boot setups with Boot Camp. It
also provides an easy way to enter and explore the EFI pre-boot environment.

Cheers,
John

On Mon, Oct 12, 2009 at 4:58 PM, M0E Lnx <m0...@gm...> wrote:

> I Presume this OSX thing is going to be a problem because of the fact
> the os-prober does not pick it up, and I'm afraid there is not much I
> can do in that area, as I dont own any mac software or hardware.
>
> My windows XP entry does work here though. Can you send me or post a
> copy of your lilo.conf to see what it came out with?
>
> I can't reproduce the ISO failure.
> I dont know which installer revision you tried, but I fixed an issue
> in this area this morning. r911 is up there and works for me. I'm
> unable to reproduce the issue using your instructions with this
> version. Hope this issue is gone ;)
>
> As for the partition listing, that is straight from parted. Whatever
> parted reports will be shown in the installer. The parted listings
> depend on the kernel modules, so I presume something with the fuse or
> ntfsprogs in the initrd are causing this behaviour. Might need to try
> to resize or create a ntfs partition with the current initrd (maybe
> gparted from the installer) to make sure everything is fine there.
>
>
> On 10/12/09, Newt <gen...@gm...> wrote:
> > Hello,
> >
> > Things are definitely getting better - not that they were bad before -
> but
> > they're
> > even better now!! Here's my list of little notes:
> >
> > During Install:
> > -Lilo installs correctly to bootsector with VL and WinXP (good job!!)
> (but
> > problems, see below)
> >      -OSX bootable partition is not detected
> >      -osprober and fdisk-l identify the partition as 'unknown'
> >      -parted-l identify the partition as 'hsf+'
> >      -I manually added an 'other' option to lilo.conf and it works
> correctly
> > -ISO 'Search Again' problem persists
> >      -try: next, next, back, search again, search again
> >      -Cannot find ISO after that
> > -Partition selection shows ntfs drives as 'fuseblk' (maybe by design?)
> >
> > After Install:
> > -Lilo cannot boot the WindowsXP boot entry
> >      -just sits at lilo message saying 'booting WindowsXP' with a cursor
> > below
> > -KDM starts/runs correctly with proprietary nvidia driver (good job!!)
> >      -the backdrop for KDM leaves black sides on widescreen 1400x900
> > -Analog clock issue will persist for small resolution screens (1024x768
> and
> > below)
> >      -the clock will be out of viewable range at these lower resolution
> > screens
> > -KDE taskbar/panel could be configured as 'centered' and would look
> better
> > at
> >  resolutions higher than 1280. As it stands, the panel is left-aligned
> and
> > anything
> >  higher than 1280 wide leaves a gap on the right-hand side of the panel.
> I
> > think a
> >  "centered" config is more aesthetically pleasing (opinion of course).
> > -vburn-iso does not start and has no icon
> > -opera, wpa_gui, and browser have no icons
> >      -I noticed that opera.desktop points to wrong location for icon
> > (hicolor)
> > -Icons added to desktop from KDE menu show up different than existing
> icons.
> >      -maybe they are configured in 'desktop view' because they appear
> > over-top of
> >       existing icons and have the fly-out options. Plus, they can't be
> > drag/drop into
> >       trash with this configuration.
> >
> > Most of these points are pretty minor and don't actually affect
> > functionality. The
> > only major item on my list is the fact that WinXP would not start from
> the
> > lilo
> > menu option. During installation, I quickly glanced at the lilo entry and
> it
> > seemed correct but I wasn't paying a lot of attention to the winxp lilo
> > entry
> > (I'll have to have another look to confirm).
> >
> > It very well could be my boot setup. I'm trying to leave the sda mbr
> alone
> > (sda is
> > my first bootable device), as well as create the ability to boot directly
> > from
> > ISO, so I'm using various techniques to accomplish this. However, my
> feeling
> > is
> > that once LILO actually boots, my system should effectively be ignorant
> to
> > the
> > complex nature of my boot scenario (perhaps not??).
> >
> > sda_mbr: windows bootloader (boot.ini) with following options:
> >          -windowsxp (works)
> >          -osx (chainloads to sdc) (works)
> >          -grub4dos (boots grldr at sda1 root partition) (works)
> >
> > grub4dos with following options:
> >          -vector iso (located at sda1 root partition) (works)
> >          -lilo on hda1 (works)
> >
> > VectorLilo (hda1) options:
> >          -windowsxp (does not work)
> >          -vector-cli (untested, but likely works)
> >          -vector (works)
> >          -osx (works)
> >
> > Cheers, newt
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > Vectorlinux-devel mailing list
> > Vec...@li...
> > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
> >
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

I Presume this OSX thing is going to be a problem because of the fact
the os-prober does not pick it up, and I'm afraid there is not much I
can do in that area, as I dont own any mac software or hardware.

My windows XP entry does work here though. Can you send me or post a
copy of your lilo.conf to see what it came out with?

I can't reproduce the ISO failure.
I dont know which installer revision you tried, but I fixed an issue
in this area this morning. r911 is up there and works for me. I'm
unable to reproduce the issue using your instructions with this
version. Hope this issue is gone ;)

As for the partition listing, that is straight from parted. Whatever
parted reports will be shown in the installer. The parted listings
depend on the kernel modules, so I presume something with the fuse or
ntfsprogs in the initrd are causing this behaviour. Might need to try
to resize or create a ntfs partition with the current initrd (maybe
gparted from the installer) to make sure everything is fine there.

On 10/12/09, Newt <gen...@gm...> wrote:
> Hello,
>
> Things are definitely getting better - not that they were bad before - but
> they're
> even better now!! Here's my list of little notes:
>
> During Install:
> -Lilo installs correctly to bootsector with VL and WinXP (good job!!) (but
> problems, see below)
>      -OSX bootable partition is not detected
>      -osprober and fdisk-l identify the partition as 'unknown'
>      -parted-l identify the partition as 'hsf+'
>      -I manually added an 'other' option to lilo.conf and it works correctly
> -ISO 'Search Again' problem persists
>      -try: next, next, back, search again, search again
>      -Cannot find ISO after that
> -Partition selection shows ntfs drives as 'fuseblk' (maybe by design?)
>
> After Install:
> -Lilo cannot boot the WindowsXP boot entry
>      -just sits at lilo message saying 'booting WindowsXP' with a cursor
> below
> -KDM starts/runs correctly with proprietary nvidia driver (good job!!)
>      -the backdrop for KDM leaves black sides on widescreen 1400x900
> -Analog clock issue will persist for small resolution screens (1024x768 and
> below)
>      -the clock will be out of viewable range at these lower resolution
> screens
> -KDE taskbar/panel could be configured as 'centered' and would look better
> at
>  resolutions higher than 1280. As it stands, the panel is left-aligned and
> anything
>  higher than 1280 wide leaves a gap on the right-hand side of the panel. I
> think a
>  "centered" config is more aesthetically pleasing (opinion of course).
> -vburn-iso does not start and has no icon
> -opera, wpa_gui, and browser have no icons
>      -I noticed that opera.desktop points to wrong location for icon
> (hicolor)
> -Icons added to desktop from KDE menu show up different than existing icons.
>      -maybe they are configured in 'desktop view' because they appear
> over-top of
>       existing icons and have the fly-out options. Plus, they can't be
> drag/drop into
>       trash with this configuration.
>
> Most of these points are pretty minor and don't actually affect
> functionality. The
> only major item on my list is the fact that WinXP would not start from the
> lilo
> menu option. During installation, I quickly glanced at the lilo entry and it
> seemed correct but I wasn't paying a lot of attention to the winxp lilo
> entry
> (I'll have to have another look to confirm).
>
> It very well could be my boot setup. I'm trying to leave the sda mbr alone
> (sda is
> my first bootable device), as well as create the ability to boot directly
> from
> ISO, so I'm using various techniques to accomplish this. However, my feeling
> is
> that once LILO actually boots, my system should effectively be ignorant to
> the
> complex nature of my boot scenario (perhaps not??).
>
> sda_mbr: windows bootloader (boot.ini) with following options:
>          -windowsxp (works)
>          -osx (chainloads to sdc) (works)
>          -grub4dos (boots grldr at sda1 root partition) (works)
>
> grub4dos with following options:
>          -vector iso (located at sda1 root partition) (works)
>          -lilo on hda1 (works)
>
> VectorLilo (hda1) options:
>          -windowsxp (does not work)
>          -vector-cli (untested, but likely works)
>          -vector (works)
>          -osx (works)
>
> Cheers, newt
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

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)

vectorlinux-devel Mailing List for vectorlinux (Page 5)

vectorlinux-devel — Vector Linux developer's list