luxInteg wrote:
> Greetings ,
>
> I would be grateful if someone could advise on the saving and retrieving
> of
> the random seed on a BLFS installation and if the random-seed cant be
Which random seed? Do you mean the one described in for
the pseudo random number generator?
> saved
Andrew Benton wrote:
> On Thu, 18 Aug 2011 21:55:24 +0200
> Pol Vangheluwe wrote:
>
>> Op 17-aug-2011, om 13:20 heeft Andrew Benton het volgende geschreven:
[...]
>> pol [ ~/ghostscript-9.00 ]$ ls -l /usr/lib/libfree*
>> -rw-r--r-- 1 root root 3454556 13 aug 21:25 /usr/lib/libfreetype.a
>> -rwx
Lars Bamberger wrote:
> Hello,
>
> whenever I try to go to a site via http_s_ in epiphany-2.30.2, I get
> this error:
Could you post a failing URL?
Mac
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message
Casey Daniels wrote:
> I finally was able to finish my first LFS system and it was a fun time.
> Now I have some questions. I plan on building my second build that I
> actually plan on using but didn't understand much about Package
> Management or Upgrading. From the Short info in the Book i
Timothy Rice wrote:
>> If your ISP uses dhcp you can run dhcpcd (it's in BLFS). It should set
>> up the network for you.
>> Alternatively, get a router. That will run a dhcp daemon which will deal
>> with the internet, then you can set static addresses for your local
>> network.
>
> Aha, thanks An
lI wrote:
[...]
> I cant myself see how 'package management' fits with compile from sources
> philosophy. Automated build procedures yes, but package-management meaning
>
> pre-compiled libraries, and executables in specified locations? There
Package management is not what you
Bruce Dubbs wrote:
> The easiest way to copy an LFS system to another computer with a similar
> architecture (e.g. i686) is with tar. The caveat is that if the HW
> (video card, drive type, etc.) is different, you will need to rebuild
> the kernel. Of course you also have to update the config
Maginot Junior wrote:
> On Sat, Jul 10, 2010 at 12:38 PM, Andrew Benton wrote:
>> On 10/07/10 15:29, Maginot Junior wrote:
>>> On Sat, Jul 10, 2010 at 5:49 AM, Matthias Feichtinger
>>> wrote:
No, never.
Use another distro
--
>>> can you at least illustrate your opnion with mo
Maginot Junior wrote:
>
> can you at least illustrate your opnion with more then "No, never." ?
> Because I don't see why I can't install my distro and why the final
> answer is "User another distro"
The goal you have in mind is explicitly opposite to the goals
of LFS.
Mike
--
p="p=%c%s%c;main(
Timothy Rice wrote:
> Hey Chris (and everyone else as well),
>
>> /usr/share/info ~/mysql-5.1.42
>> rm: remove write-protected regular file `dir'?
>>
>> It is trying to update /usr/share/info/dir. My solution was to make
>> /usr/share/info/dir owned by the "install" group and group writable.
>
>
cliffhan...@gardener.com wrote:
> Hi
>
> This looks on the face of it like a permission problem, but I can't
> solve it.
>
> Just installed K3b into KDE 4.4.2, but the program refuses to find my
> cd drive. It finds the drive if I run K3b from root, but not from a
> user.
>
> The permission
x2...@lycos.com wrote:
[...]
>I thought i'd read, several years ago, that there is a way of running
>the kernel in one of the debuggers like 'gdb'. There has to be something
>better then having to re-boot for each test. :-)
There is some low level debugging available, but it isn't a
Carl wrote:
> Well I seem to have fixed it. I changed the line for the cdrom in /etc/fstab
> from
>
> /dev/hdc /media/cdrom0 iso9660 ro,user,noauto,unhide 0 0
> to
> /dev/hdc /media/cdrom iso9660 ro,user,noauto,unhide 0 0
>> now it mounts.
All you did was change the mount
David Expósito wrote:
> hello
>
> I am compiling lfs blfs 6.3 X window and doing fine now startx tells me
> this:
[...]
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 4 20:04:40 2010
> (==) Using config file: "/etc/X11/xorg.conf"
> expected keysym, got XF86KbdLightOnOff: line 70 of pc
>
Lars Bamberger wrote:
> On 21.05.2010 09:40, Rodolfo Perez wrote:
>> root [ /etc ]# ls
>> ls: unrecognized prefix: hl
>> ls: unparsable value for LS_COLORS environment variable
>
> It would seem that something went awry in the alias definitions and/or
> the dircolors definition.
>
> Find out what
Simon Geard wrote:
> On Fri, 2010-05-07 at 12:55 -0600, Matthew Burgess wrote:
>> *Appears* is the right intonation! The build fails without PAM and I
>> think I reported it a while ago, and upstream pretty much said
>> most/all distros use PAM so they weren't interested in fixing it.
>
> Well, t
Dr.-Ing. Edgar Alwers wrote:
> On Tuesday 20 April 2010 21:56:59 Mike McCarty wrote:
>
>> Umm, since you seem to be unfamiliar with the language the kernel is
>> written in, it seems presumptuous to me for you to condemn the code.
>>
> Far away from that. I know, that
Dr.-Ing. Edgar Alwers wrote:
> Hi Bruce, Michael,
>
> I found version.h, the definition was commented out. I deleted the comment
> "#",
In C the octothorpe character '#' does NOT indicate a comment. You need
to reinsert that character.
> but the result is the same. Error 1 at the same stateme
James Richard Tyrer wrote:
> On 04/19/10 18:04, Mike McCarty wrote:
>> James Richard Tyrer wrote:
>>> Is there something wrong with this code:
>>>
>>> NetworkManager-0.8.build/src/NetworkManagerPolicy.c:
>>>
>>> #include
>>>
>>&g
I've read through the BLFS sections related to video, but am still
uncertain how to proceed toward the goal of playing MP4 (so called)
format files. It looks like MPLAYER may be the way to go. I have
an older XINE which I installed some time back, but it doesn't seem
to be able to handle those.
An
James Richard Tyrer wrote:
> Is there something wrong with this code:
>
> NetworkManager-0.8.build/src/NetworkManagerPolicy.c:
>
> #include
>
> if (isblank (*p) || (*p == '\0')) {
>
> ?? GCC-4.3.4 doesn't like it:
>
> NetworkManagerPolicy.c:272: error: implicit declaration of f
Andrew Benton wrote:
> I don't use a login manager, I select the window manager with ~/.xinitrc
> to launch openbox I
[...]
Tbanks for the nice tips!
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This messa
Andrew Benton wrote:
> On 23/03/10 18:26, Mike McCarty wrote:
>> Anyone familiar with Open Box WM?
[...]
> Yes, I've been using it for years. It's excellent. I particularly like
> the ease with which you can right click on the desktop and get a pop up
> menu that is
Anyone familiar with Open Box WM?
http://openbox.org/
It claims to be able to run GNOME and KDE apps w/o any mods,
and to be fast and simple to install and use.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
Aleksandar Kuktin wrote:
>
> AFAIK, what is knows as USB 2.0 is called EHCI in kernelworld. Judging
[...]
> As you have a VIA based motherboard, you should enable UHCI and EHCI to
> get "basic" USB functionality and then maybe enable aditional kernel
> options (mouse? keyboard? printer?).
Exter
Trent Shea wrote:
[some good stuff]
> If you can run lspci -v from a running known 'good' configuration you should
> get some usefule info, too.
Thanks!
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This
Matthew Burgess wrote:
> The kernel's menuconfig help text for EHCI says:
[...]
> For OHCI it states:
>
> "On most non-x86 systems, and on x86 hardware that's not using a USB
> controller
> from Intel or VIA, this is probably appropriate." It even suggests that
> 'lspci -v'
> will provide the
Andrew Benton wrote:
> On 16/03/10 03:54, Mike McCarty wrote:
>> OHCI -- UHCI
>>
>> Ok, how does one determine which of these he needs?
>
> lspci from pci-utils
> http://www.linuxfromscratch.org/blfs/view/svn/general/pciutils.html
I'm aware of lspci; h
OHCI -- UHCI
Ok, how does one determine which of these he needs? Is it possible
that one would need both, with some hardware setups?
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100%
Simon Geard wrote:
> On Fri, 2010-03-05 at 12:15 -0800, William Tracy wrote:
>> I know an awful lot of people come from a Windows of Mac OS background
>> and get used to point-and-click everything, but you'd think LFS would
>> filter out most of the people who really hate the CLI. :-)
>
> There's
Ken Moffat wrote:
> On 5 March 2010 13:51, Andrew Benton wrote:
> I'm obviously in the wrong place here - for people who don't use
> most of gnome or kde, surely xorg is just a place to run applications
> and xterms ?
Yes, that's the case for me. I don't use the file explorers. I do like
having
I see in BLFS 6.3 Part VIII that the desktops available are
XFce, KDE, and GNOME. I don't seem to be able to find how to build
and install XFce.
Can anyone point me to the place in the book which describes how
to build and install XFce? I see a comment that the book had been
updated, and then XFce
zzf...@embarqmail.com wrote:
> Python-2.6.4 compiles without error , but the test suite fails:
>
> edited out non failure tests
Well, welcome to the "free software development" world. When
I first started using Linux several years ago, I was apalled
at the lack of concern over compile warning
Matthew Burgess wrote:
> On a very new system (linux-2.6.33 + libdrm-2.4.18) I see the same
> thing. Looking at the README in the tarball for libdrm:
>
> "New functionality in the kernel DRM drivers typically requires a new
> libdrm, but a new libdrm will always work with an older kernel."
>
>
John Burrell wrote:
I rewrapped this for you. You might consider reading the FAQ.
> If installed as root, libdrm will overwrite these linux-api-headers
> from /usr/include/drm:
One point for "install users package management", I guess.
> test -z "/usr/include/drm" || /usr/lib/pkgusr/mkdir -p "/
brown wrap wrote:
> In file included from activate.c:27:
> /usr/include/string.h:546: error: expected declaration specifiers or '...'
> before '__locale_t'
Try looking at the source. It looks like there is some syntax error
in /usr/include/string.h or in something which includes it, or that
some
Simon Geard wrote:
> On Mon, 2010-02-15 at 13:59 -0600, Mike McCarty wrote:
>> Since I'm on the verge of starting in to build BLFS, it would
>> be helpful to know when the next release may be available. I
>> realize that can be very difficult to estimate when you do
Randy McMurchy wrote:
>
> We will try to get a BLFS-6.5rc1 out just as soon as we can. I have
> a little time to devote, so we'll just have to see. No promises. For
> the time being just use the -dev book.
Thanks for all the free effort. I appreciate it!
Since I'm on the verge of starting in to
zzf...@embarqmail.com wrote:
[...]
> Any pointers or commments from mutt users would be
> welcomed.
>
Maybe you should switch to Puppy Linux! :-)
I'd switch to not digest mode. Editing a huge thing
is too much effort.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34)
stosss wrote:
>
> Thanks, I went ahead and unpacked and built the package, copied scp to
> /usr/bin, ran the test, no errors at all, ran grep it came back clean.
> Installed the package tried connecting to one of my other OSs no
> problem. started sshd no problem.
Congratulations!
> After doing
stosss wrote:
> svn-20100203 from the 02-10-2010 archive
>
> The last sentence in the paragraph between make and make test.
>
> _To run the test suite, first copy the scp program to /usr/bin, making
> sure that you back up any existing copy first._
>
> This is probably enough for some one who ha
stosss wrote:
[where's my stuff?]
> On Fri, Feb 12, 2010 at 2:31 PM, Mike McCarty
> wrote:
[...]
>> That depends upon how you configure your build. I suggest you
>> read the section in the book
>>
>>The /usr Versus /usr/local Debate
>>
>
stosss wrote:
> svn-20100203 from the 02-10-2010 archive
>
> The last sentence in the paragraph between make and make test.
>
> _To run the test suite, first copy the scp program to /usr/bin, making
> sure that you back up any existing copy first._
>
> This is probably enough for some one who ha
Simon Geard wrote:
>
> Oddly enough, I used to have a script to do just that - written in bash
> shell of all things, though practically anything else would be better
> suited.
>
> But in practice, writing your own tool to do it is entirely unnecessary,
> since that's exactly what 'make' does. Ju
Michael Shell wrote:
> On Tue, 02 Feb 2010 22:15:14 -0600
> Bruce Dubbs wrote:
[some additional suggestions]
Thanks for the advice! I appreciate it.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This messa
James Richard Tyrer wrote:
> Mike McCarty wrote:
>> I thought the book instructed one to put in a soft link, so the stuff
>> could be accessed in "standard" locations.
>>
> Thanks Mike.
>
> That is a work around which I am currently using.
>
> Do y
Bruce Dubbs wrote:
>
> That's about 45 *feet* wide. I'll leave it out there in case anyone
> wants to try to do something useful with it, but it's not likely.
I'd think that it's not very useful for processing by _humans_,
but after all, we are all programmers of a sort here. I wonder if
one co
Simon Geard wrote:
> On Wed, 2010-02-03 at 18:49 -0600, Mike McCarty wrote:
>> I was disappointed when I saw that LFS seemingly ineluctably
>> was wedded to udev. I see that BLFS has some hints for doing
>> things without it, but then leaves the sysadmin to his own
>&g
Ken Moffat wrote:
> On 4 February 2010 00:49, Mike McCarty wrote:
>
>> So, someone with the idea "my system, my rules" and "I don't
>> want udev messing around" doesn't sound weird to me at all.
>>
> Not weird, no, but certainly asking fo
Simon Geard wrote:
> On Wed, 2010-02-03 at 19:18 -0600, Mike McCarty wrote:
>> Would someone like to educate me on the risks involved with autofs,
>> and why one would prefer autofs to whatever it is that HAL can do
>> on its own, please?
>
> I've no experience wi
Ok, after some research, I think I may know actually what autofs
does. One creates a list of devices which autofs handles. If one
does an access to the intended mount point, then autofs looks
to see if it has a physical device it can actually mount, and
does so. If no accesses take place for a whil
Ken Moffat wrote:
[...]
> Most of us manage to avoid writing initscripts until we have
> a concrete need. I'm slightly frightened by your premise that
> you need to create device nodes because udev doesn't.
>
> What sort of devices are these ?
>
> Rereading what you wrote, perhaps I'm confus
Ken Moffat wrote:
[...]
> If you know what you think you want, and they are in BLFS,
Yes, Step 0 is make a list of what I want. The descriptions
of each of the "packages" in the book are spare. Sometimes,
I'm not sure just what a package brings to the table. An example of
that is autofs. The tex
Bruce Dubbs wrote:
> I never install gdm/xdm/kdm. I've tested them for the book, but I never
> use them myself. I have much more control at the command line and
> typing startx is easy. How often do you reboot a solid system?
>
> Oops, its been 152 times for me -- since Nov 29 19:38:58 2005.
Bruce Dubbs wrote:
> Consider fluxbox or metacity before Gnome. One of the problems with
> Gnome is that it requires a lot of builds just to start a minimal system.
Is it worthwhile installing GDM or KDM to start fluxbox, or just
start it after login? ISTM that with GDM or KDM, one could install
Bruce Dubbs wrote:
Thanks for the reply!
> Mike McCarty wrote:
>> Bruce Dubbs wrote:
>
>> Well, the build has to proceed in a linear fashion, so there
>> must be a linearizable dependency list, else one would have
>> no way to bootstrap.
>
> The way if work
Well, I've built LFS a few times, like maybe five, and am about
to start in on BLFS. What I'm aiming for is a desktop system.
Mostly, my interest in LFS started when I just couldn't find
a "standard" distro which met my needs, that is, without loads
and loads of stuff I don't want, in addition to t
57 matches
Mail list logo
