I usually take the newest openSUSE kernel (from repository
Kernel_stable). But since some month I have a DVB T2 HD card, which
requires a patch (see https://bugzilla.kernel.org/show_bug.cgi?id=194171).
So I need to compile kernels myself. I have a working compilation path.
But the current path has 12 steps! It takes some time. I wonder, why it
is so complicated to configure, compile and install a Kernel under openSUSE.
Is there a better/easier/automated way to configure, compile and install
a Kernel under openSUSE?
I know this blog article. But the article uses Vanilla kernels and also
needs 6 steps. With additional patches (4 steps), third-party modules (2
steps) and cleanup (1 step) the article would also need 13 steps:
Compiling the Linux Kernel, the SUSE way
https://www.suse.com/communities/blog/compiling-de-linux-kernel-suse-way/
This is my Kernel configuration, compilation and installation path:
1. Update kernel-source and kernel-default from Kernel_stable repository
2. Save kernel-source: cp -a /usr/src/linux-4.x.y-...
/usr/src/linux-4.x.y-my
3. Apply my patches
cd /usr/src/linux-4.x.y-my
patch -b -p1 < ~myuser/.../my-kernel-patch.patch
4. Copy standard configuration:
cd /usr/src/linux-4.x.y-my
cp -v /boot/config-4.11.4-1.gcba98ee-default .config
5. Edit .config:
remove CONFIG_LOCALVERSION, CONFIG_DEBUG_KERNEL, CONFIG_EXPERT
remove some hardware-dependent settings
6. edit configuration interactively:
Disable CONFIG_EXPERT and CONFIG_DEBUG_KERNEL, because otherwise
"make binrpm-pkg" creates huge kernel binaries.
make oldconfig
[...]
Local version - append to kernel release (LOCALVERSION) [] (NEW) -my1
*
* Configure standard kernel features (expert users)
*
Configure standard kernel features (expert users) (EXPERT) [N/y/?]
(NEW)
Kernel debugging (DEBUG_KERNEL) [N/y/?] (NEW)
make menuconfig
Do some additional configuration.
7. Compile kernel
(-j4 for four processor cores, ionice and nice to reduce the load,
binrpm-pkg for RPM without source-RPM)
make clean
nice ionice -c idle make -j4 binrpm-pkg
8. Install the kernel RPM package
rpm -Uvh /usr/src/packages/RPMS/x86_64/kernel-4.x.y_my1-....x86_64.rpm
9. Install necessary symbolic links for "dkms"
cd /lib/modules/4.x.y-my1
ln -sv /usr/src/linux-4.x.y-my source
ln -sv /usr/src/linux-4.x.y-my build
10. Update third-party modules (e.g. Nvidia driver):
dkms install -m nvidia -v 375.66 -k 4.x.y-my1
11. Cleanup
cd /usr/src/linux-4.x.y-my
make clean
12. Select Grub configuration and reboot
grub2-once --list | less
grub2-once 2
reboot
Greetings,
Björn
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On Wednesday 03 July 2002 03:38, Michael wrote:
> I tried to visit this site.
> http://www.bet365.com
> The result upset me so much i sent them this.
I sent the letter below, and I encourage everyone on the list to send a
similar letter.
-----------------------------------------
Subject: Create a Real Web Site Please
From: Bryan S. Tyson <bryantyson(a)earthlink.net>
To: webmaster(a)bet365.com
When attempting to view your site using Konqueror 2.2.1 and Mozilla
0.9.4, both Linux web browsers, I was curtly informed that my browser
is "incompatible." Your site, sir, is what is "incompatible." Stick
with established standards and real html, not Microsoft proprietary
"features."
***************************************************
Powered by SuSE Linux 7.3 Professional
KDE 2.2.1 KMail 1.3.1
This is a Microsoft-free computer
Bryan S. Tyson
bryantyson(a)earthlink.net
***************************************************
We have an winNT server and need to auto mount a shared folder as if it were a
windose mapped drive Z: on SuSE8
Could someone please explain how to do this and how to make sure it is set-up
for every user everytime the system is booted.
Thanks
Regards
Keith Jacobs
New to Linux
Hello List
am using Xfce : - in /var/log/warn : i see warning
" The gnome keyring socket is not owned with the same credentials as
the user login: /run/user/1000/keyring-4i77r7/control
2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login
keyring "
...............
- any ideas how to fix ?
thanks
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On 27/06/17 12:22, Paul Groves wrote:
>
> On 27/06/17 08:34, Aaron Digulla wrote:
>> xmodmap -pke | less
>
> These keycodes do not seem to match the system. For example in the
> output of this command it says:
>
> keycode 158 = XF86WWW NoSymbol XF86WWW
>
> I ran setkeycodes e020 158
>
> When I press the e020 (Internet) button xev says I have pressed code
> 166 (Back button).
>
> How on earth has this happened? I specified 158 not 166. What have I
> done wrong?
>
>
Just been emailed this link:
https://unix.stackexchange.com/questions/49650/how-to-get-keycodes-for-xmod…
To quote this article:
Here you can see keycode 97 is unused on my system:
|keycode 94 = less greater less greater bar brokenbar keycode 95 = F11
XF86Switch_VT_11 F11 XF86Switch_VT_11 keycode 96 = F12 XF86Switch_VT_12
F12 XF86Switch_VT_12 keycode 97 = keycode 98 = Katakana NoSymbol
Katakana keycode 99 = Hiragana NoSymbol Hiragana |
The keycode X uses and the keycode the kernel uses are OFF BY 8 for
"historical reasons". So take 97 - 8 = 89 and use 89 with the
setkeycodes command (again as root):
So to make my vol - button work (xmodmap keycode 122 -8 = 114)
setkeycodes e01e 114
This has worked! I have re-mapped apl the buttons apart from my hotkeys.
>> No but there are lots of uncommon keycodes which you can use. For
>> example, F13-F35 or KP_F1...KP_F4.
>
> In the output of the command xmodmap -pke | less there are no codes
> for F13-F35 or KP_F1 etc
>
> I would like to set HK1 - HK4 to F13 - F16 How do I find the keycodes
> for these buttons
Still looking for the keycodes for F13-16
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
On the odd chance that I was ignored for possibly hijacking a thread,
I shall start a new one but copy and paste my comments in hope of an answer:
(re: Killing ReiserFS)
I have been following this thread with some interest because of having
been running ReiserFS since before he turned homicidal. I have had zero,
count that ZERO, problems in all that time so I read with some dismay
the effort to actively kill its usage in this whatever-you-call-it distro.
I think that the more relevant question to ask is not "can we keep this
file system around, pretty please" but "what distros are allowing its
use by not actively trying to kill it"? I have used opensuse since
before Mandrake went away, which has been a while and, although I don't
really want to change distros, I am not married to suse (or leap, or
whatever).
I feel that what we have here with opensuse/leap is an example of the
classic "swing" cartoon which shows the stages of project development
from sales, engineering, installation and what the customer actually
wanted. My need is not as complex as some and for that ReiserFS works
quite well.
So, my question remains, "If not suse/leap, then who"?
Hopefully someone will know what distros allow the freedom to use
whichever FS one wishes without running afoul of the FS nazis.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I go to:
<https://software.opensuse.org/search>
and search for any package, say "meld". I get a list of hits. I click on
one:
meld
Visual diff and merge tool
Show 1 Development packages
and I get this error:
<https://software.opensuse.org/package/meld>
Error
:codecs is not a valid locale
I have been getting that error for some days. However, on a new user I
don't get any error, it works.
I do not have "codecs" as locale:
cer@Telcontar:~> set | grep codec
__git_mergetools_common=$'diffuse diffmerge ecmerge emerge kdiff3 meld opendiff\n\t\t\ttkdiff vimdiff gvimdiff xxdiff araxis p4merge bc codecompare\n'
cer@Telcontar:~> locale | grep codec
cer@Telcontar:~>
- --
Cheers
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAln06z8ACgkQtTMYHG2NR9U3lgCgjdg/rLggwxeTlT1Dh2qaCp03
bocAn3DlEbzUMiMOhh0uvItf/j6c/7Z7
=vPYi
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi Folks,
There seems to be a flurry of IPv6 talk going on, maybe this is time
for me to bring up the rogue router problem again? I asked about
this a couple of times over the years but could never find anyone
to comment on it.
First, here's the RFC that describes the problem:
https://tools.ietf.org/html/rfc6104
Rogue routers have affected me personally at a customer's site.
This is a large, professionally managed, dual-stacked network with
a number of v4 class B addresses and thousands of hosts. Subnets
seem to be /20 CIDR in size, so there are plenty of "neighbors" on
any given subnet.
I've encountered the situation where misconfigured Windows systems
will advertise themselves as an IPv6 router. They then happily accept
traffic and drop it all silently on the floor. This problem doesn't seem
to bother other Windows boxes too much, but it absolutely kills SSH
connections. SSH preferentially tries IPv6 port 22, which when sent
to a dumb Windows box results in very long hangups and connection
failures. My workaround for my cohort of Linux desktops and servers
was to disable IPv6 for both ssh and sshd. This will work for as long
as the host network supports dual stacks, but eventually?
Then there's the issue of intentional MITM attacks using this vector.
If a bad actor has physical access to a subnet, or has compromised
a host on that subnet, your goose is cooked.
This link mentions some mitigations, but they're quite technical and
may require hardware support.
https://community.infoblox.com/t5/IPv6-Center-of-Excellence/Holding-IPv6-Ne…
So, what is the threat to a home IPv6 user who has WiFi and an Internet
of Things with minimal/non-existent security? I personally feel safer
behind a nice natted IPv4 firewall with ACL rules between my copper
and WiFi subnets. I just feel that I have more control of the situation
with a simpler network.
Has SUSE addressed this issue? Tell me I don't have to worry about it!
Regards,
Lew
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
This is a problem I hit on some computers only.
I "su -" from my normal user on a terminal under xfce. Then I try to start
any graphical tool, and it fails:
~# xeyes
Error: can't open display
~#
If I instead use "ssh -X root@localhost" it usually works.
This has happened to me on several computers along several years - but not
all of them.
Ideas?
- --
Cheers
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlogj6sACgkQtTMYHG2NR9W+eQCePRN8ptUoc5at81qylidoR24J
jhQAn0WnS3dm/5NxStrZJ+xnR+6YxlV3
=ZTC2
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org