Meta tags:
Headings (most frequently used words):
faq, general, frequently, and, issues, questions, lfs, blfs, information, about, these, support, guidelines, reported, bugs, compilation, errors, configuration, asked, requested, enhancements, when, reading, building, package, specific, booting, old, expired, thanks,
Text of the page (most frequently used words):
the (207), lfs (75), and (74), you (68), are (42), for (42), faq (35), not (34), this (32), that (30), blfs (29), book (29), with (26), your (24), system (23), support (22), there (21), lists (20), but (18), can (18), how (18), #package (18), use (17), when (16), packages (16), linux (16), list (15), have (15), more (14), which (14), mailing (14), what (13), please (13), information (12), all (11), should (11), will (11), general (11), about (11), some (11), questions (11), people (10), from (10), bin (10), they (10), post (9), before (9), version (9), has (9), new (9), dev (9), than (9), building (9), mail (8), only (8), these (8), get (8), sudo (8), run (8), file (8), any (8), errors (8), out (7), keep (7), where (7), know (7), command (7), root (7), work (7), upgrade (7), just (7), read (7), find (7), doesn (7), documentation (7), other (6), who (6), question (6), using (6), shell (6), report (6), does (6), yourself (6), may (6), want (6), them (6), good (6), foo (6), html (6), wrong (6), guidelines (6), text (6), such (6), error (6), help (6), why (6), try (5), well (5), many (5), obsolete (5), way (5), etc (5), commands (5), place (5), stable (5), compile (5), distro (5), unless (5), also (5), bash (5), different (5), likely (5), one (5), frequently (5), set (5), configure (5), website (4), few (4), its (4), answers (4), hard (4), take (4), care (4), webpage (4), since (4), problem (4), old (4), back (4), another (4), example (4), user (4), instructions (4), great (4), means (4), best (4), then (4), security (4), check (4), kernel (4), issues (4), while (4), page (4), fsck (4), down (4), must (4), release (4), like (4), avoid (4), someone (4), irc (4), newbie (4), directory (4), isn (4), useful (4), client (4), ask (4), reply (4), actually (4), reading (4), mention (4), email (4), items (4), versus (4), suggestions (4), experience (4), need (4), gcc (4), links (3), especially (3), those (3), answer (3), glibc (3), entry (3), build (3), account (3), already (3), top (3), don (3), tells (3), cannot (3), output (3), open (3), privilege (3), parameter (3), zsh (3), echo (3), shells (3), internal (3), updating (3), although (3), subscribe (3), development (3), look (3), hints (3), users (3), remember (3), releases (3), built (3), because (3), works (3), most (3), even (3), having (3), tarballs (3), available (3), wget (3), patches (3), whether (3), too (3), delete (3), compilation (3), see (3), been (3), pre (3), reason (3), reported (3), search (3), posting (3), first (3), time (3), idea (3), bar (3), last (3), man (3), following (3), start (3), signatures (3), flame (3), wars (3), obvious (3), via (3), anything (3), appropriate (3), pages (3), here (3), include (3), project (3), gnu (3), trouble (3), enough (3), chapter (3), community (3), channels (3), basic (3), newbies (3), intended (3), contribute (3), sometimes (3), asked (3), signal (3), specific (3), jeremy (2), whose (2), regularly (2), sort (2), wish (2), were (2), thanks (2), working (2), optimization (2), flags (2), setting (2), cflags (2), refers (2), now (2), non (2), grammar (2), found (2), usr (2), done (2), requires (2), raise (2), current (2), understand (2), case (2), standard (2), informed (2), versions (2), several (2), risk (2), become (2), primary (2), going (2), upgrading (2), rule (2), thumb (2), fixes (2), headers (2), heart (2), destroying (2), over (2), probably (2), traditional (2), download (2), linked (2), introduction (2), scripts (2), unix (2), systems (2), sulogin (2), log (2), shut (2), machine (2), init (2), beyond (2), change (2), boot (2), shuts (2), key (2), tickets (2), follow (2), note (2), snapshots (2), archives (2), once (2), knowledge (2), content (2), often (2), channel (2), newer (2), numbers (2), same (2), copy (2), missing (2), special (2), filename (2), link (2), bugs (2), minimum (2), etiquette (2), netiquette (2), existing (2), situation (2), subject (2), line (2), replying (2), without (2), trim (2), quoted (2), haven (2), off (2), posts (2), manner (2), mechanical (2), stuff (2), discussion (2), world (2), offended (2), else (2), books (2), pointer (2), couple (2), intend (2), news (2), points (2), end (2), gnome (2), belong (2), price (2), beer (2), bsd (2), things (2), little (2), everything (2), itself (2), deviation (2), reports (2), accepted (2), topic (2), written (2), hint (2), cross (2), asking (2), type (2), discussed (2), might (2), something (2), documents (2), guide (2), prerequisites (2), shows (2), audience (2), researched (2), welcome (2), web (2), scratch (2), create (2), installing (2), added (2), configuration (2), fatal (2), program (2), getting (2), gtk (2), lib64 (2), host (2), booting (2), systemd (2), null (2), config (2), bad (2), permission (2), denied (2), source (2), after (2), compiler (2), selection (2), mirrors (2), 1998, 2026, gerard, beekmans, design, huntwork, matthew, burgess, editors, produces, delightfully, faqs, tushar, teredesai, chris, lingard, utley, cheeze, countless, symptoms, lot, ids, immortalized, commit, logs, though, span, digital, forever, hey, guys, girls, come, seth, klein, creating, maintaining, dedicated, busy, let, encourage, optimize, besides, optimized, failing, spinlock, artwork, logos, portmap, describes, hardly, anyone, expired, correctly, prepend, construct, executable, lib, libfoo, chmod, 755, expect, redirection, performed, needs, write, doing, helpful, executables, constructs, piping, redirecting, final, comment, shouldn, blindly, assume, apply, upgrades, mind, safe, single, overwrite, contents, managers, uninstalling, really, convenient, management, ranging, rpm, deb, tgz, slackware, checkinstall, own, takes, present, mix, compatible, openoffice, org, java, real, dinosaurs, slightly, outdated, ensures, compatibility, stability, compare, debian, testing, generally, bleeding, edge, compared, extended, thing, decide, policy, latest, every, careful, burned, recommend, slight, conservatism, healthy, periodically, advisories, lwn, rebuild, entire, form, ability, binaries, carefully, section, named, control, rules, drawback, sense, goal, teaching, internally, refer, near, bottom, repository, normally, normal, bootup, fix, accept, password, passwd, corrupt, developers, decided, was, therefore, bootscripts, booted, wise, scope, script, late, inputrc, ticket, test, problems, changes, posted, steps, making, duplicate, versioning, schemes, odd, minor, patch, levels, greater, equal, won, day, tested, base, experiment, pain, varying, regulars, saying, fbbg, meaning, helped, unhappy, deviated, during, explaining, difference, between, soft, article, gazette, https, linuxgazette, net, 105, pitcher, inode, copies, conditions, whitespace, execution, fail, correct, symlink, containing, given, relative, created, provides, network, functions, individuals, both, administrators, rfc, 1855, major, usually, clear, field, replies, practice, due, political, unlikely, compose, whatever, calls, thread, sets, cause, appear, answering, click, consulting, original, confusing, limit, four, lines, below, hand, automatically, sending, wrap, characters, yahoo, hotmail, outlook, turned, turn, reach, rendered, completely, unreadable, subscribers, causing, give, nomime, international, membership, slang, sorts, idioms, misunderstood, witness, recent, bootstrapping, profanity, politics, war, religion, upset, somewhere, finally, considered, polite, english, language, bothersome, criticized, kindly, becomes, publicly, wordlessly, pointing, exact, spot, sufficient, feel, criticize, private, applies, heated, rude, answered, commonly, google, searches, long, demonstrate, made, effort, reasonable, person, object, manners, oriented, followed, exclusively, ignore, groups, mirror, reasons, omitted, brevity, rest, assured, individual, personal, preference, practical, draw, missed, around, awhile, less, toward, xorg, wayland, kde, sure, microsoft, intel, arm, hardware, unrelated, running, prohibited, fit, preceding, fits, except, concerning, acceptable, suggesting, improvement, customization, puzzling, send, released, bug, gladly, public, provide, method, additionally, details, reporting, procedure, resort, frustrated, attract, competent, friendly, interest, faster, clog, includes, least, tos, deal, nothing, info, yield, looking, ensure, embarrass, never, hurts, surprising, easy, overlook, fails, places, survival, difficulty, practically, starting, minimal, required, essential, life, seems, reality, quite, grasp, frustrating, lack, understanding, concepts, target, intermediate, advanced, anybody, months, console, able, successfully, assemble, substantial, editing, thought, checked, style, consistent, additions, removals, against, regular, based, contributions, addition, removal, maintainer, reached, either, direct, contributing, typical, desktop, install, browser, very, massive, contrast, distributions, allow, beginning, started, stands, aims, teach, inner, workings, downloading, natural, necessary, add, reduce, traffic, improve, noise, ratio, merely, side, effect, tries, saves, encountering, ps1, konsole, print, liberty, killed, terminated, cc1plus, directories, include_next, directives, part, installed, installs, libraries, into, much, slower, irq, nobody, cared, irqpoll, option, eth0, unknown, interface, respawning, fast, disabled, minutes, panic, syncing, vfs, unable, mount, networkd, service, failed, determine, credentials, process, assumed, value, mb_len_max, loading, cache, tcl, status, 508, 0a1, similar, message, ptys, administrator, checking, guess, interpreter, trying, chroot, segmentation, fault, didn, tree, attempt, hello, files, dos, format, processors, warnings, modules, distribution, modify, code, rid, skip, functioning, properly, uefi, make, poweroff, manager, vim, requested, enhancements, address, divided, three, credits, home, alfs, mlfs, glfs,
Text of the page (random words):
ed answers and the removal of questions that are obsolete if you intend to regularly contribute to this faq you might want to subscribe to the faq mailing list all suggestions additions and sometimes removals of the faq s are discussed there patches against the faq s are also welcome although regular text based contributions are accepted as well everything intended to go in the faq without substantial editing must be well thought out checked and researched and written in a style consistent with the existing content back to the top support guidelines what if i m a newbie to linux or lfs if you ve read the prerequisites and audience pages you know that the target audience of lfs are intermediate and advanced linux users anybody who has a couple of months experience with linux and especially the console should be able to successfully assemble an lfs system while lfs seems like a good guide for newbies to linux the reality is actually quite different experience with the support channels shows that lfs is hard to grasp and a frustrating experience for newbies because they lack understanding of the basic concepts practically this means that newbies should get some experience before starting with lfs the prerequisites page lists the minimal required linux knowledge but please also read the essential pre reading for life with lfs hint these documents and this faq are your basic linux survival guide you ll have a great time with lfs if you ve read them and may have some difficulty with lfs and the community but most likely yourself if you haven t read them where is the best place to get help when this faq fails to help there are several places to go if you re having a problem with something in the book it never hurts to go back over the book it s surprising how easy it is to overlook little things if nothing else reading the appropriate man and info pages will yield useful information on some subject if not what you were looking for and ensure that you know enough not to embarrass yourself if you have to ask someone the linux documentation project has the how tos and a great deal of other documentation you might find something there the website s search includes the mailing lists many questions have been discussed there at least once for support type help irc is often best it s faster and doesn t clog the mailing lists there s more information about the irc channels on the support webpage there are a few irc channels of interest lfs the lfs community channel lfs support support for lfs and blfs if you are asking a support question you are more likely to attract competent and friendly help in lfs support as a last resort there are the mailing lists people will get frustrated with you if you use the wrong one or cross post mailing list information is on the support webpage and tells which list to use please remember to provide enough information when you post to the mailing lists in chapter 1 of lfs you find a good method for posting additionally someone has written a hint which details the error reporting procedure which list should i use for what topic information about all the public mailing lists is available on the mailing list page here are some general guidelines about which list to use send support questions for the stable released books to lfs support for anything which doesn t belong in lfs use blfs support bug reports are gladly accepted you can report to the lfs dev mailing list if you are not having trouble following the lfs book itself do not email lfs support you may ask questions via lfs support if you are following the lfs book with some customization or deviation but you should mention your deviation in the mail to avoid from puzzling people unless you are suggesting an improvement to the lfs book itself do not email lfs dev only suggestions concerning the blfs book are acceptable on blfs dev things are a little different with blfs support everything that doesn t fit one of the preceding lists fits there except for the price of beer and gnu versus bsd flame wars the price of beer gnu versus bsd microsoft versus linux or intel versus arm flame wars and hardware discussion unrelated to building and running lfs are prohibited of special note is that if you mention xorg wayland kde gnome or anything in blfs you may be sure that your post does not belong on lfs dev or lfs support what about netiquette here are some practical points of etiquette they include only those items that will draw mention if missed those who ve been around project mailing lists awhile will find the first few obvious there are less obvious items toward the end the reasons for these points are omitted for brevity but rest assured these guidelines are more than just an individual s personal preference while the text refers to the lists exclusively it doesn t intend to ignore the news groups that mirror the mailing lists with that out of the way here are a couple manners oriented items followed by more mechanical stuff please remember that it is rude to post questions that are answered in commonly available documentation such as the lfs and blfs books this faq the lfs hints the appropriate man pages the list archives and google searches as long as you can demonstrate that you ve made an effort to find the answer and you re not offended by a pointer to documentation no reasonable person will object to your question most of the bothersome flame wars start when a newbie posts an obvious question is then criticized even in a kindly manner and becomes publicly offended please try to avoid this situation wordlessly pointing to the exact spot in the documentation is sufficient if you feel you must criticize please do it via private email not on the lists the same applies to anything else that may become heated the lists have an international membership so slang of all sorts and idioms are likely to be misunderstood witness the recent discussion of bootstrapping any mention of profanity politics war or religion even in signatures is likely to upset someone somewhere in the world so please avoid them as well finally it is considered polite to post in english since many more people on the lists know it than any other language now for the more mechanical stuff do not post in html if you use yahoo hotmail or outlook and haven t turned html off then it is on if you re using another mail client please do check before posting if you don t know how to turn html off see nomime html posts with html may reach the list but then rendered in a completely unreadable manner by the mail client of the subscribers causing them to give up reading and replying your mail wrap text at 72 characters if you do not wish to do this by hand set your mail client to do it automatically when sending reply below quoted text limit signatures to four lines trim quoted text especially signatures but do not trim so that it is confusing to read your reply without consulting the original do not click reply unless you re actually replying to a post use new or compose or whatever your mail client calls it to ask a new question or start a new thread reply sets more than just the subject line and will cause your post to appear in the wrong place unless you re actually answering the following isn t major but is useful to know on the lfs lists people usually clear the cc field and just mail the list with replies this is probably not a good idea but is existing practice due to a political situation which is unlikely to change rfc 1855 provides a minimum set of guidelines for network etiquette netiquette and functions as a minimum set of guidelines for individuals both users and administrators back to the top frequently reported bugs the ln s commands in the book are wrong no the ln s commands in the book are correct a symlink is just a special file containing the given filename so that filename is relative to the link not the working directory when the link is created try it and see more information in man ln bash missing you should understand how conditions like work in bash is a command and should be its last parameter so there must be a whitespace before or the execution of will fail bin foo is a copy of bin bar try ls i bin foo bin bar are the inode numbers the same if so they re not copies they re hard linked for more information explaining the difference between hard and soft links please take a look at the q a article on linux gazette at https linuxgazette net 105 pitcher html can i use a version newer than the one in the book if this is your first time building lfs using a version not in the book or varying from the book in any way is not a good idea the irc channel regulars have a saying fbbg meaning follow book book good they and the people on the lists have helped many an unhappy newbie who deviated from the book during that first build once you ve built a system by the book you have a stable knowledge base from which to experiment to your heart s content or pain as is often the case there s a new version of package foo if the new version is more than a day old it is likely that someone has tested the release and reported it on the mailing lists please search the archives before posting questions about whether it works and please note that different packages have different versioning schemes for example for many packages versions with an odd minor version y in x y z are development snapshots and some other packages use patch levels z in x y z greater than or equal to 90 for pre releases lfs blfs won t use development snapshots or pre releases unless there is a good reason if you d like to report the new release follow these steps to avoid making a duplicate report check for open lfs tickets or blfs tickets to see if the release has been posted there if the release is not in an open ticket report it to lfs dev or blfs dev for packages in blfs and if you like test it and report any problems or changes in compilation instructions too the delete key doesn t work please read the lfs inputrc page the system shuts down when fsck errors out unix systems normally run sulogin if the normal bootup fsck run errors out so that root can log in and fix it because sulogin will accept any password if etc passwd is corrupt the lfs developers decided this was a security risk therefore the lfs bootscripts shut the machine down if fsck errors and it must be booted with the init bin bash kernel parameter to get a root shell whether this is wise is beyond the scope of the faq but if it doesn t work for you you ll want to change that boot script before it s too late where are the lfs packages tarballs or wget scripts package tarballs are available at the lfs file repository there is also a wget list linked in the book near the bottom of the packages and patches introduction page how do i find a package or command please refer to the download lfs webpage how do i upgrade my lfs blfs system you probably know this already but lfs is not a distro in the traditional sense its primary goal is teaching people how a linux system works internally while this means you have great control over your system your distro your rules it also has the drawback of having to take care of updating it yourself please read the section named upgrade issues carefully before upgrading any package if you ve built an lfs system and have extended it to become your primary system the best thing to do is to decide on an upgrade policy do you want to keep the latest version of every package then be careful because you re going to be burned i recommend slight conservatism when upgrading to keep a healthy system a general rule of thumb which works for most people is only upgrade packages if they have security fixes periodically check lfs and blfs security advisories and subscribe to lwn to keep yourself informed about security fixes another rule of thumb is don t upgrade glibc and linux kernel headers unless you re going to rebuild your entire system these packages form the heart of your lfs system destroying them means destroying the ability to compile packages or even run binaries remember that updating packages is at your own risk lfs takes great care to present a stable mix of packages which are compatible all the way up to blfs so you can compile openoffice org and java which are real dinosaurs to compile this means that your lfs system may get slightly outdated but ensures compatibility and stability you can compare this to debian s stable and testing releases although lfs stable is generally bleeding edge compared to other distro s in general it is safe to upgrade single packages they ll just overwrite the old contents package managers take care of uninstalling old versions and it s really convenient to have some sort of package management system in place have a look at the hints there are several ranging from rpm to deb to tgz slackware to checkinstall to package users a final comment what package instructions should you use when updating a package in general you can use the standard lfs instructions although you shouldn t blindly assume they will apply to all packages to keep yourself informed about upgrades and new package instructions subscribe to lfs dev keep in mind that this is not a support list but a development list the commands in lfs blfs book does not work with sudo sudo can only run executables as root it does not understand internal grammar constructs of the shell for example case cd for if piping redirecting output to a file etc for example when the book tells to run echo bin zsh etc shells as the root user you cannot run sudo echo bin zsh etc shells as a non root user and expect it to work the output redirection is performed by the shell so the shell needs to open etc shells for write and doing so requires a privilege but sudo has no way to raise the privilege for the current shell it can only raise the privilege for the echo command with bin zsh as the parameter but this is not helpful at all for another example when the book tells to run for i in usr lib libfoo so do chmod 755 i done you cannot prepend sudo before the command and run it as a non root user for is a shell grammar construct not an executable so sudo will report for command not found if you do not know how to use sudo correctly don t use it back to the top old and expired faq s i m using a version not in the book is that a problem there s already a faq entry which describes this since hardly anyone refers to this entry it s now obsolete where s which obsolete on account of the blfs book where s portmap obsolete on account of the blfs book where can i get lfs logos obsolete on account of the blfs artwork webpage my optimized build of glibc is failing in spinlock c let s not encourage people to optimize glibc besides the when using optimization flags setting cflags entry should take care of this question thanks this faq is dedicated to all the hard working people on the support lists who keep me busy with this faq thanks go to seth w klein for creating...
|
