public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Franta <sdoma@karneval.cz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] So O.K.
Date: Sun, 12 Feb 2006 14:30:27 +0100	[thread overview]
Message-ID: <1139751028.6173.10.camel@frankies.at_home> (raw)
In-Reply-To: <342e1090602100804j71461e1eybca877e84e72249a@mail.gmail.com>

On Fri, 2006-02-10 at 14:04 -0200, Daniel da Veiga wrote:
> On 2/4/06, Franta <sdoma@karneval.cz> wrote:
> > As I said. It wont be SicroMoft. I'm still wondering. At this time of
> > writing I reduced the possibilities to Slackware or LFS.
> > I know, I'll need to do some work to get things running but if they are
> > running I know they ARE running. Nobody will "upgrade" my system to make
> > them stop working and thus make me to explore why and how to fix this.
> >
> > Don't advice me to use Windoooze. I'm a UNIX admin the last 20 years. It
> > would be the horror to become accustomed to this poorly program. Well,
> > program - I don't say this to be an OS.
> >
> 
> I got a Pentium 100 running for about 6 months now, since that time I
> did not touch it, its more stable than our proxy server *lol*
> 
> If you want the bleeding edge, all updates, all the latest versions
> and changes, you agree that at some point you'll have problems, that's
> no reason for flamming the distro and if you feel like it, DON'T!!
> Change the distro, simple as that... C'mon, I am a newbie compared to
> you. I'm running Linux for about 5 years, Gentoo for about an year,
> and still, got my udev working after some reading (the docs Philip
> mentioned)... You should be ashamed of your first post...
> 
> >
> >
> > BTW: I'm a UNIX admin the last 20 years. So don't
> >
> > On Sat, 2006-02-04 at 04:11 -1000, Beau E. Cox wrote:
> > > On Saturday 04 February 2006 04:02 am, Franta wrote:
> > > > Due to the issues I hit (nearly) every time I do an upgrade.
> > > >
> > > > I did the upograde today too. There was one on udev. I think devices
> > > > don't coming up (Sound, USB) could belong to this kind of problems.
> > > >
> > > > Well. nothing changes.
> > > >
> > > > I've tried it half an hour ago with (a very old) knoppix CD. I have USB
> > > > disks, I have sound, I have networking ...
> > > >
> > > > That said (xcuse me, I <<HAVE TO>> say that) Gentoo is far away from a
> > > > distro for usage.
> > > >
> > > > Do not reply to this post - I'll unsubscribe immediatlely after posting
> > > > and I'll go to have a lok for another distro which won't force me to
> > > > fdisk for a newly install. Maybe it'll be Slack.
> > > >
> > > > Have fun customizing and repairing your systems. I prefer to work with
> > > > it.
> > > >
> > > > Frank
> > >
> > > So OK. Bye. A little work on your part and you could be enjoying and
> > > 'working with' one of the best distros available. Maybe you should pack
> > > it in and just install Windoze...
> > >
> > > --
> > > Aloha => Beau;
> > >
> >
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
> 
> 
> --
> Daniel da Veiga
> Computer Operator - RS - Brazil
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
> PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
> ------END GEEK CODE BLOCK------
> 

Got it. Realizing that I got a new baselayout, that things heavily
changed in udev AND things heavily changed in the kernel as of versoon
2.6.13 I decided to upgrade the kernel.

I've chosen 2.6.15 and averything works again (after a ``no | make
oldconfig'').

I'd assume that the newer baselayout(s) aren't compatible with kernels
older than 2.6.13 anymore. I'll not explore that. Maybe someone knows
that beter than me.

Right, RTFM will lead to success in every case but it't annoying to do
this again and again and again.

Right too, I could leave the comp as it is but if I try to install a new
tool (yes I'm still in this phase) I'll have to upgrade anyway. After a
month without internet connection I got about 30 packages to upgrade.
For now I'll upgrade rather often to hold this number low.



-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-12 13:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 14:02 [gentoo-user] So O.K Franta
2006-02-04 14:11 ` Beau E. Cox
2006-02-04 15:08   ` Franta
2006-02-04 15:30     ` Neil Bothwick
2006-02-04 16:36       ` Michael Sullivan
2006-02-04 20:27         ` Neil Bothwick
2006-02-04 21:02           ` Michael Sullivan
2006-02-04 21:18             ` Neil Bothwick
2006-02-04 20:56     ` Rafael Fernández López
2006-02-10 16:04     ` Daniel da Veiga
2006-02-12 13:30       ` Franta [this message]
2006-02-12 14:58         ` Daniel da Veiga
2006-02-04 15:17 ` Mark Shields
2006-02-04 15:39 ` [gentoo-user] " Harry Putnam
2006-02-05  0:26   ` A. Khattri
2006-02-05 12:01     ` Franta
2006-02-05 14:06       ` Philip Webb
2006-02-10  0:47         ` Boyd Stephen Smith Jr.
2006-02-10  1:43           ` Iain Buchanan
2006-02-05 15:12       ` Benno Schulenberg
2006-02-04 17:16 ` [gentoo-user] " Ernie Schroder
2006-02-05 12:09   ` [gentoo-user] So O.K. -- help or point! Franta
2006-02-05 13:51     ` Ernie Schroder
2006-02-05 17:08     ` Richard Fish
2006-02-06  4:51       ` Franta
2006-02-06  6:19         ` Richard Fish
2006-02-06  6:02     ` Richard Fish
2006-02-06 18:25       ` Franta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1139751028.6173.10.camel@frankies.at_home \
    --to=sdoma@karneval.cz \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox