I noticed this while i went through the install process on 11.1 Beta1
It may or may not be a big deal, but i found it slightly annoying:
If one tries to install on a hard drive that has a windows formatted
partition (either NTFS or FAT) even if windows is not installed,
openSUSE tries to install after the partition on the disk, I had a 24
GB FAT storage partition on the last 24 GB of my drive, and SUSE
wanted to install in the 10 or so GB that were unused at the end of
the drive. I had dedicated the first 2/3 of the drive as unformatted
space and ext3 space, but it would not recognize that partition to
install to. I had to move the storage partition to the start of the
drive in order not to wipe it.
Just my observations,
~mbaron
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
Hi, I have just noticed that there are more than 175 packages in the temporary factory that have versions lower than
11.0, is it safe to update yet or should I wait?
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
I downloaded the DVD via Ktorrent and verified the md5sum.
I am trying to install 11.1 Beta 1 onto a partition on my USB drive;
I've been successful in the past with 11.0.
My laptop is an HP dv9000z, which is in the same family as the dv6000,
although mine has an AMD X2 64bit CPU, and NVIDIA graphics.
When I attempt to boot off of the DVD, the installation program (v3.3.3)
starts, runs udev successfully, then says "loading basic drivers...",
and then sits there. I'm not sure how long I'm supposed to wait, but
5 minutes should have been long enough. I also attempted it with the
'noapic' boot flag, with the same result.
I realize that every laptop has its quirks, and in the past, I found that
stopping and starting the USB drive (to create an interrupt and wake
things up) seems to help. This time, I'm stumped.
Anyone have a suggestion about what to do, such as a boot-time argument?
I'm not sure what "broken modules" to ask it to skip, although I don't
think I'm even getting close enough to that part of the installation
for it to consider skipping any modules.
Thanks in advance,
Bayard, N1HO
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
Well I found the priority documentation at
http://en.opensuse.org/Bugs/Definitions#Bug_Severities, it seems quite
good, so further to below, I feel we should not be releasing a distro
with any outstanding job having a criticality over Normal. Obviously
there would be exceptions, but it seems that we do indeed release a
distro with 'Major' severity outstanding calls correct? So by proxy
that would be saying that we're OK releasing a distro that has "Major
loss of function"?
Q
>>> Quentin Jackson 09/23/08 11:28 AM >>>
Regarding the question below, "What do you propose to do for this?"
I think the following is true:
If a distribution has bugs of a major or annoying nature etc it will
either be because of resource, time or management or resource and time
(and possibly more than one of those). I expect there is nothing we can
do about the quantitiy of the resources we have, at least nothing we can
count on, we also cannot make people spend a certain amount of time on
something even though we do have to have deadlines. What we probably
can do is look at the time we need to get a quality distribution out
based on past experiences. But, before we can do that, we need to
define what quality is.
Once we've defined what quality is, we probably need to look at our
priorities, ie Blocker, Major, Critical etc and clearly define what type
of faults fit into each of these categories and what bug categories will
be allowed to remain unresolved at go-live time. Someone (more than
one) needs to be assigned to recategorise these bugs to where they need
to be (especially but not limited to times nearer to go-live) to avoid
the inevitable customer logging something incorrectly.
My feeling is that we may need to decrease the frequency of which a
distro is released in order to maintain this quality, for the work that
is done, 6 months is fast!
What do you think? Along the right track? How much of this is already
in place?
Thanks,
Q
>>> Andreas Jaeger <aj(a)suse.de> 09/17/08 7:59 PM >>>
"Quentin Jackson" <Quentin.Jackson(a)exclamation.co.nz> writes:
> I think we all agree SLE is for the enterprise, hence it's name, and
> you are bang on regarding hardware support, Novell have 90% of the
> solution right, but when your wireless card won't run it kinda makes
> it impossible to continue if you rely on it. Obviously I don't expect
> every flavour to be supported for the enterprise but..... Novell could
> support the big brand corporate/workstation models via vendor
> agreement to maintain a loyal customer base of their target market -
> corporates! Who wants an OS that might not work in a few months when
> your company is forced to change hardware due to EOL? Only those
> really trying to say something with Open Source I expect which is not
> whom we're trying to bring over.
Speaking about your hardware example: We have backported to SLED10 SP2
many wireless drivers.
> I wanted to Beta test SLE 11 as I'd like to go back to it and be able
to recommend it to the enterprise again, but they turned me down, odd
considering how much more pro-active I was in selling their software
than any other vendor in NZ. Oh well, that's Novell I suppose. No
wonder all their offices here have closed down.
Our partner betas can only take a limited number of users. It might be
that the person doing the decision did not know about your experience.
> But back on topic :) My question re OpenSuSE is not to suggest that it
> should run in the enterprise but that it will run in the home /
> enthusiest market, which then if stable could potentially be used in
> business if it got a good name for itself. If it doesn't achieve
> this, what's the point of the distro? Presently as I'm sure everyone
> here is aware, we never know exactly how good an OpenSuSE release is
> until we uninstall our current one, format, install, re-install etc
> which is a major pain so unfortunatley we can't trust that things will
> work as we would like. In my opinino this is a major probe> truly serious about OpenSuSE if we can't trust that there's been a
> regulated effort to get found bugs / problems out.
What do you propose to do for this?
> For example, what's our philosophy on allowing a version to be
> released with a network manager that doesn't work properly such as
> OpenSuSE 11.0? I know it would have delayed the release to get that
> right, but what's the cost of not getting it right? It seems to me we
> may end up getting a bad rep and be setting the wrong example if
> things like that continue to happen. I even heard one of the Novell
> guys say one time that the whole reason SLE 10 was delayed so much was
> to get theOpenSuSE bugs out since it's made from the same code
The way you state it is bullshit. ;-)
SLE10 was late because of the package stack and some other areas,
openSUSE was hurt by it the same way and not the reason.
> initially. So I guess the question is can we afford to have such a
> rigid release cycle such as what we currently do and what justifies an
> extension? Do we need to re-address some of the rules about releases
> and their schedules? Perhaps this is what is happening right now with
> the delay of 11.1 alpha 3? Do we have a philosophy stating we are not
> so concerned about this stuff as we are an enthusiast distro?
Alpha3 was not delayed, it was cancelled since it was uninstallable.
> Lots of questions, it would be great to get some answers. :)
Andreas
--
Andreas Jaeger, Director Platform / openSUSE, aj(a)suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
Greetings,
I have not been able to get the beta up and running. When at the step of
installing and setting up grub I get a grub failure message every time.
Is anyone else seeing this and is there a workaround?
thank you
Mark Corbin Toshiba Satellite 305D, AMD Turion(tm) X2 Dual-Core x86_64,
2000 Mhz,
ATI Radeon 3100, Atheros AR5007EG Wireless, 3G Ram, Realtek HD Audio,
200GB Hard drive
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
There are quite a few bugs logged in bugzilla for this. For me, the yast install of the grub process was hanging and using 100% cpu. Killing that allowed the installation to continue, then it worked from there on.
Q
>>> "Mark Corbin" <m-corbin(a)comcast.net> 09/23/08 10:15 AM >>>
Greetings,
I have not been able to get the beta up and running. When at the step of
installing and setting up grub I get a grub failure message every time.
Is anyone else seeing this and is there a workaround?
thank you
Mark Corbin Toshiba Satellite 305D, AMD Turion(tm) X2 Dual-Core x86_64,
2000 Mhz,
ATI Radeon 3100, Atheros AR5007EG Wireless, 3G Ram, Realtek HD Audio,
200GB Hard drive
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
--
This message was scanned by ESVA and is believed to be clean.
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
just a test
--
Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://counter.li.org
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
You are welcome.
Ok, first hint... :-) When you are responding to mailing list, you
should use reply-to-all instead of reply, because you want send one
copy to addresser (me) and one copy to maillist, right? :-)
When you will be confused of something, or you will think you're in
dead end, feel free to ask on this mail list, maybe we will able to
help you...
Situation: You have problem with some program segmentation fault
(crash) or with yast, but you don't know how to debug it.. So ask here
and maybe we will be able to give you a hint and help you. :-)
On Wed, Sep 17, 2008 at 3:28 PM, giuseppe gran <hawake(a)gmail.com> wrote:
> Ok, perfect! Thank you for answer and all information! :)
> I'll wait the upcoming beta.
> Thanks again!
>
> Bye
> hawaake
>
>
> --
> http://www.javalightserver.org
> Linux user number 433087
> Linux registered machine number 351448
> http://counter.li.org/
>
--
S pozdravem / Best regards
Marek Stopka
Official openSUSE community member
Kontakty / Contacts
Mobil/Cell phone: 774 59 79 40
E-mail: mstopka(a)opensuse.org
WEB: www.m4r3k.org
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org
Hi All,
i'm a new users of this mailing list. I'm one of the italians
traslators of the openSUSE Wiki. I would like to partecipate to new
Beta Testing of the upcoming openSUSE 11.1. Can i do it?
Thanks in advance
Bye
hawake
--
http://www.javalightserver.org
Linux user number 433087
Linux registered machine number 351448
http://counter.li.org/
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-testing+help(a)opensuse.org