Lines Matching full:might
21 might want to switch to a rendered version: it makes it a lot easier to
36 aspects, all of which might be essential in your present case.]*
76 # * Hint: at this point you might want to adjust the build configuration;
187 a) To avoid running out of disk space during a bisection, you might need to
205 the kernels you built earlier and later you might want to keep around for
254 pitfalls, as well as problems that might occur at the particular step -- and how
265 preliminary report after segment 2 might be wise, as the regression and its
266 culprit might be known already. For further details on what actually qualifies
496 But if you are extremely short on storage space, you might want to disable
554 tag. In that case you might want to check if a successor series (say
604 that; your distribution's documentation might help, too.
635 you just built, you might want to verify if the output of these commands
648 for this might interfere with your testing.
798 identifiers that might look odd or wrong to you -- which they are not, as it's
808 You again might want to start by making sure the kernel you booted is the one
838 description of the change. The latter might fill your terminal screen, so you
839 might need to scroll up to see the message mentioning the culprit;
861 This is optional, as it might be impossible or hard to realize. The former is
923 During and after following this guide you might want or need to remove some of
925 space might run out.
938 'good') might become handy to verify something later -- thus better keep them
962 set up, as you might need a few things again. What is safe to remove depends
987 While or after reporting a bug, you might want or potentially will be asked to
1259 for example might want to skip installing the development headers for ncurses,
1260 which you will only need in case you later might want to adjust the kernel build
1264 You furthermore might need additional libraries and their development headers
1280 that -- but there are two alternatives ways to retrieve the sources that might
1354 * Be warned, when deepening your clone you might encounter an error like
1403 want to go with the defaults, as you otherwise might enable a new feature that
1443 is hard to think of everything that might be needed -- even kernel developers
1452 But if you plan to build and use self-built kernels regularly, you might want to
1504 you thus might want to disable debug symbols to avoid those downsides. If it
1523 Depending on your needs you at this point might want or have to adjust some
1593 For some readers it might seem unnecessary to check the latest codebase at this
1608 older kernel. That security feature might get into the way of something you
1626 responsibility; mainline Linux developers might or might not care.
1633 Your report might be ignored if you send it to the wrong party -- and even
1647 In case you later want to recheck if an ever newer codebase might fix the
1668 When a build error occurs, it might be caused by some aspect of your machine's
1677 The ``V=1`` activates verbose output, which might be needed to see the actual
1697 system, but lies in the code. If you run into one of those, you might thus find
1783 work earlier might fail to boot. To prevent that you will need to know how much
1802 follow-up errors that look totally unrelated. That is why developers might
1808 interest, as your testing might be flawed otherwise.
1820 There are a couple of reasons why your bug or regression might not show up with
1828 * Your problem might be a race condition that does not show up with your kernel;
1832 * In case you encountered the regression with a stable/longterm kernel it might
1845 Then check if the latest codebase for the particular series might already fix
1861 This section will reestablish a known working base. Skipping it might be
1866 and you might be building and testing ten or more kernels for nothing before
1867 starting to suspect something might be wrong with the build configuration.
1873 it's possible that the thing that regressed might never have worked in vanilla
1893 multitude of reasons why this might happen. Some ideas where to look:
1899 test the feature? Then you might want to recreate a .config file based on the
1901 some features in the .config might work as well to reduce the build time.
1951 * Occasionally building the kernel will fail or it might not boot due some
1993 to restart the bisection from scratch. The log can prevent that, as it might
1995 instead of testing ten or more kernels you might only have to build a few to
1998 The .config file is put aside, as there is a decent chance that developers might
2027 *During and after following this guide you might want or need to remove some
2072 for kernels manually: you might accidentally remove files of a 6.0.13 kernel
2083 you set up, as you might need a few things again.*
2087 the step-by-step guide might not free as much space as you would like. In that
2109 *While or after reporting a bug, you might want or potentially will be asked
2221 (for example by the kernel's build system) might contain content taken from