[gentoo-user] Re: GSoC Proposal Ranking
Vedant, notifications won't happen until after that date. We have been doing the ranking all week and will submit it before the deadline. On Tue, Apr 25, 2023, 11:33 Vedant Tewari wrote: > Hello, > I hope this email finds you well, I am a current applicant for GSoC 2023, > and I submitted a proposal for the project "Automated Gentoo Updater", I > was wondering the proposals submitted for this project have been ranked so > far, since the deadline for ranking the proposals is April 27th (2 days for > now), and I haven't received any email or communication regarding the > proposal rankings for this project, hence I was wondering if you could take > a look at this issue and notify me as soon as possible! I would appreciate > that and thank you for the consideration! > Best Regards, > Vedant >
Re: [gentoo-user] How to set umask for entire Gnome session
On Tue, 25 Apr 2023 15:30:37 -0300, Jorge P. de Morais Neto wrote: > I now want to change my user's umask from 022 to 027, so new files and > directories will also be secure. I have tried adding to ~/.profile the > line > > umask 027 That sets the umask for the shell that runs the profile file, not for your GNOME session. > > and rebooting but it did not work. I tested by, in Emacs (launched from > Gnome), creating a new file in my Home and it did not respect the 027 > umask. > > So, how do I change my user's umask for the entire Gnome session? Do you have a separate filesystem for /home? If so, the simplest option is to set umask in its mount options in fstab. This will affect all users, except root, and it won't affect files you write outside of $HOME. -- Neil Bothwick She's fine, upstanding, and wonderful laying down. pgp396Qw2dOxd.pgp Description: OpenPGP digital signature
Re: [gentoo-user] text output from the kernel during boot is not showing
On Tue, 25 Apr 2023 09:42:55 -0600, the...@sys-concept.com wrote: > > What setting is the kernel actually being told to use for screen > > resolution? What is the output of cat /proc/cmdline. > > > > This sounds like it could be something to do with kernel modesetting. > > > > I'm getting: > cat /proc/cmdline > BOOT_IMAGE=/vmlinuz-6.1.19-gentoo > root=PARTUUID=33fd3594-68f7-e143-842a-cdade6d25e34 ro > > Have similar output like on my other systems. > > Wold removing from grub : GRUB_GFXMODE=1024x768x32 > solve the problem. I think it would go to default mode: 640x480 That sets the resolution for the GRUB menu. If you can see that but the kernel boot messages don't display, you may find adding nomodeset to the boot options helps. More info at https://wiki.archlinux.org/title/kernel_mode_setting#Disabling_modesetting -- Neil Bothwick If at first you don't suceed, try the switch marked "Power" pgp45D1MgLQ7Q.pgp Description: OpenPGP digital signature
Re: [gentoo-user] text output from the kernel during boot is not showing
On 4/25/23 01:27, Neil Bothwick wrote: On Mon, 24 Apr 2023 16:02:33 -0600, the...@sys-concept.com wrote: Consider uncommenting this line and running sudo update-grub Why should I uncommenting this line with an empty parameter? GRUB_CMDLINE_LINUX_DEFAULT="" > # The resolution used on graphical terminal. > # Note that you can use only modes which your graphic card >supports via VBE. # You can see them in real GRUB with the command >`vbeinfo'. > #GRUB_GFXMODE=640x480 > GRUB_GFXMODE=1024x768x32 GRUB_GFXMODE=1024x768x32 was there before and it run perfectly find with older kernel: linux-5.10.103-gentoo Just after upgrading to kernel-6.1.19 it happened What setting is the kernel actually being told to use for screen resolution? What is the output of cat /proc/cmdline. This sounds like it could be something to do with kernel modesetting. I'm getting: cat /proc/cmdline BOOT_IMAGE=/vmlinuz-6.1.19-gentoo root=PARTUUID=33fd3594-68f7-e143-842a-cdade6d25e34 ro Have similar output like on my other systems. Wold removing from grub : GRUB_GFXMODE=1024x768x32 solve the problem. I think it would go to default mode: 640x480
Re: [gentoo-user] How to install Ruby bindings in an ebuild
On Fri, 2023-04-21 at 22:15 +0200, Ralph Seichter wrote:
>
> Hm. While that sounds useful for "full Ruby" ebuilds, I don't see how to
> circumvent the impact for the particular ebuild I am trying to extend,
> other than overriding S in src_compile() etc.
>
> The build needs to create a C shared library, Python bindings, and now
> an additional shared library containing the Ruby bindings. Might this be
> a case where a new, separate ebuild for the Ruby bindings would be a
> better option than expanding the existing build?
> >
Ultimately what you want to do is build all of that other stuff once,
and then build ruby binding for each version of ruby. You can probably
make that happen by mucking around with the each_ruby_foo and
all_ruby_foo phases, but I think a separate ebuild would work too.
Assuming that the bindings link to the library, in both cases you face
the same problem: to convince the build system to link against a
different copy of the C library. With a single ebuild, you want the
ruby-specific builds to link against the one shared library you just
built; with a separate ebuild you'd want them all to link against the
system copy that was installed by the main ebuild.
> I thought of that and tried to use ${RUBY} instead, but the variable was
> empty. Hence I use the literal 'ruby' as a workaround, until a better
> method comes to mind.
One final option would be to figure out how the eclass is finding the
supported ruby versions, and copy it. Then you could loop through them
and use your hack with each one.
Re: [gentoo-user] Cgroup confusion
Hi, # This switch controls whether or not cgroups version 1 controllers are # individually mounted under # /sys/fs/cgroup in hybrid or legacy mode. #rc_controller_cgroups="YES" So, whether or not A or B. How do I translate that into English? Gentoo has three cgroups mode: legacy, hybrid and unified. cgroups v1 are created in legacy and hybrid modes, cgroups v2 are created in hybrid and unified modes. So the question here is, when cgroups v1 are created, i.e. in hybrid or legacy mode, do you want, yes or no, controllers to be individually mounted under /sys/fs/cgroup? This parameter has no effect when you are in unified mode, because there are no cgroups v1 in this mode, so it makes sense to specify it applies only “in hybrid or legacy mode”. signature.asc Description: PGP signature
[gentoo-user] Cgroup confusion
Hello list, BOINC is behaving strangely, and following a clue it gives me I look in /etc/ rc.conf and find this: # This switch controls whether or not cgroups version 1 controllers are # individually mounted under # /sys/fs/cgroup in hybrid or legacy mode. #rc_controller_cgroups="YES" So, whether or not A or B. How do I translate that into English? Surely it must be either 'whether or not" or "whether A or B", no? And which of those does YES denote? Or perhaps "in hybrid or legacy mode" should just be omitted. -- Regards, Confused of Tideswell.
Re: [gentoo-user] text output from the kernel during boot is not showing
On Mon, 24 Apr 2023 16:02:33 -0600, the...@sys-concept.com wrote: > > Consider uncommenting this line and running sudo update-grub > > Why should I uncommenting this line with an empty parameter? > GRUB_CMDLINE_LINUX_DEFAULT="" > > > > # The resolution used on graphical terminal. > > > # Note that you can use only modes which your graphic card > > >supports via VBE. # You can see them in real GRUB with the command > > >`vbeinfo'. > > > #GRUB_GFXMODE=640x480 > > > GRUB_GFXMODE=1024x768x32 > > GRUB_GFXMODE=1024x768x32 was there before and it run perfectly find > with older kernel: linux-5.10.103-gentoo Just after upgrading to > kernel-6.1.19 it happened What setting is the kernel actually being told to use for screen resolution? What is the output of cat /proc/cmdline. This sounds like it could be something to do with kernel modesetting. -- Neil Bothwick Men who go out with flat chested woman have reasons for feeling down pgp2xLtInQ9fw.pgp Description: OpenPGP digital signature
